3.2 and TCP Server

[kiltym]

I am trying to set up O to be a TCP/IP server for NMEA data for multiple clients.

I have PolarCom and NavMonPC I want to connect to the server from O, and potentially some apps on my tablet.

However, when I connect one application, PolarCom, to O, it all works fine. When i go to connect NavMonPC, PolarCom drops out, and NavMonPC works fine.

As in, only one client can connect at a time.

Is this correct behavior for the server on O?

I am sure I have used other NMEA TCP/IP servers to support multiple clients.....? I think I did this with NavMonPC as the server, and allowed multiple clients to connect to it at the same time.

I can easily create multiple TCP servers in O to configure what I would like, but seems a bit cleaner to just use 1 if possible.

Thanks for the help.

[cagney]

Is this correct behavior for the server on O?

Unfortunately O 3.2 is currently limited to one client/Tcp server.
This is explained in the documentation.
Most likely this restriction will disappear with the next release.

[kiltym]

Ok. Thanks for the info, and sorry I didn't read that in the manual.

Will just create multiple servers for now to accomplish what I am trying to do.

[mrm]

Originally Posted by cagney

Unfortunately O 3.2 is currently limited to one client/Tcp server.
This is explained in the documentation.
Most likely this restriction will disappear with the next release.

in the meantime...

$ ncat 127.0.0.1 <OpenCPN_port> | ncat -k -l <relay_port> --send-only

or, alternative syntax:

$ ncat --sh-exec "ncat 127.0.0.1 <OpenCPN_port>" -k -l <relay_port> --send-only

should do the trick (in Linux).

Replace <OpenCPN_port> and <relay_port> with respective port numbers.

Marius

[muttnik]

Originally Posted by kiltym

I am trying to set up O to be a TCP/IP server for NMEA data for multiple clients.

Dave commented on the single-client tcp server issue in this thread.

You don't say what OS your server is. If linux I'll obviously say use kplex to "own" all the incoming datastreams, create a tcp (and/or udp) server and "feed" opencpn either from the tcp server or a pseudo tty.

I'm not a windows user (perhaps someone who is could comment) but if as I suspect your "server" computer is windows, is there the possibility of using NavMonPC to own the serial inputs, create a tcp server and feed OpenCPN either from that or a virtual com port?

[kiltym]

Originally Posted by muttnik

Dave commented on the single-client tcp server issue in this thread.

You don't say what OS your server is. If linux I'll obviously say use kplex to "own" all the incoming datastreams, create a tcp (and/or udp) server and "feed" opencpn either from the tcp server or a pseudo tty.

I'm not a windows user (perhaps someone who is could comment) but if as I suspect your "server" computer is windows, is there the possibility of using NavMonPC to own the serial inputs, create a tcp server and feed OpenCPN either from that or a virtual com port?

Agree, no lack of workarounds to the issue. Thanks for the pointer to the thread as well.

As far as using NavMonPC to "feed" O, yes that works, and what I did when I was using 3.02. But the idea (for me), of moving to 3.2, was to eliminate NavMonPC as a multiplexer since all this functionality is now built into O, which is great. I want O to "own" the data sources, and disseminate the data to clients as I need. Basically, what I was using NavMonPC for. Less software on the computer the better.

Unfortunately some clients still don't support UDP which creates this need for multiple clients on TCP, but (on Windows), NavMonPC will work, or simply create multiple TCP servers within O itself, which is the option I chose.

Anyway, not a huge deal, just stumbled on it while setting 3.2 up on my boat. Likely others will stumble on it also as it is an easy line to skim over in the manual, and not "normal" behavior when compared to other systems.