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
andtp_week
) is with respect to thetimebase
andtimeref
Software version before 2.110.0 used version 1 of this message, which did not have the
tp_week
field
Example message:
$FP,TP,2,GNSS1,UTC,NONE,124508,0.000000000000,18,2349*6D\r\n
Message fields:
# | Field | Format | Unit | Example | Description |
---|---|---|---|---|---|
1 |
| String | - |
| Message type, always |
2 |
| Numeric | - |
| Message version, always |
3 |
| String | - |
| Timpulse name (source) |
4 |
| String | - |
| Time base (see below), or null if not available |
5 |
| String | - |
| Time reference (see below), or null if not available |
6 |
| Numeric | s |
| Timepulse time seconds of week, integer second part (0–604799), or null |
7 |
| Float (.12) | s |
| Timepulse time seconds of week, sub-second part (0.000000000000–0.999999999999), or null |
8 |
| Numeric | s |
| GPS leapseconds, or null if unknown |
9 |
| Numeric | - |
| Timepulse time week number, range 0-9999 |
Values for timebase
:
Value | Description |
---|---|
null | No timepulse alignment |
| Timepulse aligned to GNSS |
| Timepulse aligned to UTC |
Values for timeref
if timebase
is GNSS
:
Value | Description |
---|---|
| Timepulse aligned to GPS |
| Timepulse aligned to Galileo |
| Timepulse aligned to BeiDou |
| Timepulse aligned to GLONASS |
| Timepulse aligned to other GNSS |
other values | Reserved for future use |
Values for timeref
if timebase
is UTC
:
Value | Description |
---|---|
| Timepulse aligned to no UTC (no precise UTC parameters known yet) |
| Timepulse aligned to Communications Research Laboratory (CRL), Japan |
| Timepulse aligned to National Institute of Standards and Technology (NIST) |
| Timepulse aligned to U.S. Naval Observatory (USNO) |
| Timepulse aligned to International Bureau of Weights and Measures (BIPM) |
| Timepulse aligned to European laboratories |
| Timepulse aligned to Former Soviet Union (SU) |
| Timepulse aligned to National Time Service Center (NTSC), China |
| Timepulse aligned to other/unknown UTC |
other values | Reserved for future use |