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.
Key not parsed messages
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
- 338 Community Topics
- 2.1K New Ideas
- 607 The Flea Market
- 7.9K Software
- 6.3K SmartSDR for Windows
- 170 SmartSDR for Maestro and M models
- 401 SmartSDR for Mac
- 264 SmartSDR for iOS
- 247 SmartSDR CAT
- 185 DAX
- 371 SmartSDR API
- 9.1K Radios and Accessories
- 19 Aurora
- 190 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 913 Maestro
- 53 FlexControl
- 859 FLEX Series (Legacy) Radios
- 886 Genius Products
- 450 Power Genius XL Amplifier
- 320 Tuner Genius XL
- 116 Antenna Genius
- 281 Shack Infrastructure
- 197 Networking
- 442 Remote Operation (SmartLink)
- 137 Contesting
- 741 Peripherals & Station Integration
- 137 Amateur Radio Interests
- 954 Third-Party Software