What tables and scalers are being used?

This question might have an answer that is to complicated for my brain to understand or figure out, but I thought I would ask.

Is there any way to find out what scalers and tables are used/loaded to calculated a value (1 data point in time) in the data stream?

For example, if a person was looking at timing (at a specific time) in a data log, can the tables and scalers be flagged, highlighted, etc to find out what is being used to calculate the timing output?

I'm using a 1227747 ECM and tunerpro.

automatically and in detail, nope.

why is that not possible? because tunerpro can't read ecm programs, only the variables.

ecm programs branch quite a bit, and decisions are made based on many conditions.

you have conditions like: (if coolant temp is greater than min coolant temp for PE spark) and (if PE spark adder is greater than 1) and (if low octane compensation is not set) add 2 degrees to spark advance, else disable pe spark advance for three loops.

sometimes the conditions don't even make sense, or are not well understood, or will change for code revisions even within the same mask.

so, tunerpro isn't very knowledgable about that kind of control flow, and there's no realistic way to teach it

tunerpro has a feature that can hilight table values based on inputs like map or whatever, such as 'if map is x and rpm is y, this area of the timing table is probably being used', that's called data tracing.

but it isn't smart enough to say 'this table is used when neutral is set, and this is used when neutral is not set.'. even if it was, not all the variables that drive the ecm's code are available on output, so it wouldn't work in many cases.

this is why documentation is really awesome, if whoever hacked your ecm originally could document not just what the scalers do but how they're used, you could read around and figure most of it out. sadly this isn't the case for most xdfs.

truly understanding how the various inputs generate the output in various conditions (disassembly, etc)

but you can make some really safe assumptions, and figure where a 'missing' variable is in a lot of cases

Thanks.