I've got an AutoXray that works great on the Vette. Then, with no warning and no special circumstances, it stops reading realtime. I can't get it to read realtime again. It says Vehicle Not Responding, but the car is running fine. The only way to get data again is to shut down the car and restart. Does this sound like an ECM problem or a scanner problem? BTW, the scanner works well on the other car I've tried it on, but they notoriously act weird with Vettes.

 

Probably a general wiring and/or connection and/or grounding and/or power problem...

 

Mine started doing that when I switched to the ARAP code. ALso does a couple other weird things like:

- Says Neutral not Detected when in park and Neutral Detected when it drive
- Says first gear not engaged, when it is

And a couple other minor things that I dont remember off the top of my head right now. There must be something in the ARAP code that is not 100% compatible with the Xray... But for the most part, the data seems good.

Any other ideas?

------------------
Mike Metzler (Desert86Roc)
Mike@SpeedworldMotorplex.com
[*] Webmaster: SpeedWorldMotorplex.com[*] Click Here For My Racing Page[*]86 IROC 305 TPI (406 build in progress)
ET's @ 1250 ft[*] 14.28 @ 95.461 mph (uncorrected, NOS, no headers)[*] 15.365 @ 86.785 mph (uncorrected, Headers, no NOS)

 

I get that tranny crap too. Also, my OD light on the dash is constantly on (87 Vette). Wiring and connections test OK. Possibly a power spike or something?

 

I was having all those similiar problems with my autoxray also. I sold it, bought the Diacom software, and have never looked back. I know it's probably not the answer you want to hear.

------------------
1989 IROC-Z 5.7L
NOS 150HP kit
ProBuilt 700R4, PI Vigilante 2800 stall lockup
Baer Brakes 12" Sport System

 

I suspect the "data link" within the ARAP is different than the 32 or 32B. I would expect to have to have Auto X-ray setup for an 89 Vette VIN for it to work correctly. It would be like converting your MAF car to SD; you'd need Auto X-ray to know that it is a different ECM/EPROM type. You have the same ECM, but not eprom/binary file.

I don't know how Auto X-ray works with different VINS, but on Diacom I would just have to enter an 89 Vette VIN and it would most likely work. You just have to set your Auto X-ray to the "6E" eprom (or have it upgraded) and it should work fine.

 

It's set to 89. Eventually, I'll get free scanner software, but Diacom wants waaayyyy too much for their stuff. I'm into the AutoXray for $90 and it'll scan any of the big three up to OBD 2. It gives me most of the info I want, but there are glitches. Hell, it might be my car doing it.

 

FYI: I finished installing my Laptop link cable today, and using Craig Moates software, my Laptop will sometimes do the same thing as the Xray does (just stops interacting). It also reports the same flags incorrectly using the ARAP code.

I would like to burn an 89 only chip, or maybe put my old 86 back in just to see what it says, but I am running good now and dont want to switch it for a while (at least through this tank of gas for mpg test purposes).

------------------
Mike Metzler (Desert86Roc)
Mike@SpeedworldMotorplex.com
[*] Webmaster: SpeedWorldMotorplex.com[*] Click Here For My Racing Page[*]86 IROC 305 TPI (406 build in progress)
ET's @ 1250 ft[*] 14.28 @ 95.461 mph (uncorrected, NOS, no headers)[*] 15.365 @ 86.785 mph (uncorrected, Headers, no NOS)

 

Mike, have you tried using Craig's software in 6E mode? Just double checking that you didn't try using Craig's software with your old setup.

 

My program doesn't differentiate between the 6E and 32/32B code. It does have a SD provision, though, which is still pretty rough in terms of accuracy. The program is set up to run on the 32B code by default. I should spend some time to update with respect to the nuances of the differences and provide the 6E ARAP option, since that's what I myself am using. Need to look more closely at the 6E protocol and provide an update, right?

I've also experienced the comm locks you are referring to. In my case, it seems to go just fine for a period of time (5-15 minutes or so), then it hard-locks, as though the ECM end of things just quits talking through the ALDL. When I shut the key off for 15+ seconds and turn the car back on, all is normal again. After a while it locks again.

If the problem is Prom-code related, that would be most interesting. I thought I had a bum ECM. Should throw the old 32 code in & see how it goes for a while. Anyone else try this?

Also, who out there is connecting +5V from the circuit to the Com port DSR pin, and who is not? This would also be of interest to me, particularly if it is needed to get my program to run and not another one.

-Craig

 

Craig,

Dont know what the AutoXray is doing, but I wired in Andrew's cable today, and just used the 3 required wires...no extra power or ground. I will try that also. I get the same result with the Xray, and your software. There was no particular pattern to when it would lock. I tried both, and they both did it sometimes, and at others, didnt. There were a couple of things I did notice about the software, but can email you about those. Your software reports the same thing as my Xray as far as the oddball readings, so I would think it has something to do with the arap code. I will put my old $32 chip back in next week, as I have a team race this next weekend, and the car has been running great regardless of the glitches in the code, so I dont want to change anything and jinx myself. The arap chip netted me a solid .3 and 4mph in 3 runs compared to my runs last week, on my tired ole peanut cammed 305 with 175k on it now.

------------------
Mike Metzler (Desert86Roc)
Mike@SpeedworldMotorplex.com
[*] Webmaster: SpeedWorldMotorplex.com[*] Click Here For My Racing Page[*]86 IROC 305 TPI (406 build in progress)
ET's @ 1250 ft[*] 14.28 @ 95.461 mph (uncorrected, NOS, no headers)[*] 15.365 @ 86.785 mph (uncorrected, Headers, no NOS)

 

I have the exact same problem with my MPSI Pro-link scanner...I have to shut the car off for a coupla minutes...fire the scantool back up...and then fire the car up to get it to reset...I'm gonna have to live with it for awhile...but plan on upgrading to one of the free software packages off the net...



------------------
GregF
87 IROC