Finally worked out how to use ROM data with EvoScan..sorta

[Kaldek]

Well after over 12 months and an on-again off-again commitment I finally learned how to use ECUFlash to look at the settings in a VR4 ROM.

My question to @TME_Steve and @BCX though is if I have all the latest/correct definition files so that the tables I'm seeing are all the ones that can be seen/edited.

BCX sent me some almost a year ago. They are:

20030010.xml
20030011.xml
20030013.xml
23810003.xml
23180004.xml
vr4base.xml

Can I confirm these are the right/most accurate definition files? There seems to be a lot less tables in these than there is for, say, an Evo7 (as seen in Merlin's tuning guide).


Guys my next question is whether these files are relevant at all for EvoScan's live logging/graphing? The following screenshot suggests they are:

If the above is correct, is the process:

1. Read ROM from ECU using ECUFlash
2. Store ROM and XML definitions in one place
3. Load the ROM and XML into EvoScan graphing?

 

[Kaldek]

Ohhhh wait I think I get the map tracing now.

Panel #1 in EvoScan Map Tracer collects data from real-time log capture - when coupled with a Wideband which is also capturing and returning actual AFR readings.
Panel #3 in EvoScan Map Tracer is the static data from the ROM.

So, this means that Map Tracer needs:

• The definition files to make sure it's reading the right table for load/AFR; and
• The ROM to actually pull the settings and display on the screen

Am I right?

 

[Kaldek]

Nobody? @TME_Steve and @BCX ? Nothing to say?

 

[TME_Steve]

Neither of us use map tracer. Looks about right though

 

[Kaldek]

OK, thanks.

 

[jungle]

If the rom and xml files are correct it should just do it. Hit graph, think F4 and oila Mine does