RomRaider

Hello all!

Just curious as to how the logger DTC reader operates, as I'm not familiar with the tmpaddr and memaddr attributes. How do you get to a tmpaddr and memaddr from a 0xFF1234 RAM address?

My initial assumption is tmpaddr is where the temporary code is stored, while memaddr is where the set code is stored. But so far, the ECU code only shows a single RAM address (and bit) for the DTC's. Obviously I'll have to talk to some Nissan oriented individuals about the specifications of DTC operation, but just thought I'd see how it'll eventually end up working on RR's end!

Current DTC support was written for Subaru ECUs and may not be compatible or work with other ECU brands.
The two addresses are as you say for the temp and stored codes and the 'bit' is the bit # in that byte location that corresponds to the particular DTC being set or not.

Well that's at least good to hear, as Nissan's RAM DTC's are 1:1 in terms of storage setup as their ROM counterpart. So since current DTC support is subie focused, how do you guys handle it? I noticed that it looks like it's handled like a RAM parameter rather than being through a read DTC's SID. So does that mean that if the proper locations and bits are specified, the DTC viewer would be able to just utilize each protocol's respective read RAM SID to read the proper bytes?

Do note that DTC support is not needed for Nissan ECU's, as NDS2/3 can do so. So if the way the DTC support doesn't allow for Nissan DTC's to be read, there's no problem

We have to use Nissan specific read RAM calls (whatever that happens to be) to get the byte data from RAM.