TCP command line problem

  • 1
  • Question
  • Updated 2 years ago
I can't get my Flex6700 to respond to TCP commands. I'm sure I had no problems a couple of weeks ago (using Terminal on Mac OS X), but now when I connect to the radio, I get the version number and handle response OK, but it just ignores any commands I type after that (such as "info" or "V"). If I make a change on the SmartSDR program on a PC, I can see the resulting status messages in my tcp terminal window on the Mac.  Using wireshark I can see an exchange - my command to the receiver and an ACK from the receiver, but with no data in the packet. I did a power on reset to the receiver, and just downloaded and installed the v1.8.3 update, but still no luck. A friend and I were messing around with the interface using python last week, so there's always the possibility that we messed something up, but I have no idea what that might have been. Does anyone have any ideas or suggestions?

Thanks,
Mike  AB1LD
Photo of Mike Burns, AB1LD

Mike Burns, AB1LD

  • 14 Posts
  • 3 Reply Likes

Posted 2 years ago

  • 1
Photo of Eric - KE5DTO

Eric - KE5DTO, Employee

  • 673 Posts
  • 203 Reply Likes
Mike,

Can you give me an example of exactly what you are sending over the wire so I can try it here and figure out what is going on?
Photo of Mike Burns, AB1LD

Mike Burns, AB1LD

  • 14 Posts
  • 3 Reply Likes
I use netcat on Terminal program in OS X (actually named "nc" in the Mac version):
> nc 10.0.1.43 4992
V1.2.0.0
H9BCAC15E
info
V

where "info" and "V" are commands that I type in an attempt to get a response.
I monitor with wireshark ( I could send the capture file if you want) and can see the "info" and "V" sent as a packet, to which there is an acknowledgement ACK packet from the Flex, but with 0 bytes of data. The response to my initial connection is similar, but the ACK packet there contains the "V1.2.0.0  H9BCAC15E" data in it.

I'm puzzled. As I said I'm sure I did this a couple of weeks ago and it worked fine. I'm concerned that our clueless monkeying around with python and the interface might have done something unintended.
Photo of Eric - KE5DTO

Eric - KE5DTO, Employee

  • 673 Posts
  • 203 Reply Likes
I think you'll need a "C|" in front of your commands in order for them to get treated as commands.  Try that and let me know what you get.
Photo of Mike Burns, AB1LD

Mike Burns, AB1LD

  • 14 Posts
  • 3 Reply Likes
Eric,

Thank you, thank you, thank you!  In fact I need a C space | space [command] but then it works. I really don't remember having to put those in, but I'm getting old I guess.

Mike
(Edited)
Photo of Eric - KE5DTO

Eric - KE5DTO, Employee

  • 673 Posts
  • 203 Reply Likes
I'm glad you got it figured out.  The spaces shouldn't be required.  I did fail to mention the sequence number.  So the format is:

C<seqence num>|<command>

This is all documented in the wiki at wiki.flexradio.com.
(Edited)
Photo of Mike Burns, AB1LD

Mike Burns, AB1LD

  • 14 Posts
  • 3 Reply Likes
Hmm - seems that the Flex takes a space as "0" for a sequence number. I was reading the wiki, but misinterpreting it. My usual trouble of confusing literals and placeholders. I'm feeling particularly stupid at the moment, so thank you for being patient.

Mike