EvoScan V.90 Is Ready
He's always promised that registered users get upgrades for free, so I wouldn't get all worked up over the price change.
Keep in mind that 'tomorrow afternoon' to him is late Sunday night for us, so don't expect to see any update emails for awhile.
Keep in mind that 'tomorrow afternoon' to him is late Sunday night for us, so don't expect to see any update emails for awhile.
Originally Posted by C6C6CH3vo
haven't found out the difference from v0.8 to v0.9 yet but it looks the same. Ill run this week when I get the chance
Lets give dude a chance to send the e-mail out...
I went ahead and tried something out and actually worked...Using the link I got for the V 0.8 software I just added a 9 in place of the 8 on the link and got the file to download :-) ...just make sure you have the e-mail you registered with and the key and you will be set...working fine for me...
Right Click, Save as...
http://www.limitless.co.nz/EvoScan/EvoScan%20v0.9.zip
I went ahead and tried something out and actually worked...Using the link I got for the V 0.8 software I just added a 9 in place of the 8 on the link and got the file to download :-) ...just make sure you have the e-mail you registered with and the key and you will be set...working fine for me...
Right Click, Save as...
http://www.limitless.co.nz/EvoScan/EvoScan%20v0.9.zip
Last edited by alan678; Sep 11, 2006 at 12:10 AM.
Originally Posted by Rob W.
I see no mention of Load calc or fixing the timestamp. I'm sure you've all already read this, but from openecu:
"Data Logger Features: EvoScan v0.9
UPDATE:
1) Realtime Graphing support, mulitiple graph support, select data items.
2) Realtime playback of saved csv data log.
(even works without being plugged into the car!)
3) Create / Edit / Save / Load Gauge template xml files.
4) Drag, Drop, and Position any number of gauges onto the screen.
5) Assign data logging item to each gauge
6) Save/Load Gauge screen layouts/gauge config into a shareable xml file.
7) Simultaneous synced WideBand serialport meter Logging Support
- Innovate LM-1 Wideband support. (Tested as Working)
- Innovate LC-1 Wideband support. (Untested)
- AEM Uego wideband support. (Untested)
- Zeitronix Zt-2 Wideband support. (Untested)
Global HotKey Support.
9) Logging status colour indicator.
10) Added logger data items, Speed/Octane/AFRMap/MAP. "
"Data Logger Features: EvoScan v0.9
UPDATE:
1) Realtime Graphing support, mulitiple graph support, select data items.
2) Realtime playback of saved csv data log.
(even works without being plugged into the car!)
3) Create / Edit / Save / Load Gauge template xml files.
4) Drag, Drop, and Position any number of gauges onto the screen.
5) Assign data logging item to each gauge
6) Save/Load Gauge screen layouts/gauge config into a shareable xml file.
7) Simultaneous synced WideBand serialport meter Logging Support
- Innovate LM-1 Wideband support. (Tested as Working)
- Innovate LC-1 Wideband support. (Untested)
- AEM Uego wideband support. (Untested)
- Zeitronix Zt-2 Wideband support. (Untested)
Global HotKey Support.
9) Logging status colour indicator.
10) Added logger data items, Speed/Octane/AFRMap/MAP. "
Does anyone know how exactly this program interfaces with the mentioned widebands (I have zt2)? I'm talking about how it's physically hooked up... What about the EGR?
Last edited by justchil; Sep 11, 2006 at 05:58 AM.
I also noticed the new map colum which is similar to Malibujack's "MDP" (used for the load calc tool) It's slightly different tho...
<DataListItem DataLog="Y" Display="MDP" LogReference="MDP" RequestID="38" Eval="1.25x" Unit="%" />
0.9's
<DataListItem DataLog="Y" Display="MAP" LogReference="MAP" RequestID="38" Eval="1.334x" Unit="KPa" GaugeMin="0" GaugeMax="350" ChartMin="0" ChartMax="350"/>
I'm not really sure how this will effect Evoscan log analyzer...
<DataListItem DataLog="Y" Display="MDP" LogReference="MDP" RequestID="38" Eval="1.25x" Unit="%" />
0.9's
<DataListItem DataLog="Y" Display="MAP" LogReference="MAP" RequestID="38" Eval="1.334x" Unit="KPa" GaugeMin="0" GaugeMax="350" ChartMin="0" ChartMax="350"/>
I'm not really sure how this will effect Evoscan log analyzer...
Last edited by justchil; Sep 11, 2006 at 06:14 AM.
MDP won't affect anything, I don't use that in the log analyzer for anything functional...
There is obviously no functional changes to the software other than updating the XML file and those dashboard widgets which I have no use for. I'd really have liked to see some functional improvements..
Someone should test the CEL code read and reset feature, I can't since I am not near my car today. I have to assume that was fixed..
His MDP settings are correct.. I had forgotten that the value was a KPA value, and I did a rough conversion that I copied off one of the DSM sites.. I used MDP for Manifold Differential Pressure, MAP sensor is also correct..
If you want the analyzer to work right, make sure the timestamp columns have not changed from the old version, and make sure the InjPulseWidth and AFRMAP columns are there, those two have to be there, as long as those two are in there and immediately following eachother (to keep error out due to timing) then it'll be fine.
There is obviously no functional changes to the software other than updating the XML file and those dashboard widgets which I have no use for. I'd really have liked to see some functional improvements..
Someone should test the CEL code read and reset feature, I can't since I am not near my car today. I have to assume that was fixed..
His MDP settings are correct.. I had forgotten that the value was a KPA value, and I did a rough conversion that I copied off one of the DSM sites.. I used MDP for Manifold Differential Pressure, MAP sensor is also correct..
If you want the analyzer to work right, make sure the timestamp columns have not changed from the old version, and make sure the InjPulseWidth and AFRMAP columns are there, those two have to be there, as long as those two are in there and immediately following eachother (to keep error out due to timing) then it'll be fine.
In all honesty, he really should have added the ability to use "Other" values in the log in subsequent calculations.. Its easy to perform a string substitution for the numeric value before doing an eval(x) function.