Blinking AT oil temp lamp on startup

[Huskymaniac]

Originally Posted by b3lha

Yeah that's the procedure. With any luck you'll never need it.

Yes. The select monitor can do it. Evoscan doesn't have support for TCU, only ECU. FreeSSM was supposed to be able to read all the transmission stuff, including tranny temp, but I'm not sure if they've got it working yet.

I can read my tranny temp using a homemade cable and some software I wrote. But it's just experimental. Nothing I could release as a product.

Are you talking about the Linux Alcyone software? Based on the cable selection page on the evoscan website, it sounds like they assume the OBD2 connector carries a SSM1 signal. I'm wondering if that cable will work with your software. What language did you use?

[b3lha]

Originally Posted by Huskymaniac

Are you talking about the Linux Alcyone software? Based on the cable selection page on the evoscan website, it sounds like they assume the OBD2 connector carries a SSM1 signal. I'm wondering if that cable will work with your software. What language did you use?

Yeah, that's it. Written in C, but the ecuscan and tcuscan programs require the "curses" library which seems to be omitted from more recently versions of linux. Have you ever done any C programming?

The OBD2 cars have SSM signal on pins 12 & 13 (or 4 & 5 if you get the numbering backwards like in the service manual). I think Nomake Wan had a go at using my software with somebodys OBD2 car. IIRC the basic communications was working, but for some reason the software wasn't happy. If you can do C programming then I'm sure you could make it work.

[Huskymaniac]

Originally Posted by b3lha

Yeah, that's it. Written in C, but the ecuscan and tcuscan programs require the "curses" library which seems to be omitted from more recently versions of linux. Have you ever done any C programming?

The OBD2 cars have SSM signal on pins 12 & 13 (or 4 & 5 if you get the numbering backwards like in the service manual). I think Nomake Wan had a go at using my software with somebodys OBD2 car. IIRC the basic communications was working, but for some reason the software wasn't happy. If you can do C programming then I'm sure you could make it work.

Yes, I have programmed in C in the past (C++ actually) but it has been awhile. It could be a fun project for my 13 year old son who likes programming and playing with Linux. However, I would prefer to have something that runs on windows and, better yet, on a pocket PC. So you think there was an issue with the software? Why would that be? If the cable is correct and the SSM protocol is the same (SSM1?) then there shouldn't be an issue, right? What problem was Nomake having? Do you know what cable he was using?

Could you PM me your phone number and what times would be good to call. This is too complicated to do by message board and I would like to discuss this with you. I have quite a few questions.

[b3lha]

Originally Posted by Huskymaniac

Yes, I have programmed in C in the past (C++ actually) but it has been awhile. It could be a fun project for my 13 year old son who likes programming and playing with Linux. However, I would prefer to have something that runs on windows and, better yet, on a pocket PC. So you think there was an issue with the software? Why would that be? If the cable is correct and the SSM protocol is the same (SSM1?) then there shouldn't be an issue, right? What problem was Nomake having? Do you know what cable he was using?

If you can understand C++ then you shouldn't have any problem with these simple little programs.

I don't recall what Nomake said the issue are/were.

If you want to have a go at this, then you need to make/buy a suitable cable. Then you need to send the commands to the TCU manually and see what data comes back.

Once you find the right command and figure out how to interpret the response then you can tweak the software, or write something new, to do it automatically.

Originally Posted by Huskymaniac

Could you PM me your phone number and what times would be good to call. This is too complicated to do by message board and I would like to discuss this with you. I have quite a few questions.

Sure. No Problem. Will do.

[Huskymaniac]

Originally Posted by b3lha

If you can understand C++ then you shouldn't have any problem with these simple little programs.

I don't recall what Nomake said the issue are/were.

If you want to have a go at this, then you need to make/buy a suitable cable. Then you need to send the commands to the TCU manually and see what data comes back.

Once you find the right command and figure out how to interpret the response then you can tweak the software, or write something new, to do it automatically.

Sure. No Problem. Will do.

Phil,

I can PM you back because your box is full. I will try to call you Saturday night.

[svxfiles]

Originally Posted by SoobCrazy

Just got my first SVX, a 1996 EP LSi. Woot!, and I've noticed a few problems with the new toy.

I read in the owners manual that if the automatic transmission oil temperature light blinks after you start the car, it means there is a problem and you should take the car to Subaru immediatly. Blinks about 16 times, IIRC.

I have also read on the SVXWN that 1996 and later models simply don't have a transmission "Power" lamp in the dash. How would you know if the trans is throwig a code without the power light?

My questions: Can I pull the codes from the TCU myself? Could the AT oil temp lamp be the TCU error code signal?

Anyone have experience with this problem?

If you do not have to a SSM, the first thing that you should do is to check the resistance of the dropping resistor, mounted between the battery and the inner fender.
If it shows no resistance...
RESISTANCE IS FUTILE!!!!!
Then you need to repair or replace the dropping resistor.
I mention this as it is the most common cause for a trans code.