Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 31-03-2013, 10:17   #1
Marine Service Provider

Join Date: Oct 2009
Location: In the U.S.
Boat: FP Tobago 35 [sold]
Posts: 402
3.2 and TCP Server

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.
__________________

__________________
Mark (It's Irie - Sailing Blog)
The Wirie AP+ and The Wirie pro - Long Range Marine WiFi and 2/3/4G Systems
kiltym is offline   Reply With Quote
Old 31-03-2013, 10:40   #2
Registered User

Join Date: Dec 2005
Location: WNA
Boat: Dufour 35
Posts: 3,250
Re: 3.2 and TCP Server

Quote:
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.
__________________

__________________
cagney is offline   Reply With Quote
Old 31-03-2013, 12:05   #3
Marine Service Provider

Join Date: Oct 2009
Location: In the U.S.
Boat: FP Tobago 35 [sold]
Posts: 402
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.
__________________
Mark (It's Irie - Sailing Blog)
The Wirie AP+ and The Wirie pro - Long Range Marine WiFi and 2/3/4G Systems
kiltym is offline   Reply With Quote
Old 31-03-2013, 12:35   #4
mrm
Registered User

Join Date: Feb 2011
Location: Poland, EU
Boat: crew on Bavaria 38 Cruiser
Posts: 651
Re: 3.2 and TCP Server

Quote:
Originally Posted by cagney View Post
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
__________________
mrm is offline   Reply With Quote
Old 01-04-2013, 05:57   #5
Registered User

Join Date: Oct 2012
Location: Brighton, UK
Boat: Westerly Oceanlord
Posts: 374
Re: 3.2 and TCP Server

Quote:
Originally Posted by kiltym View Post
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?
__________________
muttnik is offline   Reply With Quote
Old 01-04-2013, 07:08   #6
Marine Service Provider

Join Date: Oct 2009
Location: In the U.S.
Boat: FP Tobago 35 [sold]
Posts: 402
Re: 3.2 and TCP Server

Quote:
Originally Posted by muttnik View Post
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.
__________________

__________________
Mark (It's Irie - Sailing Blog)
The Wirie AP+ and The Wirie pro - Long Range Marine WiFi and 2/3/4G Systems
kiltym is offline   Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off




Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -7. The time now is 16:22.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.