another WB issue w/ evoscan, not the "norm"
another WB issue w/ evoscan, not the "norm"
Ok, so I had to restore my comp. yata yata yata, installed ecuflash/evoscan, installed the driver for the WB serial - USB cable...
So I go to WB COM set up in evoscan, and ONLY (COM3) is available. Well, when I installed the driver, it showed that the it was using (COM5). So I go outside to the car, plug in the WB, and check the COM in evoscan again, and (COM5) is there, but not checked... I check it, go out for a log, and works fine...
Heres where my issue lies...
So I unplug the cables, go upstairs to review the log, go back out, and the WB is NOT logging! Reading "0". I open up evoscan, again, and theres no (COM5) again! I plug in the cable, again, and its showing that its on (COM5)
So in a nutshell, it seems like Im gonna have to open up the COM port section, and make sure Im on the correct COM port, before I go out logging... Every Time I unplug the WB!!!
Any ideas, on whats happening??? What A PITA!
TIA
So I go to WB COM set up in evoscan, and ONLY (COM3) is available. Well, when I installed the driver, it showed that the it was using (COM5). So I go outside to the car, plug in the WB, and check the COM in evoscan again, and (COM5) is there, but not checked... I check it, go out for a log, and works fine...
Heres where my issue lies...
So I unplug the cables, go upstairs to review the log, go back out, and the WB is NOT logging! Reading "0". I open up evoscan, again, and theres no (COM5) again! I plug in the cable, again, and its showing that its on (COM5)
So in a nutshell, it seems like Im gonna have to open up the COM port section, and make sure Im on the correct COM port, before I go out logging... Every Time I unplug the WB!!!

Any ideas, on whats happening??? What A PITA!
TIA
But, I have ALWAYS used the same com ports. For the tactrix and the WB...
Its weird, cause when the USB is connected to the laptop, it shows that COM5 is checked (3,4, and 5 are available), but when I disconnect, COM5 isnt even showing. Only COM3 shows available, but not checked...
You can also try to go to Windows device manager and go to properties for serial port and select a specific port number as that helps it "stick" a lot of times as well.
Select port settings tab then advanced within device manager when port is selected and device plugged in and active.
odd and even port numbers can share resources so ideally WB port and Tactrix are odd and even or vice versa.
I have come to accept that port enumeration will jump and typically Evoscan will throw an error with WB port incorrectly selected at which point i use the shortcut to device manager to see which port it has moved to.
Select port settings tab then advanced within device manager when port is selected and device plugged in and active.
odd and even port numbers can share resources so ideally WB port and Tactrix are odd and even or vice versa.
I have come to accept that port enumeration will jump and typically Evoscan will throw an error with WB port incorrectly selected at which point i use the shortcut to device manager to see which port it has moved to.
You can also try to go to Windows device manager and go to properties for serial port and select a specific port number as that helps it "stick" a lot of times as well.
Select port settings tab then advanced within device manager when port is selected and device plugged in and active.
odd and even port numbers can share resources so ideally WB port and Tactrix are odd and even or vice versa.
I have come to accept that port enumeration will jump and typically Evoscan will throw an error with WB port incorrectly selected at which point i use the shortcut to device manager to see which port it has moved to.
Select port settings tab then advanced within device manager when port is selected and device plugged in and active.
odd and even port numbers can share resources so ideally WB port and Tactrix are odd and even or vice versa.
I have come to accept that port enumeration will jump and typically Evoscan will throw an error with WB port incorrectly selected at which point i use the shortcut to device manager to see which port it has moved to.
Another thing to note, is that it does NOT disconnect (telling me that theres a WB issue) it just logs "0"...
As always, Thanks for the insight! I really appreciate it!
Post up the SS l8r...
Trending Topics
So checked the COM port in the device manager, and its on 5...
Did a quick test of logging afr @ idle, and seems to be finding it now... 3 for 3. It still only shows COM3 available when the cable isnt in tho... weirdThanks, once again!
Edit: operating system is vista. Its a Toshiba Satelite series A215-S7422 and not sure if Im an administrator to the machine/os...
Last edited by nonschlont; Feb 5, 2010 at 11:06 PM.
AHH Vista I would go into device manager with cable plugged in and ign. on and maybe change your com5 to a com3 and that will help it stick even more. Now that you know to be plugged in it should stay at com5 as long as you don;t swap USB cable locations on your laptop like Fost said always use the same plug in locations.
LOL I have used like 5 different laptops over the years so I guess I had to try lots o "stuff"
Good Luck bro and happy tuning/logging
LOL I have used like 5 different laptops over the years so I guess I had to try lots o "stuff"
Good Luck bro and happy tuning/logging
Thread
Thread Starter
Forum
Replies
Last Post
mrm95
General Engine Management / Tuning Forum
11
Sep 7, 2015 06:40 PM




