is there any reasoning that my car would make a large number of output files? some are minutes long while others are only 4 frames of data?

Usually two reasons
1. Your using triggers and the trigger condition is being set on and off
2. The connection to obd port is not good and the communications keeps getting interrupted or power to unit is interruped

Try bending the two rows of pins on tactrix inwards very slightly like 0.5 mm, try using an old full size SD memory card or similar so pins stay aligned

Hi ..

Tactrix op2 log the ram from 0xFFF8000 TO 0XFFF8FFF

DO YOU KNOW HOW TO READ OTHER AREA?

What 'other area' are you looking to read?

From
0xFFF00000 TO 0xFFF7FFFF
0xFFF8FFFF TO 0xFFFFFFF

THE RAM IS FROM 0XFFF80000 TO 0XFFF8FFFF

(Warning: loaded question ahead)

How do I go about making these corrections myself?

The idle ignition timing tables for my ZA1JD00C are a bit messy; the same that we've seen for B01C and others. I tried using basic math (calculating the differences between start/end of tables and axes), but they seem to differ quite a bit between the various definition files. Any chance I could get some help on this?

The definition file I'm using as a base for this is the latest from OFT. In the example below, I'm missing the X axis for the "Base Timing Idle (In-Gear)(Above Speed Threshold)" table.

D00C
http://i.imgur.com/6bqoQNv.png

700C
http://i.imgur.com/t755SJB.png

3D Definition contains the coolant temp like it's supposed to, but the storage address is not defined, and it seems like the Y axis is incorrectly defined as well.
2D and 3D Definitions in D00C
http://i.imgur.com/c4jKfcK.png

RomRaider with ZA1JD00C
http://i.imgur.com/4DWKDjy.png

Unless your prepared to learn how to reverse engineer the ecu code, its going to be much easier to just flash your D00C ecu with the B01C rom it will work fine and the defs for B01C are much better

HERE YOU ARE
ZA1JF00C i dont know if i work or not
Code:

<table name="Base Timing Idle (In-Gear)(Above Speed Threshold)" storageaddress="118EFC">
<table type="X Axis" storageaddress="118ECC" />
<table type="Y Axis" storageaddress="118EF4" />

Code:

<table type="3D" name="Base Timing Idle (In-Gear)(Above Speed Threshold)" category="Ignition Timing - Advance" storagetype="uint8" endian="big" sizex="10" sizey="2" userlevel="4">
<scaling units="Base Ignition Timing (degrees BTDC)" expression="(x*.3515625)-20" to_byte="(x+20)/.3515625" format="0.00" fineincrement=".2" coarseincrement="1" />
<table type="X Axis" name="Engine Speed" storagetype="float" endian="little" logparam="P8">
<scaling units="RPM" expression="x" to_byte="x" format="#" fineincrement="50" coarseincrement="100" />
</table>
<table type="Y Axis" name="Coolant Temperature" storagetype="float" endian="little" logparam="P2">
<scaling units="Degrees F" expression="x" to_byte="x" format="#" fineincrement="1" coarseincrement="5" />
</table>
<description>This is the base timing in idle mode when vehicle speed is greater than the 'Base Timing Idle Vehicle Speed Threshold' and transmission is not in neutral.</description>

I actually am quite prepared! For the time being, I'll see about using the B01C. But if you could point me in the right direction, that would be awesome!

Best place for rom dissassembly help is the www.romraider.com forums
Ask a guy called tdd he does a lot of dissassembly think hes a moderator on that forum , they hould be able to hook you up with the ida and instruction sets for the sh72531 processor our ecu uses, vood luck im sure those guys will apreciate people helping with dissassembly

Unfortunately it did not! However, I got a little curious and, assuming the tables are the same size for each MAP, I used some basic 16-bit math to calculate the location of the table in my D00C def.

Here's what I came up with:

Which produces the following:

http://i.imgur.com/eKLfv1z.png

This is what you looking for

When we log "load", which load is it exactly?

Is it just MAF*60/rpm? Or is it the final load after all corrections are applied?

Also, where does "load_abs" come from?

Thanks!