Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
The latest SmartSDR Software:
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes

The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
How to Receive Technical Support::
If you are needing assistance with FlexRadio products, 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.

Key not parsed messages

Asher - K0AU
Asher - K0AU Member ✭✭✭
edited March 2020 in SmartSDR API
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?

Answers

  • Asher - K0AU
    Asher - K0AU Member ✭✭✭
    edited March 2020
    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).






  • Eric-KE5DTO
    Eric-KE5DTO Administrator, FlexRadio Employee admin
    edited February 2017
    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.

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.

Comment As ...

Categories