Trouble with 2-byte airflow in 96940011 ROM
Trouble with 2-byte airflow in 96940011 ROM
Hey guys,
I'm new to the whole EcuFlash thing. I bought a JDM MAP sensor from mrfred (thanks!), and I installed it last night. I made the modifications in this thread to the MAP sensor tables, and then I went to this thread for information on outputting 2-byte load, airflow, and RPM, as well as upping the baud rate to 62500. I uploaded the ROM with the modifications. The JDM MAP, load, RPM, and baud work fine, but 2-byte airflow doesn't. All I get from EvoScan is values within a few billionths of 0.09828125, which is what I'm multiplying x by in the formula (so what I'm actually reading is right around 1).
In the first row of my MUT table in EcuFlash, in column 6 I have 899A and in column A I have 899B (for 2-byte load). In column E I have 89F6 and in column 12 I have 89F7 (for 2-byte airflow). In column 16 I have 8976 and in column 1A I have 8977 (for 2-byte RPM).
In EvoScan's data.xml, I have the following rows for load, airflow, and RPM:
Does anyone know what I might be doing wrong? Thanks in advance for any help.
I'm new to the whole EcuFlash thing. I bought a JDM MAP sensor from mrfred (thanks!), and I installed it last night. I made the modifications in this thread to the MAP sensor tables, and then I went to this thread for information on outputting 2-byte load, airflow, and RPM, as well as upping the baud rate to 62500. I uploaded the ROM with the modifications. The JDM MAP, load, RPM, and baud work fine, but 2-byte airflow doesn't. All I get from EvoScan is values within a few billionths of 0.09828125, which is what I'm multiplying x by in the formula (so what I'm actually reading is right around 1).
In the first row of my MUT table in EcuFlash, in column 6 I have 899A and in column A I have 899B (for 2-byte load). In column E I have 89F6 and in column 12 I have 89F7 (for 2-byte airflow). In column 16 I have 8976 and in column 1A I have 8977 (for 2-byte RPM).
In EvoScan's data.xml, I have the following rows for load, airflow, and RPM:
Code:
<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="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/> <DataListItem DataLog="N" Color="" Display="Airflow MUT 2Byte Mod" LogReference="AirflowMUT2Byte" RequestID="02" RequestID2="03" Eval="0.09828125x" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="2500" ChartMin="0" ChartMax="2500" ScalingFactor="0.1" Notes=""/> <DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="04" RequestID2="05" Eval="1000*x/256" Unit="rpm" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8" ChartMin="0" ChartMax="80" ScalingFactor="0.01" Notes=""/>
Last edited by Tom-05-MR; Sep 12, 2007 at 06:55 AM. Reason: I can count!
Ok, I logged in Mitsulogger instead and it worked perfectly. My lines for 2-byte airflow in Mitsulogger's requestID.xml are:
6.29/64 = 0.09828125, so the formulas are the same between the two programs. Since it works in Mitsulogger but not Evoscan, it's clear that everything's ok on the ECU side and I've just got a problem with the way I've configured Evoscan. I would still appreciate any insights, if anyone else has run into a similar problem.
Code:
<Request LogReference="AirflowB00" RequestID="02" Eval="x" Unit="INT" Logged="y" Response="2"/> <Request LogReference="AirflowB01" RequestID="03" Eval="x" Unit="INT" Logged="y" Response="2"/> <Request LogReference="Airflow2Byte" RequestID="FF" Eval="6.29/64*((256*AirflowB00)+AirflowB01)" Unit="Hz" Logged="y" Response="2"/>
I'm sorry to bump my own thread again, but I worked at this all weekend and I can't figure out why Mitsulogger is logging 2-byte airflow properly but Evoscan isn't. Is there an Evoscan-specific support forum somewhere that I should take this to?
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Hey guys,
I'm new to the whole EcuFlash thing. I bought a JDM MAP sensor from mrfred (thanks!), and I installed it last night. I made the modifications in this thread to the MAP sensor tables, and then I went to this thread for information on outputting 2-byte load, airflow, and RPM, as well as upping the baud rate to 62500. I uploaded the ROM with the modifications. The JDM MAP, load, RPM, and baud work fine, but 2-byte airflow doesn't. All I get from EvoScan is values within a few billionths of 0.09828125, which is what I'm multiplying x by in the formula (so what I'm actually reading is right around 1).
In the first row of my MUT table in EcuFlash, in column 6 I have 899A and in column A I have 899B (for 2-byte load). In column E I have 89F6 and in column 12 I have 89F7 (for 2-byte airflow). In column 16 I have 8976 and in column 1A I have 8977 (for 2-byte RPM).
In EvoScan's data.xml, I have the following rows for load, airflow, and RPM:
Does anyone know what I might be doing wrong? Thanks in advance for any help.
I'm new to the whole EcuFlash thing. I bought a JDM MAP sensor from mrfred (thanks!), and I installed it last night. I made the modifications in this thread to the MAP sensor tables, and then I went to this thread for information on outputting 2-byte load, airflow, and RPM, as well as upping the baud rate to 62500. I uploaded the ROM with the modifications. The JDM MAP, load, RPM, and baud work fine, but 2-byte airflow doesn't. All I get from EvoScan is values within a few billionths of 0.09828125, which is what I'm multiplying x by in the formula (so what I'm actually reading is right around 1).
In the first row of my MUT table in EcuFlash, in column 6 I have 899A and in column A I have 899B (for 2-byte load). In column E I have 89F6 and in column 12 I have 89F7 (for 2-byte airflow). In column 16 I have 8976 and in column 1A I have 8977 (for 2-byte RPM).
In EvoScan's data.xml, I have the following rows for load, airflow, and RPM:
Code:
<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="500" ChartMin="0" ChartMax="500" ScalingFactor="1" Notes=""/> <DataListItem DataLog="N" Color="" Display="Airflow MUT 2Byte Mod" LogReference="AirflowMUT2Byte" RequestID="02" RequestID2="03" Eval="0.09828125x" Unit="Hz" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="2500" ChartMin="0" ChartMax="2500" ScalingFactor="0.1" Notes=""/> <DataListItem DataLog="N" Color="" Display="RPM MUT 2Byte Mod" LogReference="RPMMUT2Byte" RequestID="04" RequestID2="05" Eval="1000*x/256" Unit="rpm" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="0" GaugeMax="8" ChartMin="0" ChartMax="80" ScalingFactor="0.01" Notes=""/>
Thanks mrfred! The missing * was the problem. I feel bad about it being something so simple. I stole the formula directly out of this post. I didn't changed the scaling factor from 0.1 to 1; I don't actually understand what scaling factor is yet but I'll experiment with it tomorrow.
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Thanks mrfred! The missing * was the problem. I feel bad about it being something so simple. I stole the formula directly out of this post. I didn't changed the scaling factor from 0.1 to 1; I don't actually understand what scaling factor is yet but I'll experiment with it tomorrow.
Trending Topics
Thread
Thread Starter
Forum
Replies
Last Post
GST Motorsports
09+ Ralliart Engine/Turbo/Drivetrain
113
Feb 14, 2017 06:09 AM
