RomRaider

A request for help with some can bus logging on 08 sti with SI-DRIVE to help me work out which are the can messages for switching the SI drive modes. Should not take more than 10 mins work.

Using the canlogger sample code in openecu software for Tactrix cable.

1) Build the .exe and run while connected to the car calling the file sidrive_none.log.
2) Switch on the ignition wait 10 sec.
3) switch off ignition.
4) Run canlogger.exe again while connected to the car calling the file sidrive_sport.log.
5) Switch on the ignition wait 5 sec.
6) Switch SI drive to SPORT and wait 4 sec.
7) switch off ignition.
8) Run canlogger.exe again while connected to the car calling the file sidrive_sport#.log.
9) Switch on the ignition wait 5 sec.
10) Switch SI drive to SPORT# and wait 4 sec.
11) switch off ignition.
12) Run canlogger.exe again while connected to the car calling the file sidrive_intelligent.log.
13) Switch on the ignition wait 5 sec.
14) Switch SI drive to INTELLIGENT and wait 4 sec.
15) switch off ignition.

Post logs to this thread.

Many thanks in advance. If you are wondering why, I'm trying to work out the messages so for fun I can wire up the SI-DRIVE selector to an arduino or raspberry pi to send the correct message based on the switch position in a WRX, that does not have the switch or combination meter that does this in the STI. The WRX rom has the code/tables for SI-DRIVE as occording to this post. Once I get this to work and switch I can then modify the rom DBW maps for the other modes. (The stock 3 map tables are identical.)
http://www.romraider.com/forum/viewtopic.php?f=40&t=3741&start=0

if the si drive functionality is not enabled from rom it will not work -> and most likely it's not ..

anyone? I can provide a built canlogger.exe if required.

https://subdiesel.wordpress.com/ecu-ana ... -messages/

You are probably to analize inside the ecu code BIU messages with CAN ID 0x514, 0x600, 0x620.

Most probably BIU of your car is sending those messages and just an applicable switcher should be connected to BIU.

Please provide the stande-alone configuration.

I will asked in our Subi-Evo-Teff forum for support ..

My diesel doesn´t have any SI-mode

Thanks, attached is the built canlogger.exe tool from tactrix.

Sorry, that file doesn´t seem to work :

anything to know, when starting the exe ?

OP system: WIN7
Tactrix is attached to PC, but after starting window appeats and disapears right after..

Is there any stande-alone logger app, with can stored of SD-card and with starts CAN-logging after inserting the tactrix in the OBD-plug ?

Sorry should have made this clearer. To run the logger you need to open a cmd window in the directory where the canlogger.exe is.

type canlogger.exe <filenameoflogfile.log>. (if you run without the filename it will show the optional parameters.)


Then switch on ignition to start logging. Press a key to stop logging.

Im not aware of any way to do this direct on the tactrix, but guess this would involve building it for the processor somehow and making it run.

Yes the dash cluster where the SI-DRIVE switch is connected talks to the BIU. I might have to simulate this on the low speed bus, but to start I'd like to see the messages from the BIU to the ECU, as this is possible using the Tactrix. I'm not sure if it will pickup messages on the low speed bus yet.

I will give it a try. If there are any MY2008 STI around me, I can log with Vector CANalyser, but I don´t know ..

It could be able to, but this need so electrical work:

low speed bus is not connected to OBC-plug, so Tactrix will not be connected to low speed bus yet.

Some extra wire are need and for confortable connection an other OBD-plug

Thanks. It can be on a 2009/2010 STi also.

If I need access to the low speed bus, I will need to tap into the CAN BUS lines to the NAVI system, this will be more tricky than the OBD2 port especially on someone elses STi! Thats why I'm starting with the FAST ECU bus as that is told to change the selected DBW map. I think the biggest blocker to this project will be if the switching of SI-DRIVE is just a data bit(s) in a bigger generic repeated message as I won't be able to simulate/override this due to the live component sending a default/empty value constantly. I'm hoping that the messages are unique single shot messages sent when the switch is moved. Until I can identify the actual messages on both buses I can't do much more.

Those CAN messages are repeated each 20 ms on High CAN bus from BIU to ECU in order to confirm SI Mode.
Low CAN bus is most probably serves for SI Mode indication.

Analize CAN ID 0x514 and CAN ID 0x620.

Thanks, that was what I suspected. I guess I should concentrate on the low can bus. I hope the cluster does not continually repeat the same to the BIU otherwise it could be tricky to spoof.