RequestID="CALC" not working for EvoScan v2.9.0023?
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
RequestID="CALC" not working for EvoScan v2.9.0023?
The RequestID="CALC" option for doing math involving several readings is not working for me in EvoScan v2.9.0023. Nothing shows up in the readout. Is anyone else having this issue?
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Just you, I reckon!
RAX Fast Logging is totally built on CALC processing, from front to back. I mean, "Boost" is a CALC item that uses "[MAP]-[Baro]". MAP and Baro are themselves CALC items, with bitwise operations used to extract the packaged RAX data.
If you can attach your raw XML config file, I'd be happy to take a look...
Rich
RAX Fast Logging is totally built on CALC processing, from front to back. I mean, "Boost" is a CALC item that uses "[MAP]-[Baro]". MAP and Baro are themselves CALC items, with bitwise operations used to extract the packaged RAX data.
If you can attach your raw XML config file, I'd be happy to take a look...
Rich
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Just you, I reckon!
RAX Fast Logging is totally built on CALC processing, from front to back. I mean, "Boost" is a CALC item that uses "[MAP]-[Baro]". MAP and Baro are themselves CALC items, with bitwise operations used to extract the packaged RAX data.
If you can attach your raw XML config file, I'd be happy to take a look...
Rich
RAX Fast Logging is totally built on CALC processing, from front to back. I mean, "Boost" is a CALC item that uses "[MAP]-[Baro]". MAP and Baro are themselves CALC items, with bitwise operations used to extract the packaged RAX data.
If you can attach your raw XML config file, I'd be happy to take a look...
Rich
Here's a pared down version of an xml where the CALC does not work for me. This is with a 1.3 cable on an Evo 9.
Code:
<?xml version="1.0"?>
<EvoScanDataLogger>
<vehicle name="Mitsubishi MUTII MMC 1G DSM OBDI - EFI">
<ecu name="EFI mrfred broken CALC">
<Mode2 name="Mode2" type="Data List Items">
<DataListItem DataLog="N" Color="" Display="MIVEC Intake" LogReference="MIVEC" RequestID="77" RequestID2="78" Eval="72-0.6*x/32" Unit="crank deg" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-1.2" GaugeMax="28.8" ChartMin="-1.2" ChartMax="28.2" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
<DataListItem DataLog="N" Color="" Display="MIVEC CALC" LogReference="MIVECcalc" RequestID="CALC" Eval="239*[MIVEC]" Unit="whatever" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-1.2" GaugeMax="28.8" ChartMin="-1.2" ChartMax="28.2" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
</Mode2>
</ecu>
</vehicle>
</EvoScanDataLogger>
Evolved Member
Joined: Oct 2010
Posts: 2,447
Likes: 14
From: Australia
Odd. Compare to RAX Fast Logging style...
DataLog="N" to DataLog="Y" ?
Don't know...
Rich
Code:
<DataListItem DataLog="Y" Priority="2" PriorityOffset="0" Color="" Display="------RAX_D_Dat------" LogReference="RAX_D_Dat" LogHide="True" RequestID="238051b4" Eval="x" Unit="binary" MetricEval="" MetricUnit="" ResponseBytes="4" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Visible="False" />
<DataListItem DataLog="Y" Priority="1" Color="#80ffc0" Display="Baro" LogReference="Baro" RequestID="CALC" Eval="([RAX_D_Dat]BITS(23,7) + 90 ) * 0.07251887" Unit="PSI" MetricEval="([RAX_D_Dat]BITS(23,7) + 90 ) * 0.5" MetricUnit="kPa" ResponseBytes="4" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Visible="False" LogHide="false" />
<DataListItem DataLog="Y" Priority="1" Color="#c04000" Display="MAP" LogReference="MAP" RequestID="CALC" Eval="[RAX_D_Dat]BITS(32,9)*0.0964869" Unit="PSIG" MetricEval="[RAX_D_Dat]BITS(32,9)*0.6652542" MetricUnit="kPa" ResponseBytes="4" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Visible="False" LogHide="false" />
<DataListItem DataLog="Y" Priority="1" Color="#ff8000" Display="Boost" LogReference="Boost" RequestID="CALC" Eval="[MAP]-[Baro]" Unit="PSIG" MetricEval="[MAP]-[Baro]" MetricUnit="kPa" ResponseBytes="4" GaugeMin="0" GaugeMax="255" ChartMin="0" ChartMax="255" ScalingFactor="1" Notes="" Visible="False" LogHide="false" />
Don't know...
Rich
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
DataLog="N" and DataLog="Y" just indicates whether the item is logged by default, i.e., the checkbox in the display is checked. I suppose there could be some weird bug associated with it. I'm wondering if its OP 1.3 vs OP 2.0. I guess I'll try my OP 2.0 cable tomorrow. Thanks for considering.
Thread
Thread Starter
Forum
Replies
Last Post
willdatrill2007
Mitsubishi Vehicles (Airtrek / Outlander)
0
Oct 9, 2016 09:01 PM
Pitside
General Engine Management / Tuning Forum
0
Apr 29, 2014 04:02 PM
RS200Z
Evo X Engine Management / Tuning Forums
1
Jul 29, 2013 01:32 AM