Supplementary Hardware

Table Of Contents

AIS Devices





AIS Transponders


Vesper XB-8000

GPS, AIS Transponder, Wifi, Nmea2000, Nmea0183, Alarm, no screen


Vesper Watchmate 850

GPS, AIS Transponder, Wifi, Nmea2000, Nmea0183, Alarm, Screen & Filters


AIS Recievers

dAISy AIS - Reciever

This little receiver works like a charm. Its a simple and easy low cost alternative.  

Mobile AIS - battery powered WIFI AIS Receiver

Standalone battery powered AIS Receiver, WIFI enabled, including VHF Antenna.
Up to 20 hours before it needs recharging and it connects to 10 WIFI clients simultaneously.
AIS wireless to Opencpn and no mounting on the boat required, perfect for all watersport enthusiasts without their own yacht.

AIS receiver dongle

Quark-elec AIS receiver dongle: Receiving on AIS dual channel alternatively, USB power and output 3.84k NMEA183 data,Compatible with Windows 7,8,10,Mac Linux system.
Details  :
Quark-elec wireless AIS receiver: Receiving on AIS dual channel alternatively, USB power and output 3.84k NMEA183 data.With embedded WiFi module, QK-A023 can share AIS messages with nearby mobile devices wirelessly.
Details  :

RtlSdr Dongle

There is a plugin which assists with use of this device for AIS purposes. We have found that for the average user, one of the other low cost choices may be better.

AIS -Cheap VHF Ship Alarm

Hardware required: A VHF Turn your VHF on and set it to channel 87 or 88. So you also monitor channel 16 press the dual scan button. Turn the volume up and set the squelch to fine. A burst of sound will tell you that a ship is within VHF range. It’s as simple as that.

GPS Devices

Model Vendor Linux Windows Mac OS X
BU-353 S4 Global Sat ? Seems to work just fine in Windows 8.1 with supplied driver ?
BU-353 USB Various Yes, native Yes with driver up to Win7. but not on Win8.1 or 10, get BU-353-s4 Yes with driver
Foretrex 201 Garmin Pl2303 driver and gpsd. Gpsd hotplugging is disabled for the device, so you need to edit the gpsd udev rules. ? ?
GPS126 GPS128 Garmin "Send Route to GPS" Only the waypoints are transferred, not the route ?  
GPSmap 76CSx Garmin GPS is connected via USB cable. Works with OCPN stable 2.3.1 and beta 2.4.708 on Ubuntu 10.04 with kernel 2.6.38 and gpsd 2.95 via Network LIBGPS as NMEA source ? ?
Nokia E71 + EXTGps  Nokia+Symarctic  ?  WinXP SP3 Yes

Win7 Data yes - OpenCPN No
 QSTARZ 51 Channel Bluetooth GPS Qstarz Yes native. Works great as per help file wiki Bluetooth GPS Ubuntu Install Could not get it to work with Windows and MaxSea. never tried on OpenCPN on Windows.  
 RayNav 300  Raymarine Works on Linux Debian, build the serial cable and you're set  Works on Windows XP  Not tried
 NL-302U   Navilock    XP & 7U46 fine  
 NL-402U (u-blox5 chipset)  Navilock Works, tested on Ubuntu 10.10  Works tried on Windows XP and Windows 7 32-bit  Not tried
 ND-100S SiRF-III  Nobrand Works well with Ubuntu
seems similar.Successfully connected and continuously returning nmea-signal. Vista.
Works with Win 98 and XP
 Not tested
 Holux GM-210 USB      Sony Viao with Vista  
Windows Configuration Tool, best results when set GLL to 5 with Config Tool
not tested works with USB Bluetooth Dongle, WinXP SP3 works with built in Bluetooth of MacBookPro OS X 10.6.4
GM 65
Skytraq - chipset Venus 6
USB - NMEA 0183
not tested Yes, with driver
tested with Win7 64 & 32.
Yes, with driver
GP-01 USB Eastern Star 7 MC-Marine Yes, "out of the box" Yes with driver ?
GP-01S USB SiFR Star III MC-Marine Yes, "out of the box" Yes with driver Yes with driver
Earthmate GPS LT-40 DeLorme Yes, "out of the box" Yes with driver Testing
Dual ? Yes, no driver required. In properties>services check "serial port" and uncheck "Wireless iAP" ?
Droid Ultra,
Cellphone using Bl
Motorola Not tested Yes, Under Windows 8, and using Android App GPSOverBT.
Have GPSOverBT running on phone, on Windows side create new outgoing BlueTooth ComPort and select your android phone from list.
In OpenCPN under Options>Connections select your new BlueToooth ComPort and hit Apply. See coment below. See forum post
Not tested

About SBAS

Install on RPI & CubieT

Links to sites/blogs/forums with instructions for installation of OpenCPN on specific systems



OpenCPN For Dummies


One User's RPI Setup/Configuration


Rpi and HDMIPI Chartplotter

by StuartGunn


I have been using open source chartplotting for some years, starting with Seaclear on an old notebook computer and adding an Actisense multiplexer and connecting in instruments and autopilot. My previous setup was on a 41 ft boat in the Med and I had solar panels to keep up with the 3 amp load of the computer. My current boat is smaller and in the UK so I don't want the problem of large current drain. For that reason I changed to a Raspberry pi to run the chartplotter and changed to OpenCPN because Seaclear was not developed for the Rpi platform.


I have developed the system in stages and it now comprises:
            Rpi 2 within an HDMI screen as the chartplotter
            Rpi 1B running KPLEX multiplexer
            Matsutec HP33A AIS/GPS providing data
            NASA nmea wind instrument
            Raymarine ST 60 Tridata and Graphic display in the cockpit
   Seatalk/nmea translator  See CF Post
            Temperature sensor in the exhaust
            BMP180 barometer and HTU21 humidity sensors

See photos here


In developing the system the main issues I have faced are:

1. Power: shortage of power has been a constant bugbear either because the boat batteries ran down to below 12v or because of poor connections or because of surges during engine starting. I have tried various power stabilisers but my current arrangement which works well comprises a MeanWell 12v adjustable DCDC stabiliser and a 12/5 adjustable stepdown. I obtained both reasonably cheaply on Ebay; the Meanwell turned out to be from Westland helicopters old stock and the 5v unit is good and shows output voltage and current on a small screen. I have used chunky terminal blocks for all connections. I have also doubled up the boat's service battery.

2. Serial/USB devices: these come in two types,
  1. a) a unit about 5cm long with a USB at one end and 9-pinD at the other. The problem with these is that they require a 9-pinD to be soldered to a wire and then the two bolted together. Invariably the bolts are either male and male or are too short. The resulting affair is sensitive and can fail to work
  2. b) a unit which has the chip within the plug at the end of the wire. This seems to be a much more secure system but I have not got them to work properly yet and have fried 2 or 3.
  3. Whichever type of device is used the second problem comes when one needs to identify the units in a rule file so that the Rpi can recognise the correct USB port (I have 3 units attached to the multiplexer). Each unit must have a unique identifier (IDVendor, IDProduct, product, serial, etc.) but I seem to have found only 2 basic types of chips: Prolific and FTDI. IDVendor and IDProduct are identical for all units from Prolific or FTDI whatever shape they come in. Only FTDI has serial and they are aften identical. The only way to find out what data is on the unit is to buy and try it.

3. Software: I am very grateful to the developers of OpenCPN, KPLEX and other open software and I contribute financially in a modest way. However, several of my hiccups which have cost me days, have resulted from minor bugs in the software. I blame myself first but the possibility of bugs should always be considered.

4. Navigation Data: The Matsutec HP33A outputs AIS, GPS, and autopilot data but it will not mix the data at will. There are 5 different sets of data to choose from but none of them combine AIS with navigation (waypoint info). The AIS is transmitted at 38400 baud and other sets at 4800 baud. Thus it is not possible to use the Matsutec as the navigator and still receive AIS data on the chartplotter. The work-around is to usually set for AIS transmission and use the Rpi to navigate. A fallback if the Rpi fails is that the Matsutec will send data directly to cockpit instruments. I just have to change the setting through the menu.

5. Capacity of the Rpi: My first setup used an RPi B which worked well though it was sometimes overpowered by data when in the vicinity of many other vessels because of the need to handle all their AIS signals and compute potential collisions. I overcame this by switching off some of the AIS capability when traffic was heavy. I have now installed an Rpi2 and so far it seems to be coping, though I haven't been into very heavily trafficed ares yet.

6. OpenCPN sometimes fails to save the .conf file. This seems to happen possibly when voltages are low. Having spent some time setting up comms, screen defaults, dashboards etc it is upsetting to see them all disappear and a  start-up message appear. I have overcome this by saving a “good” opencpn.conf file as opencpn.x and writing a script linked to a desktop icon that removes the new .conf and replaces it with opencpn.x. If OpenCPN fails to open to the previous setup I stop it, click the reset icon and then start OpenCPN again.

Physical Setup

My boat is a Jeanneau Sunfast 32. The HDMIPI chartplotter sits next to the Matsutec GPS/AIS on the chart table. I made a wooded mount for the HDMIPI which works well. The photo of it shows a strange lug on the back. This is a second mount point to hold the HDMIPI in portrait mode but I have found that rotating the screen slows things up a lot so abandoned that idea.

There are 3 lockers next to the chart table. One is dedicated to the power supply for the boat and has the switch panel on the door. A second had previously been used for instruments cut into the door and I have removed these, repaired the holes, and converted the locker to hold the mulltiplexer and all associated nmea wiring connections.

I have put the 2 power stabilisers in the power locker and run wires to a terminal bus in the multiplexer locker.
To avoid having usb/serial connectors and the Rpi rolling around I made an open wooded box-like structure which contains the Rpi and monts the powered USB hub and connectors on the top. All connections from the Rpi GPIO are made to a terminal block on the side of the box.

Electronic Setup

I am running OpenCPN on the chartplotter and KPLEX and Python script on the multiplexer.
The following data comes in via serial/usb : nav data from Matsutec, wind from the masthead, depth and speed from SeaTalk

See CF Post:

Navigation data goes back out via SeaTalk.
Sensor data (barometer, humidity, air temperature, and exhaust temperature) come into the GPIO pins. Python scripts read the sensor data and export it to FIFO files which are in turn read by KPLEX.
KPLEX communicates with the chartplotter via TCP on the ethernet port.
KPLEX also broadcasts all data via wifi.
I can read the nmea messages from the chartplotter on OpenCPN on my tablet or SeaWi.

To Do

1. Wire in the tiller pilot: not really a priority.
2. Turn my Nexus 7 tablet into a reliable Linux unit running OpenCPN for cockpit viewing (I'm fed up with Google and Android; it just gets slower and slower)
3. Write a script to sound an alarm when exhaust temperature rises.
4. Get the sound working on the chartplotter and sound output via bluetooth to the car radio installed on board.
5. A couple of winters ago I made a weather unit which read intermittently from the barometer and humidity sensors and displayed current readings plus a constantly updating graph of the past 3 days. I programmed in Python using tkinter and matplotlib.This is the most useful thing for weather monitoring. I set it on one side because of problems with the touch location reversing on the Waveshare 3.5 inch screen I was using but at the same time I realised that it was going to be a drain on the battery. I thus hope to be able to convert the program to force the multiplexer to wake every 2 hours if asleep and record data to file and then have the viewing program runnable on the chartplotter and reading from the data file on the multiplexer. This will be a next winter project.

NMEA Gateways & Multiplexers

NMEA 0183 devices can be connected to a computer via a USB gateway or multiplexer that has been designed for that purpose. A gateway provides a single input and output whereas a multiplexer provides several inputs and one or more outputs.

Although an NMEA 0183 device can be connected directly to a serial port, this is not recommended since the NMEA uses V.11 (RS-422) signals and serial ports use V.28 (RS-232) signals. The two can inter-work, but reliability cannot be guaranteed.

Most of these devices use serial-USB interface chips made by just two manufacturers: FTDI & Prolific. Both these chip makers provide Windows & Mac OS X device driver downloads on their web sites.
Model Vendor Type Linux Windows Mac OS X
MiniPlex-USB(-AIS) ShipModul  Mux Yes, FTDI driver  Yes, with driver Yes, with driver
USG-1 Actisense  GW     Yes, with driver
NM42U Noland  Mux  Yes    
NMEA,Seatalk,AIS,USB  Mux  Yes  Yes, with driver Yes, with driver
magicPlex8 Mux Yes,Ethernet Yes, Ethernet Yes,Ethernet

Seatalk & NMEA

There are several hardware devices that will provide translation and conversion of Seatalk/SeatalkNS to NMEA.

See these forum threads:

Seatalk/Seatalk1 (3wire) to Nmea 0183  Bidirectional   "Seatalk LInk"
The devices provided here are quite good.
I am using Tiny SeaTalk NMEA Bridge with galvanic isolated USB. Good support.

Nmea 0183 to  Nmea 2000
Articsense NGW-1  (two programmable versions one for Instruments, another includes AIS)
The Actisense NMEA 2000 to NMEA 0183 Gateway is the easiest way to link between a boat’s old and new data networks.  Bidirectional converter from NMEA 0183 to NMEA 2000. Allows use of NMEA 0183 devices on NMEA 2000 network. 10-35 VDC.

Nmea 0183 to SeatalkNS to Nmea2000

Articsense NGW-1-STNG  Convert NMEA 0183 data into SeaTalk NG and vice-versa, providing seamless integration with Raymarine products. The NGW-1-STNG option combines a standard NGW-1-ISO with a Raymarine SeaTalk NG adapter cable to interface legacy instruments to the NMEA 2000 based SeaTalk NG bus. 
Now available with the SeaTalk NG to NMEA 2000 adaptor Cable - STNG-A06045
Conversion Sentences List:

See these links:
Excellent overview of Seatalk, Seatalk1, SeatalkNS:
Boat Projects: Beginners Guide to Raymarine's Seatalk and Derivatives

Raymarine Seatalk or Seatalk1 to/from Nmea0183 Bridge Converter E85001

Raymarine NMEA Multiplexer E55059

Raymarine SeaTalk NG Networking
Raymarine NMEA 0183 Multiplexer

Raymarine Seatalk - NMEA bridge for Brookhouse multiplexer

Thomas Knauf a SeaTalk Technical Reference

Shipnetwork OpenSeaMap-dev

For direct connection to PC or Laptop device use an FTDI USB to Serial Converter.
USB RS232 Cables
From Jamestown Distributors Website

The E55053 SeaTalk 2 / NMEA 2000 Interface Cable (1.5m) is for connecting E-Series displays to Raymarine SeaTalk 2 or 3rd party NMEA 2000 Devices. The SeaTalk 2 / NMEA 2000 Interface Cable features a twist-lock connector at the E-series display end, and a standard 5-pin waterproof SeaTalk 2 style connector at the other.

The E55054 SeaTalk / Alarm Output Interface Cable (1.5m) is for connecting E-Series displays to Raymarine SeaTalk instrument networks. Also supports connection to an external alarm. The SeaTalk / Alarm Output Interface Cable 6-Pin twist lock connector a E-Series display end, and wire leads at the other.

The E85001 PC/NMEA/SeaTalk Interface Box converts signals between SeaTalk, NMEA 0183, and RS232 formats. Enables RayTech navigation software to converse in SeaTalk with compatible devices. Can be used to host PCs running NMEA based navigation software on a SeaTalk network. Also supports operation of the Raymarine Main Alarm when an alarm condition exists on the SeaTalk bus. This item is no longer available

The E86001 PC Serial Data Cable (2M) is used for connecting computers running RayTech navigation software to the E85001 interface box. Also used to tie NMEA GPS units to a PC's serial data port. The cable is fitted with a screw-lock DB-9 female connector on one end, and bare wire leads at the other, suitable for connection to your GPS or PC interface

Seatalk (Seatalk1) to Nmea2000

Raymarine Converter Panbo
Raymarine SeaTalk 1 to SeaTalk ng Converter Kit  
Model #:  E22158  Defender Item #: 254238   $87.99
Works with Select SeaTalk 1 Instruments, GPS sensors and LifeTag, 
Easy Plug-and-Play Connectivity with SeaTalk ng Networks. Good for ST60 Instruments.
Use the Panbo "N2K Cable Mixxing not a big whoop" directly below to connect to Nmea2000.

Modify Raymarine Seatalk NG cable by adding a Nmea2000 Adapter
Panbo:  N2K, cable mixing not a big woop by Ben Ellison and posted on Feb 5, 2008

Raymarine SeaTalk NG To NMEA2000 DeviceNet Male Connector,  Adapter Cable 
Mfg #:
A06046  Defender Item # : 257913   $28.99
NMEA 2000 micro male connector on one end and SeaTalk NG connector on the other end
sed when connecting NMEA2000 standard devices to Raymarine SeaTalkng data network & visa versa.
The adapter cable has a standard white Raymarine spur connection on one end, and a NMEA2000 DeviceNet Male connector on the other. The adapter is approximately 10-inches long.
This adaptor has a DeviceNet connector with pins ("male"). That's what you need to plug into a DeviceNet T-connector as the drop cable.

"I have been advised that these connections will send and recieve data both ways."

"As it turns out, I could not get either of those cables to resolve the ambiquity, and I made my own by cutting some other cables in half and splicing them.
(A male devicenet connector at the tee end of every drop (or "spur" in STng talk) because a standard tee has two female and one male connectors. )   --Seatalk-to-STng converter also produces valid NMEA 2000 PGNs..."

"As far as I can determine, True Wind info is not present on the Seatalk bus, in either Seatalk1 or SeatalkNG, at least in a hybrid system. I have ST60 displays and ST70 pods and displays, and I can only find Apparent Wind data present on either bus. Which means that each display must be calculating its own True Wind data."




Serial Cables

Building a serial (rs232) cable for your gps and/or ais

This article is in not complete. You are welcome to assist in its construction by editing it as well. Everyone is allowed to edit after creating an account and/or logging in.


FTDI RS232 to USB adapter cable
I thought I would pass along my experience with FTDI's RS232 to USB adapter
cable. I got mine from Mouser Electronics ( part number 895-TTL-232R-5V-WE).

One end is USB type A male. The other end is tinned wire.

I connected pin 2 to Data Out and pin 5 to Ground. The output I saw (using
either hyperterm or tera term) was garbled. The problem was that RS232 wants 0
to -5 V and my instrument was putting out 0 to 5 V.

I was able to use a utility program from FTDI
( User's Guide\
) to invert the expected input on that pin and every thing worked.

If your nav instrument actually uses the RS422 protocol called for by the NMEA
standard, FTDI has a similar cable for that.

The part number above is for a cable with a black, opaque USB plug. There is a
"BT" option that has a black cable and a transparent plug with a couple of LEDs
in it. Besides letting you know the thing is working, it could provide a little
entertainment on night watches.

I like this adapter since it is a single stage, single part solution.

Coleman Blake

RS-232 & RS-422/485

RS232-RS422 Differences and Details

RS-232 vs RS-422/485 main difference on a physical interface level is that

RS-232 uses 3 wires plus common ground: one wire for Tx, one wire for Rx. Both Tx and Rx are referenced to a common ground. In other words: RS-232 is voltage driven. In RS-232 both Tx and Rx are referenced to a common ground, with common GND is achieved by a third wire connecting equipment GNDs on both ends. (In broader scope, I have seen setups where only two wires were used (Tx, Rx) and the GND reference was provided as a part of a common supply GND or common chassis. Not a good engineering practice and well beyond the scope of our topic.) So in summary, yes, RS-232 is two data wires with voltages referenced to a third wire.

RS-422/485 uses 4 wires: a pair of wires wires for Tx (Tx+/Tx-) and a pair of wires for Rx (Rx+/Rx-). These pairs create two current loops. In other words: RS-422/485 are current driven.

Voltage driven interfaces are cheaper (less wires) but more sensitive to noise, while current loops show high immunity to electro-magnetic interference and are preferred in industrial environments (well, *were* preferred, nowadays most new designs are optical fibre).

However, both RS-232 and RS-422 are capable of speeds well into Megabit/s range although it is rare to see them used at such speeds.

Some Detaiis about RS-232 and RS-422
RS-232 and RS-422, similar data speed with different signal characteristics (line length different) both do 38400 bps for AIS.
RS-422(/485) is often referred as industrial because of its capability over longer distances.
RS-442 operates on higher voltage and has tw separate loops so is less sensitive, support cable greater distances (100 meters). RS-232: 0<>+12V    RS-422: -12V<>+12V
Mixing of the two systems, e.g. RS-232 connected to RS-422, can perhaps work but it's not recommended.
RS-442 connected to an old RS-232 PC port can sometimes damage the port (too high voltage).
RS-422(Rx) can sometimes read RS-232(Tx) if the circuit detects the lower voltage but certain messages will likely be missed.

Now, with technology cleared up a bit, a little troubleshooting advice from a long term SysOp. The easy way to see if a problem is with the converter or with a device not sending data is:
1. Disconnect the device from the converter.
2. Connect pin 2 & 3 together at the converter (assuming a RS-232 DB-9 connector; in other words, short Tx with Rx)
3. Run a computer terminal program with the converter attached and connect to the (emulated) serial interface of the converter.
4. Set data transmission to NO FLOW CONTROL (i.e. no XON/XOFF, no RTS/CTS), any speed and parity/stop bits should do here.
5. Check that 'local echo' option of your terminal emulator is OFF,
4. Start typing.
5. If the typing is echoed back to the terminal, converter is transmitting/receiving and drivers are performing.
6. If doubled echo is seen it is also OK, it means that 'local echo' option was left on.
7. If no echo is seen, investigate on the PC side.

Now, after checking your converter,
1. Remove the short between pins 2&3 and connect data cable from your device to the converter.
2. Set data speed and parity to correct values.
3. Look at your terminal program again. Any incoming data present?
4. If yes, device is transmitting and link is working correctly. Time to configure nav software.
5. If not, investigate cable and device further.

Next problem are the RS232/USB converters especially their drivers for Windows...
You will know which RS you have on the device from the instruction manual of the device.
Once you are sure which you have, RS-232 and RS-422 you will need to get the proper serial converter to USB.
1. Install your RS-422-to-USB converter driver,
2. Open Device Manager (Windows) & expand the Ports to see your virtual port -- probably COM3 or COM4.
3. Click the Port Settings tab and set Bits per second to  or 4800bps for GPS or 38,400bps.
4. Keep the default settings for the rest: 8-N-1-N.
5. Launch OpenCPN,
6. Open the configuration menu -> Connections
7. Add a Connection (your virtual port number).
8. Set the port to 4800 or 38,400.
9. Click the Show NMEA Debug Window
Hopefully you will see your AIS NMEA sentences streaming through.

In Windows all usb connections are recorded in a file, and when a USB device is removed, the drivers remain. You should always try to plug the USB device into the same port as before if at all possible. Label your USB Hub and Cables. If you have used USB a lot, with different devices, you may want to carefully clear out all the historic settings of usb in windows. There are several usb tools which will allow you to inspect this list and remove individual entries. Doing this (avoiding hd etc). Helped my computer's usb behavior. Label all usb cables and ports.
How to easily remove old USB device drivers:

This thread on CF may be useful.
How to Connect AIS to laptop
For Diagram of the pinout

USB (PC) to Nmea 2000

Actisense NGW-1-USB
Connected it to a SimNet network (Nmea2000)  and plugged the USB into my computer. This gave the traffic on the network except for AIS communication.

From the Actisense manual I learned that there are two varients of the NGW-1-USB:
1. Standard
2. AIS version

I had the standard.  Fortunately, the difference is only in the firmware and I was able to update to the AIS version by downloading from the Actisense website.

USB to Autopilot

What number pins do I use to send data to autopilot on a usb to serial? ( Is it 3 and 5)

Serial RS232 (DB-9)

If you want to transmit to the AP then the Tx (3) pin from the USB-serial has to go to the Rx (2) pin of the autopilot.
To get data from the AP into the PC you have to connect the other two crossed.
So in short: pin 5 to pin 5, pins 2 and 3 crossed.
The input pins on the autopilot show no tx /rx or gnd only hi and low but on the output from ocpn are tx and gnd . Which should be on tx-rx the hi or low?
Input hi = Rx (receive) on the AP side - here goes the Tx from OCPN
Input lo = GND
When talking about lo and hi that's RS422 speak (differential lines) and as Gerhard stated there should be no problem with modern RS232 connectors.
Remember that while RS-232 Serial uses a +/-9v signaling scheme, NMEA uses 0-5v.
Only good quality Serial/USB converters will switch on 0-5v, so don't try to get by with a cheap one.
We've used Keyspan converters since our first AIS in 2006 with no problems.
Correct, Keyspan are first choice. However mostly because of driver problems with the cheap ones for the poor Windows people... The small difference between RS422 and RS232 doesn't matter.

Wifi vYacht & Others

vYacht wifi
vYacht Opensource
vYacht SignalK
vYacht Connections


WiFi Rs422 485 Serial Adapter Converter Module Wireless External Dipole Antenna


Wifi repeater to tablet PC

AIS and GPS NMEA data from AIS/GPS receiver can be send out to an tablet or iPad via WiFi (over UDP or TCP).
The following link shows the network settings in OpenCPN.
OpenCPN Networking / repeater to tablet PCs

Quark-elec QK-A023 receiver works like an AP broadcasts AIS messages through WiFi to nearby mobile terminals. Detail:QK-A023 AIS receiver

Wind Sensor/NMEA Output

Clipper Mast Head Unit

Clipper Mast Headunit Has NMEA at 4800 Baud Rate sentences are MWV and XDR not compatible with VWR sentence needed for ST1000 Autopilot but runs guages on OpenCpn

SailTimer Wind Instrument

SolarPV powered, bluetooth
Data in standard NMEA 0183 format works with many apps.
Mini-Server accessory, for converting to wifi or wiring in to NMEA 0183 networks for other marine electronics such as chartplotters.

Autonnic A5120 wind vane

Has NMEA 0183 output. Can be ordered from  View specs at!wind/czjc

Airmar WS-150WX Wind & Weather Sensor with GPS

(New Airmar WS-200WX with Nmea 0183 and NMEA 2000, former PB150/PB200)
AIRMAR WS-150WX WIND and Weather Sensor with GPS etc (new WS-200WX with Nmea 0183 and NMEA 2000, former PB150/PB200)

I like these Device most!
No mechanics and fast wind and additional Data
NMEA 0183 Sentence Structure
$GPDTM   Datum Reference
$GPGGA   GPS Fix Data
$GPGLL  Geographic Position—Latitude and Longitude
$GPGSA GNSS DOP and Active Satellite
$GPGSV Satellites in View
$GPRMC Recommended Minimum GNSS
$GPZDA Time and Date
$HCHDG Heading, Deviation, and Variation
$WIMDA Meteorological Composite   Air Temp, Barometric Preasure
$WIMWD  Wind Direction and Speed
$WIMWV Wind Speed and Angle
$WIMWR Relative Wind Direction and Speed
$WIMWT True Wind Direction and Speed
$YXXDR Transducer Measurements (Roll and Pitch)

AIRMAR WS-150WX Sensor

AIRMAR WS-150WX WIND and Weather Sensor with GPS etc (new WS-200WX with Nmea 0183 and NMEA 2000, former PB150/PB200)

I like these Device most!
No mechanics and fast wind and additional Data
NMEA 0183 Sentence Structure
$GPDTM   Datum Reference
$GPGGA   GPS Fix Data
$GPGLL  Geographic Position—Latitude and Longitude
$GPGSA GNSS DOP and Active Satellite
$GPGSV Satellites in View
$GPRMC Recommended Minimum GNSS
$GPZDA Time and Date
$HCHDG Heading, Deviation, and Variation
$WIMDA Meteorological Composite   Air Temp, Barometric Preasure
$WIMWD  Wind Direction and Speed
$WIMWV Wind Speed and Angle
$WIMWR Relative Wind Direction and Speed
$WIMWT True Wind Direction and Speed
$YXXDR Transducer Measurements (Roll and Pitch)

Autopilot Integration

This article is in not complete. You are welcome to assist in its construction by editing it as well. Everyone is allowed to edit after creating an account and/or logging in.