2-byte RPM HOW-TO

Reply Subscribe

Thread Tools

Search this Thread

Dec 5, 2007 | 03:16 PM

#46

tephra

EvoM Guru

iTrader: (6)

Joined: Mar 2007

Posts: 9,486

Likes: 66

From: Melbourne, Australia

paste in your evoscan xml for the load and rpm...

i suspect its just the formula

Reply Like

Dec 5, 2007 | 07:46 PM

#47

broddey

Evolving Member

iTrader: (5)

Joined: Nov 2005

Posts: 498

Likes: 0

From: Tampa, FL

Thanks in advance for help. All the way at the bottom is where the changes are.

Attached Files

evo9base.txt (10.7 KB, 21 views)

Reply Like

Dec 5, 2007 | 08:28 PM

#48

tephra

EvoM Guru

iTrader: (6)

Joined: Mar 2007

Posts: 9,486

Likes: 66

From: Melbourne, Australia

evoscan not ecuflash

Reply Like

Dec 5, 2007 | 08:40 PM

#49

broddey

Evolving Member

iTrader: (5)

Joined: Nov 2005

Posts: 498

Likes: 0

From: Tampa, FL

And of course it wont let me upload now.

Last edited by broddey; Dec 5, 2007 at 08:45 PM.

Reply Like

Dec 5, 2007 | 10:24 PM

#50

tephra

EvoM Guru

iTrader: (6)

Joined: Mar 2007

Posts: 9,486

Likes: 66

From: Melbourne, Australia

just copy/paste the 2 lines

Reply Like

Dec 6, 2007 | 02:59 PM

#51

broddey

Evolving Member

iTrader: (5)

Joined: Nov 2005

Posts: 498

Likes: 0

From: Tampa, FL

<table name="2 Byte RPM High Bit" address="3EE6E" category="MUT" type="1D" level="1" scaling="Hex16" />

<table name="2 Byte RPM Low Bit" address="3EE72" category="MUT" type="1D" level="1" scaling="Hex16" />

<table name="2 Byte Load High bit" address="3EE66" category="MUT" type="1D" level="1" scaling="uint16" />

<table name="2 Byte Load Low bit" address="3EE6A" category="MUT" type="1D" level="1" scaling="uint16" />

It seems I have inadvertanly copied and pasted the ecuflash code to the evoscan roms, as they are both identical.

I have glanced around at all the available roms for both ecuflash and evoscan and they are identical, with the addition of the mod options. What am I doing wrong?

Evo IX rom 13, 2 byte rpm values are 6B1E High and 6B1F Low, 2 byte load values are 27169 and 27168.

Last edited by broddey; Dec 6, 2007 at 03:02 PM.

Reply Like

Dec 6, 2007 | 04:14 PM

#52

tephra

EvoM Guru

iTrader: (6)

Joined: Mar 2007

Posts: 9,486

Likes: 66

From: Melbourne, Australia

ok - evoscan is a logger, ecuflash is an editor - they use different format xml files.

your evoscan lines should look like -

Code:

        <DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="02" RequestID2="03" Eval="1000/256*x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8000" ChartMin="0" ChartMax="8000" ScalingFactor="0.1" Notes="" Priority="1" Visible="False" />
        <DataListItem DataLog="N" Color="" Display="Load MUT 2Byte Mod" LogReference="LoadMUT2Byte" RequestID="00" RequestID2="01" Eval="0.3125*x" Unit="units" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="300" ChartMin="0" ChartMax="300" ScalingFactor="1" Notes="" Priority="1" Visible="False" />

Reply Like

Dec 6, 2007 | 04:55 PM

#53

broddey

Evolving Member

iTrader: (5)

Joined: Nov 2005

Posts: 498

Likes: 0

From: Tampa, FL

I found the files under DATA that, oddly enough, start with <DataListItem.

So I add the <DataListItem code to the end of the xml in the data file right? Do I have to specify which mode its in, and if so, which one is it? My last few lines of code look like this:

<ecu name="ABS">
<Mode1 name="Mode1" type="Diagnostic Trouble Codes">
<DTC_TEMP Code="16" DiagnosticItem="Battery voltage abnormal" />
<DTCControl_TEMP Code="CA" DiagnosticItem="Clear Fault Codes" Notes="returns 0x00" />
</Mode1>
<Mode2 name="Mode2" type="Data List Items">
<DataListItem DataLog="N" Color="" Display="G Sensor" LogReference="ABS_GForce" RequestID="00" Eval="0.0195*x" Unit="V" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="2.5V at Zero Gs" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="Battery Level" LogReference="ABS_Battery" RequestID="00" Eval="x" Unit="V" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Front Right Sensor" LogReference="ABS_FR" RequestID="00" Eval="x" Unit="km/h" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Front Left Sensor" LogReference="ABS_FL" RequestID="00" Eval="x" Unit="km/h" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Rear Right Sensor" LogReference="ABS_RR" RequestID="00" Eval="x" Unit="km/h" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
<DataListItem DataLog="N" Color="" Display="Rear Left Sensor" LogReference="ABS_RL" RequestID="00" Eval="x" Unit="km/h" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Priority="1" Visible="false" />
</Mode2>
<Mode6 name="Mode6" type="Actuator Tests">
<ActuatorTest Display="?0xF1" LogReference="0xF1" Code="F1" ActivatingContent="" Notes="" />
</Mode6>
</ecu>
</vehicle>
</EvoScanDataLogger>

Last edited by broddey; Dec 6, 2007 at 05:26 PM.

Reply Like

Dec 6, 2007 | 06:25 PM

#54

tephra

EvoM Guru

iTrader: (6)

Joined: Mar 2007

Posts: 9,486

Likes: 66

From: Melbourne, Australia

ecu=EFI and mode=2

Reply Like

Dec 11, 2007 | 10:46 AM

#55

broddey

Evolving Member

iTrader: (5)

Joined: Nov 2005

Posts: 498

Likes: 0

From: Tampa, FL

If I wanted the gauge max closer to 400 for 2 byte load, all I do is change it in the code, correct?

Do I also have to change the chart max?

Reply Like

Dec 18, 2007 | 07:21 AM

#56

Gpunkt

Newbie

Joined: Sep 2007

Posts: 18

Likes: 0

From: Germany

Lines for 88840017.

<table name="MUT02 2-byte RPM MSB" category="MUT" address="3794e" type="1D" level="1" scaling="Hex16" />
<table name="MUT03 2-byte RPM LSB" category="MUT" address="37952" type="1D" level="1" scaling="Hex16" />

Change Values like 88840016

(0x)6AFE - hi-byte
(0x)6AFF - low-byte

Reply Like

Oct 28, 2018 | 07:14 PM

#57

MR Turco

EvoM Staff Alumni

iTrader: (16)

Joined: May 2007

Posts: 3,233

Likes: 3

From: Massachusetts

Does anyone have the 2byte RPM values for 9653 V7? I am revving over 8k RPM and need some logging. I could be an idiot but I've never hit a wall searching for something i was sure existed. thanks for the help

Reply Like

Oct 29, 2018 | 04:23 AM

#58

MR Turco

EvoM Staff Alumni

iTrader: (16)

Joined: May 2007

Posts: 3,233

Likes: 3

From: Massachusetts

I don't know how but i scrolled past it in Jamie's thread a dozen times - here is the info if someone else is looking:

https://www.evolutionm.net/forums/ec...te-thread.html

96530006
2byte load
MUT 00 = 898A
MUT 01 = 898B

2byte RPM
MUT 02 = 8962
MUT 03 = 8963

2byte AirFlow
MUT 04 = 89E2
MUT 05 = 89E3

MUT 3D TABLE ADDRESS = 36200