Jump to content

Whats The Best Power Programmer For My 07 Sierra 5.3


Recommended Posts

Posted
What do you guys think the best programmer is? I think im debating between superchips or edge...

 

 

 

For the money you are way better to get a custom tune. Everyone is going with blackbear tunes and love their trucks afterwards. I have Edge right now I like the guages but I only used economy mode and I don't think it helps much. Diablo is a much better tuner but no TCM support. Seriously look at Blackbearperformance.com it cheaper and better than a programmer.

Posted

I have the Diablosport Predator and love it. Once you start playing around with adjustable parameters it really makes a difference. You can also download custom tunes with it (though I haven’t done this personally). The forum on their site is very helpful between all of the members and the techs. If you are looking to go the ‘handheld’ programmer route, I’d give them a look. Only major downside, as said, no TCM Support (yet anyway, they keep claiming to be adding it to future updates available through the website).

 

Good luck.

Posted

i have the Edge but i keep mine on 'performance' ,, runs smoother than economy, appears to keep into V4 mode alot longer than economy mode when applicable , not much of a gear head when it comes to altering all the variations as a custom tune can ,, dash mount is a nice benefit

Posted
I had the Edge Evolution. <------keyword: "had" :D

 

Join us for the Blackbear MN tune!!!!

 

It will be worth it. There are a lot of us going. Cabela's isn't that far from Cresco . . .

Posted

I have the Edge, I like the additional guages. I keep mine in Economy expect when towing and average 20 mpg on the highway and 17 mpg back and forth to work. I'm sure a custome tune would give better performance, but I don't want to be stuck paying for premium fuel, and the edge lets me run regular and still get decent gas mileage.

Posted
I have the Diablosport Predator and love it. Once you start playing around with adjustable parameters it really makes a difference. You can also download custom tunes with it (though I haven’t done this personally). The forum on their site is very helpful between all of the members and the techs. If you are looking to go the ‘handheld’ programmer route, I’d give them a look. Only major downside, as said, no TCM Support (yet anyway, they keep claiming to be adding it to future updates available through the website).

 

Good luck.

 

+1 for the Predator if you are looking for a hand held tuner. It is awesome and I highly recommend it. Actually the "canned" tunes that come with it are not awesome but you can tweak them yourself or have a custom tune emailed to you from Diablosport.

Posted

I already get 21 mpg without a tuner and this was by adding my roll up cover i bet. i would say get the blackbear tune, its said to give 2-3 mpg along with the countless performance gains. Im getting it in December.

Posted

I got zero MPG gains with the Edge. Then again, I got zero MPG gains with my Nelson tune too. My right foot and the smile on my face probably have alot to do with it too.

 

:D

Archived

This topic is now archived and is closed to further replies.

  • Latest Articles

  • Posts

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...