Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

NMEA 0183

From Wikipedia, the free encyclopedia
Communication standard for marine electronics

NMEA 0183 is a combined electrical and data specification for communication betweenmarine electronics such asecho sounder,sonars,anemometer,gyrocompass,autopilot,GPS receivers and many other types of instruments. It has been defined and is controlled by theNational Marine Electronics Association (NMEA). It replaces the earlierNMEA 0180 andNMEA 0182 standards.[1] In leisure marine applications, it is slowly being phased out in favor of the newerNMEA 2000 standard,[2][3] though NMEA 0183 remains the norm in commercial shipping.

Details

[edit]

The electrical standard that is used isEIA-422, also known as RS-422, although most hardware with NMEA-0183 outputs are also able to drive a singleEIA-232 port. The standard calls for optically isolated inputs. There is no requirement for isolation for the outputs.

The NMEA 0183 standard uses a simpleASCII,serial communications protocol that defines how data are transmitted in a "sentence" from one "talker" to multiple "listeners" at a time. Through the use of intermediate expanders, a talker can have a unidirectional conversation with a nearly unlimited number of listeners, and usingmultiplexers, multiple sensors can talk to a single computer port.

At theapplication layer, the standard also defines the contents of each sentence (message) type, so that all listeners can parse messages accurately.

While NMEA 0183 only defines an RS-422 transport, there also exists a de facto standard in which the sentences from NMEA 0183 are placed inUDP datagrams (one sentence per packet) and sent over an IP network.

The NMEA standard is proprietary and sells for at least US$2000 (except for members of the NMEA) as of September 2020.[4][5] However, much of it has been reverse-engineered from public sources.[6][7]

UART settings

[edit]
TypicalBaud rate4800
Data bits8
ParityNone
Stop bits1
HandshakeNone

There is a variation of the standard called NMEA-0183HS that specifies a baud rate of 38,400. This is in general use byAIS devices.

Message structure

[edit]
  • All transmitted data are printableASCII characters between 0x20 (space) to 0x7e (~)
  • Data characters are all the above characters except the reserved characters (See next line)
  • Reserved characters are used by NMEA0183 for the following uses:
ASCIIHexDecUse
<CR>0x0d13Carriage return
<LF>0x0a10Line feed, end delimiter
!0x2133Start of encapsulation sentence delimiter
$0x2436Start delimiter
*0x2a42Checksum delimiter
,0x2c44Field delimiter
\0x5c92TAG block delimiter
^0x5e94Code delimiter for HEX representation of ISO/IEC 8859-1 (ASCII) characters
~0x7e126Reserved
  • Messages have a maximum length of 82 characters, including the $ or ! starting character and the ending <LF>
  • The start character for each message can be either a $ (For conventional field delimited messages) or ! (for messages that have special encapsulation in them)
  • The next five characters identify the talker (two characters) and the type of message (three characters).
  • All data fields that follow are comma-delimited.
  • Where data is unavailable, the corresponding field remains blank (it contains no character before the next delimiter – seeSample file section below).
  • The first character that immediately follows the last data field character is an asterisk, but it is only included if a checksum is supplied.
  • The asterisk is immediately followed by achecksum represented as a two-digithexadecimal number. The checksum is thebitwise exclusive OR ofASCII codes of all characters between the$ and*, not inclusive. According to the official specification, the checksum is optional for most data sentences, but is compulsory for RMA, RMB, and RMC (among others).
  • <CR><LF> ends the message.

As an example, a waypoint arrival alarm has the form:

$GPAAM,A,A,0.10,N,WPTNME*32

Another example for AIS messages is:

!AIVDM,1,1,,A,14eG;o@034o8sd<L9i:a;WF>062D,0*7D

NMEA sentence format

[edit]

The main talker ID includes:[8][9]

NMEA message mainly include the following "sentences" in the NMEA message:[10]

SentenceDescription
$Talker ID+GGAGlobal Positioning System Fixed Data
$Talker ID+GLLGeographic Position—Latitude and Longitude
$Talker ID+GSAGNSS DOP and active satellites
$Talker ID+GSVGNSS satellites in view
$Talker ID+RMCRecommended minimum specific GPS data
$Talker ID+VTGCourse over ground and ground speed

One example, the sentence for Global Positioning System Fixed Data for GPS should be "$GPGGA".

Vendor extensions

[edit]

Most GPS manufacturers include special messages in addition to the standard NMEA set in their products for maintenance and diagnostics purposes. Extended messages begin with "$P". These extended messages are not standardized.

Software compatibility

[edit]

NMEA 0183 is supported by various navigation and mapping software. Notable applications include:

Sample file

[edit]

A sample file produced by a Tripmate 850 GPS logger. This file was produced inLeixlip,County Kildare,Ireland. The record lasts two seconds.

$GPGGA,092750.000,5321.6802,N,00630.3372,W,1,8,1.03,61.7,M,55.2,M,,*76$GPGSA,A,3,10,07,05,02,29,04,08,13,,,,,1.72,1.03,1.38*0A$GPGSV,3,1,11,10,63,137,17,07,61,098,15,05,59,290,20,08,54,157,30*70$GPGSV,3,2,11,02,39,223,19,13,28,070,17,26,23,252,,04,14,186,14*79$GPGSV,3,3,11,29,09,301,24,16,09,020,,36,,,*76$GPRMC,092750.000,A,5321.6802,N,00630.3372,W,0.02,31.66,280511,,,A*43$GPGGA,092751.000,5321.6802,N,00630.3371,W,1,8,1.03,61.7,M,55.3,M,,*75$GPGSA,A,3,10,07,05,02,29,04,08,13,,,,,1.72,1.03,1.38*0A$GPGSV,3,1,11,10,63,137,17,07,61,098,15,05,59,290,20,08,54,157,30*70$GPGSV,3,2,11,02,39,223,16,13,28,070,17,26,23,252,,04,14,186,15*77$GPGSV,3,3,11,29,09,301,24,16,09,020,,36,,,*76$GPRMC,092751.000,A,5321.6802,N,00630.3371,W,0.06,31.66,280511,,,A*45

Note some blank fields, for example:

  • GSV records, which describe satellites 'visible', lack the SNR (signal–to–noise ratio) field for satellite 16 and all data for satellite 36.
  • GSA record, which lists satellites used for determining afix (position) and gives aDOP of the fix, contains 12 fields for satellites' numbers, but only 8 satellites were taken into account—so 4 fields remain blank.

Revisions

[edit]

NMEA 0183 continued to be maintained separately: V4.10 was published in early May 2012, and an erratum noted on 12 May 2012.[15] On November 27, 2018, it was issued an update to version 4.11, which supportsGlobal Navigation Satellite Systems other thanGPS.[16] As of December 2023, NMEA has published the version 4.30 which replaces Version 4.11 and includes updates to the entire suite of GNSS sentences with significant interface updates for the use of GPS, GLONASS, GALILEO, BDS, QZSS, and NavIC/IRNSS satellite systems.[17][18]

History of NMEA 0183 Versions
Ver.YearChangesRefs
1.??1983Initial release
2.001992Migrate fromRS-232 toRS-422
2.011994
2.101995
2.201997
2.301998
3.002000
3.012002
4.002008
4.102012
4.112018
4.302023
History of NMEA 0183-HS Versions
Ver.YearChangesRefs
1.002000Initial release of 38.4K baud, known as "high speed"
1.012012

See also

[edit]

References

[edit]
  1. ^Peter Bennett (Sep 15, 1997)."The NMEA FAQ". Archived fromthe original on 2014-02-15. Retrieved2013-10-21.
  2. ^"NMEA 0183 vs NMEA 2000". November 2018. Archived fromthe original on 2013-08-19. Retrieved2020-10-20.
  3. ^Spitzer, Steve. (May 2009)."NMEA 2000 white paper"(PDF). Archived fromthe original(PDF) on 2021-03-02. Retrieved2020-10-20.
  4. ^"Publications and Standards from the National Marine Electronics Association (NMEA) / NMEA 0183". NMEA. November 2008. Archived fromthe original on 2013-10-21. Retrieved2013-10-21.
  5. ^"National Marine Electronics Association - NMEA".www.nmea.org. Archived fromthe original on 2022-03-31. Retrieved2020-09-24.
  6. ^Raymond, Eric S. (March 2019)."NMEA Revealed".
  7. ^Dale DePriest."NMEA data". Archived fromthe original on 2020-10-20. Retrieved2020-10-20.
  8. ^Eric S. Raymond (2024-05-26)."NMEA Revealed - Talker IDs". Retrieved2024-05-31.
  9. ^"NMEA 0183 - Standard For Interfacing Marine Electronic Devices - Talker Identifier Mnemonics"(PDF). 2020-01-31. Archived fromthe original(PDF) on 2022-09-02.
  10. ^Donald Choi."Introduction to GPS Data NMEA & RTCM". p. 15. Retrieved2024-05-31.[dead link]
  11. ^"Google Maps for Android". Retrieved2013-10-21.
  12. ^Marc Balmer (2006–2008)."/sys/kern/tty_nmea.c".BSD Cross Reference.OpenBSD.
  13. ^"ObserVIEW - Free Vibration Analysis Software". Retrieved2022-10-18.
  14. ^"QGIS Documentation - Live GPS tracking".GitHub. Retrieved2024-03-06.
  15. ^"ERRATA # 0183 120512"(PDF). NMEA. Archived fromthe original(PDF) on 2016-04-17. Retrieved2013-10-21.
  16. ^"NMEA PUBLISHES UPDATED VERSION OF NMEA 0183 FOR NEW GLOBAL SATELLITE SYSTEMS"(PDF). November 2018. Archived fromthe original(PDF) on 2019-01-31. Retrieved2019-01-30.
  17. ^"NMEA 0183 - Latest Version of NMEA 0183 (Version 4.30)".National Marine Electronics Association (NMEA) - Marine Electronics Standards, Training & Certification. Retrieved2025-11-25.
  18. ^"NMEA PUBLISHES NEW VERSION OF NMEA 0183 FOR NEW GLOBAL SATELLITE SYSTEMS"(PDF). January 2024.

External links

[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=NMEA_0183&oldid=1324066764"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2026 Movatter.jp