RomRaider

I am trying to search for how to locate ECUID..however cant find related information. Can anyone show me how to calculate or locate ECUID.. I am not looking for CALID which has a fix reference at 0x200(16bits) or 32bits(0x2000), Canbus( 0x2000 or 0x2004)


I would like to modify Romraider logger definition to suit my application to log ROM that have not been officially supported however known to be compatible with particular supported ROM.

learning view will show the ECU id even if the ROM is not supported.

thanks..the car is not with me thus cant do real time log to find out the ECUID.. ANyway is there any write up on how to calculate where is ECUID, I have the ROM with me, should I post the ROM(stock,) here for people to help retrieving it

If it is already supported by RomRaider, you can look in the ECU defs. Search for the cal id and the ecu id is there as well. If it has not been submitted, then post it and I'll tell you the ecu id (there is not any easy method that applies to all ECUs).

Hi ,
The ROM AZ1H102W, JDM Exiga GT 2.0 Auto have been submitted and pending for rom definition. I cant tune but at least start logging, I hope to be able to log the extended parameters like FLKC and FBKC therefore trying to create custom logger definition myself to log.

I am attaching the file for your reference.

thanks

6304504107
it will inherit entirely from AZ1H101W

thank you very much...for your great help...

Thanks alot..I tested it on a ExigaGT..the extended ecu parameters are logging correctly.

By any chance..there is compatibility of this JDM SGT A2TB100V to existing logger definition and ECUID of it.

Trying to help out local community to conduct datalogging on folks put on funny intake MAF housing of openpod.

no

I did some probing with Hex Editor on A2TB100U (SGT MT) ROM and comparing it with A2TB100V(SGT AT) ROM..I found them very similar..There are fix offset for tables at memory addresses lower than 0xCAxxx .

My guess with binary signature search using A2TB100U as base .
ECUID :51 04 50 40 07 (A2TB100V)

On A2TB100U, base on the official definition, I found the timing compensation(Coolant) have 2D array..but the Y-axis data and the data are not in consecutive memory block.. usually 2D data are Axis data then follow by data..for this timing compensation (coolant) table..table data and Axis data are offset by a few memory block. some more.the start address is at odd address no.

A2TB100U -Official definition address
<table name="Timing Compensation (Coolant Temp)" storageaddress="0xC9A51">
<table type="Y Axis" storageaddress="0xC9830" />
</table>


<table name="CL Delay Maximum Engine Speed (Per Gear)" storageaddress="0xC5CFC" />
=> This pointing to all zero area..and looking further on a few memory address up..the pattern of
4000,3900,4000,3900,4000,3900,4000,3900,4000,3900 up which match the CL per gear control rpm..
=> Any possibility of typing wrong address ?

the room.
Is there a chance this ROM(A2TB100V) will use same base address of A2TB100U for extended parameter logging ?
Can I PM you the definition(A2TB100V) that i generated for comment? Please rest assure, I wont post the xml here to confuse public.

I've already finished the A2TB100V. It is very close to the A2TB100U, however, many of the data offsets have changed, which means inheriting entirely from this ROM will not work as far as the ECU defs are concerned. For the logger defs, it will work - all the extended parameter addresses should be identical between the two. Sorry, I do not have time to look at your defs.

Yes..i have done comparison (not scientific method with IDA but just pattern recognition and double confirmation on axis header count to ensure they are referring to same thing and getting correct table size). Definitely can not inherit wholesale .

Hopefully , one day I will start the route of IDA reverse engineering fun...after spending more than 20 hours staring at string of binary number..i started to learn some of basic out of it.

ECU ID
5C 42 50 40 07- AZ1G101N EDM MY09 Forester
5C 12 50 40 07- AZ1G101R-Existing supported ROM

Any chance they both share the same ECU Extended logging parameter ?
I am looking for FBKC and FLKC extended logging parameter for AZ1G101N.