Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR or 4O3A Genius Product Software?
SmartSDR v3.9.19 and the SmartSDR v3.9.19 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
The latest 4O3A Genius Product Software and Firmware
SmartSDR v3.9.19 and the SmartSDR v3.9.19 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
The latest 4O3A Genius Product Software and Firmware
If you are having a problem, please refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Update: SmartSDR version 3.0.27 disconnecting from DXLab Commander
Options
Dave AA6YQ
Member ✭✭
Last week, I released Commander 14.1.6, which disables SmartSDR's "keep alive" option (a possible source of TCP disconnects) and logs any Commander-initiated closure of the TCP port even if "log debugging info" is not enabled. These changes have not eliminated all reported TCP disconnects between Commander and Flex Signature radios running SmartSDR version 3.0.27; the diagnostics indicate that the disconnects are not being initiated by Commander.
My advice to Flex Signature radio users is still "remain with SmartSDR version 2.4.9 unless you have a compelling reason to upgrade."
Further progress on identifying the cause of these TCP disconnects requires a version of SmartSDR that can be configured to log unexpected events to a local file.
Many thanks to Dave G7HJX, Roger N3RC, Rick WR0H, Ronald W4RJF, Jamie WW3S, Chris N6WM, Mark W3II, Dave NX6D, Jeff KI0KB, Tim WA5YOM, John K3MA, and John K1ESE for their help with this effort.
My advice to Flex Signature radio users is still "remain with SmartSDR version 2.4.9 unless you have a compelling reason to upgrade."
Further progress on identifying the cause of these TCP disconnects requires a version of SmartSDR that can be configured to log unexpected events to a local file.
Many thanks to Dave G7HJX, Roger N3RC, Rick WR0H, Ronald W4RJF, Jamie WW3S, Chris N6WM, Mark W3II, Dave NX6D, Jeff KI0KB, Tim WA5YOM, John K3MA, and John K1ESE for their help with this effort.
0
Comments
-
Dave,
Do you think this is a local LAN thing? I run 3.0.27 with DX Commander and the connection stays rock solid albeit either over the VPN to the remote via Softether or via Smartlink connections. Guess I was completely unaware of this problem until reading about it here.
Good luck and thanks to all for chasing this.
0 -
There's no way to know, Larry, as there's currently no practical way to determine whether or not SmartSDR 3.0.27 is initiating the disconnections and, if so, why. Eric KE5DTO has initiated a request to extend SmartSDR to log errors and unexpected events to a local file; when this has been implemented, tracking down the root cause should be straightforward.
The known facts are
1. no one reported TCP disconnects between Commander and SmartSDR 2.3.9 or 2.4.9.
2. Commander is not initiating the TCP disconnects some ops encounter with SmartSDR 3.0.27.
0
Leave a Comment
Categories
- All Categories
- 328 Community Topics
- 2.1K New Ideas
- 593 The Flea Market
- 7.8K Software
- 6.2K SmartSDR for Windows
- 168 SmartSDR for Maestro and M models
- 396 SmartSDR for Mac
- 260 SmartSDR for iOS
- 246 SmartSDR CAT
- 179 DAX
- 369 SmartSDR API
- 9.1K Radios and Accessories
- 15 Aurora
- 160 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 909 Maestro
- 51 FlexControl
- 854 FLEX Series (Legacy) Radios
- 873 Genius Products
- 446 Power Genius XL Amplifier
- 312 Tuner Genius XL
- 115 Antenna Genius
- 278 Shack Infrastructure
- 196 Networking
- 438 Remote Operation (SmartLink)
- 135 Contesting
- 723 Peripherals & Station Integration
- 136 Amateur Radio Interests
- 942 Third-Party Software