Did some changes to e38 tableseek file, and now it will find the TX and RX tables stored in OS for any e38 e67 bin. End of table is open, so user needs to figure where it ends, Usage will be for display mainly.


Extract file to XML folder overwriting previous versions.

9:BSCM,10:HBP,11:CGM,12:VDCM,13:BECM_A Here is some more to add to the list, I am sure there is correlation between number and ID on some GMW document, or they just got added on demand. No matter how long is the list last 2 are always.NumOfRxDevices and InvalidRxDevice , they always takes last 2 num...

Knackersjewels wrote: ↑Sat Apr 27, 2024 9:25 pm Bumping, as this is what I need right now

Check this link.
https://universalpatcher.net/a2l-application/

Tre-Cool, once I map some of the code and see what is needed, I can add some tableseek logic to find it on any e38 bins.

Currently you need to trace it in ghidra from start of calibration offset for CAN RX/TX settings.

If I counted correctly this is where bytes are stored from that message, r31 is the offset they get stored in numerical order. Now tracing down to individual bits will take some time, due to ppc crap code. Here is how bits are copied for first byte , r4 is the bit position, some bits might get inver...

For anyone wondering how Cal data is defined per node, there is a table in OS that defines it, similar to DTC list logic. second dword per node defines???length ??size and some other ??data. M:000755C8 TX_table_dword_755C8:.long 0xC9 # DATA XREF: TX1_main_sub_74334+104o ROM:000755C8 # TX1_main_sub_7...

Newer versions might have support for other j-tools. Which IDS version did you use with autel.

Not possible, even different versions works with specific firmware of vci2. It needs specific vci2 dlls

I have some luck and got mdi working with it, but the process wasn`t very straightforward.

This looks like a seed/key request.

Try 128E

Do you have some vins to look at.

Can you read e37 with hptuners.