Diablosport Forums

Background:
- I am running the 2004 Ram 1500 PCM and 5.7 Hemi Engine in my 2004 Dakota.

- Only issues I had on the install that I could not fix were VIN mismatch between the Ram Hemi PCM and my Dakota's ABS module and Stock Stereo System (and AC/Heater controls). To remedy these issues, the dealer had to replace the Ram VIN in the PCM with the Dakota VIN.

The only thing not working is the Cruise Control due to a different number of connections through the clock spring. (will work this later)

I have about 30K miles on the swap (completed March 2012).

I have recently looked at tuning options.

Superchips: T42 error when attempting to pull stock tune from PCM. Have heard speculation from 1)because of the Dakota VIN in the Ram PCM to 2)maybe previous owner tuned the PCM and it is not stock (before the donor Ram was totaled).
I had the dealership momentarily place the Ram VIN back in the PCM and still received same T42 error.
Superchips engineers won't touch it (now I need to sell my Superchips 3865 Flashpaq.)

Diablosport inTune: Based on the success of another person who completed a Dakota/Hemi swap, I am now trying this product.
1) I updated the handheld tuner this weekend. (took about 3 hours)
2) I plugged it into the truck and it told me that for this VIN (the 2004 Dakota VIN), it needed to go online for a PCM update.
3) I took it back in connect to my PC and it stated on the handheld that the update for (Dakota VIN) was successful.
4) I plugged it back into the truck and it read that it was preparing to install an update to the PCM, press continue.
5) It then read that it was ready to install the update to the PCM and if I wanted to go ahead and install. X or (check). I chose NOT to install until I could talk to a rep here.
6) spent the rest of the evening searching and reading similar topics here.

I checked the info file and it referenced my Dakota VIN with the Ram PCM part number (56029166AF) and CM1(transmission controller) part number (56028810AD).

My understanding is that the 2004 Dakota IS NOT supported, but assume the tune is based on PCM Part number, not by VIN. I assume that if the VIN read (alphabet 123) it must stay (alphabet123) while it is married to it.

Question(s)
1) Is the programmer referencing the update because of the PCM Part number (56029166AF) or the Dakota VIN?
2) What are my next steps?

it is updating it as if it were an 04 ram to the latest calibration from dodge so it can be tuned.

Mike,

Thanks for the quick response. I know that for the donor Ram that the PCM version goes up to AI.

So by latest calibration, you are referring to updating from 56029166AF to 56029166AI or am I reading too deep into this?

What is your recommendation, should I pull the trigger on the PCM update? Does it care about the integrity of the VIN as it relates to an '04 Ram 1500?

So the statement by Diablosport that "Plug the inTune into your vehicle’s diagnostic port and it will automatically detect your year, make and model. The inTune will then provide you with a list of DiabloSport preloaded tunes" is based on the PCM Part Number?

it is reading that vin and calibration ID and seeing it as an 04 ram.. so it is going to update it, and tune it, as an 04 ram..

Reminder: it's my 2004 Dakota VIN that it is reading.

So is it using the Dakota VIN to determine what or how to tune or is it just using the PCM number?

the intune does not care what the VIN is for, it just uses it to identify what type of pcm should be there for an 04 ram, and then checks the calid, if the calid is not supported, it prompts you to update the cal, once you let it load the update you will be able to tune it.

Thanks

So, if I load the PCM update from the tuner into the Ram PCM, I am at no risk of corrupting the update ("brick/paperweight" the PCM) because of the Dakota VIN that is currently in the Ram PCM?

When you say calibration ID (calid), are you referring to 56029166AF?

yes, thats the calid, no, it will not affect the VIN.

I really appreciate you working with me and I promise I am not trying to be difficult. I am just trying to understand the risk. To understand the risk, I need to explain everything to the experts (you) so you can convey the risk to me (if any). Maybe this conversation would have been better over the phone instead of written text.

So am I correct in understanding that it will write the latest calibration ID (calid) needed for an 04 RAM (56029166AF), NOT for the 04 Dakota even though the Dakota VIN is in the PCM?

I would presume (and partially based on what 06MonteSS stated) it will write the updated calibration ID (calid) need for the 04 RAM (56029166AF) since an 04 Dakota is NOT supported by inTune.

I don't want to the PCM on my daily driver.

I guess I am not being very clear...yes, load the update, then you will be able to tune it.

okee dokee

Success!

It took two tries to install PCM update. First attempt was met with "an error occurred while trying to install update" and then it was in recovery mode.

Second attempt went through fine.

I installed the 87 Octane tune for now.

I appreciate you guys' assistance on this.

Comments:
In the Tool Info->Vehicle Info menu:
Using Last Vehicle info, I now see:
Version: 1r04d
LTW: 87 Octane Tune
Calid: 56029166AH (used to read AF)
(next) 56028810AD
VIN: 1D7HG38N94(and the rest of Dakota VIN)
Veh Vin: 1D7HG38N94(and the rest of Dakota VIN)
Serial: CIKT... etc
Custom: No
Locked: 1/1

I believe that is all normal, right?

good to go.

Mike,

So I have several years experience tuning my LT1 Procharged 91 S10 (ODB1) using Craig Moates set-up (Moates.net).

I am not yet looking to dig that deep into my Hemi Dakota, but is there a way to compare (side by side) the parameters of the tunes in the inTune for my set-up?

I would like to know (example) what the current target idle RPM is for D w/o AC. or how much timing is set in the stock tune vs the Diablo tune at WOT.

you could datalog each tune to see differences but you cant open the tune files without our CMR tuning software, which is a professional level tuning suite.

we dont make any changes to anything idle related for example.