Jump to content

serious question on tune


ktm237

Recommended Posts

Posted

I was thinking the same thing. Maybe someone can shed some light. Or point to a link

 

 

Sent from my iPhone using Tapatalk

  • Replies 35
  • Created
  • Last Reply
Posted

So the flash counter... it just counts how many times it's been flashed? I am the damn GM of a dealership, if I want to use the GM approved equipment that my Gm shop owns to reflash my truck 300 times and not change a thing, who's to say I shouldn't do that? That would run up my flash counter wouldn't it? I have access to all of the equipment in my shop and a reasonable understanding to run it all. So what good is a flash counter if I never touch my truck with an aftermarket tuner but fiddle with it every weekend?

 

My point being, I'd argue it if my DSM says my truck was reflashed with anything non-authorized if they can't find it because it was put back to stock.

 

Any thoughts on this?

 

The flash counter is for GM to keep track of how many times it was changed/flashed, that's obvious.

The thing with that is, if the dealership does not have any record of flashing the truck, GM then knows it was someone other than a GM approved shop that flashed it or changed something. GM will argue that their people did not do it because there is no record and that some sort of aftermarket modifications were done at some point.

 

I am one of those who knows a warranty can not legally be void just because of an aftermarket modification but certain dealerships will lie to you and tell you otherwise. There are laws that protect customers from this type of nonsense but there are people who will try and argue otherwise. There are several topics with that argument in it even though the exact laws that protect us were cited and posted, they believe what they want.

 

GM doesn't want anybody that is not approved by them to do any work or modifications to these vehicles, it's silly but that's their thing. I guess they believe they have been replacing engines/transmissions on their own dime because of other peoples mistakes for far too long.

Posted

Is there a good thread where folks are comparing notes on what they are running in a diablo tuner?

 

I just got mine today and am unsure of what to choose for some of the settings.

 

I put in the diablo tune with dod off, tm off, 8% throttle boost, and left pretty much everything else alone.

 

What should I use for throttle boost and why?

After a lot of reading on different sites, forums, and posts this is what I've come up with as a good setup with a balance between performance, driveability, and well lower risk of damage you could say. Of course this is just my opinion and I'm no expert but this is what seems to work best for me and what I feel most comfortable with.

 

I use the Diablo (91/flex) tune.

I've settled on keeping DOD on just for the 1mpg I lost with it off. This one really is just preference I think whether you want a V8 all the time or not. I don't have issues in V4 mode or coming out of V4 to V8 when I get on the gas. If I don't want V4 mode I just put it in M5. I've not ready anything in regards to oil consumption with the new ecotechs so I'm banking on GM having fixed that issue.

I would recommend putting your throttle boost back to 0. Reason is there have been a number of complaints about the tranny shifting/banging hard on shifts at WOT only. On 1-2 shifts the most I think. I've experienced this myself. It kind of feels like the tranny is going to break when it happens. From what I've heard from DiabloSport it has to do with the throttle boost. If you post on their forum they have actually custom tweaked this in the tunes for a number of people who have reported it. I got one from them last week but have not had a chance to try it yet as the roads have been snowy in my area.

Also in the Diablo stock tune they have already dialed engine torque management way back (something we as end uses cannot adjust). The TM for the tranny is separate and it's only on or off and I would recommended leaving it turned on in the TCM tranny tune. From what I've read it's much safer on these 6 speed trannys for it to have some TM applied during shifts and I don't want to break mine. I've settled on the hard TCM shift vs the firm one. Just feels a little nicer to me.

 

Hope this helps.

  • 9 months later...
Posted

I have a Diablo Intune I2030 for sale. I sold my 2014 Silverado that I had it on. I returned the truck to stock so the tuner is unlocked and ready to use. I bought it directly from Diablo December 2016. $200.00

Posted

I have a Diablo Intune I2030 for sale. I sold my 2014 Silverado that I had it on. I returned the truck to stock so the tuner is unlocked and ready to use. I bought it directly from Diablo December 2016. $200.00

Posted

My Camaro has a killer Livernois tune and I want one for my truck (it has a 6.2 as well) but I will wait until the warranty is up. It's a long hard wait but worth it to me. Those who don't wait I totally get it and don't blame you one bit. As for the raging tire size/dealer fix debate...I'm glad your dealer can help and not sure why anyone would care and argue so much against the fact. Too many people feel the need to be experts on everything.

Archived

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

  • Latest Articles

  • Posts

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...