Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR, Power Genius, Tuner Genius and Antenna Genius Software?
SmartSDR v3.7.4 and the SmartSDR v3.7.4 Release Notes | SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.8.8 and the Power Genius XL Release Notes v3.8.8
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
SmartSDR v3.7.4 and the SmartSDR v3.7.4 Release Notes | SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
SmartSDR v1.12.1 and the SmartSDR v1.12.1 Release Notes
Power Genius XL Utility v3.8.8 and the Power Genius XL Release Notes v3.8.8
Tuner Genius XL Utility v1.2.11 and the Tuner Genius XL Release Notes v1.2.11
Antenna Genius Utility v4.1.8
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.
Key not parsed messages
Options
Asher - K0AU
Member ✭✭
I'm getting debugger console messages:
Slice::StatusUpdate: Invalid key/value pair ()
Slice::StatusUpdate: Invalid key/value pair ()
Slice::StatusUpdate: Key not parsed (post_demod_low=300)
Slice::StatusUpdate: Key not parsed (post_demod_high=3300)
running FlexLib 1.7.3 against software 1.6.21 in the radio. Is the 1.6.21 API still downloadable or does everything need to upgrade in lockstep? Or are the messages unrelated to revision levels out of step?
Slice::StatusUpdate: Invalid key/value pair ()
Slice::StatusUpdate: Invalid key/value pair ()
Slice::StatusUpdate: Key not parsed (post_demod_low=300)
Slice::StatusUpdate: Key not parsed (post_demod_high=3300)
running FlexLib 1.7.3 against software 1.6.21 in the radio. Is the 1.6.21 API still downloadable or does everything need to upgrade in lockstep? Or are the messages unrelated to revision levels out of step?
0
Answers
-
Also these messages coming after the display goes to sleep. Anyone else seen anything similar? (BTW it would be great if the error messages could be in syslog format with timestamps)
On startup the client correctly connects to:
-----------------------------------------
Discovered 192.168.1.180 FLEX-6700: 3313-0588-6700-2693 (xcvr-1 0x055D13BE)
then several hours late while sleeping it does this:
----------------------------------------------------------------
Discovered 0.0.0.0 FLEX-6700: 3313-0588-6700-2693 (xcvr-1 0x47B2ECFA)
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Meter Packet: Expected 6 got 15
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
Radio::Connect() -- Error creating TCP client
The requested address is not valid in its context 0.0.0.0:4992
Exception thrown: 'System.Net.Sockets.SocketException' in System.dll
I also see hundreds of these messages along the way:
-------------------------------------------------------------------
The thread 0x2554 has exited with code 0 (0x0).
The thread 0x3220 has exited with code 0 (0x0).
0 -
Asher,
Thanks for the questions. First, the key/value is debug output about data the radio is sending that FlexLib is not currently using. It is there mostly as a nudge to our developers if something appears there that shouldn't.
I'm not sure how to explain the 0.0.0.0 radio discovery. The radio should typically have a good IP address before sending out any discovery packets, so that is curious. If it were me, I would probably try to get it into this mode and divide the problem using WireShark to inspect the packets coming from the radio to decide whether it is sending a blank IP address or whether something is happening after that to cause the IP address to become cleared on the Discovery client side.0
Leave a Comment
Categories
- All Categories
- 246 Community Topics
- 2.1K New Ideas
- 488 The Flea Market
- 7.3K Software
- 5.9K SmartSDR for Windows
- 134 SmartSDR for Maestro and M models
- 328 SmartSDR for Mac
- 241 SmartSDR for iOS
- 224 SmartSDR CAT
- 161 DAX
- 343 SmartSDR API
- 8.5K Radios and Accessories
- 6.9K FLEX-6000 Signature Series
- 768 Maestro
- 42 FlexControl
- 836 FLEX Series (Legacy) Radios
- 726 Genius Products
- 391 Power Genius XL Amplifier
- 251 Tuner Genius XL
- 84 Antenna Genius
- 223 Shack Infrastructure
- 150 Networking
- 370 Remote Operation (SmartLink)
- 118 Contesting
- 582 Peripherals & Station Integration
- 116 Amateur Radio Interests
- 810 Third-Party Software