Jump to content

Recommended Posts

Posted (edited)

Hey guys so Im looking into getting a tuner for my 2015 Silverado 1500 5.3 main reason I’m looking into it is just to try and boost the horsepower and get some gas mileage up not looking for any crazy performance just wanted to see what you guys recommend I was looking at the hypertech 3000 I was first interested in the superchips but for the same price I saw hypertech had much better reviews what do you guys use or what works best for the 2015 Silverado 5.3? Thank you 

Edited by mauricio023
  • mauricio023 changed the title to 2015 Chevy Silverado 1500 5.3 tuner
Posted

I have the Hypertech Max Energy 2.0. My truck is a 2016 w/ 5.3L and 6L80 trans. I wanted a programmer to improve the drivability, not necessarily improve mileage. The throttle response and shift response adjustments made the biggest difference in the drivability. I no longer have to stomp the pedal to the floor to get it to downshift to pass on the highway. I used it to turn off the AFM and the mileage didn’t change a bit. My truck rarely dropped to 4 cylinders anyway due to a 2-1/2” lift, larger aggressive tires and removal of the lower bumper and air dam. The Hypertech has settings to increase mileage but I would assume that they would make the truck feel even more gutless than the stock tuning does. I may try the economy tuning just to see if it makes a difference. 

Posted

I tried a hypertech on my 2010 silverado and it gave me audible knock at wot with 87 octane. I wasn't interested in running higher octane at the time, so I just left the stock tuning and turned afm off. Turning afm off was the best feature, but I don't think handhelds do this anymore. At least not hypertech. I believe they're concered about lawsuits from the epa.

 

This doesn't mean it won't work for you. But your really better off spending the extra money on custom tune, and in all seriousness, better sooner than later. Before everyone closes up shop and stops tuning. 

Posted (edited)

I use the FashPaq F5 tuner.
Turned off AFM (though I had already disabled it through AutoSync and BTDiesel) and did the performance tune for 91+ octane.
There is, also, a choice for an 87 octane tune but I wasn't interested in that.
In my experience, it's a very good tuner - I changed RPMs at start and idle. I could, also, tune shift points but I really don't know enough to mess with that.

Edited by MikeBMW
  • Like 1
Posted
19 minutes ago, MikeBMW said:

I use the FashPaq F5 tuner.
Turned off AFM (though I had already disabled it through AutoSync and BTDiesel) and did the performance tune for 91+ octane.
There is, also, a choice for an 87 octane tune but I wasn't interested in that.
In my experience, it's a very good tuner - I could, also, tune shift points but I really don't know enough to mess with that.

I'm running a Superchips Flashpaq F5 also.

I'm running the 93 tune

Turned off AFM

Raised idle to 700 rpm

Raised all shift points 5-7 mph

Speedometer recalibrated for 38" tires

This is a very easy to use tuner.

Works as advertised. 

It really wakes up the 5.3 above 3000 rpm.

  • Like 1
  • Thanks 1
Posted
1 minute ago, dieselfan1 said:

I'm running a Superchips Flashpaq F5 also.

I'm running the 93 tune

Turned off AFM

Raised idle to 700 rpm

Raised all shift points 5-7 mph

Speedometer recalibrated for 38" tires

This is a very easy to use tuner.

Works as advertised. 

It really wakes up the 5.3 above 3000 rpm.

Totally agree, Jim! I did forget to mention retuning for my 35s (wish I had 38s :D )
Thanks for the info about shift points, I'm going to give that a try. :)

Posted (edited)

No, because that is a separate function that is tied into the ABS and stabilitrak system.

Edited by CamGTP
  • Like 1
  • 2 weeks later...
Posted

I have a Diablo I3 tuner and just sold my truck.  If anyone is interested let me now.  It is only a couple months old. 

Posted
2 hours ago, Csjumper2003 said:

I have a Diablo I3 tuner and just sold my truck.  If anyone is interested let me now.  It is only a couple months old. 

 

What did you buy?

Posted

Yeah it was bitter sweet.  But got tired of the round and round with GM and at 90000 it was getting up in miles and 6 years old.  Got a lot of the options I wanted without having to do a whole fully loaded truck

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,136 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...