My 383 SR did a number on me today, speedo suddenly drops to zero while driving down the road, ALDL port stops tranmsitting any data, car suddenly loses all power and won't idle on it's own, and check engine light comes on. Since the ALDL won't communicate when this happens, had to use a wire jumper A-B to pull the code. Weird - it shows a code of 10 (ten)!

I've reset the computer, and the same condition occurs within 50 yards of driving.

I know the routine on pulling the codes - get 12 three times, get 10 flashes, repeat this for a total of three times, and repeats with the 12 three times, then the 10 three times, etc.

Anyone have any idea on this? I will admit, I changed the bin in my Ostrich just before this happened. Using TP-RT 4.0 I turned off the AIR millivolt offset and set the CCP to enable only after 254. No other changes in the BIN.

So, any ideas???

 

Alwasy always back track and retest the last known good version.

Do this religously when u have problems.

I would try that first and see what happens.

I dont have a book near me so I'm not to sure what a code 10 is either.

Loose connections also cause havoc too, so if it persists with a different bin u may want to investigate your setup

later
Jeremy

 

I'm doing that right now, thoughy of that too.

Weird part is that nothing shows 10 as qvn being an error code anywher that I can find...

 

Looks like it's something in the bin. Previous bin appears fine. Will research the diffs tomorrow and report back.....

 

I compared the BIN I downloaded to the previous BIN, and the only things different in them according to TP-RT 4.0 was:

checksum (obviously!)
air enable min temp
ccp enable min temp
air rich/lean reduction volts
and the closed loop delay timers (was trying to shorten them up).

All values displayed were within ranges allowed (under 150* C and under 60 seconds).

So, the only thing I can figure is the download must have gone bad, except I did a verify/compare after I loaded it and no differences were found.

Anyone have any ideas on why or what caused this wird undocumented error code (a ten)? And the ensuing engine conditions? (No power, no speedo or VSS signal, ALDL locks up, won't idle on its own, and Check Engine light on steady)

 

It happens every so often to me as well. The actual code section gets corrupted and the computer locks up or goes crazy, especially if it happens before the Computer Operating Properly hardware can be initialized. It could also be a bad connection. I wouldnt get too worried. Just reburn and possibly clean the contacts on the eeprom/adaptor. Ive found that over time a layer of corrosion builds up and causes the computer to misread the prom. Little 2000 grit sandpaper cleans the contact surfaces on the pins right up.

 

I have the same problem with my burner as well. The ziff socket is getting dirty and i have to jiggle the eeprom around to get it to burn correctly. Sort of like the problems I had with my old Nintendo.

 

Only problem with that idea is I'm using an Ostrich, so no chips or chip burners were involved. And since I even tried a different ECM while I was experiencing the problem, it had to be something in the Ostrich. What, I have no idea....

 

Didnt see that in the origional post. Id probably say it was a fault when you downloaded the bin if it works now.

 

Yep. And it is working fine now with the previous BIN. Haven't tried reloading the BIN that had the problem....

 

It could be a problem with the XDF file. I have seen a couple of glitches when converting an ECU to XDF. Some data doesn't make it in the conversion. You might re-check the values for those table entries in the XDF. Just a thought. HTH

 

Good idea - will do - THANKS!!