This is Decipha's Universal ADX for Datalogging the EEC-V with a Moates Quarterhorse. It is editable and MUST be addressed to be used with our XDF's.

I have NO CLUE how to use these but can assist in getting you going with the PID's addressing.

Unfortunately I have not developed an ADX at this time.

See the QH Addressing Guide for more info.

As per Moates on creating a ADX:

If you want to make a datalogging definition for a processor, you’re going to need to:

• Disassemble the code well enough to pinpoint RAM locations for things you care to log.
• For any items that are stored in ram locations 0x0000 through 0x0100 (EECIV) and 0x0000 through 0x0400 (EECV ??? need to verify, may be different for 2 vs. 4 bank.  You can generally tell because private locations will always return the same data), you are going to need to write patch code to relocate these items to blank/unused space.  You can relocate items to either RAM or “ROM” space (because the QH gives read-write access via the J3 port to “ROM” locations stored in RAM on the QH) but you need to make sure NOTHING ELSE IS USING THE ADDRESS SPACE.  If you use RAM or “ROM” that is already in use for other things, you will end up with a processor that does not run properly!!!
• Build a definition including the patch code you’ve come up with
• Create an initialization macro for the QH specifying which RAM addresses need to be included in each data packet, using both stock and patch-code-remapped locations
• Do some analysis to come up with formulas for converting from raw values to real world data
• Build the data values using the formulas you’ve come up with and the packet structure you’ve specified with the QH initialization packet