Help interfacing with 2007 Legacy CAN/OBD2 ECU

[serendipity]

I received my Tactrix cable and have started trying to interface with my 2007 Legacy Spec B.

I hope I'm not just making a noob mistake, but it appears at first glance that EcuFlash and the openport cables are not working on the CAN/OBD2 ECUs showing up in the 07 Subarus.

EcuFlash gives an error and stops, but the log is not very enlightening.

I get a series of "ssm2_init" messages, then "kernel get version" then "validating denso kernel ram area addr: FFFF0000 len: 0008".

So it's not getting to the point where it can read the CalID, but I don't know if it's a protocol error or if maybe the address has just changed.

Any tips or things I can try to narrow down what the changes are in the new ECU?

Is anyone aware of a diagnostic connector on 07s that needs to be shorted?

[zigzagzok]

bump...
anyone has any idea?....

[merchgod]

Try to find version 1.28 of Ecuflash. This seemed to work on an 07 wrx. Uninstall 1.29a and all related drivers first before installing.

[zigzagzok]

Try to find version 1.28 of Ecuflash. This seemed to work on an 07 wrx. Uninstall 1.29a and all related drivers first before installing.

tried that cant work
now for a long shot...
the wiring on the OBD plug at the car end goes something like this, from the left to the right

green/yellow , purple with red strip, red, black red strip, black red strip, pink

then next row

white, blue

total of 6 pts on one row, and another 2 pts on the other

when the tatrix cable is connected seems that one or more of the legs will miss several of the wires, is this normal?...

[zigzagzok]

Try to find version 1.28 of Ecuflash. This seemed to work on an 07 wrx. Uninstall 1.29a and all related drivers first before installing.

tried that cant work
now for a long shot...
the wiring on the OBD plug at the car end goes something like this, from the left to the right

green/yellow , purple with red strip, red, black red strip, black red strip, pink

then next row

white, blue

total of 6 pts on one row, and another 2 pts on the other

when the tatrix cable is connected seems that one or more of the legs will miss several of the wires, is this normal?...

here are the pics of the connector to see if it makes sense

[Fitz]

The connector looks fine. The pin that is 'missing' is 15. That is the ISO 9141-2 L line and is optional. Based on what you describe of the trace it sounds like rudimentary communication has been established (ie, ecuFlash has sent some SSM packets at 4800 baud and gotten some responses).

I would be more concerned about the pinout on the programming jumper connector. Also, I would try hooking the vehicle up to a battery charger. The one Sub I tried with the universal cable was very sensitive to voltage.

Good Luck,
-jjf

[zigzagzok]

The connector looks fine. The pin that is 'missing' is 15. That is the ISO 9141-2 L line and is optional. Based on what you describe of the trace it sounds like rudimentary communication has been established (ie, ecuFlash has sent some SSM packets at 4800 baud and gotten some responses).

I would be more concerned about the pinout on the programming jumper connector. Also, I would try hooking the vehicle up to a battery charger. The one Sub I tried with the universal cable was very sensitive to voltage.

Good Luck,
-jjf

no luck then - the batt voltage was typically 12.48V when i try to hook up ecuflash; (with the green test connector linked up)
to me it seems that the green / yellow connector is not hooked up at all to the tactrix cable - cld that be the reason why i keep getting the following response?

[00:11:59.124] Version 1.29.906
[00:11:59.124] 8 memory models read.
[00:12:00.375] 140 ROM metadata models read.
[00:12:00.375] checksum module "subarudbw" loaded.
[00:12:00.375] flashing tool "wrx02" loaded.
[00:12:00.375] flashing tool "wrx04" loaded.
[00:12:00.375] flashing tool "sti04" loaded.
[00:12:00.375] flashing tool "sti05" loaded.
[00:12:00.375] flashing tool "mitsukernel" loaded.
[00:12:00.375] flashing tool "mitsukernelocp" loaded.
[00:12:00.375] flashing tool "mitsubootloader" loaded.
[00:12:19.413] ssm2_init
[00:12:19.643] ssm2_init
[00:12:19.643] ssm2_init
[00:12:19.653] ssm2_init
[00:12:19.673] ssm2_init
[00:12:19.673] ssm2_init
[00:12:19.693] ssm2_init
[00:12:19.703] ssm2_init
[00:12:19.723] ssm2_init
[00:12:19.733] ssm2_init
[00:12:19.913] kernel get version
[00:12:20.434] validating denso kernel ram area addr: FFFF0000 len: 0008

my tactrix cable

[tuning g]

bump

[Fitz]

Between the loading messages and the ssm2_init messages you are presumably selecting ROM Read, what flash method are you then selecting?

-jjf

Note: On the Evo, typically you only need the jumping connector installed. However, on some of the Subs, I believe you do need to bring the programming voltage back to the cable.

[mickeyd2005]

Did someone find an answer to this?

Is it because Subaru has changed the 2007 ECU to ISO 15765 CAN? It appears that all cars by 2008 will use this new protocol.

http://en.wikipedia.org/wiki/OBDII

AFAIK, the tactrix cable is only compatible with ISO9141-2, so does this mean a new modification to the tactrix cable is needed?

[Jon [in CT]]

Did someone find an answer to this?

Is it because Subaru has changed the 2007 ECU to ISO 15765 CAN? It appears that all cars by 2008 will use this new protocol.

http://en.wikipedia.org/wiki/OBDII

AFAIK, the tactrix cable is only compatible with ISO9141-2, so does this mean a new modification to the tactrix cable is needed?

I think the answer is bad device driver install. EcuFlash is unable to communicate with the ECU.

The US 2007 Legacy has adopted OBD via CAN. However, the ISO9141 K line pin is still present and connected to the ECU and it's now documented as "SSM Communications Line." That's the pin which the Tactrix cable uses to send and receive data, so maybe it still works.

People have been able to read and rewrite ECUs from US 2007 WRX and STI. But I don't have access to a 2007 Impreza service manual and can't determine whether those cars support OBD via CAN.

[zigzagzok]

Did someone find an answer to this?

Is it because Subaru has changed the 2007 ECU to ISO 15765 CAN? It appears that all cars by 2008 will use this new protocol.

http://en.wikipedia.org/wiki/OBDII

AFAIK, the tactrix cable is only compatible with ISO9141-2, so does this mean a new modification to the tactrix cable is needed?

I think the answer is bad device driver install. EcuFlash is unable to communicate with the ECU.

The US 2007 Legacy has adopted OBD via CAN. However, the ISO9141 K line pin is still present and connected to the ECU and it's now documented as "SSM Communications Line." That's the pin which the Tactrix cable uses to send and receive data, so maybe it still works.

People have been able to read and rewrite ECUs from US 2007 WRX and STI. But I don't have access to a 2007 Impreza service manual and can't determine whether those cars support OBD via CAN.

[zigzagzok]

Did someone find an answer to this?

Is it because Subaru has changed the 2007 ECU to ISO 15765 CAN? It appears that all cars by 2008 will use this new protocol.

http://en.wikipedia.org/wiki/OBDII

AFAIK, the tactrix cable is only compatible with ISO9141-2, so does this mean a new modification to the tactrix cable is needed?

I think the answer is bad device driver install. EcuFlash is unable to communicate with the ECU.

The US 2007 Legacy has adopted OBD via CAN. However, the ISO9141 K line pin is still present and connected to the ECU and it's now documented as "SSM Communications Line." That's the pin which the Tactrix cable uses to send and receive data, so maybe it still works.

People have been able to read and rewrite ECUs from US 2007 WRX and STI. But I don't have access to a 2007 Impreza service manual and can't determine whether those cars support OBD via CAN.

from the diagrams seems that the voltage lines for the 07 ECU is different

http://forums.openecu.org/download.php?id=976
http://forums.openecu.org/download.php?id=975