Im trying to run evoscan on my car but it keeps saying it connects then it says it cant open comport 1 and shuts itself of anyone know what it might be?

 

Your cable is plugged into a comport? I think not.

 

I remember having that problem, It was something about the driver I had to update.

 

Wrong, he's not plugged into a "comport".

 

Yep, my friend had this issue on his laptop, it was dealing with the wideband o2 in the menu configured for com 1 and he actually had a com 1 hardware device... so evoscan tried to open com 1 which nothing is connected to. we just changed it to com 3 ( which didnt exist hardware) and it worked fine. give that a try and let us know!

 

thanks ill try it tomm and see if it helps thanks

 

Got this problem myself. Does anyone know the driver update you need? I know it's some windows 1.1 something update, just don't remember which one it was.

 

I got a different problem when trying to use evoscan and log the data. As soon as I start the car, the 3 ACD LED blink and ABS indicator blink as well. I could datalog the data without the car moving.

My question is it safe to drive around in datalogging mode while the ACD light and ABS blinking? I'd been told the ACD/ABS feature is disabled when they are blinking. I had not flash my ecu with ECUFlash (yet).

 

There is no physical COM port on a computer. COM ports are I/O pathways assigned by the OS and can be changed. I assume that the COM1 and COM2 selections are for cables with a serial (DB9) connection and the 3rd automatically searches for the USB cable on several COM ports. The COM port assigned to a USB device will change based on the order in which the devices are recognized by the OS.

Ok, with that out of the way ... It sounds like a driver issue to me. To troubleshoot, first make sure that a COM port is assigned for the device. To do that, right click My Computer and select properties. Under the Hardware tab, select Device Manager. There should be a category there marked as COM ports (or something similar. Sorry, can't run out to the car and check right now). You Tactrix cable should show up in this list if it is plugged in and installed correctly.

If it isn't showing up, try going through the uninstall process for ECUFlash and then delete the remaining directory after the uninstall completes. Re-install and see if it helps. If not, try to find another computer to test and see if it's recognized there. If not, it could be a cable issue and you might need to contact your cable vendor.

Hope this helps and good luck.

 

Check the pull-down menu labeled "Select ECU." "EFI" should be selected there. I'm not sure where else to go with that one. Good Luck!

 

Just select "USB Cable FTDI FT232" and be done with it.

 

I have this same issue and was able to log at idle. I was able to pull my map with ECUFlash but i'm worried if I should do anything with even logging the car. I renamed the CSV to .txt.

 

Just so everyone knows I got my answer back from limitless as to the issue with the blinking acd.

"That is normal for mitsubishi diagnostic mode.. on your vehicle you can cut pin1 wire on the obdII plug and the lights will no longer flash."

 

Also when logging with that cable anything above I believe 10MPH and 1500RPMs will stop the blinking lights. This may be a good sticky as this information is not shown when searching.