Bookmark and Share Email this page Email Print this page Print

Marine networking evolution

Aug 30, 2013

Better marine electronics pushes network development

NMEA 2000 networking connectors lined up during a vessel installation.

NMEA 2000 networking connectors lined up during a vessel installation.

Bill Bishop

(page 1 of 2)

It was a heady atmosphere during the 1957 New York Boat Show. The buzzwords were “automotive styling” for boats: prominent space age fins, curved windshields, and chrome. Meanwhile a Raytheon 1700 radar cost just $2,195. What proved the most important development of all, however, was that a group of marine electronics dealers desiring a unified voice formed the National Marine Electronics Association (NMEA).

During the first years NMEA worked on developing better relationships with manufacturers, and over time invited them to join. They engaged the Coast Guard, Federal Communications Commission (FCC) and organizations such as Radio Technical Commission for Maritime Services (RTCM) in discussions. NMEA formally incorporated in 1968, and in the 70s the NMEA News began publication. In time this would morph into Marine Electronics Journal. Finally in 1980, 23 years after its formation, the first NMEA marine electronics communication standard was published. NMEA 0180 was born.

In 1980 the loran was the dominant high tech navigation tool, and autopilots were coming of age. The first NMEA standards bridged the gap between these devices using ASCII English characters and simple serial data communications. NMEA 0180, and its predecessor 0182 version, published in 1982, were a point-to-point communication protocol, and by today’s standards slow and fairly limited. The early versions, however, provided the building blocks for the future.

Bill Bishop

Unlike the handy connectors that are part of the NMEA 2000 standard, NMEA 0183 devices can have a colorful gaggle of thin wires that must be individually connected.

NMEA 0183 started with version 1.5 (4800 bps), and fairly quickly was upgraded into NMEA 0183 version 2.0 in 1992. Since 1989, NMEA has been collaborating with the International Maritime Organization (IMO), and the International Electrotechnical Commission (IEC). With the adoption of NMEA 0183 version 2.0, the IEC essentially mirrored it and created the now de facto international standard IEC 61152. These efforts continue to this day and the IEC standard now incorporates NMEA 2000 by reference.

Serial interface change
One of the big changes between the first versions of NMEA, and the new one was the switch from RS-232 to RS-422 serial data protocols. This changed the wiring and data interconnection requirements of NMEA 0183. RS-422 supported far high-data transfer rates, and more important it was inherently more resistant to the electrical noise often generated on boats. This was the start of the NMEA communication standard most of us are now familiar with. The newest version, NMEA 0183 4.10, according to NMEA, is in theory backward compatible to version NMEA 0183 2.0. This is generically correct, but factors including manufacturers software can preclude this from actually happening. There is also a NMEA 0183 high speed (38,400 bps) standard used for AIS data transmission, and other higher bandwidth applications.

Technological development has always been the driver in changes to the NMEA standards. When satellite GPS, and AIS information became available, new data packages or “sentences” had to be created. When technologies like loran become obsolete, old sentences are deleted. Currently there are 153 NMEA 0183 sentences.

That’s not the whole picture, however. An issue with the NMEA 0183 communications is that many manufacturers wrote and used proprietary sentences to enhance their own systems’ capabilities. Although the NMEA’s communication standards are consistent, some manufacturers’ software implementation and interpretation may differ. Will a system ignore another system’s proprietary NMEA sentence or choke on it? Does the chartplotter’s software support newly added NMEA features? And so on.

Implementation of NMEA 0183 electrical interfaces have always been a bit clumsy, and at times it can be at best an inscrutably confusing affair. In most cases it consists of a fat wire with many smaller gauge wires with lots of pretty colors hanging out the end of it.

A special vocabulary
Interfacing NMEA 0183 devices requires knowing a special vocabulary. We have “talkers” that send data (TX), and “listeners” that hear data (RX). Talkers can often send data to several listeners, but a listener can only hear one talker. NMEA wiring has assorted, and not very standard, nomenclature. For example TX+ can also be called TX A. Ship grounds may be needed to complete circuits or NMEA grounds might be required. These variants of wiring schemes can make it difficult for someone not familiar with the details to do NMEA connections.

The large players are still supporting the older NMEA 0183 protocol up to a point, and most show no significant pull back from NMEA 183 hardware communications at this time. The overall number of ports available for NMEA 0183 communication doesn’t generally seem to be shrinking. Software support does vary, and shows little efforts are being made to move up to the newer versions of NMEA 0183. Furuno’s NavNet systems, including the new TZtouch via a gateway, supports versions up to 3.0 (circa 2000). Garmin and Raymarine both support versions up to 3.1 (circa 2002), and Simrad supports up to 4.0 (circa 2008).

Bill Bishop

OneNet is NMEA’s high bandwidth network layer that will take  advantage of Ethernet.

Legacy gear
The big reason NMEA 0183 will remain in place for at least a few more years is to support the vast quantities of legacy non-NMEA 2000 equipment such as autopilots that already exist on vessels. In the end NMEA 0183 may very slowly fade into oblivion for marine electronics, but will continue on in other commercial applications.

NMEA 2000 is a form of Controller Area Network (CAN) bus, technology developed in the early 80s by the automotive industry, and which is closely related to the well known, and understood J1939 communication standard managed by the Society of Automotive Engineers. Work started on the NMEA 2000 (N2K) standard in 1994, and was first published in 2001. It took several more years before it was more widely implemented, and like all new standards it was not without some controversy.

One of the notable elements of the N2K standard was the anticipation of capabilities yet to come, that NMEA 0183 technically would never be able to deal with. This included items such as throttle control, engine data interfaces, power monitoring and management and even IMO Electronic Chart Display and Information System (ECDIS) interfaces. What NMEA couldn’t anticipate was the explosion of mobile devices and wireless technologies, and the increasing rate of technological change. N2K, however, solved the majority of the problems associated with older NMEA 0183 protocol, and will eventually replace it. Wiring has largely became plug and play at the connector level. N2K can be up to 50 times faster, prioritizes data flow, all devices can receive and send data, and it supports up to 50 devices. No more talkers and listeners.

Unlike NMEA 0183 there is an industrial physical wiring standard called DeviceNet that NMEA 2000 is based on. The NMEA 2000 wiring uses a backbone cable with tee’s that allows for the connection of drop cables from compatible devices such as chartplotters or wind instruments. The backbone is separately powered by 12 volts DC, and a 120-ohm resistor is installed at each end. Typically this is all standardized, but there are field replaceable connectors available when needed for tight wire pulls. Some manufacturers have developed their own proprietary wire and connector versions such as Raymarine’s SeaTalk NG, and Simrad’s SimNet. These require adapters to connect other standard NMEA 2000 devices.

NMEA 2000 uses parameter group numbers (PGNs) to identify the data form being sent on the network. For example, PGN 127508 is battery status and includes voltage, current, and battery temperature. There are now more than 150 defined PGNs in the standard and many more are in the process of certification. Data is sent in three forms. If the message is eight bytes or less, it is sent as a single CAN frame. Messages of up to 256 bytes, which are the majority of the messages, are transmitted as fast packets, which are a grouping of frames. The last form is a multi-packet, an aggregate of fast packets not exceeding 1,785 bytes.

The new NMEA OneNet standard is being designed by NMEA to standardize NMEA 2000 messages over IEEE 802.3 as an Ethernet network layer that will reside above NMEA 2000. Currently Ethernet is used to support data that requires a lot of bandwidth such as radar displays and video and each manufacturer has their own proprietary system such as Garmin’s Marine Network. The first OneNet standard is due to be published in late 2014.

Courtesy Actisense

NMEA 0183 devices can be connected to 2000 networks with gateways like the Actisense NGW-1.

We currently have two standard marine data systems to deal with. The older, and slower NMEA 0183, and the more robust, faster NMEA 2000. Bridging between them requires gateways such as Actisense’s NGW-1. These types of devices translate NMEA 0183 to 2000, and NMEA 2000 to 0183. Gateways can also port NMEA data to PCs via USB, and from CAN bus and other networks. The new NMEA OneNet standard will use gateways to communicate with NMEA 2000.

There are many other forms of networks in the marine market place. CAN bus based systems make up the majority. They include NMEA 2000, J1939 used by many engine manufacturers, and supported by instrument and display manufacturers. There are also derivatives such as Mastervolt’s MasterBus, and Brunswick’s SmartCraft to name a few. Most all of these have the capability to be translated into N2K/0183 readable data with a gateway, although it may be a proprietary device.

Edit Module

Add your comment: