3kelvin

Hi people. I was wondering if anyone had run into this kind of issue before. I am sort of at a loss. I have lots of computer experience and some car experience ... even wrote an OBDII scantool in Java. This problem has me stumped.

I have a 91RS ... 1228746 ECU ($61).

I bought a cable from aldlcable.com ... the USB version. It looked like a good product and I hate making cables. So installed the drivers and tested the cable using Hyperterminal. Looks like I am getting data ... lots of weird characters on Hyperterminal.

BTW I have the USB cable set up as COM2, 2400 bits/second, 8 bits, no parity, 1 stop and no flow control.

But when I fire up winaldl, things get weird.

One the RAW data tab, only MW2, PROMIDA, PROMIDB are populated most of the time. Every now and then data will show up in other cells, semi randomly.

Everything else on all other tabs is zero. Sensor data, BLM, INT, O2. All empty or zero.

So it looks like I am getting data, but I suspect winaldl can't decode the data I'm getting. That makes me think the data might not be being framed correctly.

Or maybe I'm just doing something wrong. If anyone else has run into something like this, I'd sure appreciate a response.

Thanks

ResurrectingZ

I had the same problem, and it got solved. Here is what I was told

3kelvin

I appreciate the suggestion. Beginning to wish I had made my own cable after all ... this connector shell is not designed to be easily removed!

3kelvin

ResurrectingZ: I finally got it to work.

Turns out winaldl flashes a number (sample?) red if it is having problems decoding the serial data and green if not. I set the baud to 4800 instead of the recommeded 2400 (for a 160 bps interface) and it came right up.

Thanks for the words!