no reason why the 2.0 cable wont do any DTC code action?

 

did last night

thanks

 

I did another log and noticed something odd. In the beginning of the log, I am sampling about 15-17 samples per second. As the log goes on, it slows down to 4-5 samples per second- max. Any ideas on this?

 

can only think of CPU.

dunno maybe a vista thing?

can you use a inverter to power the laptop in the car as a test?

 

Have you tried enabling/disabling multithreading?

 

How do you disable/enable multithreading? I don't have a power inverter for the car. maybe I should invest.

Edit: found the options for disabling multithreading. I'll give it a try tomorrow.

 

Check the "logging" menu. There is all kinds of fun speed related stuff in there.

 

What is multithreading?

 

I figured out what it is! Whenever I open the real time logging graph while logging, it slows it down. When the graph isn't open while logging- it's super fast.

 

 

Anyone else having problems accessing evoscan site this evening? We push it over bandwidth limits?

 

I cant download either.

 

access denied was a problem with my Web Hoster company, they have fixed their lame as server up.

 

I am going to shift web hosting to the United States, this isn't the first time my web hoster has screwed up their server.

 

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.