let any of your sensor wire signals short out to the sensor ground with a DSP tune during a flash.
If you think you have a problem with a sensor or some other odd wiring issue, do not load your DSP tune onto your car. We just found this out the hard way but if you have a short or bad sensor (TPS) it will corupt the file and or the download into the PCM.
The really weird thing about it, it doesn't show up on the tune and its all loads a-ok with no warnings. We didn't know that we had a bad sensor on the car because it was hit or miss (dead spot in the TPS that was kind of on or off). If you are having some issues that cannot be figured out with your tune, make sure that all your sensors are in good condition.
One more thing to make mention of, if you load any other tune into the PCM after this corupt tune gets loaded into the PCM, it will corupt all other tunes after that. You have to return to stock, reload a new tune (don't use the old one that you pulled off the car or the original one that you got from your CMR dealer or the one you wrote and saved). More or less its a start over from scratch with a new tune (good thing I have Cal files saved).
Just FYI guys for those few that have some crazy issues with their DSP (not sure if this would effect the Trinity, but I would have to say yes to that since the flash files are the same).
Is it the fact that the changes don't get applied or is it something else?
I wish I could tell you what happend but the tune looked good but a hard code for both uppper and lower sensors was set and would not clear. Not only that but the car wanted to run a 11.0 AFR's, its like it was being told to demand those AFR's. We couldn't change the idle RPM either, not matter what (CMR or hand held changes) we did.
I pulled the tune from the PCM and checked it, it was all good and then I loaded another tune. After loading the other tune the car ran worse. So, we decided to go back to stock, and load the cal file for this set up. After doing this all the codes were gone, and the car ran just fine.
Its like the code in the PCM was manipulated or something along those lines was changed. When looking at the tune, nothing was changed but the car was very screwed up tune wise.
I wish I could tell you what happend but the tune looked good but a hard code for both uppper and lower sensors was set and would not clear. Not only that but the car wanted to run a 11.0 AFR's, its like it was being told to demand those AFR's. We couldn't change the idle RPM either, not matter what (CMR or hand held changes) we did.
I pulled the tune from the PCM and checked it, it was all good and then I loaded another tune. After loading the other tune the car ran worse. So, we decided to go back to stock, and load the cal file for this set up. After doing this all the codes were gone, and the car ran just fine.
Its like the code in the PCM was manipulated or something along those lines was changed. When looking at the tune, nothing was changed but the car was very screwed up tune wise.
Ok thats what I thought. The jacked up sensor might have been its own seperate issue, but there have been issues with other CMRs not having thier tune's changes applied when flashed.
The usual work around is using a Cal file. It sounds like using the Cal file is what actualy worked for you. I don't think the sensor issue was the cause here.
DS is supposedly working on it. There's a couple threads in the CMR section about it too.
imo I think its a DSDL issue more than anything.
I had some issues like this too just using the handheld and DSDL. I have a custome tune that all I did was RENAME and added a comment to it under "Advanced tuning" in DSDL. It will show perfect in CMR, but if I upload it to the Trinity and Flash it, all I effectively get is a stock tune. 0 changes. I first knew it was jacked up when the rear O2 cel popped up and max boost was 14psi.
btw your website link in your sig is broken.
Last edited by duster360 : 10-12-2009 at 09:57 AM.
Ok thats what I thought. The jacked up sensor might have been its own seperate issue, but there have been issues with other CMRs not having thier tune's changes applied when flashed.
The usual work around is using a Cal file. It sounds like using the Cal file is what actualy worked for you. I don't think the sensor issue was the cause here.
DS is supposedly working on it.
imo I think its a DSDL issue more than anything.
I had some issues like this too just using the handheld and DSDL. I have a custome tune that all I did was RENAME and added a comment to it under "Advanced tuning" in DSDL. It will show perfect in CMR, but if I upload it to the Trinity and Flash it, all I effectively get is a stock tune with a Desired Trq change. I first knew it was jacked up when the rear O2 cel popped up.
btw your website link in your sig is broken.
Using the Cal file is what worked but it was a pre-built cal file (modded file for 750's and other goodies). I didn't use the cal file that came from DS so I suspect that the sensor was the issue. The only reason I say it was this is because the tune ran find until the sensor shorted out (didn't now until much later) and we tried to make some changes to the tune, that is when all hell broke loose with the car.
I have found that renaming files is a no no. Everytime I do this the tune will not load properly, you have to save it from the CMR "save as" with the tune open. Just going in and making a change to the file name has been a problem for me from day one.
Thanks for the heads up on the link, I will look into that.
Using the Cal file is what worked but it was a pre-built cal file (modded file for 750's and other goodies). I didn't use the cal file that came from DS so I suspect that the sensor was the issue. The only reason I say it was this is because the tune ran find until the sensor shorted out (didn't now until much later) and we tried to make some changes to the tune, that is when all hell broke loose with the car.
I have found that renaming files is a no no. Everytime I do this the tune will not load properly, you have to save it from the CMR "save as" with the tune open. Just going in and making a change to the file name has been a problem for me from day one.
Thanks for the heads up on the link, I will look into that.
Thanks for the headsup on the rename.
I don't doubt that the sensor was jacked up, just look into this issue further before just blaming it alone and moving on. I think it might have been just coincidence not the route cause.
No I wasn't talking about the DS made cal files. This "fix" was to wrap all your custom changes, new and old into a single cal file and apply that to an original drg file.
I don't doubt that the sensor was jacked up, just look into this issue further before just blaming it alone and moving on. I think it might have been just coincidence not the route cause.
No I wasn't talking about the DS made cal files. This "fix" was to wrap all your custom changes, new and old into a single cal file and apply that to an original drg file.
Ah, gotcha. That is what fixed it, so I will have to take a look into this. Just odd that it the tune freaked out after some basic changes were made to it (done this several times with out a hick up yet, but one never knows what may or may not happen when changing tunes).
On another note, my tune for the shop car (pump gas tune) is all jacked up as well now, just found this out last night. Tune in the PCM is OK, but some how the tune on the laptop is all messed up. Looks like it might not be a bad idea to run a back up and format the disk this week.
The AutoGuide.com network consists of the largest network of enthusiast-owned enthusiast-operated automotive communities.
AutoGuide.com provides the latest car reviews, auto show coverage, new car prices, and automotive news. The AutoGuide network operates more than 100 automotive forums where our users consult peers for shopping information and advice, and share opinions as a community.
Attention, Do Not....
Linear Mode
