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.

6c=priority f0 or f1 it doesn`t matter, this is the tool ID and can vary from f0-fd Last byte of pid request does have some meaning, and without it mode 22 is not working. Anyway mode 22 logging is way slower than DPID mode. To see actual communication on bus you can goto universal patcher vpw conso...

It is possible gt is not supported with pcmhammer, try some older version of hammer. You can also try running this script in universal patcher to confirm gt is good-> logger-> select device->connect->vpwconsole tab->check print to screen->upload script button->select attached file and wait till scri...