evoscan v2.7 AEM error: port closed
Thread Starter
Evolving Member
iTrader: (2)
Joined: Mar 2010
Posts: 107
Likes: 0
From: I...O...W...A...
evoscan v2.7 AEM error: port closed
I wired up my AEM WB cable (blue wire to pin 2) (black wire to pin 5) on DB9 rs232 Female connector. I turned on my evoscan and ticked External WB. I also selected AEM WB on the drop down, Switched the Serial Port cable to USB from COM port 9 to COM port 3, and selected COM port 3 on the drop down menu as well in Evoscan. When starting the logger it says in the bottom left hand feedback area: AEM error: the port is closed, and reads 0 at all times.
Anyone have this issue? I googled this and searched on here couldn't find any helpful information.
Thanks in advance
Anyone have this issue? I googled this and searched on here couldn't find any helpful information.
Thanks in advance
Evolved Member
iTrader: (33)
Joined: Jul 2002
Posts: 5,313
Likes: 1
From: Raleigh, Transplanted from Toronto, Canada
Yeah my inital comport was COM25......WTF. My tactrix was on com 9 but com's 3-24 are being used. I switched the tactrix to COM2 and the USB adpater to COM9. Still no workie.
I un-installed and re-installed it from prolific's website (This is a Dynex USB to serial adapter). I'm on Windows 7 Professional 64bit.
Hopefully this helps anyone that has this issue and is searching for answers on the site.
I un-installed and re-installed it from prolific's website (This is a Dynex USB to serial adapter). I'm on Windows 7 Professional 64bit.
Hopefully this helps anyone that has this issue and is searching for answers on the site.
I fixed the problem. Im using Windows 7 64bit and using the Dynet usb to serial cable from Best Buy btw. I uninstalled the existing driver. I then copied the driver from the CD onto the desk top, right click on the setup program, and ran it with Windows XP compatibility mode. Then I restarted the computer and pluged in the usb-serial cable. I then went to the device manager under ports, selected the cable, clicked on advanced settings, and unclicked the box that says “Use FIFO Buffers” Im not sure what that that means, but it seemed to work.
I was getting the same error on v2.9 using the Gigaware Serial=>USB converter on Win7 64bit. HyperTerminal was reading fine but no-go on Evoscan.
I tried many different settings, but ^THIS was ultimately what I needed. Thanks for posting your solution, now I can tune!
I then went to the device manager under ports, selected the cable, clicked on advanced settings, and unclicked the box that says “Use FIFO Buffers” Im not sure what that that means, but it seemed to work.
Thread
Thread Starter
Forum
Replies
Last Post
darkmitsu
Lancer Engine Management / Tuning Forums
141
Dec 31, 2022 05:41 AM
needsboost
General Engine Management / Tuning Forum
3
Jul 11, 2013 11:09 AM




