Howdy. I've got a mostly stock '83 TA with LG4 and 5 speed. I've been having a little trouble getting it to run "right" lately (problems started with a mouse nest in the snorkel) so I bought an ALDL cable off ebay (Red Devil River) just so I could run real time scan data and confirm all the sensors are (or not) behaving properly. So far I haven't been successful getting TunerPro to talk to the car. Got the COM port identified and TunerPro reports "cable found and functional" but the app reports "hardware not found" even when I have it hooked up to the car.

I've loaded an ADX for an LG4, but it seems like I also need a .bin and an .xdf - and am assuming the fact I haven't loaded any is why it's not working. Can anybody point me to a source for appropriate files? And/or comment on other potential issues?

Thanks,
Steve

 

Is your ecm a 1226025 ?
you don’t need a bin or xdf to datalog just to edit and view a bin.
have you tried winald?

 

I'm not sure what the ECM # is. But I just tried winaldl (hadn't heard of that - and it looks fine for what I need - reading sensor data - thanks!), and that doesn't want to communicate either. I picked a configuration (1984 truck? that had an LG4 listed). Maybe it's just a port configuration thing, I don't know what's going on. But I set the winaldl configuration to the same port (COM3) and baud rate (2400) in device manager, not sure what else I can check.

 

You should check the ecm service number first.
It might not be supported in either program.
tuner pros sure has the listed applications based off ecm service number.
Gear head efi also has adx files. You might be out of luck or may have to look at a old otc scanner
off ebay. Not much support for ccc .

 

Hmmm... Well, after a bit more reading of installation instructions on the provided CD, I think I've found the first problem. The ODB connector on CCC engines outputs data on pin D - all other injected one's use pin E. The cable I received is (probably) expecting data on E. Guess I need to deal with this issue before spending any more time on it...

 

EFI is on E or M, baud rate dependent.

Being a CCC setup likely need a 10K resistor across ALDL port pins A & B.

RBob.

 

Hopefully you can figure this out swamp2. I have a different ecm and have the EXACT same Tuner Pro RT issue with connecting.
Also where did you find instructions on a CD? I downloaded my version from their site but did not see any instructions>

 

vinny R - I bought it off ebay from Red Devil River, it came with the 12 pin/USB cable and a CD. On the CD were some autorun menus, and an option for installation and operation of TunerPro. My case may not be the same as yours - I have a computer controlled qjet carb. The troubleshooting instructions are pretty explicit that a different cable is needed as the CCC vehicles output the data on pin D and the normal cable assumes E and M.


The original ebay listing made no reference to a different cable to be ordered for CCC vehicles, and I was completely ignorant of the differences. So anyway I've attempted contacting the seller for return/exchange but haven't heard back yet after a couple days. Which is a bit annoying. Anyway, hopefully when I get past that, it'll work.

 

You might want to email them

http://www.reddevilriver.com/site/4b...t_Us.html#2786

 

I am using a Moates cable. Sorry I missread your post, I thought the CD was for Tuner Pro RT, not the cable.

 

Ok, I got a "universal" cable sent out from Red Devil. This just has a couple pins instead of a molded connector, so you can plug it into whatever data pin your car uses (D, E, or M). After some fussing around I got it to read live sensor data on Tunerpro RT. So that was the main problem. Still can't get the data presented on the nice dashboard display like I've seen on videos, just a list - but I'm getting what I need.

Seems my TPS is wacko - lowest reading is like 1.2V - hopefully explains why it's running so rich and fouling plugs. Can anybody advise what "normal" readings should be for O2 and MAP?

Thanks,
Steve