beautypg.com

7 time & date (zda), Example, Units – Rikaline GPS-22 User Manual

Page 11: Rikaline, 2 rtcm received data

background image

GPS-22 Manual

Rikaline

Specifications subject to change without prior notice

Rikaline

Marketing Corp.

End of message termination


(1) All “course over ground” data are geodetic WGS84 directions.

4.1.7 Time & Date (ZDA)

Table 4-11 contains the values for the following example:

$GPVTG,114523.62,12,04,2001,10,34*6E


Table 4-11 ZDA Data Format

Name Example

Units

Description

Message ID

$GPZDA

ZDA protocol header

Hour, Min, Sec, Sub

Sec

114523.62

Hhmmss.ss

Day

12

Day in UTC, 01to 12

Month

04

Month in UTC, 01 to 12

Year

2001

Year in UTC

Local Zone Hours

10

Local zone hours, +/- 13 hours

Local Zone Minutes

34

L

ocal zone minutes, 0 to +59

Checksum *6E

End of message termination


4.2 RTCM Received Data

The default communication parameters for DGPS Input are 9600 baud, 8 data bits, stop bit, and no

parity. Position accuracy of less than 5 meters can be achieved with the GPS-22 by using Differential GPS
(DGPS) real-time pseudo-range correction data in RTCM SC-104 format, with message types 1, 5, or 9. As
using DGPS receiver with different communication parameters, GPS-22 may decode the data correctly to
generate accurate messages and save them in battery-back SRAM for later computing.

4.3 Syntax Setting
4.3.1 Basic Manufacturing Default:


Datum: WGS84.
Baud Rate: 9600/4800.
Output: GGA, GSA, GSV, RMC or by demand.

* Details please see paragraph 4.4


4.3.2 Output Setting
4.3.2.1 General Description

The NMEA Standard v2.1 dictates that proprietary NMEA sentences have the following structure:

$Paaaxxxxxxxxxxxxx*hh

where aaa – mnemonic code, XEM in our case; xxxxxxxxx…– data; hh – sentence checksum

Two types of input sentences are defined: query and set. Query sentences request certain information from
the receiver. Set sentences allow configuring the receiver with certain configuration parameters or forcing
the receiver to perform a specific action. For each type of input sentences, a corresponding output response
sentence is defined.
For a query sentence, the response sentence contains requested data. For a set sentence, the response
sentence contains the status of the action requested in the set sentence. Taking these aspects into account,
the following is the general structure of the specific NMEA sentence:

$PXEMmaa,x1,x2,x3,x4,….,xN*hh