derbynet
derbynet copied to clipboard
jeffpiazza
Windows 11 Serial Adapter Issues
Using Windows 11 and Chrome...with UBS-Serial adapter.
Yesterday I had no problem connecting to the K1 timer using either the software timer or the DerbyTimer.jar option.
Today, I cannot connect using either option. Both options recognize the COM port but fail to connect with the timer. The timer connects to the starter. The computer recognizes the UBS port.
Derby-timer.jar shows the COM port in red and has a message at the bottom that states "(Pausing between scans)". Above that, it says "Resume Scanning" in gray text but there is no way to click that language. It will connect to localhost but not the timer.
The DerbyNet software timer let's me approve use of the COM port but never identifies the timer.
Both options were working fine yesterday - so what am I missing?
I've tried uninstalling and reinstalling DerbyNet and Java. I renamed the COM port. I tried different USB ports on the computer. I reset the COM port to 0 value using regedit. Multiple restarts - and yes, unplugged then plugged the cables back in a dozen times.
Here is a timer log:
+14:04:24.410I Started at 2022-01-29_14:04:24 +14:04:24.413I derby-timer.jar version dev-1359-20211018 +14:04:24.413I os.name = Windows 11 +14:04:25.132S INT openPort fails for COM3: Port busy +14:04:26.820S INT openPort fails for COM3: Port busy +14:04:26.878S INT openPort fails for COM3: Port busy +14:04:27.582S INT openPort fails for COM3: Port busy
Thank you in advance.
"Port busy" implies that some other process has possession of the resource.
Any chance you're running the in-browser interface and the java interface at the same time? I probably should have put some sort of safeguard against that, but it didn't occur to me earlier.
Anything is possible – I am far from a computer genius.
How would I stop one or the other? I’ve restarted the computer and tried resetting the port by resetting the values in regedit. I deleted the DerbyNet files and reinstalled it from a new download of the zip file and the same issue remains.
Either way, no matter which time I start with it is not to be able to communicate with the timer. I ran both successfully just the past 2 days in testing.
Bryan
From: Jeff Piazza @.> Sent: Saturday, January 29, 2022 4:21 PM To: jeffpiazza/derbynet @.> Cc: D. Bryan Willis @.>; Author @.> Subject: Re: [jeffpiazza/derbynet] Computer Not Connecting to Timer (Issue #180)
"Port busy" implies that some other process has possession of the resource.
Any chance you're running the in-browser interface and the java interface at the same time? I probably should have put some sort of safeguard against that, but it didn't occur to me earlier.
— Reply to this email directly, view it on GitHubhttps://github.com/jeffpiazza/derbynet/issues/180#issuecomment-1024997392, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXQZJYAQYATTKFSDETGWFYTUYRR37ANCNFSM5NDMVOXA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
Try restarting the browser (even for derby-timer.jar), and if that doesn't work, try a reboot?
Sorry, I missed the part where you said you'd already tried those things.
Try downloading https://jeffpiazza.org/download/etxdbw/derby-timer.jar, which is the version from about a week ago. If you're able to connect with that jar but not the more current one, that would be reason to suspect recent changes being the culprit. (That would be surprising, but still.)
No worries.
I found a couple of hidden instances of the UBS-Serial Port in the device manager on 2 separate COM ports. Seems that might be a cause for the port busy issue. I've deleted those but won't have a chance to check if that is the fix until tomorrow.
I appreciate the quick responses today.
Ran into this same issue tonight. We had to postpone our derby unfortunately, nobody could figure it out. Might be related to W11 updates but definitely let me know if someone figures out what's going on.
+20:18:00.688I 2022-02-07_20:18:00 +20:18:06.352S INT openPort fails for COM5: Port busy +20:18:16.362S INT openPort fails for COM5: Port busy +20:18:26.363S INT openPort fails for COM5: Port busy +20:18:36.372S INT openPort fails for COM5: Port busy +20:18:46.396S INT openPort fails for COM5: Port busy +20:18:56.404S INT openPort fails for COM5: Port busy
We were able to resolve the issue by going into Device Manager then uninstalling the hardware and driver for the serial to USB port. We then did a fresh install of the driver and were able to get both the DerbyNet timer and the Derby-timer.jar to connect with the timer.
From: acespacepilot @.> Sent: Monday, February 7, 2022 7:22 PM To: jeffpiazza/derbynet @.> Cc: D. Bryan Willis @.>; Author @.> Subject: Re: [jeffpiazza/derbynet] Computer Not Connecting to Timer (Issue #180)
Ran into this same issue tonight. We had to postpone our derby unfortunately, nobody could figure it out. Might be related to W11 updates but definitely let me know if someone figures out what's going on.
+20:18:00.688I 2022-02-07_20:18:00 +20:18:06.352S INT openPort fails for COM5: Port busy +20:18:16.362S INT openPort fails for COM5: Port busy +20:18:26.363S INT openPort fails for COM5: Port busy +20:18:36.372S INT openPort fails for COM5: Port busy +20:18:46.396S INT openPort fails for COM5: Port busy +20:18:56.404S INT openPort fails for COM5: Port busy
— Reply to this email directly, view it on GitHubhttps://github.com/jeffpiazza/derbynet/issues/180#issuecomment-1032114452, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AXQZJYC5GYKN7X75C6BX5LLU2BV4LANCNFSM5NDMVOXA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.***>
@acespacepilot, any chance there were two browser windows running the timer interface, or a browser and derby-timer.jar simultaneously?
What browser were you using?
Are you able to look at the javascript console if this occurs again? I don't know what we might find there, just hoping it could provide some clue.
(Are you saying this issue required postponing your derby? I'm so sorry if that's the case. Maybe have a downloaded derby-timer.jar available as a backup when trying again.
We were using the derby-timer.jar interface as our primary communication means. It seems that this was in fact related to a Windows 11 update. After a bunch of digging and research, I followed instructions here to finally resolve: http://somedisassemblyrequired.com/index.php/2022/01/14/please-install-corresponding-pl2303-driver-to-support-windows-11-and-further-os/
Sounds similar to what @etxdbw did with uninstalling and reinstalling serial port drivers. This unfortunately did require postponing our derby since we spent over an hour and a half troubleshooting and couldn't keep the kids waiting any more. Didn't get to the solution for another hour. Next time, I think we'll keep a Linux or Windows 10 box on hand to run the derby-timer.jar and act as the interface to the gate. We had tried doing that tonight with an extra W10 box but couldn't get it to connect to our local host server (kept getting strange errors in the derby-timer.jar when trying to input the numeric IP address of our host server, it's possible we had some kind of block/firewall on the machine or issue with the network).