2003 Hemi Ram tuning issue

[hemifever]

I tested on a 2003 Hemi Ram at the initial support release. I'd change the timing curve around and get logs. The logs always were identical to the stock logs. It's like the timing table changes never registered.

I have another 2003 Hemi Ram customer with a turbo. I'm not getting a/f to change at all. I've brought the commanded a/f down to a 10.1 and added 50% to the VE tables. No a/f change. In fact, he gets the same a/f whether bone stock, with the can tune, or with me trying to increase it. The max ve has been raised to a 2. The timing also doesn't register a change. The timing is the same stock, as with the can tune or with my changes.

I can't recall if the speed limiter is a supported option. It's in the CMR code for an '03. I increased it to 150 mph and it still cuts out on his truck at 105.

I've walked him through loading tunes and he got the can tune loaded in and downloaded which is what I used as the base file. So it's loading tunes.

[mikel]

Any chance he is selecting the tune file as the base file when prompted to do so?

That would make it so he is always installing a stock tune....

[hemifever]

Well that might be a possibility. Here are his steps:

He downloads my tune file to his desktop. Then he runs dsdownloader and hits the express tab. He chooses send file to tool. It pulls up a browser and he goes to the desktop and selects the tune. When he ok's that it brings up a Yes/No dialogue that says if you have the original backup click Yes, if not then click No. If he clicks No then it halts. So he clicks Yes and it proceeds to load the file.

When he hooks up the tuner to the truck he selects custom tune and selects the tune in that list.

[mikel]

He should be browsing to select his original to make sure it is comparing the correct file.

[hemifever]

I had him save his original file back out. He selects send tune to tool and selects my tune file. Then it asks for the original backup location which he selects. The tune loads in fine. But still, there is no difference in my custom file vs. the stock file. Timing is the same, a/f is the same. I had him try and pull off the last tune written and it said it was locked by the dealer. Me in this case. Doesn't that sound like the custom tune is in fact loading?

He loaded the 93 octane tune in and sure enough, the timing is different. With this customer my custom tune isn't loading in correctly from what it appears. What can he be doing wrong?

[mikel]

Sounds like maybe in issue with the tool, we'll have to look into it.
I know several people are custom tuning with this, so it really should be working fine....

[hemifever]

His processor # is 56028769AF. I've sent him back his 93 octane CAN tune that he emailed me as a base to load in as a custom tune. I'm interested to see if that responds as a the original stock file.

[hemifever]

The customer loaded in the 93 octane tune as a "custom tune" and it didn't work like loading the 93 octane tune right off the tuner. Timing values were the same as stock. It loads in the "can" tune and responds but doesn't load it in as custom.

[pickups]

I had the same thing happen on Friday. I was trying to work off of the 93 octane tune and load it to the truck and there would be no change. I decided to try and use the original tune file to work off of and load that. Once I started working off of the original, the changes started to take place and I was able to tune the truck.

[hemifever]

I'll have him try that today and see what happens. When he tried the 93 octane file loaded in as a custom tune, at WOT it shifted out of the 1-2 shift about 1000 rpms early and when it got to 4000 rpms in 2nd gear it just rev'd and the truck quit pulling. Hopefully that was just a quirk and this thing didn't take out his trans. He returned it all back stock and it shifted okay but he's very hesitant to load another tune in there.