how can i do this?

after adding the two lines to 98640014.xml file

<table name="00" address="0x2E9E2" type="ID" level="1" scaling="unit16" />
<table name="01" address="0x2E9E6" type="ID" level="1" scaling="unit16" />

when i open ECU Flash it give the following message:

parse error at line 366, column 74:
unknown table type [ID].

then i press OK

[06:41:18.093] Version 1.29.906
[06:41:18.093] 8 memory models read.
[06:41:29.140] ROM metadata models 98640014.xml is invalid.
[06:41:30.500] 141 ROM metadata models read.
[06:41:30.500] checksum module "subarudbw" loaded.
[06:41:30.500] flashing tool "wrx02" loaded.
[06:41:30.500] flashing tool "wrx04" loaded.
[06:41:30.500] flashing tool "sti04" loaded.
[06:41:30.500] flashing tool "sti05" loaded.
[06:41:30.500] flashing tool "mitsukernel" loaded.
[06:41:30.500] flashing tool "mitsukernelocp" loaded.
[06:41:30.500] flashing tool "mitsubootloader" loaded.

thanks for the help. i am almost there.

 

type is 1D, not ID

ie ONE D

 

I graphed my first 2 byte load logging:



RPM = RPM/10 (for the pedantics )

What are there those spikes/dips @ 85 and 94ish??

 

This is slightly OT, but I wonder if they match for those who have disabled "lean spool." Lean spool may be altering AFR MAP. Just a guess.

 

Also, it is uint16, not unit16.


Eric

 

well spotted!

ps how come EvoScan can't playback/graph the load value?

 

I’m not sure, but one possible explanation is, that the high and low byte will be read one after the other. In this short time there can be a carry over that can be lost.
Example:
0x00FF at timemark 0
0x0100 at timemark 1
When the high Byte was read at timemark 0 and the low Byte at timemark 1, the a 0x0000 will come out with is wrong.

I think you should just ignore these positions.

What are the values of the two single bytes in this right and left of these values?

 

As the other already posted, there are a few bugs in it.
You can also use these lines, becuse the are alread read/write hex. This is the schema I also use.
Add this to 98640014.xml
<table name="MUT_0x00" category="Misc" address="2e9e2" type="1D" level="1" scaling="Hex16"/>
<table name="MUT_0x01" category="Misc" address="2e9e6" type="1D" level="1" scaling="Hex16"/>

 

thanks.

ok i will add these lines and then what?

do i have to flash a modified hex to the my ecu so i can log the load.

i am really confused and didnt understood the next step after modifiying the xml file?

 

Yes.
Load your current rom in ecuflash and make a backup (always make backups), after adding the lines I posted.
You see unter "MISC" the two tables named "MUT_0x00" and "MUT_0x01"
Change the value of MUT_0x00 to 885C (in the rom I have there was a 87B3 in there)
Change the value of MUT_0x01 to 885D (in the rom I have there was a 87B2 in there)
Then burn this rom to your car. (Remember ALWAYS have a backup of all your changes in a hirachical order)
Then you can go on with your steps 2 (with the changes others posted) and 3.

 

Hate to bump up an old topic, but when I try and enter this in EvoScan 0.98, I get the following error:

"Sorry, your Data.xml is Invalid or out of date, send yours to evoscan@limitless.co.nz and Hamish will happily fix it for you"

Then I hit "Start Playback" and I get the following error box:

"Column 'AccelEnrich does not belong to table LogData"

Am I putting these lines in the wrong place? I didn't notice anything about AccelEnrich in the modified code so I'm wondering where that came from (this did not happen before I started futsing with things). Thanks for helping a mech-e who's not a good comp-e

 

it is missing the new param on each line: ScalingFactor="1"

<DataListItem DataLog="Y" Display="2byteLoad" LogReference="2byteLoad" RequestID="FF" Eval="((256*[Load0])+[Load1])*0.3125" Unit="load" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes="2 byte load read from ECU" />

 

Thanks

 

Just like to say this is working great.. thanks jcsbanks ^_^; The 2byte airflow also .

 

Would 2-byte RPM make the dyno charting programs(DLL) any better? Just curious.