10.10.10.1:10110

[DoubleDutch]

You can do it a couple of different ways. One is to install the SignalK "SignalK to NMEA0183" plugin, and test to see if you are getting anything out on TCP port 10110 (you should). Don't forget to enable to plugin, and check the NMEA strings you want sent out. If you still can't see it, try also installing the "UDP NMEA0183 Sender". That plugin sends out using UDP and does allow you to configure the network (10.10.10.255) and UDP port you need to send data out on (10110 is fine).

If you don't want to mess with SignalK plugins, you can configure an outgoing network connection in OpenCPN. With that one, you have full flexibility to choose port number, TCP or UDP, addresses, etc. Of course, the downside is that you need to have OpenCPN running on your RPI server.

Hi - Me again... This is starting to drive me crazy.... Lets take a step back.

• I found this URL: http://ais.exploratorium.edu:80 which is AIS information for the San Francisco Bay Area. When I open the URL: you will see what I believe to be NMEA AIS Data
  
• On my RPI, in OpenCPN I created an input port and point it to the above URL. Now, when in OpenCPN I look at the SFO Bay area: I see AIS targets! Hooray!
  
• I now want to see these same targets in Navionics on my iPad and that bit doesn't work
  

My questions:

1. Looking at your post above: given that I added this SFO-AIS data to OpenCPN; I have to create the outgoing network connection in OpenCPN because "Signal K" doesn't know about SFO-AIS? I'm not sure how to do that without restricting it to a specific IP address (of my iPad)
   
   
2. Is configuring SFO-AIS in Signal-K an option / is it best practice to configure all inputs in the Signal-K server, so the only connection in OpenCPN is to the Signal K server and my iPad connects to Signal-K not OpenCPN
   
   
3. With the configuration as I currently have it where, as I understand it OpenCPN is the "aggregator" and given the above SFO-URL and having configured the Access Point in OP - why can I not go to http://10.10.10.1:10110 and see this NMEA data (whilst port 3000 does show the Signal K server so the WiFi configuration must be OK?)
   

Almost losing sleep over this :-)