openecu.org

All,

Does anyone know how to decode/interpret the Select Monitor ID? Below is an example sequence of hex bytes of a couple I've come across if that helps:

2E 44 58 41 05 = ecuExplorer reports as 'MY03 Impreza 2.0 WRX (EURO) [AH750-5141]'

3D 44 58 30 05 = ecuExplorer reports as 'MY05 Impreza 2.0 WRX (EURO) [AJ830-8820]

The length of the sequence of bytes might be longer than this however the first and last hex values in the examples above make ecuExplorer display a different model year and different ECU version number.

Any help here appriciated,
-Steve.

the 5 bytes are the ecu id, the rest are the params it supports.
the only one i was able to decode from the ecu id was the 2nd hex byte (the 44 in your examples)

High byte is region code
0=Japan
1=US/Canada
4=Europe
5=Australia
A=South America

Low byte is displacement
2=2.5L
4=2.0L
6=1.6L
A=3.0L

xswrex wrote:the 5 bytes are the ecu id, the rest are the params it supports.
the only one i was able to decode from the ecu id was the 2nd hex byte (the 44 in your examples)

High byte is region code
0=Japan
1=US/Canada
4=Europe
5=Australia
A=South America

Low byte is displacement
2=2.5L
4=2.0L
6=1.6L
A=3.0L

Great info thanks. FYI - if you reverse engineer ecuExplorer's 'labels.dat' file you can easily see that it uses all five hex numbers as a look up for the text to display.

Anyone else with the formula for the remaining data elements in the sequence?
-Steve.

Great info thanks. FYI - if you reverse engineer ecuExplorer's 'labels.dat' file you can easily see that it uses all five hex numbers as a look up for the text to display.

i started in DL1 trying to get the ecu id based on analyzing the hex but could never get it 100% so i resorted to using a lookup table, which is what you are seeing in the label.dat file.

calvin.

bump,

Any progress on this?

NoCtrl wrote:bump,

Any progress on this?

ecuEdit Logger

Sorry, I dont see how this can help me decode the string...
..are there docs or source code hidden inside the "trial version" .exe file?

ah, well I hoped to avoid to extract the label.dat in ecuexplorer and then digging up specs for all the cars..

NoCtrl wrote:Sorry, I dont see how this can help me decode the string...

What's a purpose?

First, I need a logger, and nothing aviable fits my needs.
I want to integrate logged data in real time with the rest of my "carpc"
Second, my car has a JECS ECU, and I really want to peek inside it.
So Im startin on a logging/query tool in python.