R
rootcon
Greetings,
I have a 1995 Subaru legacy in both automatic transmission and manual.
Both cars have the obdII connector and say they are OBDII compliant
(iso9141-2) on the emissions sticker, but they do not respond to obdII
scans.
I am using the multiplex engineering (www.multiplex-engineering.com)
t16_003 connector and freediag (freediag.sourceforge.net). I've
successfully used this system on a 2000 Subaru Legacy and a 2001
Corolla, but they fail on both 1995s. I understand that in the
initiation, timing is strict at 5 baud, and this is where both ecus
fail to respond. I've also heard reports from others that 1995s don't
work with this software.
I modified the source code to not scan for test modes 5-9 (perhaps my
engine doens't support it), but that didn't help.
Does anyone know what subaru did differently in the early years of
OBDII to cause this non-compliance? ..Specifically in the initiation.
I'm a c++ programmer, so I can modify the software if someone cues me
in.
I have a 1995 Subaru legacy in both automatic transmission and manual.
Both cars have the obdII connector and say they are OBDII compliant
(iso9141-2) on the emissions sticker, but they do not respond to obdII
scans.
I am using the multiplex engineering (www.multiplex-engineering.com)
t16_003 connector and freediag (freediag.sourceforge.net). I've
successfully used this system on a 2000 Subaru Legacy and a 2001
Corolla, but they fail on both 1995s. I understand that in the
initiation, timing is strict at 5 baud, and this is where both ecus
fail to respond. I've also heard reports from others that 1995s don't
work with this software.
I modified the source code to not scan for test modes 5-9 (perhaps my
engine doens't support it), but that didn't help.
Does anyone know what subaru did differently in the early years of
OBDII to cause this non-compliance? ..Specifically in the initiation.
I'm a c++ programmer, so I can modify the software if someone cues me
in.