SmartSDR CAT will not connect to Radio on LAN

  • 1
  • Problem
  • Updated 9 months ago
I am trying to use the 6600M at a different site than at home.  I am not using it remotely, I am on-site with the radio.  I have used this config before and it worked fine.

I have the 6600M and the PC connected to a router that is supplying DHCP.  The PC and the radio get addresses and I can ping the radio from the PC.

I just need SmartSDR CAT to connect to Writelog to control the radio.  So that is the only program I am opening.  When I open it it says no radios available.  I fired up SmartSDR and get the same.

I disabled the firewall on the PC for LAN connections and there is no firewall active.

Any ideas on this?  


Thanks, John  K0TG
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like

Posted 9 months ago

  • 1
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 580 Posts
  • 206 Reply Likes
Since you can ping the radio, can you telnet to port 4992 on the radio? It should give you a dump of radio information if you connect (telnet radio_ip 4992). Also, if you "sniff" the network, do you see UDP broadcast packets on port 4992? These are what tell SSDR and CAT that the radio is there. Is there any possibility the router is blocking broadcasts?
(Edited)
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like
Thanks for your response.
I can telnet to that port and see the radio.  I made sure the firewall is off on the router.  I just checked it again to be sure.  Both devices are on the same network, so there is no routing involved and there is no Internet access on that LAN.
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like
I now have bypassed the router/switch completely.  I connected the PC to the radio directly.  I can ping the radio, but not connect to it.

73, John  K0TG
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 580 Posts
  • 206 Reply Likes
Another question: what do you mean by "telnet to the port and see the radio"? If you telnet to the radio TCP port, it will immediately dump a whole bunch of information about its state. If you don't see that, something is not right.
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like
Just re-read this.  I did not answer that.  I did see the dump when I did a telnet to that address and port.
Photo of Bill - W9KKN

Bill - W9KKN

  • 31 Posts
  • 13 Reply Likes
Stupid question, but are you running the same version of SmartCAT as the radio is running? 
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 577 Posts
  • 205 Reply Likes
John, if you find a solution, please report back to this thread if you would. I plan on doing exactly what you are doing in the near future (operating my 6600M at a local event, using a Windows laptop), and would certainly love to know the cause of your problems.

Ted VE3TRQ
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like
Will do.

BTW, I just looked and the firewall is set to permit SmartSDR to communicate.  I may have to open a ticket on this one.  Thanks for the help.


John  K0TG
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 577 Posts
  • 205 Reply Likes
Just spent some some with my friend Google :-) Came up with the following:
Question: I build a networked application that discovers another components using UDP broadcast messages. It worked fine for a long time, but when I tried to run it again a few days ago it stopped to work only in my machine. The firewall and the antivirus are disabled, but the problem persists. These packets arrive to machine, confirmed through sniffer, but application does not receive nothing.

Response: The problem was in all UDP messages and not only broadcasts. It was caused by the service "Network Provisioning Service (xmlprov)" that was not running. After start this service, all UDP messages started to be received again.
The general complaint seems to be that Windows may or may not pass on something addressed to "255.255.255.255:4992", but DOES pass on things addressed to "192.168.0.255:4992". Would think the code for SSDR and CAT would ensure broadcast are passed in, but maybe there is some Windows config or component involved as the OP above seemed to think. A shot, anyway, since WireShark and tcpdump will pick off the packets before the upper layers deal with them and deliver them.

(Edited)
Photo of johnk0tg

johnk0tg

  • 26 Posts
  • 1 Reply Like
Looked promising.  I do not see that service on the PC.  Windows 10.   I think I have to go to plan B (another radio for now).  Bummer.  

But thanks so much for the help.  Will post here what the resolution is.


John  K0TG
Photo of Ted  VE3TRQ

Ted VE3TRQ

  • 577 Posts
  • 205 Reply Likes
Well, my curiosity got the better of me, so I disconnected my 6600M from my network, turned off the WiFi on my Win10 laptop, and connected directly with a patch cable to the radio.

Turned on the radio, waited for both radio and PC to get a link local address (both radio and PC were set for DHCP), connected the front panel (to avoid SSDR), connected DAX and CAT, ran WSJT-X and immediately began decoding FT8 :-).

No special setups on my PC, just what worked with WiFi in the past, only now completely isolated from all networks except the PC and radio.

As a second attempt, I repeated the process, only this time waited for radio and PC to give themselves a link local address, and tried to connect with SSDR on the PC instead of the "M" front panel. SSDR Radio Chooser found the radio no problem. Upshot is, it DOES find the radio, as did DAX and CAT.

Good luck finding your PC problem, John.
(Edited)