ProScan: comm port issue (in use by this instance)

[ProScan]

I switched to the Uniden driver. I see the same thing as you do with the Microsoft file details and Uniden driver date & version.

I retested 1 to 4 and added test 5. I still can't get it to fail (scanner requiring a power cycle/ USB reinserted). Murphy's law.
I'm going to try later using the SDS200 and USB port.

Test 1. ProScan port set to None then ProScan shutdown then Windows reboot
Test 2. ProScan port set to 5 then ProScan shutdown then Windows reboot
Test 3. ProScan port set to None then Windows reboot
Test 4. ProScan port set to 5 then Windows reboot
Test 5. ProScan port set to 5 then pull the power plug on the computer

 

[ndebaggis]

You're not kidding about Murphy's Law! I also set my power settings to disable "USB Selective Suspend" which I picked up through the years of dealing with old "normal" COM ports disappearing and having to migrate over to the USB to Serial converters to support POS printers. Most of the time when it happens I either do a set port in ProScan or unplug/re-plug the USB cable while ProScan is running then do a set port in ProScan. I almost never have to fully power cycle the scanner itself. I might try uninstalling the ports and drivers then reinstall using the Sentinel drivers and see where that goes.

 

[ProScan]

I did some more testing. I'm still not sure what's going on. I suspect it's more of a scanner issue. Perhaps it's because the internal UART is getting the power from the USB port and not from the scanner.

I started with the Uniden driver
I rebooted the computer with ProScan running and the comm. port opened
The first 30 reboots, the scanner didn't need a power cycle
After 30 reboots, the scanner needed a power cycle
Then I tested with Freescan running and the comm. port opened
I rebooted 2 times and the scanner needed a power cycle
Then I switched to the Microsoft driver
With Freescan running and the comm. port opened
I rebooted 2 times and the scanner needed a power cycle

All using BCD996P2

 

[FrensicPic]

{edit} It should work and this should work too.
DB9 null modem female to female slimline data transfer serial port adapter 2 Pack

Working fine from the rear data port on the 996P2. So far, none of the issues I described above.
Thanks.

 

[ih784]

I have this issue as well. SDS100, USB to serial converter. Bob, when Proscan detects that its process is being terminated is Proscan issuing a close COM port command to the scanner? I'm wondering if the COM is left in the open state during process termination during a PC reboot while Proscan is running...

Good afternoon, I’m receiving “in use by this instance” also on an SDS100. I hope to find a solution because ProScan is running on a headless/remote device. As it stands, when I restart the computer I need to re-select the port as well. Which requires a monitor, keyboard and mouse lol. I’ll buy any adapter that fixes it.

 

[ProScan]

Good afternoon, I’m receiving “in use by this instance” also on an SDS100. I hope to find a solution because ProScan is running on a headless/remote device. As it stands, when I restart the computer I need to re-select the port as well. Which requires a monitor, keyboard and mouse lol. I’ll buy any adapter that fixes it.

You shouldn't have to reselect the port # when the computer reboots unless the port # changes. It's advisable to power cycle the scanner after the computer reboots. Regarding the “in use by this instance” message, do this 1) Set the Port to None 2) Click the Set button 3) Try the Auto Detect button again.

 

[ih784]

I do have to power cycle the scanner. But, I still have to access the computer that’s rdp to select or refresh the port to clear the “in use by this instance” message and then the sds100 becomes visible in that port again. I guess I don’t have to reselect the port I just do because I attempt to go between “none” and “port 3” where the scanner is plugged in at.