EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
Only if you are logging calculated load, if you are logging 2byte load, it doesn't matter.
Evolved Member
Joined: Oct 2002
Posts: 2,788
Likes: 1
feature request: when you look at a graph and you hoover your mouse over a point in the graph it shows you the values at that current point. I would like to be able to do the same thing by dragging a line through the graph, or clicking on the graph and having that little box stay in place (like how logworks or aem logger does it). It would make it much easier to analyze the data.
Tried using v2.6b11 according to the instructions on page 1. I only register 2 samples per second at most, and usually I get one sample every 3 seconds. This is on an Evo 9 using an OpenPort 2.0 cable.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
you must be doing something wrong, most people get >100 samples per second. Ensure you don't have any graphs open, and you don't have any gauges open, and you can check your settings in the logger menu, and you can check what items you have checked.
Evolving Member
Joined: May 2007
Posts: 208
Likes: 0
From: Europe
I noticed that in device manager (on laptop which has low sampling), I can find unidentified comm port, which can't be uninstalled
Anyway OP 2.0 has worse compatibility comparing with OP 1.3, but I guess, it has to be this way, as OP 2.0 is more complex device
Last edited by dolphin888; Apr 30, 2009 at 01:58 PM.
- TPS
- RPM
- KnockSum
- InjPulseWidth
- TimingAdvance
- O2Sensor
- Battery
- AFRMAP
I never use the graphs or gauges. All settings have been verified. I bought this laptop exclusively for tuning / datalogging based on based on reviews (Asus EeePC with a 900 MHz Intel Celeron processor and 2 GB of RAM. I never could get EvoScan 2.5 to work with this computer using the OpenPort 1.3U cable. Flashing works great with both cables on this laptop.
I'm guessing I'll be told in the near future that I need to buy a different laptop.
I'm only logging:
- TPS
- RPM
- KnockSum
- InjPulseWidth
- TimingAdvance
- O2Sensor
- Battery
- AFRMAP
I never use the graphs or gauges. All settings have been verified. I bought this laptop exclusively for tuning / datalogging based on based on reviews (Asus EeePC with a 900 MHz Intel Celeron processor and 2 GB of RAM. I never could get EvoScan 2.5 to work with this computer using the OpenPort 1.3U cable. Flashing works great with both cables on this laptop.
I'm guessing I'll be told in the near future that I need to buy a different laptop.
- TPS
- RPM
- KnockSum
- InjPulseWidth
- TimingAdvance
- O2Sensor
- Battery
- AFRMAP
I never use the graphs or gauges. All settings have been verified. I bought this laptop exclusively for tuning / datalogging based on based on reviews (Asus EeePC with a 900 MHz Intel Celeron processor and 2 GB of RAM. I never could get EvoScan 2.5 to work with this computer using the OpenPort 1.3U cable. Flashing works great with both cables on this laptop.
I'm guessing I'll be told in the near future that I need to buy a different laptop.
I've logged with my EeePC and 1.3 cable (I use it for logging at the track) and get great sample rate:
It would be interesting to see more people's results from logging a 8/9 with a OP 2.0 cable.
just like every winter i go into hibernation. lol so i got to catch up with this stuff.
is there any bugs or issues with the ecuflash 1.41 or evoscan 2.6??? i want to down load the latest versions that are bug free or hassle free. right now i have 1.29 and evoscan 2.0
is there any bugs or issues with the ecuflash 1.41 or evoscan 2.6??? i want to down load the latest versions that are bug free or hassle free. right now i have 1.29 and evoscan 2.0
