[b3lha]

Originally Posted by Mrdjc

Right if I try that.. I get...

TX>78812000<TX
812081812081
81208181208181
208181208181
208181208181
208181208181
208181208181
20818120818120
8181208181

Looks reasonable. I would say your hardware is working correctly.

Originally Posted by Mrdjc

I don't get a ROM ID from VWRX at all. If I only select battery voltage to poll (1335) I'll get 0, 12.16, 0, 0, 0, 12.16, 0, 0, 12.16, 12.16 (it just flickers back and forth on/off)

Try it in RS232 Comm Tool (1335)

TX>78133500<TX
133598133598
13359813359813
359813359813
359813359813
359813359813
359813359813
35981335981335
981335981335

The Hex Com Tool shows that the ECU is consistantly returning a value of 98 hex, which is 12.16 volts. Sounds about right. I don't know why the VWRX program would report anything else. It may be worth emailing Kevin or asking via the forum on his site.

Originally Posted by Mrdjc

My ECU ID in Evoscan is...
ECU ID: 742FA1

That ECU ID looks reasonable. It is similar to the one from my Legacy (7432A1). It looks like Evoscan is also reading good data.

Originally Posted by Mrdjc

How do you go about figuring out the addresses? (Especially since the dump tool doesn't work!) Wish there was some magic program that would go through the entire range and figure it all out for me!

Yeah. If only such a tool existed. The only way to accurately find the values is to reverse-engineer the program code. You need to be a computer geek with assembly language skills and a lot of spare time.
Some of the locations on my Legacy ECU match the ones for ROMID 7332xx in the VWRX SelectMonitor.ini file, so you could try those. It may be worth talking to Vikash (vrg3) on the LegacyCentral website. He has done a lot of work on decoding the Legacy ECU.

Originally Posted by Mrdjc

Phil, Do you have MSN/Yahoo or Skype messenger? Might be worthwhile sitting here and trying things. (I'm in my car right now.)

Sorry, I don't have any kind of Instant Messenger set up at work.