Address 02: Auto Trans Cannot be reached

No problem. Let me know if you need anythnig else.

Yes! At the exact same time

*Edited 1044 only clarification*
After reading the internal notes it appears as if the 02-Auto trans is is K-only and the guys believe they can try to work on a fix. 03-ABS however didn't debug 1044 clearly with the HEX-V2 and it uses TP 1.6. That might have been due to connecting to 02 first since this is a 2-part (i.e. two separate protocols) problem?

Either way, one more 1044 HEX-V2 session of address 03 alone might shed more light. If you do repeat that please make sure to firstly empty the Debug/ABS/1044 folder so the new session is easy to locate.

Best,
Dana

OK, will try debug 1044, ABS only on V2 interface.

Just to clarify, when doing this the ABS lights come on, on the dash. It appears to be getting comms then dropping out?

There are also some other weird issues with HEX-V2 where it appears to disconnect from the laptop (as if I'd unplugged it) and then reconnect. Device Manager shows the interface vanishing and reappearing.

This only happens when reading the Navigation system 37. I've also seen hangs when trying to read the mobile phone unit 77.

None of this happens with the HEX+CAN.

Thanks for the additional info! Almost sounds like the HEX-V2 interface is crashing.

Debug files sent.

The HEX+CAN interface talks to the Transmission and ABS with KWP2000. It talks TP 1.6-2000 to the Nav.

Quick update. Updated the HEX-V2 and it now reads the TCM. Still struggles with ABS and Nav.