RomRaider

So a friend of mine is trying to datalog his 03 JDM Nissan Stagea and while CID's work as expected, extended parameters yield checksum errors. The RAM addresses are verified, as is the definition file. So I'm not quite sure why the ECU is causing problems. Using the exact same definition file (with the proper RAM addresses for my ROM added) yields absolutely no issues. So there's probably something going on with his ECU, but just wanted to see if there's anything on RR's side that could help.

Attached below is his RR system log using trace mode. The checksum match error is always "Expected: 2E, Actual: 12" with a preceding "readMsg: only read 4 of 5 bytes from response message" So in my ignorant eyes, the issue is RR logger isn't reading the data from the 5th byte, causing a checksum error.

If may not be an actual checksum issue.
The request is: 0AAC8183FFFF84A802110A01
Looking at the response 037FAC12, 7F AC if I recall means not supported. So either AC is not supported or the mode or the address.

This seems to work as expected: 05AC8102110A4F
response: 02EC816F
AC + 40 = EC which is an acknowledgement.

Huh. Yea that's a negative ARB ID error. Nisprog errors when he tries to do a RAM dump as well. So I wonder if it means that he can't read the RAM area with $AC? Seems strange for Nissan to exclude RAM reading from $AC, but it is a JDM Nissan Stagea SH7055 ECU.