Finally got my fuel pressure problem straightened out and needed a new chip so that I could take my maiden voyage with the new engine. I go inside and open TunerPro RT and adjust my .bin for the new injector constant and try to program the chip with my AutoPROM. The chip erases, blank checks, and programs fine (or seems to), but it fails the verification every time. I've tried with two laptops, two chips (27FS512s), and different .bins with the same verification failure. I just did a chip last week with no problems. Today I decided to reinstall the USB drivers from Moate's site and still no dice. Anyone know what the problem might be? I'm really itching to drive my car with the new 383.

Try this: install the chip and do a key-on, engine-off while watching the SES light. The SES light should briefly turn on, blink off, then turn on solid.

If the SES does the blink off then the EPROM is OK. If the SES flashes rapidly or just turns on solid then the PROM burn is bad.

Can repeat the test after key-off for 10 seconds or more.

RBob.

I'll give this a shot.

I forgot to mention, though, that I did try to save the buffer to file after one of the verification failures and the .bin had some crazy numbers in the injector constant area.

Edit: I just tried saving buffer to file again and the injector constants, base timing and spark advance table all checked out okay. I'll give it a try once I get a full charge on my new battery.

I think I've finally gotten all the cars mechanical issues worked out and now need to adjust the bin some more. I'm still getting the verification failure and now can't save buffer to file with a good bin.

I did some more experimenting. Anytime I burn one of the BINs i've changed lately and then save back to file the fields that I changed get all screwed up. If I burn an older BIN and then save it back to file everything compares the same. I still get verification failure on every burn.

Recognizing this I though maybe I could just save the BIN I want to burn as a new name without making any changes to it and see if it worked. I did this burned a new chip and then saved back to file and got the same fields screwed up with the same values as the previous burn.

What could cause the issues with only screwing up the modified fields?

Update: Opened up a fresh AUJN.bin and used the difference tool in TunerPro to make the necessary adjustments that I want (using the file I've been having problems with). Burned my new file then saved it back to file (all of which have been renamed, of course) and then opened up the difference tool again. The time the difference tool had nothing to report to me.

I still got a verification failure, but the burn looks good so far. I'm going to go try it in the car.

Well, car ran like pooh. Any other ideas as to what my have gone wrong?

FYI: after running the car, I brought the chip back inside to check it and now TunerPro shows all kinds of differences. I need to get this figured out.