RomRaider

Hallo together,

after Subaru Diesel Crew is alive somehow , there are some interessing news to finde on there block:

At the EURO5 Diesel, we got some problems with reading some values via SSMviaCAN. The readout seems to be "ff ff" instate of realistic values (e.g. distance since last regeneration, count of regeneratios).

As SDC worte, this values can be read bei advanced OBD measuring with Mode 0x22:

https://subdiesel.wordpress.com/generic ... e22pid114a

They also worte that the lastest petrol Subaru (> MY 2014 WRX ?) uses the same mode for reading subaru specific values.
They are once again the first ones, how public the new Subaru logging mode.

SDC got some values identifiered allready with a android app called "torque-bhp", witch support logging on extended OBD-logging mode.

As I remamber, RR supports allready Mode 1 for logging some values of the WRX, but not all.

So, IMO it makes sense, to got on developing RomRaider logger to Mode 0x22 for logging all Subaru specific values of WRX and Diesel and take over the infos SDC allready found.

Maybe this is also the reason, why we cannot connect to EURO6 Diesel (no SSMviaCAN, only Mode 0x22 OBD logging ?)

BR Jochen

Tryed today with very basic tactrix OBD-Mode22 stande-alone-config:

distance since last regeneration and count of regenerations work with Mode22 reading ..

What I at the moment do not know:
Are every SSM-III parameter awailble on OBD-Mode22 reading ?

What is the difference between SSMviaCAN and OBD-Mode22 ?
Tactrix also supports OBD-Mode23 for BRZ/GT86 reading. As I unterstand, they read RAM-IDs via Mode23.
Do we have a chance to read ECU-parameter of E5 ECU without patching ?

BR Jochen

Going ahead with stand-alone logger Mode 0x22 logging:

Logging "normal" PIDs works quite good, but if I configure "switches" (PID 125B e.g.) stand-alone logger will not work.
No matter, if this PID is part of a config or single value logged.
Also interperating PID 125B as a normal value (should provide 0 or 255), will not help.

Anyone knows ishues about this ?

Next point:

logging 16bit value will not match with the formular, SDC provides.
How to chance high byte first, low byte frist interpretation of raw data ?

Thanks for help !

@Dale:

are there any interrest in implementation Mode0x22 logging in RomRaider ?

Jochen

Took some more time in trying to unterstand, why Tactrix crashes while reading switches and other parameter:

ECU sends a negativ responce, when e.g. PID 0x125F is requested.
W: 22 12 B5
R: 7F 22 31

When I read SSM-III sniffs, I see, tester will start the diagnosic setion with a setion request. Tactrix doesn´t and starts directly with requesting PID values.
Maybe this is the reason, why several PID are refused.

Do not know, if troque-app (testprogramm in Handy-app) will start an diagnosic setion with start request too, so some more PID are anabled.

CAN someone sniff a setion starting with torque-app ?

Got it working now on Tactrix stand alone logger

All SSM-IV values of the EURO5 Diesel ECU are readable, as well as all possible switches.
Even the non reatable SSMviaCAN values..

Reading values in Mode 0x22 is very easy, so I research with CANalyser and find the adresses..
No start of diagnosic setion or a security challed is needed.

Going on with some workshop tools..

Now we need a little update of RomRaider Logger

Excellent work

BRZ/86, new WRX/FXT along with the new Legacy 2.5i and EZ36 plus the other various FB20/FB25 2013+ software would love this

I will try to connect the CANalyser to a Toyota GT86 next week, witch should be simular to the BRZ on diagnostic side.

What I allready reggonized, when I try to connect with a BRZ diag request to the EURO5 Diesel ECU:
the reques ID differs to the Subaru.
I hope this is the only difference, but I will see.

If someone here got a EURO6 Diesel, I like to test the Stand-alone logger config to this engine too

Tested with CANalyser so fare: yes

So, if anyone got RAM-addresses, we can read E5 ECU-Parameter.

Reading the ROM or even the application area with mode23, like ecuMEM does on k-line based SSM-II, need a security access

I've been using the Diesel Crew Mode 0x22 PID definitions to setup fields in Torque Pro and use either Tactrix OPv2 or an ODBLink MX/LX dongle to log Mode 0x22 PIDs on a 2015 WRX (Hitachi ECM, limited SSM PIDs defined by RR team, no extended/floating point SSM PIDs supported by ECM).

Its working good, however the list of Mode 0x22 fields is limited and somewhat biased toward the Subaru diesel engines (understandably so).
I can also log SSM-over-CAN on this car and performance is fast, but like I mentioned above the list of fields is slim.

Intrigued to hear about CANalyzer. I've browsed the software shops website, looking to use it to expand the list of 2015+ WRX/Forester/Levorg etc Mode 0x22 PIDs.

Could you help me or point me in the right direction? What do I need to get things going to define more Mode 0x22 PIDs and test them out?

Sorry for late replay..

Vectors CANalyser is pro-software to work on CAN-busses.You an just is to send self configured IDs als well as use it as a CAN-gateway or programm in caple complete functions or sequences, with a send on CAN or reseve IDs.

I just "rebuild" the OBD communication with CANalyer and tested PID 1st. to get a positiv replay from the ECU and 2nd to try to research factor and off sets of the reseaved values