Problems Reading VCM On 2005 Ford Explorer XLS 4.0L V6

[fullthrottle]

(Note, I already Sent this to support but I figured I'd post it here too)

Hello, I recently purchased two Ford Credits in order to begin tuning my 2005 Ford Explorer XLS with a 4.0L V6. I was not able to get to the licensing phase because I could not get a proper VCM Reading. Attached, you will find a VCM Suit Info Log and a few screenshots of the problems I was having. Yes, I did follow the instructions to a T and even turned the key off like it asked me too. I will also attach a copy of the corrupt tune file. Please let me know what I need to do next. Is there a BETA release out there that I need to get my hands on or something?

VCM Suite Info log.txtford explorer stock tune.hptExplorer photo 1.PNGexplorer 2.PNGexplorer 3.PNG

[fullthrottle]

Last Screenshot

explorer 4.PNG

[ElecTech]

First, what version of 2.24 are you using?

Second, it does look like this calibration has not been defined yet, so you'll need to send it in to support along with that infolog.

Finally, even when they do define it, it looks like you will be able to open the file and see the contents, but you won't be able to modify or flash it back into a vehicle because the checksums have been messed with.

I tried to open the file with the latest beta version and it still would not open and send to send it to support.

[Eric@HPTuners]

It just needs to be defined. The checksum error comes up anytime we don't have a definition for something as well.

[ElecTech]

That's good. I was basing it off of an Edelbrock file that I have that gives me the "You can't modify it or Flash it" message, but I can open it and view it just fine.

[Eric@HPTuners]

That's good. I was basing it off of an Edelbrock file that I have that gives me the "You can't modify it or Flash it" message, but I can open it and view it just fine.

Ford or GM file?

[ElecTech]

Ford or GM file?

Its a Ford. 2005 Mustang with E-Force install using the Diablo based Edelbrock flash file. 2.24 won't tolerate it at all, if memory serves me, but 2.25 will open it to view, just not allow you to save changes or flash the file.

[fullthrottle]

Great. Thank you for the reply Eric. I've already sent it into support. Is this something that's going to take some time or will this be a relatively quick and easy fix? My apologies for the ignorance, I'm just used to being pampered with LSx stuff. :-)


Also thank you Jaime for your response as well.




Mike

[Eric@HPTuners]

Its a Ford. 2005 Mustang with E-Force install using the Diablo based Edelbrock flash file. 2.24 won't tolerate it at all, if memory serves me, but 2.25 will open it to view, just not allow you to save changes or flash the file.

Email it over to me. 2.25 will fix the checksum issue automagically if I have the right information entered for that specific OSID.

Great. Thank you for the reply Eric. I've already sent it into support. Is this something that's going to take some time or will this be a relatively quick and easy fix? My apologies for the ignorance, I'm just used to being pampered with LSx stuff. :-)


Also thank you Jaime for your response as well.




Mike

It will probably be a couple of weeks.

[fullthrottle]

Email it over to me. 2.25 will fix the checksum issue automagically if I have the right information entered for that specific OSID.




It will probably be a couple of weeks.

Ok, is this something that is common among vehicles that no one else has tried to tune using HPT software?

Your email is [email protected] right?

Edit: my apologies you were talking to Jaime as it pertained to the email.

[Eric@HPTuners]

Ok, is this something that is common among vehicles that no one else has tried to tune using HPT software?

Your email is [email protected] right?

Edit: my apologies you were talking to Jaime as it pertained to the email.

Send your read to support at hptuners dot com

Yes, If it is a vehicle no one has sent in for us to define, it is common.

[fullthrottle]

Thank for the quick turnaround guys. I received my beta download. Thanks for defining the calibration so quickly. Now Find a good Exhaust and CAI and wait for the new data logger for this thing so I can get tuning.