¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Re: COM port oddity with Commander.


 

Sounds like a USB initialization error.

The error is generated when attempting to start Commander (through
the launcher) after a reboot, nothing else has been run manually.
Are you doing a power down reboot or simply a "Restart"?

Is the TS-590S powered on before starting/rebooting Windows or
is the TS-590S off when Windows is rebooted?

Are sleep/hibernation enabled in Windows? Is "Fast Boot" enabled?
(Hint: disable sleep, hibernate and fast boot).

73,

... Joe, W4TV

On 2025-05-07 6:09 AM, Tim Sweeney via groups.io wrote:
Sorry for the missing details. That's what I get for posting just before going to bed!
The rig generating the port is a TS-590S. The device it generates is listed as "Silicon Labs CP210x USB to UART Bridge".
The error is generated when attempting to start Commander (through the launcher) after a reboot, nothing else has been run manually. I can't find anything in Startup Apps that is serial related. I tried to find a process grabbing the port with Process Explorer, but nothing shows up. If I go through the uninstall/reboot/reinstall procedure, and Commander opens the port successfully, Process Explorer shows it. Is there another way to see what might be reserving the port when Commander can't open it?
Thanks!

Join [email protected] to automatically receive all group messages.