Evo X Logging
#781
Update: EvoScan v2.7 Beta5
- New Feature: Added "Set DataLog Folder..." option under the Logging menu.
- New Feature: EvoX SST Gearbox Temp Reading added to 2008 JDM EvoX, someone can test it on the other EvoX's see if it is accurate.
You can download and extract the files in this zip file into your exisiting evoscan v2.6 installation folder. (c:\Program files\Evoscan\EvoScan v2.6\)
EvoScanv2.7beta5.zip
I have two data.xml files that have different values on my pc, can anyone confirm the correct formulas for these ones:
Mode23 2008 JDM EVOX:
InVVT Eval="(x-4096)*-0.01953" or Eval="(x-3552)/48.64+10"
Load (MIVEC) and (Timing if IATS GT 75F) RequestID="2380876c" or RequestID="23808774"
Load (Timing if IATS LE 75F) RequestID="23808F68" or RequestID="23808F70"
Mode23 USA EVOX:
InVVT Eval="(x-4096)*-0.01953" or Eval="(x-3552)/48.64+10"
NEW: SST Temp in DegC
<DataListItem DataLog="N" Color="" Display="SST Transmission Temp" LogReference="SST_TM_Temp" RequestID="CAN28-0" Eval="x-50" Unit="Deg F" MetricEval="x-50" MetricUnit="Deg C" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
- New Feature: Added "Set DataLog Folder..." option under the Logging menu.
- New Feature: EvoX SST Gearbox Temp Reading added to 2008 JDM EvoX, someone can test it on the other EvoX's see if it is accurate.
You can download and extract the files in this zip file into your exisiting evoscan v2.6 installation folder. (c:\Program files\Evoscan\EvoScan v2.6\)
EvoScanv2.7beta5.zip
I have two data.xml files that have different values on my pc, can anyone confirm the correct formulas for these ones:
Mode23 2008 JDM EVOX:
InVVT Eval="(x-4096)*-0.01953" or Eval="(x-3552)/48.64+10"
Load (MIVEC) and (Timing if IATS GT 75F) RequestID="2380876c" or RequestID="23808774"
Load (Timing if IATS LE 75F) RequestID="23808F68" or RequestID="23808F70"
Mode23 USA EVOX:
InVVT Eval="(x-4096)*-0.01953" or Eval="(x-3552)/48.64+10"
NEW: SST Temp in DegC
<DataListItem DataLog="N" Color="" Display="SST Transmission Temp" LogReference="SST_TM_Temp" RequestID="CAN28-0" Eval="x-50" Unit="Deg F" MetricEval="x-50" MetricUnit="Deg C" ResponseBytes="1" GaugeMin="0" GaugeMax="1000" ChartMin="0" ChartMax="1000" ScalingFactor="1" Notes="" Priority="1" Visible="False" />
#786
I uninstalled all the other versions and extracted the 2.7 b5 to several different locations and used two different unpack programs and it is still having the same error. It opens the evo x GUI, but you can't do anything with it, then when you close the GUI it has a similiar error window pop up.
#787
#788
I uninstalled all the other versions and extracted the 2.7 b5 to several different locations and used two different unpack programs and it is still having the same error. It opens the evo x GUI, but you can't do anything with it, then when you close the GUI it has a similiar error window pop up.
option2) wait until full v2.7 is released with full installer.
#790
redownload EvoScanv2.7beta5.zip the last one had the wrong files.
#792
In the meantime, if you have a PLX-AFR, you can use the EVOXLogger that I posted earlier in this thread. It supports the PLX, just make sure you modify the "wb.config" correctly. If you aren't using an USDM EVO X, then modify the "monitors.config" and add the proper addresses (you are from sweden right? dunno what type of EVOX's they have out there).
Code:
# # Type:COMPORT:TestMode # PLX:COM4:false
Last edited by funks; Oct 6, 2009 at 10:14 AM.
#793
Thanks!
Yes, we have EDM EVO X in Sweden and I guess JDM-calc would be suitable for EDM just
like in evoscan where I use JDM-mode23 settings...
Then I will place an order on the PLX-AFR with the nice OLED-gauge :-)
Yes, we have EDM EVO X in Sweden and I guess JDM-calc would be suitable for EDM just
like in evoscan where I use JDM-mode23 settings...
Then I will place an order on the PLX-AFR with the nice OLED-gauge :-)
#794
#795
Code:
# # Name:Source:HexAddress:ReturnBytes:RPNFormula:Priority # 1) Make sure there are NO SPACES (including @ end) # 2) Make sure your formula is correct - "x" is the value returned from the car. # TPS:OP2:0x8086F1:1:x,100,*,255,/:1 RPM:OP2:0x808747:1:31.25,x,*:1 Load:OP2:0x808766:2:x,10,*,32,/:1 TimingAdv:OP2:0x8089FF:1:x,20,-:1 KnockSum:OP2:0x808A43:1:x:1 PSIG:OP2:0x808712:2:x,4,/,0.19347,*,14.5,-:1 # or for BAR - BAR:OP2:0x808712:2:x,4,/,0.01334,*,1,-:1 WideBandAF:WB:0x000000:0:x:1
Code:
# # Name:Source:HexAddress:ReturnBytes:RPNFormula:Priority # 1) Make sure there are NO SPACES (including @ end) # 2) Make sure your formula is correct - "x" is the value returned from the car. # TPS:OP2:0x8086F9:1:x,100,*,255,/:1 RPM:OP2:0x80874F:1:31.25,x,*:1 Load:OP2:0x80876E:2:x,10,*,32,/:1 TimingAdv:OP2:0x808A07:1:x,20,-:1 KnockSum:OP2:0x808A4B:1:x:1 PSIG:OP2:0x80871A:2:x,4,/,0.19347,*,14.5,-:1 # or for BAR - BAR:OP2:0x80871A:2:x,4,/,0.01334,*,1,-:1 WideBandAF:WB:0x000000:0:x:1
Last edited by funks; Oct 6, 2009 at 10:41 AM.