SmartSDR RadioClient Messaging documentation

  • 3
  • Question
  • Updated 4 years ago
  • Answered
I'm working on a Flex client for use on the Mac. I've gone through the SmartSdr Objective-C download. I'm wondering if somewhere there is a complete list of the messages sent back and forth between the Radio and the client program. If there is, is it current and is there a list of "deltas" produced when a new SmartSDR version is produced? I can probably find this information by scanning the FlexLib source code but that is a pretty tedious approach.
Photo of Doug - K3TZR

Doug - K3TZR

  • 112 Posts
  • 15 Reply Likes

Posted 4 years ago

  • 3
Photo of Eric - KE5DTO

Eric - KE5DTO, Official Rep

  • 719 Posts
  • 211 Reply Likes
Official Response

Welcome to the club!  Based on your question, the best answer that I have for you is our wiki which documents the Ethernet API.  All of this and more is available from our API website here:  Note that the wiki requires a quick login creation (automated).

We do our best to keep up with the commands there, but you may occasionally find a command that hasn't made its way there yet.  If you run into these, please point them out to us so we can bring the wiki up to date.

To answer your question about the "console gui" command -- This command says to the radio that the connected client would like to be the exclusive client for Panadapater and Waterfall data.  Today there can only be one such client connected at a time.  At some point in the future we plan to expand this functionality to allow multiple concurrent clients to stream displays, but today this command is how we indicate this to the radio.  Note that if you try to send this command while another client that has already sent it is connected, your command will be rejected.

Any other specific questions are welcome.  Thanks for joining in the fun.
Photo of Steve - N5AC

Steve - N5AC, VP Engineering / CTO

  • 1034 Posts
  • 1009 Reply Likes
Official Response
Just as further answer to the original question about producing an API differences document for each version: this is a great idea and one we've thought of too.  I think we would like to do this in the future, but right now we're working hard to balance our resource usage on different projects.  I understand that this effort would help the developers, but there is also a fairly simple way to get to what you need -- simply look at the text file listing the changes between versions.  Then try each function and look at the commands/responses that are passed between the radio and the SmartSDR Windows client.  I know this isn't as convenient as getting list, but realistically we've not had the time to go produce the information you're looking for.  I would like to be able to do it in the future though.