My autoprom fails to verify if I load a bin and when I test it in the car the car runs in limp mode BUT if I turn on the ignition it verifys fine. But that means that I cant take it inside and upload the bin I have to be in the car all the time. Is it some firmware upgrade that can fix it? I have version 2.16A.

 

It should verify fine when the AutoProm is disconnected from the ECM's pin header. The problem should only occur when the AUtoProm is hooked p to the ECM and the power is off.

In some cases, you may also need to try changing the position fo the ZIF handle on the AutoProm.

Finally, always make sure no chip is in the ZIF socket of the AutoProm when emulating.

 

I'v tried that also. I tried a couple of bin with out success. I also tested to:

1 Start tunerpro opened right xdf (8D) opened a bin.
2 Upload binfilen in Autoprommens RAM, pressed the verify and I got verify error, = bin file in tunerpro is not equal to the one I just uploaded the Autoprommens memory.
3 Download the file to TP from APs memory that I just uploaded. Pressed verify and got approved = The downloaded file in TP match the file that is in AP memory.
4 I save the downloaded file to another name.
5 compare the original file with the one I downloaded from the AP memory and there are diff of 45 bytes and there are differences in the tables I have not even been in. So it's no wonder that it can not verify when they do not match. Autoprommen changes in cells, I've looked at SA main for an example, a cell in the bin file is 44 degrees if you look at autoprommens framework, it is 41 degrees. So something is strange with it. Is it possible to completly erase the Autoprom memory and do another test from scratch?

 

What related to my post did you try? The verification issue has nothing to do with the files and everything to do with the hardware's physical connection state to the vehicle.

With the emulation header disconnected from the vehicle (on either side) and the ZIF socket closed with no chip in it, it should verify.

 

No It wont, only sometimes when I'm connected to the ECM's pin header and have the ignition turned on.


The problem is I have never manage to verify a uploaded bin only connected to USB. The only time it verifies, is if I do it like the above with the ignition turned on AND if I upload a bin to AP then download it to TP and then press verify, it verifies but that only means that the file in AP memory is the same as the file I just downloded. .

Tried that also a couple of times.

No I dont have a chip in the ZIP socket.

 

http://www.moates.net/contact_us.php

 

I'v done that also a couple of days ago and no1 has answered. I have also sended a mail to craig through thirdgen but no answer.

 

Give them time. There's only two of them to distribute the work of designing, manufacturing, distribution, and support. They will get back to you. =)

 

I understand that and I'll give it a couple of more days, but time is running out here and we have the winter knocking at our doors soon and I'm in the middle of tuning and as soon as I'm done I'm driving to the dyno but not if the snow starts falling then I have to wait until next year. :-)

 

You could have comm errors happening if the bin is getting scrambled.
Latency set = 1 in port setup reinstall the AP driver, etc.
Try slowing the comm rate (never made a diff for me but might in this case)
Check all your cables very well or try different ones if you have them.
Most if not all of the issues I've ever had lead back to a cable that has been abused while in the car.
The other thing you can do is to download "free serial port monitor" that will let you see what is transmitting and receiving.
you might be able to at least diagnose where the data is not going correct.
HTH

 

If you can spare it for a couple of days I can try it in my car.

/N.

 

JP86SS---> If its connected in the car with ignition turned on it works and I can verify the bin I just uploaded so I dont think its any problem with the cables, port-settings and so on I use the same usb cable in the car as I do in my home.

 

have you disabled checksum by uploading in preference?

/N.

 

I have checked the "Disable checksum by uploading 0xAA to offset 0x08. Is that enough or do I have to do some more?

 

Hey,

Sorry it's taken me a bit to get back with you on this. I've had my head buried in some firmware work among other things.

If you could go to my website and select the live support session option, I'll see if we can get you straightened out. Shoot me a fresh email, and we can set up a time. I can walk through your PC and make sure everything is set up correctly.

Of course, if something's not right with the APU1, we'll get that taken care of for you.

Hope this helps,
Craig

 

I have tried the live support session but no1 answered so I used your contact form and waiting for an answer right now.

 

On my 749 ECM in my Typhoon, I have to have the key ON when I upload to the Autoprom for the BIN to verify. If I disconnect the Autoprom from my ECM, I can upload and verify fine. Sounds like the same situation. I tried a couple of Autoproms and had Mangus look at it. I think it is just the way it works in my vehicle.

 

skwayb--> It doesnt seems like we have the same problem or you typed wrong. Your autoprom can verify when you are connected to the ecm and have the key on and if you disconnect from ECM you can verify. I can only verify when I am connected to ecm and have the key on. And its not the only problem, as I wrote earlier, If I upload a bin to the ram and offcourse it fails to verify and then I'm download it to TP and save it to another filename and then compare the orginal and the 1 that I saved 45 bytes are different, so something is wrong with it.

 

Try uploading but usig a different XDF.
the header could be FUBAR or something that is not transferring the data upward correctly. As you said, the downloaded bin does match the memory so communication "should" be working correctly. Only thing I keep thinking is the file is just not right going up.
Something to try anyway.

 

If you've got time, shoot me a call tomorrow. Mark and I will both be here, and between us we ought to get it figured out. 225-341-3547, 10a-6p CST.

 

I got a mail from Dave and he said "It sounds like you may need to return the autoprom for repair.
Please make sure you describe the problems you are having as well as
possible in the comments field on the RMA order."
But It would be great if you could use the live support option and check it out.