Skip to main content
Skip table of contents

FP_A-TP

This message is available from the firmware version 2.102.2.

An updated version of this message is available in our patch release 2.102.3. Please reach out to support@fixposition.com to request the update file.

Note that the VRTK2 is configured for 1 Hz timepulse, also know as pulse per second (PPS), and alignment to UTC. Typically, it will be GPS’ UTC (USNO), but depending on availablility of signals and data it can switch to other UTC. This is a decision done in the u-blox receiver and nothing we can control.

Description:

This message contains information on the timepulse. It is output before the timepulse signal. The time of the timepulse is reported with [ps] precision as a time of week with respect to a time scale. Typically, this is GPS’ UTC (USNO). Note that the [ps] precision does not imply this level of accuracy. The latter is typically around [0.1us] or better.

The message is only output when a time pulse is available, i.e. when the GNSS receiver has a navigation solution. The value of timepulse time (tp_tow_sec and tp-tow_psec) is with respect to time reference (timebase and timeref). The message is output for the upcoming timepulse, providing the information for the next, future timepulse.

Configuration:

  • FP_A-TP_GNSS1 for output of the message for the timepulse for the GNSS1 receiver.

Notes:

  • The time (tp_tow_sec/tp_tow_psec and tp_week) is with respect to the timebase and timeref

  • Software version before 2.110.0 used version 1 of this message, which did not have the tp_week field

Example message:

CODE
$FP,TP,2,GNSS1,UTC,NONE,124508,0.000000000000,18,2349*6D\r\n

Message fields:

#

Field

Format

Unit

Example

Description

1

msg_type

String

-

TP

Message type, always TP for this message

2

msg_version

Numeric

-

2

Message version, always 2 for this version of the TP message, 1 for the old message format in FW 2.102.2

3

tp_name

String

-

GNSS1

Timpulse name (source)

4

timebase

String

-

UTC

Time base (see below), or null if not available

5

timeref

String

-

USNO

Time reference (see below), or null if not available

6

tp_tow_sec

Numeric

s

195391

Timepulse time seconds of week, integer second part (0–604799), or null

7

tp_tow_psec

Float (.12)

s

0.000000000000

Timepulse time seconds of week, sub-second part (0.000000000000–0.999999999999), or null

8

gps_leaps

Numeric

s

18

GPS leapseconds, or null if unknown

9

tp_week

Numeric

-

2233

Timepulse time week number, range 0-9999

Values for timebase:

Value

Description

null

No timepulse alignment

GNSS

Timepulse aligned to GNSS

UTC

Timepulse aligned to UTC

Values for timeref if timebase is GNSS:

Value

Description

GPS

Timepulse aligned to GPS

GAL

Timepulse aligned to Galileo

BDS

Timepulse aligned to BeiDou

GLO

Timepulse aligned to GLONASS

OTHER

Timepulse aligned to other GNSS

other values

Reserved for future use

Values for timeref if timebase is UTC:

Value

Description

NONE

Timepulse aligned to no UTC (no precise UTC parameters known yet)

CRL

Timepulse aligned to Communications Research Laboratory (CRL), Japan

NIST

Timepulse aligned to National Institute of Standards and Technology (NIST)

USNO

Timepulse aligned to U.S. Naval Observatory (USNO)

BIPM

Timepulse aligned to International Bureau of Weights and Measures (BIPM)

EU

Timepulse aligned to European laboratories

SU

Timepulse aligned to Former Soviet Union (SU)

NTSC

Timepulse aligned to National Time Service Center (NTSC), China

OTHER

Timepulse aligned to other/unknown UTC

other values

Reserved for future use

JavaScript errors detected

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

If this problem persists, please contact our support.