Its been working fine until today. It will log on and off real fast and will not log anything. I can use v97 with no problems. Any ideas on what i should do?

 

anyone?

 

bump

 

Is your wideband controller set to the correct COM port?

 

com port 1, which is what it was when it working a couple days ago.

 

I would suggest checking the COM port by looking at the Windows device manager. COM ports are assigned in the order that the system sees the device, so if you switched the USB ports for the wideband and tactrix cable, or perhaps plugged them in in a different order, you might get a different COM port assigned.

I'm just bringing this up because it's usually the cause when mine won't log. The port assigned for my wideband jumps between 1, 5 and 6.

 

I tried again tonight with no luck. Com port was 1 for wideband. Even closed the session out and retried with wideband disconnected from the serial port. Still would connect/disconnect simultaneously. After doing some logs using v.97 and having no problems but could not log wideband with i tried v.99 again. I clicked on debug file for wideband and my baudrate went to 19200 and the engine rpm raised to about 3600 and engine had a skip. I closed it out and cut the engine off and restarted her and she ran fine. Anything i should do now?

 

ttt

 

ttt?

 

com port 1 error? my friend had the same issue on his laptop. he had a hardware com port 1 and evoscan was trying to access this as the wideband and nothing was there to access (the tactrix cable can act as a com port so be wary of it becoming com 1). our fix was to select com 3 (anything but com 1) in evoscan for the wideband and it worked (because com 3 does not exist in hardware). can you change the com port of your wideband to something else? try different combinations.