UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`GORDON * HOWARD ASSOCIATES, INC.
`Petitioner
`
`v.
`
`LUNAREYE, INC.
`Patent Owner
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`______________________________________________________
`
`INTER PARTES REVIEW OF U.S. PATENT NO. 6,484,035
`CASE NO. IPR2014-01213
`______________________________________________________
`
`
`
`Before MICHAEL W. KIM, GEORGIANNA W. BRADEN, and
`J. JOHN LEE, Administrative Patent Judges.
`
`
`
`
`
`
`
`LUNAREY EXHIBIT 2019
`
`
`
`LUNAREYE EXHIBIT 2019
`
`

`

`NATIONAL MARINE ELECTRONICS ASSOCIATION
`
`NMEA 0183
`
`STANDARD FOR INTERFACING MARINE ELECTRONIC DEVICES
`
`Version 2.01
`
`August 1, 1994
`
`COPYRIGHT® NMEA 1994
`
`LUNAREYE EXHIBIT 2012
`
`

`

`LUNAREYE EXHIBIT 2012
`
`LUNAREYE EXHIBIT 2012
`
`

`

`,.,
`
`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`CONTENTS
`
`PREFACE
`
`1. INTRODUCTION
`
`2. MANUFACTURER'S DOCUMENTATION
`
`3. HARDWARE SPECIFICATION
`
`4. DATA TRANSMISSION
`
`5. DATA FORMAT PROTOCOL
`
`6. DATA CONTENT
`
`7. APPLICATIONS
`
`APPENDIX I - Sentences Not Recommended For New Designs
`
`APPENDIX II - Glossary or Terms
`
`APPENDIX III -Manufacturer's Mnemonic Codes
`
`INDEX
`
`NMEA 0183 Version 2 .0 1 - - - - - - - - - - - -
`
`I
`
`LUNAREYE EXHIBIT 2012
`
`

`

`LUNAREYE EXHIBIT 2012
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`Preface .......................................................... I
`Availability and Updates of the Standard ................................. 1
`1. Introduction .................................................... 2
`1.1 Scope ................................................... 2
`1.2 Intended Application and Limitations on Use ...................... 2
`1.3 Definitions ............................................... 2
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ............... 2
`1.4 References
`2. Manufacturer's Documentation ...................................... 3
`3. Hardware Specification ............................................ 3
`....................................... 3
`3.1 Interconnecting Wire
`3.2 Conductor Definitions ....................................... 4
`3.3 Electrical Connections/Shield Requirements ....................... 4
`3.4 Connector ............................................... 4
`3.5 Electrical Signal Characteristics ............................... 4
`3.5.1 Signal State Definitions ............................... 4
`3.5.2 TALKER Drive Circuits ............................... 4
`3.5.3 LISTENER Receive Circuits ............................ 4
`3.5.4 Electrical Isolation ................................... 5
`3.5.5 Maximum Voltage on Bus .............................. 5
`4. Data Transmission ............................................... 6
`5. Data Format Protocol ............................................. 6
`5.1 Characters ............................................... 6
`5.1.1 Reserved Characters .................................. 6
`5.1.2 Valid Characters .................................... 6
`5.1.3 Undefined Character ................................. 6
`5.1.4 Character Symbols ................................... 7
`.................................................. 7
`5.2 Fields
`5.2.1 Address Field ....................................... 7
`5.2.2 Data Fields ........................................ 7
`5.2.3 Checksum Field ..................................... 8
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
`5.3 Sentences
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
`5.3.1 Approved Sentences
`5.3.2 Query Sentences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
`5.3.3 Proprietary Sentences
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
`5.3.4 Valid Sentences .................................... 12
`5.3.5 Sentence Transmission Timing ......................... 12
`5.3.6 Additions to Approved Sentences ........................ 12
`6. Data Content
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
`TABLE 1 • RESERVED CHARACTERS ........................... 13
`TABLE 2- VALID CHARACTERS ............................... 13
`TABLE 3- CHARACTER SYMBOL TABLE ......................... 14
`TABLE 4 ·TALKER IDENTIFIER MNEMONICS .................... 15
`TABLE 5 ·APPROVED SENTENCE FORl'viATTERS
`................. 16
`TABLE 6 • FIELD TYPE SUMl'viARY ............................. 18
`6.3 Approved Sentences
`. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
`7. Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`II
`
`LUNAREYE EXHIBIT 2012
`
`

`

`LUNAREYE EXHIBIT 2012
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`Preface
`
`NMEA Interface Standards are intended to serve the public interest by facilitating interconnection
`and interchangeability of equipment, minimizing misunderstanding and confusion between
`manufacturers, and assisting purchasers in selecting compatible equipment.
`
`Standards are adopted by NMEA without regard to whether or not their adoption may involve
`patents on articles, materials or processes. By such action, NMEA does not assume any liability to
`any patent owner, nor does it assume any obligation whatever to parties adopting these Standards.
`
`This Standard defines electrical signal requirements, data transmission protocol and timing, and
`specific sentence formats for a 4800 baud serial data bus. Each bus may have only a single TALK(cid:173)
`ER but may have multiple LISTENERs.
`
`Because of differences in baud rate and other transmission parameters, NMEA 0183 data is not
`directly compatible with NMEA 0180 or NMEA 0182 Standards.
`
`Equipment that is specified by IMO to meet the SO lAS regulations is governed by the requirements
`of IEC 1162-1: Digital Interfaces. Maritime Navigation and Radiocommunications Equipment and
`Svstems. The IEC Standard is aligned closely with the NMEA 0183 Standard. Where possible,
`differences between the two documents, and sections that pertain specit1cally to IEC requirements,
`are indicated herein by
`the symbol "*" in the margin.
`
`Availability and Updates of the Standard
`
`This standard may be modit1ed by action of the NMEA Interface Standards Committee as the
`need arises.
`
`Updates to this Standard are published periodically in:
`
`Marine Electronics - The Official Journal of the NMEA
`National Marine Electronics Association
`P.O. Box 3435
`New Bern, NC 28564-3435
`U.S.A.
`
`For additional or updated copies
`of this standard, contact:
`
`l:'<"MEA Executive Director
`P.O. Box 3435
`New Bern, NC 28564-3435
`U.S.A.
`
`Telephone: (919) 637-7759
`FAX: (919) 637-8136
`
`For technical information, contact:
`
`Chairman, NMEA 0183 Standards
`Committee:
`
`Frank Cassidy
`Datamarine International, Inc.
`53 Portside Drive
`Pocasset, MA 02559
`U.S.A.
`
`Telephone: (508) 563-7151
`FAX: ( 508) 564-4 707
`
`NMEA 0183 Version 2 .0 1 - - - - - - - - - - - -
`
`1
`
`LUNAREYE EXHIBIT 2012
`
`

`

`LUNAREYE EXHIBIT 2012
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`I. Introduction
`
`1.1 Scope
`
`This standard is developed to permit ready and satisfactory data communication between electronic
`marine instruments, navigation equipment and communications equipment when interConnected via
`an appropriate system.
`
`1.2 Intended Application and Limitations on Use
`
`This standard is intended to support one-way serial data transmission from a single TALKER to one
`or more LISTENERs. This is data in printable ASCII form and may include information such as
`position, speed, depth, frequency allocation, etc. Typical messages might be 20 to a maximum of 79
`characters in length and generally require transmission no more often than once per second.
`
`The electrical definitions in this standard are not intended to accommodate high-bandwidth
`applications such as radar or video imagery, or intensive database or file transfer applications.
`
`Since there is no provision for guaranteed delivery of messages and only limited error checking
`capability, this standard should be used with caution in critical applications.
`
`1.3 Definitions
`
`1.3.1 General
`
`Common terms are defined in Appendix II, Glossary, of this Standard. Where there is a cont1ict
`terms shall be interpreted wherever possible in accordance with the references in Section 1.4.
`
`1.3.2 TALKERs
`
`A TALKER is any device which sends data to other devices within this standard. The type of
`TALKER is identitied by a 2-character mnemonic as listed in Section 6.2 (Table 4).
`
`1.3.3 LISTENERs
`
`A LISTENER is any device which receives data from another device within this standard.
`
`1.4 References
`
`1.4.1 American National Standards Institute:
`1. ANSI X 3.15 1976 Al'ISI Character Structure and Character Parity Sense for
`Serial-by-Bit Communication
`2. Al'ISI X 3.16 1976 ANSI Bit Sequencing of the Al'IS Code for Information Interchange
`in Serial-By-Bit Data Transmission.
`3. ANSI X 3.4 1977 ANSI Code for Information Interchange
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`2
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`1.4.2 Electronic Industries Association Standards:
`A. EIA-422-A December 1978 (CCI1T X.27/V.ll)
`
`1.4.3 International Electrotechnical Commission:
`3, rue de Varembe
`P.O. Box 131
`1211 Geneva 20
`SWITZERLAND
`A. IEC 945, Marine Navigational Equipment - General Requirements
`B. IEC 1162-1: Digital Interfaces. Maritime Navigation and Radiocommunications
`Equipment and Systems
`
`1.4.4 American Practical Naviaator, Defense Mapping Agency Hydrographic/Topographic Center,
`Publication No. 9, DMA Stock No. NVPUB9V1, Volumes I and II
`
`1.4.5 Interface Control Document, Navstar GPS Space Segment/Navigation User Interface.
`Rockwell International Corporation Document No. ICD-GPS-200 Revision B (November
`30, 1987)
`
`2. Manufacturer's Documentation
`
`Operator"s manuals or other appropriate literature provided for equipment that is intended to meet
`the requirements of this standard shall contain the following information:
`
`1. Identification of the A and B signal lines.
`2. The output drive capability as a TALKER.
`3. A list of approved sentences, noting unused fields, Proprietary sentences transmitted
`as a TALKER, and transmission interval for each sentence.
`4. The load requirements as a LISTENER.
`5. A list of sentences and associated data fields that are required as a LISTENER.
`6. The current software and hardware revision if this is relevant to the interface.
`7. An electrical description or schematic of the LISTENER/TALKER input/output
`circuits citing actual components and devices used, including connector type and part
`number.
`8. The Version No. and Date of Update of the standard for which compliance is
`assured.
`
`3. Hardware Specification
`
`One TALKER and multiple LISTENERS may be connected in parallel over an interconnecting wire.
`The number of LISTENERS depends on the output capability and input drive requirements of
`individual devices.
`
`3.1 Interconnecting Wire
`
`Interconnection between devices may be by means of a two-conductor, shielded, twisted-pair wire.
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`3
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`3.2 Conductor Definitions
`
`The conductors referred to in this standard are the signal lines "A" and "B", and shield.
`
`3.3 Electrical Connections/Shield Requirements
`
`All signal line "A" connections are connected in parallel with all device "A" connections and all signal
`line "B" connections are connected in parallel with all device "B" connections. The shield should be
`connected to the TALKER chassis and should not be connected at any LISTENER. However, the
`shield should be continuous (unbroken) between all LISTENERs.
`
`3.4 Connector
`
`No standard connector is specified. Wherever possible readily available commercial connectors
`should be used. Manufacturers shall provide means for user identification of the connectors used.
`
`3.5 Electrical Signal Characteristics
`
`This section describes the electrical characteristics of transmitters and receivers.
`
`3.5.1 Signal State Definitions
`
`The idle, marking, logical "1", OFF or stop bit state is defined by a negative voltage on line "A" with
`respect to line "B".
`
`The active, spacing, logical "0", ON or start bit state is defined by a positive voltage on line "A" with
`respect to line "B".
`
`Note that the above "A" with respect to "B" levels are inverted from the voltage input/output
`requirements of standard UARTs and that many line drivers and receivers provide a logic inversion.
`
`3.5.2 TALKER Drive Circuits
`
`No provision is made for more than a single TALKER to be connected to the bus. The drive circuit
`used to provide the signal "A" and the return "B" shall meet, at a minimum, the requirements of
`EIA-422-A (December 1978).
`
`3.5.3 LISTENER Receive Circuits
`
`Multiple LISTENERs may be connected to a singleT ALKER. The LISTENER receive circuit shall
`consist of an optoisolator and should have protective circuits to limit current, reverse bias and power
`dissipation at the optodiode a~ shown in Figure 1. Reference is made to example circuits in Section
`7.0 of this Standard.
`
`The receive circuit shall be designed for operation with a minimum differential input voltage of 2.0
`Volts and shall not take more than 2.0 mA from the line at that voltage.
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`4
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`For reasons of compatibility with equipment designed to earlier versions of this standard, it is noted
`that the "idle, marking, logical "1 ", OFF or stop bit state" had previously been defined to be in the
`range -15 to + 0.5 Volts. The "active, spacing, logical "0", ON or start.bit state" was defined to be
`in the range +4.0 to + 15 Volts while sourcing not less than 15 rnA.
`
`·······················-··································
`LISTENER NO. 2
`··················-··········---··························
`
`PROT£CTIV£
`CIRCUITS
`
`•································· ························
`LISTENER NO. 1
`
`E:IA-422
`
`TALKER
`
`FIGURE I
`
`3.5.4 Electrical Isolation
`
`Within a LISTENER there shall be no direct electrical connection between the signal line, "A",
`return line, "B", or shield and ship's ground or power. Isolation from ship's ground is required.
`
`3.5.5 Maximum Voltage on Bus
`
`The maximum applied voltage between signal lines "A • and "B" and between either line and Ground
`will be in accordance with the EIA-422 specification.
`
`For protection against miswiring and for use with earlier TALKER designs, all receive circuit devices
`should be capable of withstanding 15 volts between signal lines "A" and "B" and between either line
`and ground for an indefinite period.
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`5
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`4. Data Transmission
`
`Data is transmitted in serial asynchronous form in accordance with ANSI standards (reference
`paragraph 1.4.1). The first bit is a start bit and is followed by data bits, least-significant-bit first as
`illustrated by Figure 2. The following parameters are used:
`
`Baud rate
`Data bits
`Parity
`Stop bits
`
`4800
`8 (d7 = 0)
`None
`One
`
`DO
`
`DI
`
`D2
`
`D3
`
`D4
`
`D5
`
`D6
`
`D7
`
`-
`
`1
`
`START
`BIT
`
`5. Data Format Protocol
`
`5.1 Characters
`
`DATA BITS
`
`FIGURE 2
`
`r
`
`1
`
`STOP
`BIT
`
`All transmitted data shall be interpreted as ASCII characters. The most significant bit of the 8-bit
`character shall always be transmitted as zero (d7 = 0).
`
`5.1.1 Reserved Characters
`
`The reserved character set consists of those ASCII characters shown in Section 6.1 (Table !). These
`characters are used for specitic formatting purposes, such as sentence and field delimiting, and may
`not be used in data tields.
`
`5.1.2 Valid Characters
`
`The valid character set consists of all printable ASCII characters (HEX 20 to HEX 7E) except those
`defined as reserved characters. Section 6.1 (Table 2) lists the valid character set.
`
`5.1.3 Undefined Character
`
`ASCII values not specified as either "reserved characters" or "valid characters" are excluded and may
`not be transmitted at any time.
`
`NMEA 0183 Version 2 . 01 - - - - - - - - - - - -
`
`6
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`5.1.4 Character Symbols
`
`When individual characters are used in this standard to define units of measure, indicate the type
`of data field, type of sentence, etc. they will be interpreted according to the character symbol table
`in Section 6.1 (Table 3).
`
`5.2 Fields
`
`A field consists of a string of valid characters, or no characters (null field), located between two
`appropriate delimiter characters.
`
`5.2.1 Address Field
`
`An address field is the first field in a sentence and follows the "$" delimiter, it serves to define the
`start of sentence. Characters within the address field are limited to digits and upper case letters.
`The address field may not be a null field. Only sentences with the following three types of address
`fields may be transmitted:
`
`5.2.1.1 Approved Address Field
`
`Approved address fields consist of five characters defined by this standard. The first two characters
`are the TALKER Identifier, listed in Section 6.2 (Table 4). The next three characters form the
`Sentence Formatter used to define the format and the type of data. Section 6.2 (Table 5) and
`Appendix I list approved Sentence Formatters.
`
`5.2.1.2 Query Address Field
`
`The query address consists of five characters and is used for the purpose of requesting transmission
`of a specitic sentence on a separate bus from an identified TALKER.
`
`The first two characters are the TALKER Identifier of the device requesting data, the next two
`characters are the TALKER ldentitier of the device being addressed and the tina! character is the
`query character "Q".
`
`5.2.1.3 Proprietary Address Field
`
`The proprietary address tield consists of the proprietary character "P" followed by a three-character
`Manufacturer"s Mnemonic Code, used to identify the TALKER issuing a proprietary sentence, and
`any additional characters as required. A list of valid Manufacturer·s Mnemonic Codes is contained
`in Appendix III.
`
`5.2.2 Data Fields
`
`Data Fields in approved sentences follow a •; delimiter and contain valid characters in accordance
`with the formats illustrated in Section 6.2 (Table 6). Data fields in proprietary sentences contain
`only valid characters but are not defined by this standard.
`
`Because of the presence of variable data fields and null fields, specitic data fields may only be
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - -
`
`7
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`located within a sentence by observing the field delimiters ",'. Therefore it is essential for the
`USTENER to locate fields by counting delimiters rather than counting total number of characters
`received from the start of the sentence.
`
`5.2.2.1 Variable Length fields
`
`Although some data fields are defined to have fixed length, many are of variable length in order to
`allow devices to convey information and to provide data with more or less precision, according to
`the capability or requirements of a particular device.
`
`Variable length fields may be alpha· numeric or numeric fields. Variable numeric fields may contain
`a decimal point and may contain leading or trailing "zeros".
`
`5.2.2.2 Data Field Types
`
`Data fields may be alpha, numeric, alphanumeric, variable length, fixed length, fixed/variable (with
`a portion fixed in length while the remainder varies). Some fields are constant, with their value
`dictated by a specific sentence definition. The allowable field types are summarized in Section 6.2
`(Table 6), Field Type Summary.
`
`5.2.2.3 Null Fields
`
`A null field is a field of length zero, i.e. no characters are transmitted in the field. Null fields shall
`be used when the value is unreliable or not available.
`
`For example, if heading information were not available, sending data of "000" is misleading because
`a user cannot distinguish between '"000'" meaning no data and a legitimate heading of "000'".
`However, a null field, with no characters at all, clearly indicates that no data is being transmitted.
`
`Null fields with their delimiters can have the following appearance depending on where they are
`located in the sentence:
`
`n n
`
`..
`
`It • "
`
`'
`
`"",<CR><LF>"
`
`The ASCII NULL character (HEX 00) shall not be used as the null field.
`
`5.2.3 Checksum Field
`
`A checksum field may optionally be transmitted in any sentence. However some approved sentences
`specifically require the checksum field. The checksum field is the last tield in a sentence and follows
`the checksum delimiter character "*".
`
`The checksum is the 8-bit exclusive OR (no start or stop bits) of all characters in the sentence,
`including"," delimiters, between but not including the."$" and the"*" delimiters.
`
`The hexadecimal value of the most significant and least significant 4 bits of the result are converted
`to two ASCII characters (0-9, A-F) for transmission. The most significant character is transmitted
`first.
`
`NMEA 0183 Version 2 .01 . - - - - - - - - - - - -
`
`8
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`5.3 Sentences
`
`This section describes the general structure of sentences. Details of specific sentence formats are
`found in Section 6.3 and Appendix I. Some sentences may specify restrictions beyond the general
`limitations given in this part of the standard. Such restrictions may include defining some fields as
`fixed length, numeric or text only, required to be non-null, transmitted with a certain frequency, etc.
`
`The maximum number of characters in a sentence shall be 82, consisting of a maximum of 79
`characters between the starting delimiter"$" and the terminating <CR> <LF>.
`
`The minimum number of fields in a sentence is one (1). The first field shall be an address field
`containing the identity of the TALKER and the sentence formatter which specifies the number of
`data fields in the sentence, the type of data they contain and the order in which the data fields are
`transmitted. The remaining portion of the sentence may contain zero or multiple data fields.
`
`The maximum number of fields allowed in a single sentence is limited only by the maximum sentence
`length of 82 characters. Null fields may be present in the sentence and shall always be used if data
`for that field is unavailable.
`
`All sentences begin with the sentence start delimiter character "$" and end with the sentence
`termination delimiter <CR> <LF>.
`
`5.3.1 Approved Sentences
`
`Approved sentences are those designed for general use and detailed in this Standard. Approved
`sentences are listed in Section 6.3 and Appendix I. Preferred sentences are contained in Section 6.3
`and these sentences should be used wherever possible. Appendix I contains sentences that may be
`phased-out of use, are not recommended for new designs, but may be met in practice.
`
`An approved sentence contains, in the order shown, the following elements:
`
`"$"
`<address field>
`(","<data field>]
`
`HEX 24 - Start of sentence
`TALKER identifier and sentence formatter
`Zero or more data tields
`
`(","<data tield>]
`[" .. <checksum tield>]
`<CR><LF>
`
`Optional checksum tield
`Hex OD OA- End of sentence
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - -
`
`9
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`5.3.1.1 Approved Sentence Structure
`
`The following provides a summary explanation of the approved sentence structure:
`
`$aaccc,c--c*hh< CR> <LF>
`
`ASCII
`
`HEX DESCRIPTION
`
`"$"
`
`aaccc
`
`24
`
`Start of Sentence.
`
`Address Field. Alphanumeric characters identifying type of TALKER,
`and Sentence Formatter. The first two characters identify the
`TALKER. The last three are the Sentence Formatter mnemonic code
`identifying the data type and the string format of the successive fields.
`Mnemonics will .be used as far as possible to facilitate readouts by
`users .
`
`• •
`
`2C
`
`Field delimiter. Starts each field except address and checksum fields.
`If it is followed by a null field, it is all that remains to indicate no data
`in a field.
`
`C···C
`
`""'"
`
`hh
`
`Data Sentence block. Follows address tield and is a series of data
`fields containing all of the data to be transmitted. Data field sequence
`is fixed and identified by 3rd and subsequent characters of the address
`field (the "Sentence Formatter"). Data fields may be of variaqle length
`and are preceded by delimiters ",".
`
`2A
`
`Optional Checksum Delimiter. Follows last data tield of the sentence.
`It indicates that the following two alpha-numeric characters show the
`HEX value of the CHECKSUM.
`
`Optional Checksum Field. The absolute value calculated by
`exclusive-OR'ing the 8 data bits (no start bits or stop bits) of each
`character in the Sentence, between, but excluding "$" and "". The
`hexadecimal value of the most signiticant and least significant 4 bits of
`the result are converted to two ASCII characters (0-9, A·F) for
`transmission. The most signiticant character is transmitted first. The
`"CHECKSUM" field is optional, except when indicated as mandatory.
`
`<CR><LF> OD OA
`
`Terminates Sentence.
`
`NMEA 0183 Version 2 .01 . - - - - - - - - - - - -
`
`10
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`5.3.2 Query Sentences
`
`Query sentences are intended to request Approved sentences to be transmitted in a form of two
`way communication. The use of query sentences implies that the LISTENER shall have the
`capability of being a TALKER with its own bus.
`·
`
`The approved Query sentence contains, in the order shown, the following elements:
`
`"$"
`<aa>
`<aa>
`"Q"
`" "
`<ccc>
`["*"<checksum field>]
`<CR><LF>
`
`HEX 24 - Start of sentence
`TALKER Identifier of requester
`TALKER Identifier for device from which data is being requested
`Query character identifies Query address
`Data field delimiter
`Approved sentence formatter of data being requested
`Optional checksum field
`HEX OD OA - End of sentence
`
`5.3.2.1 Reply To Query Sentence
`
`The reply to a Query sentence is the Approved sentence that was requested. The use of Query
`sentences requires cooperation between the devices that are interconnected, a reply to a Query
`sentence is not mandatory and there is no specitied time delay between the receipt of a query ~n·::
`the reply.
`
`5.3.3 Proprietary Sentences
`
`Proprietary sentences provide a means for manufacturers to use the sentence structure detinitions
`of this standard to transfer data which does not fall within the scope of approved sentences. This
`will generally be for one of the following reasons:
`
`1. Data is intended for another device from the same manufacturer, is device specitic, and not
`in a form or of a type of interest to the general user;
`
`2. Data is being used for test purposes prior to the adoption of approved sentences;
`
`3. Data is not of a type and general usefulness which merits the creation of an approved
`sentence.
`
`A proprietary sentence contains, in the order shown, the following elements:
`
`"$"
`"P"
`<aaa>
`[<valid characters> J
`["*"<checksum tield> J
`<CR><LF>
`
`Hex 24 - Start of sentence
`Hex 50 - Proprietary sentence ID
`Manufacturer's Mnemonic code
`Manufacturer's ·data
`Optional checksum field
`Hex OD OA - End of sentence
`
`NMEA 0183 Version 2 .01 - - - - - - - - - - - -
`
`11
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`Beyond limiting overall sentence length and requiring the use of only valid characters, details of
`proprietary data fields will not be included in this standard and need not be submitted for approval.
`However it is required that such sentences be published in the manufacturer's manuals for reference.
`
`5.3.4 Valid Sentences
`
`Approved sentences, Query sentences and Proprietary sentences are the only valid sentences.
`Sentences of any other form are non-valid and shall not be transmitted on the bus.
`
`5.3.5 Sentence Transmission Timing
`
`Frequency of sentence transmission when specified shall be in accordance with the approved
`sentence definitions (Section 6.3 and Appendix I). When not specified, the rate should be
`consistent with the basic measurement or calculation cycle but generally not more frequently
`than once per second.
`
`It is desirable that sentences be transmitted with minimum inter-character spacing, preferably as a
`near continuous burst, but under no circumstance shall the time to complete the transmission of a
`sentence be greater than 1 second.
`
`5.3.6 Additions to Approved Sentences
`
`In order to allow for improvements or additions, future revisions of this Standard may modify
`existing sentences by adding new data fields after the last data field but before the optional checksum
`delimiter character "•" and checksum field. LISTENERs should determine the end of the sentence
`by recognition of <CR> <LF> and ..... rather than by counting field delimiters. The checksum value
`should be computed on all received characters between, but not including,"$" and "•" whether or not
`the LISTENER recognizes all fields.
`
`NMEA 0183 Version 2 .01 . - - - - - - - - - - - -
`
`12
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interlacing Marine Electronic Devices
`
`6. Data Content
`6.1 Character Definitions
`
`<CR>
`<LF>
`$
`•
`
`\
`
`A
`
`TABLE 1 - RESERVED CHARACTERS
`HEX
`DECIMAL
`OD
`13
`OA
`10
`24
`36
`2A
`42
`2C
`44
`21
`33
`5C
`92
`5E
`94
`7E
`126
`
`Carriage return } End of sent-
`Line feed
`} tence delimiter
`Start of sentence delimiter
`Checksum field delimiter
`Field delimiter
`Reserved for future use
`Reserved for future use
`Reserved for future use
`Reserved for future use
`
`34
`35
`
`37
`38
`39
`40
`41
`
`43
`
`Hex Dec
`Space 20
`32
`Reserved
`•
`22
`#
`23
`Reserved
`%
`25
`26
`&
`27
`(
`28
`)
`29
`Reserved
`+
`2B
`Reserved
`20
`2E
`2F
`30
`31
`32
`33
`34
`35
`36
`37
`38
`39
`3A
`3B
`3C
`3D
`3E
`3F
`
`I
`0
`1
`2
`3
`4
`5
`6
`7
`8
`9
`
`<
`=
`>
`?
`
`45
`46
`47
`48
`49
`50
`51
`52
`53
`54
`55
`56
`57
`58
`59
`60
`61
`62
`63
`
`TABLE 2- VALID CHARACTERS
`Hex DEC
`40
`64
`@
`A
`41
`65
`42
`B
`66
`c
`43
`67
`D
`44
`68
`45
`E
`69
`46
`70
`F
`47
`G
`71
`48
`H
`72
`49
`I
`73
`4A
`74
`J
`K
`4B
`75
`L
`4C
`76
`40
`M
`77
`4E
`N
`78
`0
`4F
`79
`p
`50
`80
`51
`81
`Q
`52
`R
`82
`s
`53
`83
`T
`54
`84
`u
`55
`85
`v
`56
`86
`w
`57
`87
`X
`58
`88
`y
`59
`89
`z
`SA
`90
`[
`5B
`91
`Reserved
`1
`50
`Reserved
`SF
`
`93
`
`95
`
`'
`a
`b
`c
`d
`e
`f
`g
`h
`
`Hex DEC
`60
`96
`97
`61
`62
`98
`63
`99
`64
`100
`65
`101
`66
`102
`103
`67
`104
`68
`69
`105
`6A
`106
`107
`6B
`6C
`108
`6D
`109
`6E
`110
`6F
`111
`70
`112
`113
`71
`114
`72
`73
`115
`74
`116
`75
`117
`76
`118
`77
`119
`78
`120
`79
`121
`122
`·7A
`7B
`123
`7C
`124
`70
`125
`}
`Reserved
`
`J
`k
`I
`m
`n
`0
`p
`q
`r
`s
`t
`u
`v
`w
`X
`y
`z
`{
`
`NMEA 0183 Version 2.01
`
`13
`
`LUNAREYE EXHIBIT 2012
`
`

`

`NMEA 0183 - Standard For Interfacing Marine Electronic Devices
`
`6.1 Character Definitions
`(continued)
`
`TABLE 3 - CHARACTER SYMBOL TABLE
`
`Status symbol; Yes; Data Valid; Warning Flag Clear; Auto; Amperes
`Alphabet character variable A through Z or a through z
`Bars (pressure, 1000Mb equal 1 Std. Atm.); Bottom
`Celsius (Degrees); Course-up
`Valid characters; Calculating
`Degrees (of Arc)
`Error; East; Engine
`Fathoms
`Feet
`Great Circle; Green
`Good
`Compass Heading; Head-up; Hertz; Humidity
`Hours; HEX number
`Inches
`Input operation completed
`Kilometers; Km/hour
`Kilograms
`Left; Local; Lost Target
`Latitude; Liters; Liters/second
`Meters; Meters/second; Magnetic; Manual; Cubic Meters
`Minutes; message
`Nautical miles; Knots; North; North-up; Newton
`Numeral; address
`Purple; Proprietary (only when following"$"); Position sensor; Percent
`Query; Target-Being-Acquired
`Right; Rhumb line; Red; Relative; Reference; Radar Tracking; Rev/min
`South; Statute miles; Statute miles/hour; Shaft
`Seconds
`Time difference; True; Track; Tracked-Target
`Test
`Dead Reckoning Estimate
`Sign, if minus ". • (HEX 2D)
`Data invalid; No; Warning Flag Set; Manual; Volt
`West; Water; Wheelover
`Numeric Character variable
`Longitude
`Time
`
`A
`a
`B
`C
`c
`D
`E
`F
`f
`G
`g
`H
`h
`I
`