EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
Hamish, im loving 2.9. My TPS warnings appear to be due to me cropping my logs down to just WOT. The looping of runs also appears to be an issue with this as well. It seems that if evoscan only sees 100% throttle it will chart the dyno plots together even though they may be separate csv files. Not a big deal just have to crop my runs with a few rows before and after WOT to make it happy.
Also seeing some older posts of the evoscan dyno plots I see where you are able to pick a point and it display the hp/tq value at that point much like the dynojet software. Is this missing from 2.9 or am I just not finding it?
Would love an easy way to import my drf files to do comparisons. DRF is the dynojet run files for those wondering. In the Winpep software you can export put the drf to an easily imported txt file for excel. Obviously if you are on the dyno and logging with evoscan this isnt an issue, but if you werent logging, or had a logging issue i this think would be a cool feature.
Also seeing some older posts of the evoscan dyno plots I see where you are able to pick a point and it display the hp/tq value at that point much like the dynojet software. Is this missing from 2.9 or am I just not finding it?
Would love an easy way to import my drf files to do comparisons. DRF is the dynojet run files for those wondering. In the Winpep software you can export put the drf to an easily imported txt file for excel. Obviously if you are on the dyno and logging with evoscan this isnt an issue, but if you werent logging, or had a logging issue i this think would be a cool feature.
the dyno graphs will scan for multiple power runs in one csv file. when the TPS goes less than 80, it determines to be the next run. maybe easiest for you to put an extra row in between each run with TPS of 0 (zero)
also you can put them into two different csv files, and press load log1, and then press load log2.
just hover over the actual line on the chart and it should display the TQ/HP. email or pm me the csv log and I can check it out if its still not showing the tooltip.
yeah I like the idea of DynoJet files being able to use it in EvoScan. could add DRM import. send me a sample log.
Just remember to untick the Wind Drag setting when power graphing in EvoScan with the dyno.. because there is no wind resistance in the dyno room
also you can put them into two different csv files, and press load log1, and then press load log2.
just hover over the actual line on the chart and it should display the TQ/HP. email or pm me the csv log and I can check it out if its still not showing the tooltip.
yeah I like the idea of DynoJet files being able to use it in EvoScan. could add DRM import. send me a sample log.
Just remember to untick the Wind Drag setting when power graphing in EvoScan with the dyno.. because there is no wind resistance in the dyno room
just hover over the actual line on the chart and it should display the TQ/HP. email or pm me the csv log and I can check it out if its still not showing the tooltip.
yeah I like the idea of DynoJet files being able to use it in EvoScan. could add DRM import. send me a sample log.
Another feature i think would be awesome and pretty easy to implement would be a logcfg.txt export for the OpenPort 2.0 customers. Have it use your selected parameters in evoscan and generate the bulk of the logcfg.txt file. I know theres a few tools out there that can do this but it would be nice if it was all in one place.
Hey i am wondering what are the exact hardware I need to monitor all my external parameters not just from the ECU(boost, oil pressure, oil temperature, AFR with innovate LC-1, Air Intake Temperature with ROM patch from mrfred) what all do i need?
I know I need:
- evoscan standalone gps unit
- which datalogging table for 2005 evo viii?
- I would like to log other sensors so i know i need this usb DLP-I08 cable
- wideband connectivity cable? i plan on getting an innovate LC-1. Can't I just connect this to DLP-I08 cable with the 0-5v wire?
- the rest???
I know I need:
- evoscan standalone gps unit
- which datalogging table for 2005 evo viii?
- I would like to log other sensors so i know i need this usb DLP-I08 cable
- wideband connectivity cable? i plan on getting an innovate LC-1. Can't I just connect this to DLP-I08 cable with the 0-5v wire?
- the rest???
You have edited the data.xml and you have doubled up on the WidebandAF rows. just tidy up the data.xml with the items you want to datalog using notepad. I have sent you a PM with my email address so that you can email me your data.xml and I can see where you went wrong. there is a subaru data.xml on the www.evoscan.com/gpsnav website. email me if you need further computer tech support.
Hey i am wondering what are the exact hardware I need to monitor all my external parameters not just from the ECU(boost, oil pressure, oil temperature, AFR with innovate LC-1, Air Intake Temperature with ROM patch from mrfred) what all do i need?
I know I need:
- evoscan standalone gps unit
- which datalogging table for 2005 evo viii?
- I would like to log other sensors so i know i need this usb DLP-I08 cable
- wideband connectivity cable? i plan on getting an innovate LC-1. Can't I just connect this to DLP-I08 cable with the 0-5v wire?
- the rest???
I know I need:
- evoscan standalone gps unit
- which datalogging table for 2005 evo viii?
- I would like to log other sensors so i know i need this usb DLP-I08 cable
- wideband connectivity cable? i plan on getting an innovate LC-1. Can't I just connect this to DLP-I08 cable with the 0-5v wire?
- the rest???
formulas can be found here and calculated here
http://www.evoscan.com/technical-veh...ideband-review
Last edited by johnnnyjeans; May 3, 2012 at 04:31 PM.
v2.9.0021 update released
-Fix when ticking the "Display Selected Items only" option. (before it would cause all sorts of weird errors)
-Clutch slip is now ignored on the virtual dyno graphs. (so you don't get those backwards facing power/torque lines)
-Automatically increases RPM axis range on virtual dyno graphs. (before it would only extend the rpm axis to show rpm till max power. now it will show more rpm axis even if the power is decreasing.)
-Clutch slip is now ignored on the virtual dyno graphs. (so you don't get those backwards facing power/torque lines)
-Automatically increases RPM axis range on virtual dyno graphs. (before it would only extend the rpm axis to show rpm till max power. now it will show more rpm axis even if the power is decreasing.)
EvoScan GPSNav new version released... 1 June 2012 - EvoScanPPC v1.6 Download Here
- Allows the first DTC code of EvoX MUTIII DTC to be displayed. It shows the total count of DTC, but just displays the first DTC.
- Just the exe is updated, replace the EvoScanPPC.exe on your sdcard folder \EvoScanPPC\ with the exe from inside this zip file.
- Allows the first DTC code of EvoX MUTIII DTC to be displayed. It shows the total count of DTC, but just displays the first DTC.
- Just the exe is updated, replace the EvoScanPPC.exe on your sdcard folder \EvoScanPPC\ with the exe from inside this zip file.
5 June 2012 - EvoScanPPC v2.7 Download Here
Now allows gauge display to use the PeakHold Minimum.. The Maximum worked, but the Minimum didn't, this has now been fixed. Great for those G-Force Sensor screens. PeakHold with Minimum set will display as Blue. the PeakHold with Maximum set will display as Red. Just the exe is updated, replace the EvoScanPPC.exe on your sdcard folder \EvoScanPPC\ with the exe from inside this zip file.
Now allows gauge display to use the PeakHold Minimum.. The Maximum worked, but the Minimum didn't, this has now been fixed. Great for those G-Force Sensor screens. PeakHold with Minimum set will display as Blue. the PeakHold with Maximum set will display as Red. Just the exe is updated, replace the EvoScanPPC.exe on your sdcard folder \EvoScanPPC\ with the exe from inside this zip file.
Last edited by evoscan; Jun 4, 2012 at 10:08 AM.
Congratulations on releasing 2.9 Hamish. Some great features included in this version 
I'm having a problem which was reported a couple of pages ago where the values in the load/rpm axis are getting screwed up after I load my ROM in the 'Live Map Tracer' screen (see attached).
As the previous poster said, it all works fine if I copy my ROM into the 'C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo' folder and then select and open it from there inside the 'Live Map Tracer'.
It's as if EvoScan isn't checking all the usual the folders correctly for my xmls or something?
I'm having a problem which was reported a couple of pages ago where the values in the load/rpm axis are getting screwed up after I load my ROM in the 'Live Map Tracer' screen (see attached).
As the previous poster said, it all works fine if I copy my ROM into the 'C:\Program Files\OpenECU\EcuFlash\rommetadata\mitsubishi\evo' folder and then select and open it from there inside the 'Live Map Tracer'.
It's as if EvoScan isn't checking all the usual the folders correctly for my xmls or something?
Romid is 90550701, xml file is called 90550701_MBV7-V1_0.xml, which is just a modified version of the 90550701.xml that Burgers posted up last year I think.
I cleared out everything from the C:\Documents and Settings\Username\My Documents\EvoScan v2.9\ROMS folder, then double checked there were no old/duplicate xmls in the ECUFlash 'rommetadata' folder and now it's working OK
A bit of an odd one...
Out of interest, where does EvoScan get the xml/hex files that go into the \EvoScan v2.9\ROMS folder? I saw after I deleted these files and re-opened EvoScan, that 3 files appeared:
01_LANCER_EVO7-RalliArt_EDM_90550001.hex
90550001.xml
evo7base.xml
I cleared out everything from the C:\Documents and Settings\Username\My Documents\EvoScan v2.9\ROMS folder, then double checked there were no old/duplicate xmls in the ECUFlash 'rommetadata' folder and now it's working OK

A bit of an odd one...

Out of interest, where does EvoScan get the xml/hex files that go into the \EvoScan v2.9\ROMS folder? I saw after I deleted these files and re-opened EvoScan, that 3 files appeared:
01_LANCER_EVO7-RalliArt_EDM_90550001.hex
90550001.xml
evo7base.xml



