Skip to main content
Skip table of contents

NMEA-GN-ZDA

Description:

Standard NMEA: Time and date

Configuration:

  • NMEA-GN-ZDA_GNSS for combined (average) output from both receivers

    • The time is the average between GNSS1 and GNSS2.

  • NMEA-GN-ZDA_GNSS1 for output from GNSS 1 receiver

    • This is the standard NMEA ZDA for GNSS1.

  • NMEA-GN-ZDA_GNSS2 for output from GNSS 2 receiver

    • This is the standard NMEA ZDA for GNSS2.

  • NMEA-GN-ZDA_FUSION for output from Fusion

    • The time is from fusion.

  • NMEA-GN-ZDA_GNSS1TOS for top-of-second 1Hz strict NMEA output from GNSS 1 receiver

    • Like NMEA-GN-ZDA_GNSS1, but only the top-of-second message

    • Always strict NMEA (the high-precision NMEA configuration has no effect)

    • The intended use is for time sync applications that use the PPS output of GNSS1

    • See also NMEA-GN-RMC_GNSS1TOS and NMEA-GN-GGA_GNSS1TOS

  • NMEA-GP-ZDA_GNSS, NMEA-GP-ZDA_GNSS1, NMEA-GP-ZDA_GNSS2, NMEA-GP-ZDA_FUSION and NMEA-GP-ZDA_GNSS1TOS

    • Legacy messages. These messages also have GN constellation but the talker ID is “GP”

Example message:

CODE
$GNZDA,090924.00,10,10,2023,00,00*63\r\n

Example message with non-standard high-precision fields:

CODE
$GNZDA,090411.0001,10,10,2023,00,00*69\r\n

Message fields:

#

Field

Format

Unit

Nullable

Example

Description

1

time

hhmmss.ss(ss)

-

Y

151227.40

UTC time (hours, minutes and seconds)

2

day

Integer (01-31)

-

Y

04

Day (UTC)

3

month

Integer (01-12)

-

Y

01

Month (UTC)

4

year

Integer (yyyy)

-

Y

2024

Year (UTC)

5

local_hr

Integer (00-±13)

hr

Y

-3

Local zone hours, always 00 (= UTC)

6

local_min

Integer (00-59)

min

Y

00

Local zone minutes, always 00 (= UTC)

Notes:

  • These messages does not contain any information that would let one tell them apart. Do not enable more than one of these in the same port.

  • This message is according to NMEA 0183 v4.11 (and erratas).

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.