turning off K4 IP connectivity
|
Brian Kuebert NZ4N
Hi Folks, I've got a K4 and have been happily using the DX Commander TCP connectivity to the radio with no problem since it's release. I'm trying some new configurations and want to turn this off and go back to a serial port. When I have DX Commander open and uncheck the "Communicate via TCP" box it correctly disconnects and if I then click "Reset" it correctly connects via the serial port I have defined. This is all good and as expected. When I exit and restart, though, Commander connects via TCP (the communicate via TCP box is checked again) - it seems to have forgotten that I turned off TCP connectivity. This happens also if I even delete the IP Address entry in addition to unchecking the communicate via TCP box and if the port I'm connecting to is a physical USB-to-Serial port or is a virtual port connecting ultimately to other software (like win4K4suite) - seems related to the configuration not getting correctly remembered when disabling TCP connectivity rather than related to what I'm connecting to (at least on the surface). Has anyone else seen this behavior? Or is this a possible defect maybe? 73, Brian NZ4N |
|
|
|
If you are restarting via Launcher AND have settings In workspace AND are configured to load settings from workspace, THEN it would go back to those settings.
Outlook LT Gil W0MN Hierro Candente Batir de Repente 44.08226 N 92.51265 W EN34rb
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Brian Kuebert NZ4N
Sent: 02 December 2022 12:54 To: dxlab@groups.io Subject: [DXLab] turning off K4 IP connectivity
Hi Folks,
I've got a K4 and have been happily using the DX Commander TCP connectivity to the radio with no problem since it's release.
I'm trying some new configurations and want to turn this off and go back to a serial port. When I have DX Commander open and uncheck the "Communicate via TCP" box it correctly disconnects and if I then click "Reset" it correctly connects via the serial port I have defined. This is all good and as expected. When I exit and restart, though, Commander connects via TCP (the communicate via TCP box is checked again) - it seems to have forgotten that I turned off TCP connectivity.
This happens also if I even delete the IP Address entry in addition to unchecking the communicate via TCP box and if the port I'm connecting to is a physical USB-to-Serial port or is a virtual port connecting ultimately to other software (like win4K4suite) - seems related to the configuration not getting correctly remembered when disabling TCP connectivity rather than related to what I'm connecting to (at least on the surface).
Has anyone else seen this behavior? Or is this a possible defect maybe?
73, Brian NZ4N -- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop |
|
|
|
Joe Subich, W4TV
In addition, if you have defined more than one radio in
toggle quoted message
Show quoted text
Commander -> Config -> MultiRadio and have not cleared the TCP setting there it will be restored on restart. 73, ... Joe, W4TV On 2022-12-02 2:48 PM, Gilbert Baron W0MN wrote:
If you are restarting via Launcher AND have settings In workspace AND are configured to load settings from workspace, THEN it would go back to those settings. |
|
|
|
Dave AA6YQ
+ AA6YQ comments below
In addition, if you have defined more than one radio in Commander -> Config -> MultiRadio and have not cleared the TCP setting there it will be restored on restart. + If you have selected and enabled your K4 in the Control panel at the top of Commander's Configuration window's MultiRadio tab, you must click the Select button to the right of the Model selector to gain access to the small "Commander Multi-transceiver Connectivity Selection" window, which provides the ability to enable or disable communication via TCP. As Joe W4TV points out above, Commander will apply this setting whenever you select your K4 - along with the IP address and IP Port you've specified in the "Commander Multi-transceiver Connectivity Selection" window. 73, Dave, AA6YQ |
|
|
|
Brian Kuebert NZ4N
Thanks for the idea - that was it! Workspace was the culprit. Really appreciate the feedback.
73, Brian NZ4N |
|
|
|
Brian Kuebert NZ4N
Thanks, Dave - I found this as well while digging around the settings. Once I removed the setting in the multi-transceiver connectivity selection window the workspace was the last piece of the puzzle.
Thanks again for all the great ideas! 73, Brian NZ4N |
|
|