Only One TCP in CAT for SO2R?

Mark Adams

I was struggling to fix an issue where my Slice A and B were somehow Radios 2 and 1 respectively in N1MM. I think it is right now, but after deleting all the Comm ports and then adding them back in, the instructions show that you only add one TCP: Port 5002 Slice A entry.

Is a TCP: Port 500x Slice B needed?

I cannot seem to find the answer. Here is what I have running now and everything seems to be working.

73, Mark K2QO

Mike-VA3MW

Hi Mark

You can have as many CAT ports as you require. Right now, you show Slice A on a TCP port and Slice B on COM5 and connected to N1MM.

I assume that you have configured N1MM / Radio 1 to use TCP port 5002 and Radio 2 to use CAT port 5. There is nothing wrong with this if that is what you have intended to do and both methods to provide CAT command and control to the radio.

There are many ways to make this work.

In my example below, I only use TCP ports where possible. Each port number needs to be unique.

One big advantage of using TCP ports is that you could, if you wish, use N1MM on 1 computer and SmartSDR on a totally different computer allowing you more screen real estate if you choose. And, if you got carried away, you could run your digital programs on a 3rd computer all working very happily. You do this by changing 127.0.0.1 to the IP address of the other computer.

Make sure you use SO2R (and not SO2V or SO1V) if you want to use 2 Panadapters. N1MM treats it like 2 different radios.

73, Mike va3mw

Mark Adams

OK Mike,

It is a bit clearer. All my stuff was running fine until a few weeks ago and it is fixed. I run my 6500 in N1MM/SO2R with the settings I showed in the screenshot. The confusion is that in the document, "Setup for SO2Rwith a Flex-6700 Guide and N1MM+" by KE5DTO and K9CT, shows the config I'm using but doesn't have the added TCP Port for Slice B like you show.

So, in my example, if I ONLY used TCP I could delete COM4, COM6, and COM8 and replace them with TCP on 60000 - 6000X. You show a Winkeyer on 60003 AND Serial Com 13. Why specify ANY Comm ports? Just use all TCP.

Is TCP vs Serial better for some connections, but not others? Does it practically not matter?

It is the mix of these I find confusing.

Looks like a good topic for a Friday video!!!

73, Mark K2QO

Mike-VA3MW

Hi Mark

I had both as N1MM worked ok with TCP ports but WKDemo (the Win Keyer Demo software) only works with serial ports, as I am sure the same is true for many Logging programs that support a WinKeyer.

Serial is over 1/2 a century old. :) I'm moving more and more to TCP ports (raw sockets) just because it is easier to maintain I guess. FlexRadio VSP ports are a lot of overhead as well.

K5XH

Thanks for the screen shot Mike. I haven't tried this with my N1MM setup but I would like to soon.

Question - Is the IP address you show the radio's IP or the computer's IP? Your comments seem to indicate that it is the computer's IP but the (very sparse) mention of using TCP in the N1MM docs says it is the radio's IP. I wish all this was documented better!

Thanks,

Mark K5XH

Mike-VA3MW

Hi Mark

127.0.0.1 means to send the connect to THIS computer. It is also known as local host.

This page explains it in a bit more detail and you might it useful.

https://www.lifewire.com/network-computer-special-ip-address-818385

For the purposes of N1MM communicating to a FlexRadio, the IP address should always be 127.0.0.1 AND SmartSDR for CAT must be running on the same computer. SmartSDR CAT will then pass on the communications to the radio no matter where it is.

From a communications view, it looks like this:

N1MM <127.0.0.1:xxxx>SmartSDR CAT with port number xxxx <HamShack Ethernet>Radio

73

K5XH

Thanks Mike! I have been using N1MM for years and always used the CAT method. I'll give this a try.

73, Mark

Mike-VA3MW

The guys that write N1MM code are bringing it into the 21st century. :)

Using IP connectors is much more stable in the long run

73