Evoscan 0.99 Random "USB device not responding"
Thread Starter
Evolved Member
Joined: Aug 2006
Posts: 1,427
Likes: 4
From: Sag-Nasty, MI
Evoscan 0.99 Random "USB device not responding"
Hey guys,
I did a couple searches but can't even find the thread I think I posted about this quite a while ago
My ECUflash works fine, but when starting to datalog with Evoscan, at some random interval of time (usually just when I'm about to hit the gas) all the sudden I hear "link disengaged" and look over and the error pops up "USB device not responding".... in the text box on Evoscan it says something along the lines of "write error init -4", (forgot to save a screenshot)
It was happening last year alot, and I was told to change my settings from the "USB" on the upper left corner to "Com1" and set the timeout delay a little higher, I used to set it to 4000 and doing so did not happen as much.
This is a real pain in the ***, I've missed logging drag runs on race gas because of this timing out at the line...
I'm running version 0.99 with the USB cord to OBDII, logging AFR with AEM on a serial port, and the computer is a Dell laptop running XP
Any new ideas on this?
It seems to be doing it more and more lately, sometimes rebooting the computer would help, but not lately, yesterday I kept hitting retry a ton of times out of sheer frustration, and it started working all the sudden
Can't do that every time!
I did a couple searches but can't even find the thread I think I posted about this quite a while ago
My ECUflash works fine, but when starting to datalog with Evoscan, at some random interval of time (usually just when I'm about to hit the gas) all the sudden I hear "link disengaged" and look over and the error pops up "USB device not responding".... in the text box on Evoscan it says something along the lines of "write error init -4", (forgot to save a screenshot)
It was happening last year alot, and I was told to change my settings from the "USB" on the upper left corner to "Com1" and set the timeout delay a little higher, I used to set it to 4000 and doing so did not happen as much.
This is a real pain in the ***, I've missed logging drag runs on race gas because of this timing out at the line...
I'm running version 0.99 with the USB cord to OBDII, logging AFR with AEM on a serial port, and the computer is a Dell laptop running XP
Any new ideas on this?
It seems to be doing it more and more lately, sometimes rebooting the computer would help, but not lately, yesterday I kept hitting retry a ton of times out of sheer frustration, and it started working all the sudden
Can't do that every time!
