开云体育

COM port oddity with Commander.

Tim Sweeney All Messages By This Member #229126 I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. ? Edition ? ?Windows 11 Pro Version ? ?23H2 Installed on ? ??11/?19/?2022 OS build ? ?22631.5189 Experience ? ?Windows Feature Experience Pack 1000.22700.1077.0 ? Commander ver 16.1.0 ? Anyone had this variation of the error crop up? Thanks! ?
Dave AA6YQ All Messages By This Member #229127 + AA6YQ comments below I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. + Commander is attempting to open the specified COM port. Windows is responding with " Invalid Port Number (8002)", which Commander then reports to you. The error message means that either the specified COM port does not exist, or it has already been opened by another application. + What make and model device is responsible for creating the COM port? + Which other applications are running at the time the error is reported? 73, Dave, AA6YQ
Tim Sweeney All Messages By This Member #229129 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! ?
Joe Subich, W4TV All Messages By This Member #229131 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!
Tim Sweeney All Messages By This Member #229132 Hi Joe, you're on to something, I think. ? But to answer the questions, fastboot and hibernation are disabled (always), sleep is enabled but only manually triggered,? and I had tried both cold boot and restart with the same result, as well as both radio on and radio off when booting. ? But I overlooked the fact that even when the radio is "off", it's still really "on" internally, and the USB port is powered up as long as there is 12V to the rig. So I found unplugging the USB, rebooting, and re-plugging it clears the problem in the same way as uninstalling, rebooting and allowing the system to reinstall the device clears it. There's something about the combination of the device being fully detached (or uninstalled) and a reboot that resets things in a way that physical detachment or reboot separately do not. ? This is a new problem, as I've been running this same stuff for years now with no issue. The only things that have changed are newer versions of Win 11 and DXLab. Since DXLab doesn't have a say in the matter, perhaps it was a Win 11 update that changed the game. The USB driver involved is from 2019, so I doubt that changed.? ? Just to fill in as many data points as possible: putting the machine to sleep doesn't change the state of things once it's awakened. If it was talking to the rig when put to sleep, it will still talk to it when awakened.? ? Thanks!
Matthias Zwoch All Messages By This Member #229133 Am 07.05.2025 um 05:52 schrieb Tim Sweeney via groups.io: I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. Edition ? ?Windows 11 Pro Version ? ?23H2 Installed on ? ??11/?19/?2022 OS build ? ?22631.5189 Experience ? ?Windows Feature Experience Pack 1000.22700.1077.0 Commander ver 16.1.0 Anyone had this variation of the error crop up? Thanks! I had and have similar problems with Win11 24H2. When I start Arduino Development Tool it gets port 4 for the communication with the ESP32 processor to program. But port 4 is already assigned to my second trx FT-DX10 and DXLab. So I have to unplug the FT-DX10 when I want to flash a prcessor and vice versa I cannot run Arduino when the FT-DX10 is in use. There are many free port numbers which could be used. But until yet I found no way to change that odd behaviour in the Win11 port assignment. 73 Matthias, DD7NT
Tim Sweeney All Messages By This Member #229134 HI Matthias - What happens if you plug in one device, say the rig, and then go into Device Manager and change the COM port number in the Advanced Settings for that port? It should retain that change across assignments, I think.? ? In my case it's not a port conflict or changing assignments that's at issue. Just a consistently assigned port that is inconsistent in its functioning!? ? 73, K1BR ?
Joe Subich, W4TV All Messages By This Member #229135 On 2025-05-07 11:13 AM, Tim Sweeney via groups.io wrote: There's something about the combination of the device being fully detached (or uninstalled) and a reboot that resets things in a way that physical detachment or reboot separately do not. Try Device Manager -> Ports (COM & LPT) ... open the serial port for your TS-590 -> Advanced Settings and check the Miscellaneous Settings. I would start with "Serial Enumerator" checked and all the other options not checked. This is a new problem, as I've been running this same stuff for years now with no issue. The only things that have changed are newer versions of Win 11 and DXLab. Since DXLab doesn't have a say in the matter, perhaps it was a Win 11 update that changed the game. Likely an update changed some default. However, I would check with Kenwood for an updated driver in addition to the port settings in Device Manager. 73, ... Joe, W4TV On 2025-05-07 11:13 AM, Tim Sweeney via groups.io wrote: Hi Joe, you're on to something, I think. But to answer the questions, fastboot and hibernation are disabled (always), sleep is enabled but only manually triggered,? and I had tried both cold boot and restart with the same result, as well as both radio on and radio off when booting. But I overlooked the fact that even when the radio is "off", it's still really "on" internally, and the USB port is powered up as long as there is 12V to the rig. So I found unplugging the USB, rebooting, and re-plugging it clears the problem in the same way as uninstalling, rebooting and allowing the system to reinstall the device clears it. There's something about the combination of the device being fully detached (or uninstalled) and a reboot that resets things in a way that physical detachment or reboot separately do not. This is a new problem, as I've been running this same stuff for years now with no issue. The only things that have changed are newer versions of Win 11 and DXLab. Since DXLab doesn't have a say in the matter, perhaps it was a Win 11 update that changed the game. The USB driver involved is from 2019, so I doubt that changed. Just to fill in as many data points as possible: putting the machine to sleep doesn't change the state of things once it's awakened. If it was talking to the rig when put to sleep, it will still talk to it when awakened. Thanks!
Tim Sweeney All Messages By This Member #229139 On Wed, May 7, 2025 at 10:10 AM, Joe Subich, W4TV wrote: Try Device Manager -> Ports (COM & LPT) ... open the serial port for your TS-590 -> Advanced Settings and check the Miscellaneous Settings. I would start with "Serial Enumerator" checked and all the other options not checked. There are very limited options with this driver, just buffer sizes and COM port number.? ? I did get an updated driver from Kenwood, but the behavior persists.
Dave AA6YQ All Messages By This Member #229141 + AA6YQ comments below The rig generating the port is a TS-590S. The device it generates is listed as "Silicon Labs CP210x USB to UART Bridge". + Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): + If it reports the same error as Commander, then engage with Kenwood technical support. ? ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ
Matthias Zwoch All Messages By This Member #229142 Am 07.05.2025 um 18:43 schrieb Tim Sweeney via groups.io: HI Matthias - What happens if you plug in one device, say the rig, and then go into Device Manager and change the COM port number in the Advanced Settings for that port? It should retain that change across assignments, I think. In my case it's not a port conflict or changing assignments that's at issue. Just a consistently assigned port that is inconsistent in its functioning! 73, K1BR _._,_._,_ Yes, that works. I changed the two port numbers both in device manager and DXLab and no conflict will appear. This setting survived a win11 restart - fine. But if I plug off and on the cable for the FT-DX10 the ports are back on the old number :-( 73 Matthias DD7NT
Tim Sweeney All Messages By This Member #229143 On Wed, May 7, 2025 at 12:58 PM, Dave AA6YQ wrote: + Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): + If it reports the same error as Commander, then engage with Kenwood technical support. Well, the behavior of ARCP is similar to Commander, but with one difference. If I reboot with the rig USB plugged in, neither program can open the COM port. The difference is that a simple unplug->plug-in of the USB cable in the current session allows ARCP to connect, while Commander still can't. Commander needs the full unplug->reboot->plug-in cycle to get access to the port again. ? I've rearranged the cable so I can access it from a front USB port, and as long as I remember to yank the cable before I boot up I'm in business. Once it's working, it seems to stay working until the next reboot, even through sleep/wake events. ? 73, Tim K1BR
Gilbert Baron W0MN All Messages By This Member #229144 开云体育 The Kenwood manual emphasizes that you must use the Kenwood driver and be sure you have the latest ?Kenwood firmware. Download from Kenwood and get the Kenwood Radio Programming Software working as a test and you should have no problem after that. They provide a link to do that. I had to do? it many years ago on mine and have never had a USB problem with my Kenwood TS590SG since. I have used it for many many years. Be careful to follow all instructions about installing the driver. ? Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb ? ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of Dave AA6YQ via groups.io Sent: Wednesday, May 7, 2025 2:59 PM To: [email protected] Subject: Re: [DXLab] COM port oddity with Commander. ? + AA6YQ comments below The rig generating the port is a TS-590S. The device it generates is listed as "Silicon Labs CP210x USB to UART Bridge". + Consider downloading and running Kenwood's ARCP-590 application (with Commander terminated): + If it reports the same error as Commander, then engage with Kenwood technical support. ? ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ -- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
Tim Sweeney All Messages By This Member #229145 Hi Gil - I checked and I've been running the latest firmware, and did update the driver today. Still no joy, but at least it's usable. The problem is recent, so I'm really suspicious that it's related to a Win 11 update in some way, just because everything else on the system has been static.? If I get ambitious I might try a factory reset of the rig itself, just for completeness sake. ? Thanks and 73, Tim K1BR ?
Dave w6de All Messages By This Member #229146 开云体育 I’ll offer some of my findings with mysterious USB actions. --USB cables have length limitations.? I believe that there is a normal expectation of one meter length.? To exceed that length, I bought a powered USB two port hub and placed it between the radio and computer. --Throw away your cheap flimsy USB cables.? Buy clear shield USB cables where you can see the woven shield through the semi-clear cover.? These will be thicker and less flexible than the cheaper cables but I have found them to be more reliable and work with longer than 3 Meter cables. --Modern Radios using USB to computer communications usually have power switches that do not completely power down the radio.? They continue a keep alive power to some their internal circuitry.? Including the USB connections.? Use the power button on your radio to shut down but do not turn off your 12 Volt power supply in order to maintain your USB connections. --Computers also have keep alive power to their communications ports, USB, ethernet and sometimes WIFI ports.? Check your computer to see if it has an on/off switch on the back near the power cable connector. If it has a power switch then it most likely will have keep alive power to maintain all your communications alive after shut-down.? Shut-down is not power down!? Do not also turn off the computer power switch. Most but not all Laptop computers do not maintain their external communications after shut down.? --If you still have USB connection loss on shut-down, try to use a powered USB hub between your radio and computer. --Do not turn off your power bar that you have all your station equipment connected to at the end of an operating session. --If you have any USB to serial port conversion cables, always use a converter cable with an FTDI chip in it.? Converter cables can be 10 feet long.? I buy mine at Amazon and select Dtech cables. ? 73, Dave, w6de ? ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of Tim Sweeney via groups.io Sent: 7 May, 2025 03:53 To: [email protected] Subject: [DXLab] COM port oddity with Commander. ? I've recently started encountering the infamous "Invalid Port Number (8002), thePort = primary CAT port, port number = 4, settings = 115200,N,8,1" message box when trying to start Commander. Device manager shows COM4 to be up and working. Unplugging / re-plugging the USB cable and disabling / reenabling the COM port doesn't resolve it. The only solution seems to be to uninstall the device, reboot and let Windows reinstall it. Then the port will open fine until the machine is rebooted again. Then we're back to invalid port and the need to reinstall. ? Edition ? ?Windows 11 Pro Version ? ?23H2 Installed on ? ??11/?19/?2022 OS build ? ?22631.5189 Experience ? ?Windows Feature Experience Pack 1000.22700.1077.0 ? Commander ver 16.1.0 ? Anyone had this variation of the error crop up? Thanks! ?

Previous Topic Next Topic