EvoScan v2.6 And New EvoScan GPS/Logger/Reflashing Touchscreen Review
That's my biggest gripe with Evoscan 2.5 and Vista...sometimes as soon as I go WOT to log a pull..it stops datalogging..anybody have a reason/solution to this?
I'm having an issue logging in an EVO 8 with the 2.0 cable while using windows XP. I get logs maybe every 7 seconds. I only ticked the necessary tabs in order to properly tune such as rpm, timing, and knock sum (+ whatever evoscan needs to be on to run them), and I have logger super speed enabled with realtime data logging graph disabled. I also tried a 62500 baudrate and I'm seeing no difference.
Now with the 1.3 cable, there is absolutely NO problems logging the EVO 8. I still haven't had a chance to log an EVO X with the 2.0 cable. I should be able to get one tomorrow.
By the way: is there anything that can be done about the slow logging speed of Stiscan?
UPDATE:
OK, I tried to log in an EVO X MR and I'm still having the same problem, under the same conditions but using 500000 baudrate. It only gives me a log once every second. Is there anything else I could do to make this work?
Also, a have a 1.8Ghz processor and 1.5GB of RAM, and I'm noticing the performance graph is in the upper 90% area when using the 2.0 cable.
Now with the 1.3 cable, there is absolutely NO problems logging the EVO 8. I still haven't had a chance to log an EVO X with the 2.0 cable. I should be able to get one tomorrow.
By the way: is there anything that can be done about the slow logging speed of Stiscan?
UPDATE:
OK, I tried to log in an EVO X MR and I'm still having the same problem, under the same conditions but using 500000 baudrate. It only gives me a log once every second. Is there anything else I could do to make this work?
Also, a have a 1.8Ghz processor and 1.5GB of RAM, and I'm noticing the performance graph is in the upper 90% area when using the 2.0 cable.
Thread Starter
Former Sponsor
iTrader: (4)
Joined: Dec 2003
Posts: 723
Likes: 1
From: TGA, New Zealand
ok thanks for the feedback on the EvoX and the Beta11, I'll work to increase the logging speed. But CAN protocol logging is always going to be slower than Evo7/8/9 MUTIII logging due to the design by the car manufacturers.
I'm having the same issue as above, a sample every couple seconds, or only about 5-6 samples during a 3rd gear pull.
PCMscan has a full rich log during a 3rd gear pull. Same laptop, same car, same 2.0 cable.
Evoscan 2.5 works perfect with 1.3 cable logging Evo 8/9. Same laptop.
Do you know why some of us are having really bad logging (as in useless) and some are getting ok sampling (as in slow but still somewhat useful)?
You omitted the fact that you were having problems with the evo 10, which is a completely different infrastructure. Travis then provided his input on both XP and Vista machines utilizing numerous evoscan versions. Lets put it to you this way, people like travman have been using evoscan since it was beta, not even a release version back in v0.99 days. His input and experience with the stock ecu and associated software is valuable. Your temper tantrums of the day however, do nothing to help people out, especially when you omit the specifics on your problem.
danl, once again useless babble is all you have to input. It's been a few pages since all that was cleared up. Nice quote in your signature though........it's nice to be looked up to. Want to race your stock ECU car against mine? WPOS.
I'm not going to argue with you. I made a good point and that is that. You don't need to mock people, especially those trying to help you.
p.s.
I've been going faster than your current 127mph since 2006 in a stock ecu. Actually make that fall 2005. That was without the need of a built motor or cams.
p.s.
I've been going faster than your current 127mph since 2006 in a stock ecu. Actually make that fall 2005. That was without the need of a built motor or cams.
Last edited by dan l; May 13, 2009 at 05:33 PM.
Consider this....since my statement about having problems there are about 3 pages of other problems being brought up. Also keep in mind that my EVOX ECU spent over 2 months with Hamish so he could bring a logger to the community.
I'm ready for the race anytime. Next weekend should work out great, BR Sport Compact Nationals.
I'm ready for the race anytime. Next weekend should work out great, BR Sport Compact Nationals.
Evolved Member
Joined: Apr 2009
Posts: 536
Likes: 0
From: US
Currently the logging in PCMscan is leaps and bounds faster than EvoScan on my current laptop on a Evo 10.
I'm having the same issue as above, a sample every couple seconds, or only about 5-6 samples during a 3rd gear pull.
PCMscan has a full rich log during a 3rd gear pull. Same laptop, same car, same 2.0 cable.
Evoscan 2.5 works perfect with 1.3 cable logging Evo 8/9. Same laptop.
Do you know why some of us are having really bad logging (as in useless) and some are getting ok sampling (as in slow but still somewhat useful)?
I'm having the same issue as above, a sample every couple seconds, or only about 5-6 samples during a 3rd gear pull.
PCMscan has a full rich log during a 3rd gear pull. Same laptop, same car, same 2.0 cable.
Evoscan 2.5 works perfect with 1.3 cable logging Evo 8/9. Same laptop.
Do you know why some of us are having really bad logging (as in useless) and some are getting ok sampling (as in slow but still somewhat useful)?
I was getting super slow logging at first on the EVO X, but I'm not sure what I changed to now get 60+ samples a second. I do know that I have "Disable multithreading" checked. I did that since I only have a single-core processor in my laptop. Maybe try that and see if it helps?
