Gearshift Maps

[b3lha]

Originally Posted by longassname

Actually the tx from the ecu is pulled high and clipped not clamped and the rx line is clipped on both sides then they go through the 74hc125 to pins 12 and 13 on the 6303

I made a schematic to duplicate the select monitor interface for an interface to a ftdi ttl232r cable: http://www.ecutune.com/posts/ttl232r-selectmonitor.pdf

That's awesome. An interface design that is guaranteed to work!

[longassname]

sweet

maybe it's the tcu from the us obd2 svx. I just got one. I'm doing a lot of soldering today but I'll try to pull the firmware off all the US tcu's you don't already have the firmware for and email them to you today. I'll take a couple pictures of the 96 tcu. Same plugs, same box.

[longassname]

you got all the obdII ecu parameters and com commands from the 96 select monitor bin now right?

[longassname]

i saw a picture of a select monitor II on your website; do you have one/can you get your hands on it again to look inside? I happen to own a master cartridge for all 01 through 04 model subarus.

[b3lha]

Originally Posted by longassname

maybe it's the tcu from the us obd2 svx.

It's in the 1992 cartridge.

Originally Posted by longassname

I just got one. I'm doing a lot of soldering today but I'll try to pull the firmware off all the US tcu's you don't already have the firmware for and email them to you today. I'll take a couple pictures of the 96 tcu. Same plugs, same box, don't remember seeing an atmospheric pressure sensor.

you got all the obdII ecu parameters and com commands from the 96 select monitor bin now right?

Thanks. I'm looking at the 92 cartridge first because everything I've worked on so far has been OBD1. I assume there must be some memory paging going on with the 96 rom because it's 64k not 32k. I'm pretty sure I can figure it out when I get around to it.

Originally Posted by longassname

i saw a picture of a select monitor II on your website; do you have one/can you get your hands on it again to look inside? I happen to own a master cartridge for all 01 through 04 model subarus.

No. I just pulled that picture off the net. I've been negotiating to borrow one off somebody. I was planning to eavesdrop every single cartridge and post the parameters on my site. A lot of people are guessing addresses for datalogging and getting them wrong.

[longassname]

Originally Posted by b3lha

No. I just pulled that picture off the net. I've been negotiating to borrow one off somebody. I was planning to eavesdrop every single cartridge and post the parameters on my site. A lot of people are guessing addresses for datalogging and getting them wrong.

It would be a lot faster to pull them off the master cartridge. I believe the 2001-2004 is the least supported range of obdII Subarus so that should fill in a big gap of knowledge. I'll pull and read the ROM off it and send you the bin.

[b3lha]

When I built my first cable, I did a scan of all the possible SSM command bytes and found 78 (ecu), 45 (tcu) and 89 (a/c). The cruise and 4ws units did not respond.

In the select monitor code, there is an extra step when talking to the cruise control unit:

example:

a26d 96 40       ldaa (0x0040) ; Unit Flags: x,y,z,4ws,crs,a/c,tcu,ecu
a26f 85 08       bita 0x08         ; 
a271 27 06       beq [0xA279]
a273 d6 11       ldab (0x0011) ; TxRx CSR1
a275 ca 06       orab 0x06       ; Transmit_Enable + Transmit_Interrupt_Enable
a277 d7 11       stab (0x0011) ; TxRx CSR1

I'm wondering if this is some kind of flow control. Presumably using pin 4 of the yellow plug B35.

[longassname]

It looks like the extra wire from the cruise control control unit is the same as the extra wire from the ecu. I just traced it and it also goes straight to pin 35 of the cartridge which I discovered yesterday dead ends where there is no resistor installed to connect it to vcc in the cartridge.

that does mean the two are connected when the select monitor is plugged in so the ecu could be providing something to the cruise control unit

[longassname]

i just probed the select monitor connector on my car and pin 8 wasn't showing any continuity to the other pins. pin 4 looked to be pulled low through a 4k resistor showing 4k continuity between ground and 12v and showing 12v between it and 12v.

[longassname]

when you get a chance if you could check the values of r213 and r315 and see if there is a r408 and 409 in the uk and jdm tcu I'd appreciate it.

[oab_au]

Originally Posted by longassname

when you get a chance if you could check the values of r213 and r315 and see if there is a r408 and 409 in the uk and jdm tcu I'd appreciate it.

R408, and R409 are both present on the Aust board.

Harvey.

[longassname]

thanks, what's the part number on your board? how about the lable on the ROM that's in it?

Originally Posted by oab_au

R408, and R409 are both present on the Aust board.

Harvey.

[longassname]

I figured out why I couldn't find my 94 bin before. The 705404 firmware is the firmware out of the e23aa12p ROM from a 93/94/95 TCU (I just read an e23aa12p ROM and that's what came out of it and I compared it to your 705404 and they are in fact identical). We should have nomake check the ROM id on his TCU. I'm guessing he has a TCU with the e23aa12p ROM. The firmware you don't have is from the e23aa11p ROM and the obdII firmware from the mq labled tcu with the e34ua1dL ROM.

[oab_au]

Originally Posted by longassname

thanks, what's the part number on your board? how about the lable on the ROM that's in it?

The board No. A64-001 67.
Rom No. E34EV1D1

Harvey.

[longassname]

67 or 637?

Originally Posted by oab_au

The board No. A64-001 67.
Rom No. E34EV1D1

Harvey.