GaryDoug

HI guys,

My first new topic here, so I hope I am doing it right.

I am helping a programmer who is developing an Android app for the 160 and 8192 baud PCM's and have run into a little problem. In order to help, i bought a used PCM which supposedly came from an 86 Z28 carbed car. Unfortunately that is all the information I can find on it (painted on at that). I used WINALDL to scan it, but it required me to invert the signal and feed that into a regular TTL-to-Serial USB FTDI module (not RS232). The module works fine with a 94 Formula PCM so I know it works ok. That seemed strange to me that it needed to be inverted, but it did work ok with WINALDL. I would like to use TunerProRT to verify that is necessary but I cannot get it to connect. I am not even sure I am using the correct definition file (1227165_160.ads) for a carb engine. Does this sound like the correct file? Is there any way I can verify which PCM I have without a label attached? Am I wasting my time with this PCM?

Also, is it a quirk with WINALDL that inversion of the signal is a requirement, even when using a non-RS232 adapter?

Thanks for any help you can offer.

RBob

iTrader: (1)

The carb ECMs use a lamp driver module that inverts the serial data.

The 1227165_160.ads definition file isn't the correct one, but may be close enough to work.

RBob.

GaryDoug

Aaaah. I saw the lamp driver in the service manual diagram, but wasn't aware it was inverting. So I guess the carb ECM is programmed to output an inverted signal instead of a normal one?

Is there a "correct" file to use for this ECM? Or would I have to make my own? Even when the signal is inverted, TunerPro will not connect using that file.

Thanks

GaryDoug

OK I will answer my own questions now:

"So I guess the carb ECM is programmed to output an inverted signal instead of a normal one?"

Yes

Is there a "correct" file to use for this ECM?

Probably not.

Or would I have to make my own?

Probably, yes.

Even when the signal is inverted, TunerPro will not connect using that file.

It connects now after changing the packet payload size from 25 to 20, which matches the ECM. Bad data, but now I just have to edit the value fields to fit the ECM.