I'm getting many more timeouts with EvoScan 2.0 when attempting to start a logging session. Is anyone else having this issue as well?

 

I had the problem, that ES2.0 shows more knocksum (on older logs) than the XML said. Old Evoscan showed real knocksum.

 

I was/am. Contacted Hamish about it.

He said there are newer FTDI drivers included in the install.

Default location: C:\Program Files\EvoScan\EvoScan v2.0 Map Tracer Edition\USB Drivers\x86

I ran DPInst.exe and it loaded the new drivers. Haven't had a chance to test it out yet.

 

not sure why there would be more timeouts.. only that its supposedly using the faster .net2.0 microsoft framework.

Knocksum shouldn't have changed, what do you mean by older logs, and what are you referring to about the xml?

the ftdi drivers wont make any difference, fundamentally they should still be the same.

 

For example: Evoscan 2.0 shows me in my log from august (logged with evoscan 0.99) a knocksum about "9" counts. With Evoscan 0.99 the same log shows me a max. knocksum of "2" counts at the same part. In the logged data (csv) - opened with excel the knocksum is at this part about 2 counts - like evoscan 0.99...

 

I was rarely getting timeouts with v0.99, but with 2.0, every other attempt to log was giving me a timeout. I only did three successful logs, so maybe it was just a statistical aberation.

BTW, the message box telling me that EvoScan couldn't connect is a PITA. While I'm driving the car, I have to move my mouse down to the box to hit the "ok" button, and then move it back to the start/start stop button. It pretty much makes it impossible to do a run if I'm starting the log just before I need to go WOT.

 

Can you not just hit "Enter" to clear the box and then use the CTRL+Space shortcut to start the log?

 

I could not get a single log done with v2.0 yesterday because as soon as I started to log it would time out and within 15 seconds it had reconnected and disconnected 10 times.

 

Im too lazy to go to the site and look, but how much is it to get the updated version?

And I guess if everybody is having connection problems than it really isnt worth the map tracer function.

On a side note, MRFRED any updates on jdm 3bar sensors?

 

FWIW, I couldn't get it to connect at all yesterday.

Installed the updated drivers as mentioned above..... still no luck.

Then it struck me: I did the buad rate mod

I'd gotten use to the auto retry/baud rate "feature" of the v1.0 alpha.....

Corrected the baud rate in evoscan..... fired right up.

 

I couldn't update the new drivers. System says me - my language are not supported (german) and break down the installation.

 

I just tried it. Worked perfectly for me - aside from not being able to log my wideband.

 

Thats really odd. I am seeing a place to select the com port. Try reinstalling it. Its worth a shot

 

What wideband do you have? I downloaded 2.0 yesterday but have not installed it yet.

 

Dudical, did you plug your wideband in to the computer and try to select com port? I was only getting com 3 as well. Then I plugged everything in to the laptop. More comm selections appeared.

I'm getting a couple of time outs on start of logs as well.