®

PROTEMPIS ACUTIME 360™
MULTI-GNSS SMART ANTENNAUSER GUIDEFor use with:l

Acutime 360 multi-GNSS smart antenna (P/N 106406-XX)l

Acutime 360 Starter Kit (P/N 106222-XX)

Firmware Version 1.08 and later

Version 1.08
Revision B
June 2022
P/N: 107467-00

Legal Notices
Corporate OfficeProtempis
USA
www.protempis.com
Email: support@protempis.com© 2022, Protempis All rights reserved.
Protempis, and the Globe & Satellite logo are trademarks ofProtempis registered in the United States and in othercountries.
All other trademarks are the property of their respective
owners.

Release NoticeThis is the June 2022 release (Revision B) of the Acutime 360
documentation.

The Australian Consumer Law
Our goods come with guarantees that cannot be excluded
under the Australian Consumer Law. You are entitled to a
replacement or refund for a major failure and forcompensation for any other reasonably foreseeable loss ordamage. You are also entitled to have the goods repaired or
replaced if the goods fail to be of acceptable quality and thefailure does not amount to a major failure.
Protempis' warranty (set out below) is in addition to any
mandatory rights and remedies that you may have under theAustralian Consumer Law.

LIMITED WARRANTY TERMS AND CONDITIONS
Product Limited Warranty
Subject to the following terms and conditions, Protempis Inc.
(“Protempis”) warrants that for a period of one (1) year fromdate of purchase this Protempis product (the “Product”) will
substantially conform to Protempis's publicly available
specifications for the Product and that the hardware and any
storage media components of the Product will be substantially
free from defects in materials and workmanship.

Product Software
Product software, whether built into hardware circuitry as
firmware, provided as a standalone computer software
product, embedded in flash memory, or stored on magnetic orother media, is licensed solely for use with or as an integral
part of the Product and is not sold. If accompanied by aseparate end user license agreement (“EULA”), use of any
such software will be subject to the terms of such end user
license agreement (including any differing limited warranty
terms, exclusions, and limitations), which shall control over theterms and conditions set forth herein.
Except for the limited license rights expressly provided herein,
Protempis and its suppliers have and will retain all rights, title
and interest (including, without limitation, all patent, copyright,

trademark, trade secret and other intellectual property rights)
in and to the Product Software and all copies, modifications
and derivative works thereof (including any changes which
incorporate any of your ideas, feedback or suggestions).
You shall not (and shall not allow any third party to): (a)decompile, disassemble, or otherwise reverse engineer the
Product Software or attempt to reconstruct or discover any
source code, underlying ideas, algorithms, file formats orprogramming interfaces of the Product Software by anymeans whatsoever (except and only to the extent thatapplicable law prohibits or restricts reverse engineering
restrictions); (b) distribute, sell, sublicense, rent, lease, or use
the Product Software (or any portion thereof) for timesharing, hosting, service provider, or like purposes; (c)remove any product identification, proprietary, copyright, orother notices contained in the Product Software; (d) modify
any part of the Product Software, create a derivative work ofany part of the Product Software, or incorporate the Product
Software into or with other software, except to the extent
expressly authorized in writing by Protempis; (e) attempt tocircumvent or disable the security key mechanism that
protects the Product Software against unauthorized use(except and only to the extent that applicable law prohibits or
restricts such restrictions); or (f) publicly disseminate
performance information or analysis (including, without
limitation, benchmarks) from any source relating to the
Product Software. If the Product Software has been provided
to you as embedded in any hardware device, you are notlicensed to separate the Product Software from the hardware
device. If the Product Software has been provided to you
separately from a hardware device but is intended to beloaded onto a hardware device specified by Protempis (suchas a firmware update), your license is limited to loading the
Product Software on the device specified by Protempis, andfor no other use.

Software Fixes
During the limited warranty period you will be entitled toreceive such Fixes to the Product software that Protempis
releases and makes commercially available and for which itdoes not charge separately, subject to the procedures fordelivery to purchasers of Protempis products generally. If you
have purchased the Product from a Protempis authorized
dealer rather than from Protempis directly, Protempis may, at
its option, forward the software Fix to the Protempis
authorized dealer for final distribution to you. Minor Updates,
Major Upgrades, new products, or substantially new software
releases, as identified by Protempis, are expressly excluded
from this update process and limited warranty. Receipt ofsoftware Fixes or other enhancements shall not serve toextend the limited warranty period. For purposes of thiswarranty the following definitions shall apply: (1) “Fix(es)”means an error correction or other update created to fix aprevious software version that does not substantially conformto its Protempis specifications; (2) “Minor Update” occurs
when enhancements are made to current features in asoftware program; and (3) “Major Upgrade” occurs whensignificant new features are added to software, or when a
new product containing new features replaces the further
development of a current product line. Protempis reserves theProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 2

right to determine, in its sole discretion, what constitutes a Fix,
Minor Update, or Major Upgrade.

Warranty Remedies
If the Protempis Product fails during the warranty period forreasons covered by this limited warranty and you notify
Protempis of such failure during the warranty period,
Protempis will repair OR replace the nonconforming Productwith new, equivalent to new, or reconditioned parts or
Product, OR refund the Product purchase price paid by you,at Protempis’s option, upon your return of the Product inaccordance with Protempis's product return procedures thenin effect.

How to Obtain Warranty Service
To obtain warranty service for the Product, please contact
your local Protempis authorized dealer. Alternatively, you may
contact Protempis to request warranty service by sending anemail to support@protempis.com. Please prepare to provide:– your name, address, and telephone numbers– proof of purchase– a copy of this Protempis warranty– a description of the nonconforming Product including themodel number– an explanation of the problem
The customer service representative may need additional
information from you depending on the nature of the problem.
Any expenses incurred in the making of a claim under thiswarranty will be borne by you.

Warranty Exclusions and Disclaimer
This Product limited warranty shall only apply in the event andto the extent that: (a) the Product is properly and correctly
installed, configured, interfaced, maintained, stored, andoperated in accordance with Protempis's applicable
operator's manual and specifications, and; (b) the Product is
not modified or misused.
This Product limited warranty shall not apply to, andProtempis shall not be responsible for, defects or
performance problems resulting from: (i) the combination or
utilization of the Product with hardware or software products,
information, data, systems, interfaces, or devices not made,supplied, or specified by Protempis;(ii) the operation of the Product under any specification otherthan, or in addition to, Protempis's standard specifications for
its products; (iii) the unauthorized installation, modification, or
use of the Product; (iv) damage caused by: accident, lightningor other electrical discharge, fresh or salt water immersion orspray (outside of Product specifications), or exposure toenvironmental conditions for which the Product is notintended; (v) normal wear and tear on consumable parts(e.g., batteries); or (vi) cosmetic damage. Protempis does notwarrant or guarantee the results obtained through the use of
the Product, or that software components will operate error
free.
NOTICE REGARDING PRODUCTS EQUIPPED WITHTECHNOLOGY CAPABLE OF TRACKING SATELLITE
SIGNALS FROM SATELLITE BASED AUGMENTATIONSYSTEMS (SBAS) (WAAS/EGNOS, AND MSAS),OMNISTAR, GPS, MODERNIZED GPS OR GLONASSSATELLITES, OR FROM IALA BEACON SOURCES:PROTEMPIS IS NOT RESPONSIBLE FOR THE
OPERATION OR FAILURE OF OPERATION OF ANYSATELLITE BASED POSITIONING SYSTEM OR THE
AVAILABILITY OF ANY SATELLITE BASEDPOSITIONING SIGNALS.
THE FOREGOING LIMITED WARRANTY TERMS STATEPROTEMPIS’S ENTIRE LIABILITY, AND YOUR
EXCLUSIVE REMEDIES, RELATING TO THE PROTEMPISPRODUCT UNDER THIS LIMITED WARRANTY. EXCEPTAS OTHERWISE EXPRESSLY PROVIDED HEREIN, THE
PRODUCT, AND ACCOMPANYING DOCUMENTATION
AND MATERIALS ARE PROVIDED “AS-IS” AND WITHOUTEXPRESS OR IMPLIED WARRANTY OF ANY KIND, BY
EITHER PROTEMPIS OR ANYONE WHO HAS BEEN
INVOLVED IN ITS CREATION,
PRODUCTION, INSTALLATION, OR DISTRIBUTION,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OR GUARANTEES OF
MERCHANTABILITY, ACCEPTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, TITLE, ANDNONINFRINGEMENT. THE STATED EXPRESSWARRANTIES ARE IN LIEU OF ALL OBLIGATIONS OR
LIABILITIES ON THE PART OF PROTEMPIS ARISING OUT
OF, OR IN CONNECTION WITH, ANY PRODUCT.
BECAUSE SOME STATES AND JURISDICTIONS DO NOTALLOW LIMITATIONS ON DURATION OR THE
EXCLUSION OF AN IMPLIED WARRANTY, THE ABOVE
LIMITATION MAY NOT APPLY OR FULLY APPLY TO YOU.

Limitation of Liability
TO THE MAXIMUM EXTENT PERMITTED BYAPPLICABLE LAW, Protempis'S ENTIRE LIABILITYUNDER ANY PROVISION HEREIN SHALL BE LIMITED TO
THE AMOUNT PAID BY YOU FOR THE PRODUCT ANDINNO EVENT SHALL Protempis OR ITS SUPPLIERS BE
LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR
CONSEQUENTIAL DAMAGE WHATSOEVER UNDER ANY
CIRCUMSTANCE OR LEGAL THEORY RELATING IN
ANYWAY TO THE PRODUCTS, SOFTWARE AND
ACCOMPANYING DOCUMENTATION AND MATERIALS,(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR
LOSS OF BUSINESS PROFITS, BUSINESSINTERRUPTION, LOSS OF DATA, OR ANY OTHERPECUNIARY LOSS), REGARDLESS OF WHETHER
Protempis HAS BEEN ADVISED OF THE POSSIBILITY OF
ANY SUCH LOSS AND REGARDLESS OF THE COURSE
OF DEALING WHICH DEVELOPS OR HAS DEVELOPEDBETWEEN YOU AND Protempis. BECAUSE SOMESTATES AND JURISDICTIONS DO NOT ALLOW THE
EXCLUSION OR LIMITATION OF LIABILITY FORCONSEQUENTIAL OR INCIDENTAL DAMAGES, THE
ABOVE LIMITATION MAY NOT APPLY OR FULLY APPLYTO YOU.
PLEASE NOTE: THE ABOVE Protempis LIMITEDWARRANTY PROVISIONS WILL NOT APPLY TO
PRODUCTS PURCHASED IN THOSE JURISDICTIONS(E.G., MEMBER STATES OF THE EUROPEANECONOMIC AREA) IN WHICH PRODUCT WARRANTIESARE THE RESPONSIBILITY OF THE LOCAL Protempis
AUTHORIZED DEALER FROM WHOM THE PRODUCTS

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 3

ARE ACQUIRED. IN SUCH A CASE, PLEASE CONTACTYOUR LOCAL Protempis AUTHORIZED DEALER FOR
APPLICABLE WARRANTY INFORMATION.

Official Language
THE OFFICIAL LANGUAGE OF THESE TERMS AND
CONDITIONS IS ENGLISH. IN THE EVENT OF A
CONFLICT BETWEEN ENGLISH AND OTHER LANGUAGE
VERSIONS, THE ENGLISH LANGUAGE SHALLCONTROL.

NoticesClass B Statement – Notice to Users. This equipment has
been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC rules. Theselimits are designed to provide reasonable protection against
harmful interference in a residential installation. Thisequipment generates, uses, and can radiate radio frequency
energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio
communication. However, there is no guarantee thatinterference will not occur in a particular installation. If thisequipment does cause harmful interference to radio or
television reception, which can be determined by turning theequipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:

Notice to Our European Union Customers
At Protempis, we recognize the importance of minimizing theenvironmental impacts of our products. We endeavor to meetyour needs, not only when you purchase and use our
products, but also when you are ready to dispose of them.
That is why Protempis is actively pursuing, and will continue topursue, the expanded use of environmentally friendly
materials in all its products, and why we have established aconvenient and environmentally friendly recycling program.
As Protempis makes additional recycling facilities available foryour use, we will post their locations and contact information to
our website.
Recycling in Europe:
To recycle Protempis WEEE:
Spectra Precision GmbH C/O RCL EHV
Ekkersrijt 2066, 5692 BA Son, Netherlands– Reorient or relocate the receiving antenna.
– Increase the separation between the equipment and thereceiver.
– Connect the equipment into an outlet on a circuit different
from that to which the receiver is connected.
– Consult the dealer or an experienced radio/TV technician for
help.
Changes and modifications not expressly approved by the
manufacturer or registrant of this equipment can void yourauthority to operate this equipment under Federal
Communications Commission rules.

CanadaThis digital apparatus does not exceed the Class B limits forradio noise emissions from digital apparatus as set out in theradio interference regulations of the Canadian Department ofCommunications, ICES-003.
Le présent appareil numérique n’émet pas de bruits
radioélectriques dépassant les limites applicables aux
appareils numériques de Classe B prescrites dans lerèglement sur le brouillage radioélectriqueédicté par leMinistère des Communications du Canada, ICES-003.

For product recycling instructions and more information, go towww.protempis.com/ComplianceDeclaration of Conformity
We, Protempis, United States of America declare
under sole responsibility that the product: Acutime 360
smart antenna complies with Part 15B of FCC Rules.

Operation is subject to the following two
conditions:(1) this device may not cause harmfulinterference, and (2) this device must accept
any interference received, including interfrence
that may cause undesired operation

EuropeThis product has been tested and found to comply with therequirements for a Class B device pursuant to European
Council Directive 89/336/EEC on EMC, thereby satisfying therequirements for CE Marking and sale within the European
Economic Area (EEA). These requirements are designed toprovide reasonable protection against harmful interference
when the equipment is operated in a residential or commercial
environment.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 4

Document History
VersionV1.08 Rev B
V1.08 Rev A

Date
June 2022
May 2021

AuthorCV
FAE

ChangesProtempis update
Updates for firmware 1.08

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 5

Safety Information
Warnings and cautions
An absence of specific alerts does not mean that there are no safety risks involved. Always
follow the instructions that accompany a Warning or Caution. The information it provides isintended to minimize the risk of personal injury and/or damage to property. In particular,
observe safety instructions that are presented in the following format:
WARNING – This alert warns of a potential hazard which, if not avoided, could result insevere injury or even death.
CAUTION – This alert warns of a potential hazard or unsafe practice which, if not
avoided, could result in injury or property damage or irretrievable data loss.
CAUTION – Electrical hazard – risk of damage to equipment. Make sure all electrostatic
energy is dissipated before installing or removing components from the device. An
electrostatic discharge (ESD) can cause serious damage to the component once it isoutside the chassis.

NOTE – An absence of specific alerts does not mean that there are no safety risks
involved.

Operation and storage
WARNING – Operating or storing the Acutime 360 antenna outside the specified
temperature range can damage it. For more information, see the product specifications
on the data sheet.

Routing any cable
CAUTION – Be careful not to damage the cable. Take care to avoid sharp bends or kinks
in the cable, hot surfaces (for example, exhaust manifolds or stacks), rotating or
reciprocating equipment, sharp or abrasive surfaces, door and window jambs, andcorrosive fluids or gases.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 6

Contents
Legal Notices

2

Document History

5

Safety Information

6

Warnings and cautions

6

Operation and storage

6

Routing any cable

6

Introduction

12

Overview

13

Features of the Acutime 360 multi-GNSS smart antenna

13

Hardware features
Interface protocols
Standard timing software features

13
13
13

Operation

14

Starter kit

14

Use and care

14

Related information

15

Technical assistance15

Setting up the Acutime Smart antenna

16

System requirements

17

Hardware
Computer
System software

17
17
17

Installing and using the software

17

Protempis VTS software
Data fields

17
18

Acutime 360 starter kit
Universal Interface Module (UIM)Power converter (AC/DC)

19
19
20

Setting up the starter kit

21

Starter kit components

22

Integration
Acutime Smart antenna
Performance specifications
Environmental specifications
Physical characteristics

Interface cables

23
23
24
25
25

25
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 7

Contents

Power requirements

26

Serial port interfaces
Pulse-Per-Second (PPS)Timing pulse connections
Serial ports
Event input

26
27
27
27
28

System Operation

29

Startup

29

Timing receiver performance

30

Communicating with the receiver

30

Port B configuration
Port A configuration31
31

Automatic operation

31

Satellite masks
Elevation mask
SNR mask
PDOP mask
Operating modes
PPS output options

31
32
32
32
33
33

Serial data communication

34

GNSS constellation configuration

34

Timing operation

35

Customizing operations

35

Configuration parameters
Port A and B configuration
PPS configuration
Position information
Self-survey configuration
NMEA 0183 protocol and data output options

Protempis Standard Interface Protocol

36
37
37
37
38
38

40

Introduction to TSIP

41

Interface scope

41

TSIP packet structure

41

Physical interface characteristics

42

Nomenclature
Protocol capabilities
Primary port features – port B
Secondary port features – port A
Event Input

42
42
43
43
43

Packets output at startup

43

Receiver warm-start

43

Default background packets (Port B)

44

Default automatic position and velocity reports

44

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 8

Contents

Automatic primary and supplemental timing reports

45

Low-latency timing packets
Satellite data packets

45
45

Customizing receiver operations

46

Customizing receiver output for the application
Customizing receiver operation

46
47

Command Packets: User to Acutime 360 antenna

47

Report Packets: Acutime 360 to user

49

Packet Descriptions

50

Command packet 0x1C-01: Firmware version
Report packet 0x1C-81: Firmware component version information
Command packet 0x1C-03: Hardware component version information
Report packet 0x1C-83: Hardware component version information
Command packet 0x1E: Initiate Cold, Warm, or Factory ResetCommand packet 0x1F: Request Software Version
Command Packet 0x21: Current Time Request
Command packet 0x23: Initial Position (XYZ Cartesian ECEF) command
Command packet 0x24: Request GNSS satellite selection
Command Packet 0x26: Health Request
Command packet 0x27: Request Signal Levels
Command packet 0x2B: Initial Position (Latitude, Longitude, Altitude)
Command packet 0x2F: UTC Parameters request
Command packet 0x30: Set UTC Date and Time for future roll over dateCommand packet 0x31: Accurate Initial Position (XYZ Cartesian ECEF)
Command packet 0x32: Accurate Initial Position (Latitude, Longitude, Altitude)
Command packet 0x35: Set or Request I/O Options
Command packet 0x37: Request status and values of last position
Command packet 0x38: Request/load Satellite System Data
Command packet 0x39: Satellite Attribute Database Command
Command packet 0x3A: Request last raw measurement
Command packet 0x3B: Satellite ephemeris status request (for GPS only)
Command packet 0x3C: Request satellite tracking status
Command packet 0x7A: NMEA Interval and Message Mask command
Report packet 0x31: Accurate Initial Position (XYZ Cartesian ECEF)
Report packet 0x32: Accurate Initial Position (Latitude, Longitude, Altitude)
Report packet 0x41: GPS Time report
Report packet 0x42: Single-precision position fix
Report packet 0x43: Velocity fix, XYZ ECEF
Report packet 0x45: Software version information
Report packet 0x46: Health of Receiver report
Report packet 0x47: Signal level for all satellites tracked
Report packet 0x4A: Signal precision LLA position fix
Report packet 0x4B: Machine/Code ID and Additional status report
Report packet 0x4F: UTC parameters report
Report packet 0x54: Bias and Bias rate report
Report packet 0x55: I/O Options

51
51
51
52
52
53
53
53
53
54
54
54
55
55
55
56
57
58
58
59
60
61
61
61
62
62
63
63
63
64
64
65
66
66
67
67
68

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 9

Contents

Report packet 0x56: Velocity Fix, East-North-Up (ENU)
Report packet 0x57: Information about last computed fix
Report packet 0x58: Satellite System Data/Acknowledge from Receiver
Report packet 0x59: Satellite Attributes Database Report
Report packet 0x5A: Raw Data Measurement Data
Report packet 0x5B: Satellite Ephemeris Status Report (GPS only)
Report packet 0x5D: Satellite Tracking Status
Report packet 0x6C: All-in-View Satelite selection
Report packet 0x7B: Set NMEA Message Output
Report packet 0x83: Double Precision XYZ
Report packet 0x84: Double precision LLA position (Fix and Bias information)
Command packet 0xBB: Set Receiver Configuration
Command packet 0xBC: Set Port Configuration

TSIP superpackets

68
68
69
73
74
75
76
77
78
78
78
79
80

82

Command packet 0x8E-02: Request UTC Information
Command packet 0x8E-0B: Request or configure superpacket output
Command packet 0x8E-20: Request Last Fix with Extra Information
Command packet 0x8E-26: Write Receiver Configuration to Non-volatile Memory (Flash)Command packet 0x8E-41: Request Manufacturing Parameters
Command packet 0x8E-42: Stored Production Parameters
Command packet 0x8E-4A: Set PPS characteristics
Command packet 0x8E-4D: Automatic Packet Output Mask
Command packet 0x8E-4E: Set PPS output option
Command packet 0x8E-4F: Set PPS widthCommand packet 0x8E-A2: UTC/GNSS Timing
Command packet 0x8E-A5: Packet Broadcast Mask
Command packet 0x8E-A6: Self-Survey Command
Command packet 0x8E-A9: Self-Survey parameters
Command packet 0x8E-AB: Request Primary Timing packet
Command packet 0x8E-AC: Request Supplemental Timing packet
Command packet 0x8E-AD: Request or Configure Superpacket Output
Report packet 0x8F-02: UTC information
Report packet 0x8F-0B: Comprehensive Time
Report packet 0x8F-20: Last Fix with Extra Information (binary fixed point)
Report packet 0x8F-26: Save Receiver Configuration to Non-volatile Storage Memory
Report packet 0x8F-41: Stored manufacturing operating parameters
Report packet 0x8F-42: Stored Production parameters
Report packet 0x8F-4A: Set PPS characteristics
Report packet 0x8F-4D: Automatic Packet Output Mask
Report packet 0x8F-4E: PPS output
Report packet 0x8F-4F: PPS width
Report packet 0x8F-A2: UTC/GPS Timing
Report packet 0x8F-A5: Packet Broadcast Mask
Report packet 0x8F-A6: Self-Survey Command
Report packet 0x8F-A9: Self-Survey Parameters
Report packet 0x8F-AB: Primary Timing Packet
Report packet 0x8F-AC: Supplemental Timing Packet

82
82
82
83
83
83
83
84
84
85
86
86
87
88
88
89
90
90
91
92
94
94
94
95
95
96
96
97
97
97
97
97
99

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 10

Contents

Report packet 0x8F-AD: Primary UTC Time

Unused or miscellaneous packets

103

106

Report packet 0x13: Unparsable packet

106

NMEA 0183 Protocol

107

Introduction

107

NMEA 0183 communication interface

108

NMEA 0183 message structure

108

Talker IDs

109

Field definitions

109

NMEA 0183 message options

110

Acutime 360 antenna proprietary NMEA messages

NMEA 0183 message formats

111

112

GGA - GPS Fix Data
GLL - Geographic Position - Latitude/Longitude
GSA - GPS DOP and Active Satellites
GSV - GPS Satellites in View
RMC - Recommended Minimum Specific GPS/Transit Data
VTG - Track Made Good and Ground Speed
ZDA - Time & Date
AH - Almanac Health
AL - Almanac Page
AS - Almanac Status
CR - Configure Receiver
EM - Enter Monitor mode
EP - Ephemeris
IO - Ionosphere
KG - Set Initial Position
NM - NMEA Configuration
PS - PPS Configuration
PT - Serial Port Configuration
RT - Reset
TF - Receiver Status and Position Fix
UT - UTC data
VR - Version
ZD - Extended Time and Date

Exception behavior

112
113
113
114
115
116
116
117
118
119
120
122
122
124
125
125
127
127
128
129
130
130
132

133

Interruption of GNSS signal

133

Acutime 360 Antenna GPS-only Variant

134

Introduction

134

Default communication interface

135

PPS pulse width

135

Default constellations

135

Default messages

135

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 11

1
Introduction
Welcome to the Protempis Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide.
This user guide describes how to install, set up and use the Protempis® Acutime™ 360 multiGNSS smart antenna and timing receiver.
For more information on Protempis timing and synchronization products go to
http://www.Protempis.com/timing/.
For more information on GNSS, go to: http://www.Protempis.com/gps_tutorial/.
Overview
Features of the Acutime 360 multi-GNSS smart antenna
Operation
Starter kit
Use and care
Related information
Technical assistanceProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 12

Introduction

Overview
The Acutime 360 antenna integrates the latest multi-GNSS technology into a rugged, selfcontained antenna unit that provides optimal GNSS timing performance, in all weather
conditions, with continuous operation, long- term reliability, ease of operation, and simple
installation.
The Acutime 360 antenna provides an accurate one pulse-per-second (PPS) output tosynchronize and time broadband wireless, cellular base stations, Time Difference of Arrival(TDOA) applications, and many other Supervisory and Data Acquisition (SCADA) applications.

Features of the Acutime 360 multi-GNSS smart antenna
Hardware features
The Acutime 360 antenna contains the following in a sealed, weatherproof housing:l

An active patch multi-GNSS antenna with a proprietary pre-amp design and integrated
band-pass filtering providing excellent performance against jamming signals.

l

A connector that supports both the power and data interface connection.

l

Two user-configurable RS-422 I/O communication ports.

The Acutime 360 antenna operates with a 5 to 36 VDC power supply with protection against
reverse polarity. Internal circuitry reduces the power to operate the receiver at 3.3 VDC.
When power is applied, the Acutime 360 antenna initializes by itself, acquires satellite signals,
and begins a self-survey, which culminates in a transition from the Positioning Mode to an Overdetermined Clock Mode.)Interface protocols
You can select the protocol for the Acutime 360 antenna. There are two options:llProtempis Standard Interface Protocol (TSIP) is a binary packet protocol that allows thesystem designer maximum configuration control over the GNSS receiver for optimum
performance in timing applications. TSIP supports multiple commands and their associatedresponse packets for use in configuring the Acutime 360 antenna to meet yourrequirements. See Appendix A, Protempis Standard Interface Protocol.
NMEA 0183 (National Marine Electronics Association) is an industry standard protocolcommon to marine applications. It provides direct compatibility with other NMEA- capabledevices such as chart plotters and radar. The Acutime 360 antenna supports the ZDA
NMEA message for GNSS timing. You can select other NMEA messages and output rates
as required. See Appendix B, NMEA 0183 Protocol.

Standard timing software featureslAutomatic self-surveylOver-determined (OD) Clock Mode

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 13

IntroductionlTime-keeping from a single satellite (a minimum of two satellites is needed for re-acquiring
the time)lTiming SuperpacketslTiming Receiver Autonomous Integrity Monitoring (T-RAIM)ll

Position integrity (P-RAIM). When the receiver detects a position difference greater than
100 meters from its stored position, it will restart the self-survey.
Cable delay compensation

Operation
When the Acutime 360 antenna is turned on, it runs a self-survey process and then switches
into the Over-determined Clock Mode. In this mode, the reference position from the self-survey
is retained in memory and the receiver solves only for clock error and clock bias. This mode also
provides for T-RAIM, which allows the receiver to remove a satellite that provides incorrect
information from the timing solution. If a receiver is moved more than 100 meters from its
surveyed location, a new self-survey ensures position integrity by automatically initiating andcorrecting the reference location.
The first time that the Acutime 360 antenna is turned on, it searches for satellites from a cold
start with no almanac, time, ephemeris, or stored position. The Acutime 360 antenna begins tocompute position and time solutions within the first 46 seconds, but it must track satellites
continuously for approximately 15 minutes to download a complete almanac and ephemeris. Do
not interrupt the initialization process.
The Acutime 360 antenna generates a 1 PPS output, synchronized to GPS or Coordinated
Universal Time (UTC) or GLONASS time within 15 ns (one sigma). This level of accuracy is
obtained using an Over-determined Clock solution and T-RAIM. The 1 PPS output and data
signals conform to the RS-422 standard and support very long cable runs. The Acutime 360
antenna outputs a comprehensive time packet after each 1 PPS on a dedicated serial port, it
can accept an external event input, and report time stamps in response to an event signal.
NOTE – The delay inherent in the cable from the antenna to the receiver can beovercome by determining the length of the cable and then entering the offset based on
information from the cable manufacturer about the specific cable type.

Starter kit
The Acutime 360 Starter Kit contains all the components required for a high-performance, costeffective reference time source that uses GNSS technology to precisely synchronize
computers, servers and Internet applications for evaluation and engineering purposes. It is
quick and easy to install.

Use and care
TheAcutime 360 antenna is a high-precision electronic instrument and should be treated withreasonable care.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 14

Introduction

CAUTION – There are no user-serviceable parts inside the Acutime 360 antenna andany modification to the unit by the user voids the warranty.

Related information
An electronic copy of this manual is available in portable document format (PDF). Use Adobe
Reader to view the file.
Contact your local sales representative or Protempis Support for more information about the
support agreement contracts for software and firmware

Technical assistanceIf you have a problem and cannot find the information you need in the product documentation,
send an email to the Protempis Technical Assistance Center using the following address:
tsgsupport@Protempis.com.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 15

2
Setting up the Acutime Smartantenna
Protempis recommends that you install the Protempis VTS software before setting up the
Acutime 360 smart antenna, as this will enable you to monitor the acquisition of satellites once
you start up the multi-GNSS antenna.
A starter kit is available for testing, evaluation, and engineering purposes. This section
describes the components of the starter kit, and how to set it up.
NOTE – The VTS software and the starter kit should NOT be considered for thecommercial service grade product, but only for lab testing, lab evaluation, andengineering purposes.
NOTE – Protempis does not have any responsibility for any kind of abnormal behaviors
during the commercial grade service with the VTS software and/or the starter kit.
The hardware integration is described in Integration.
Smart Antenna Placement
System requirements
Installing and using the software
Acutime 360 starter kit
Setting up the starter kit
Starter kit components

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 16

Setting up the Acutime Smart antenna

System requirements
Hardwarel

For evaluation or engineering purposes:ll

The Protempis Acutime 360 multi-GNSS smart antenna starter kit, see later in thischapter.

For permanent installation:lProtempis Acutime 360 multi-GNSS smart antennalInterface cable with DB-25 connectorlUniversal Interface Module

Computer
An office computer powered by a version of the Microsoft® Windows® operating system(Windows XP or later).

System softwarelllProtempis VTS software. This is used to monitor the Acutime 360 antenna’s performanceand to assist system integrators in developing a software interface for the smart antenna.
The software is compatible with the Windows operating systems. See Protempis VTS
software.
Protempis Standard Interface Protocol (TSIP). This consists of command packets andreport packets. See Appendix A Protempis Standard Interface Protocol.
NMEA-0183. See Appendix B NMEA 0183 Protocol.

Installing and using the software
All software programs for the Acutime 360 starter kit are available online from the Protempis
website at http://www.Protempis.com/Timing/Acutime-360.aspx. These programs enable you
to monitor the Acutime 360 antenna and change its settings.
TIP – Install and set up the monitor program before turning on the Acutime 360 antenna—
this allows you to watch the timing process, from start up to fully functioning.

Protempis VTS software
CAUTION – Use only the Protempis VTS software with this product. Previous software
versions may not be compatible.
To install the Protempis VTS software from the website:
1. Go to http://www.Protempis.com/timing/acutime-360.aspx and then select Support for
TGS / Installation Files.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 17

Setting up the Acutime Smart antenna

2. Select and then download Protempis VTS.exe to the computer’s hard drive.
3. To run the application, double-click the file. The Protempis VTS screen appears.
4. To specify the communications port and protocol for your office computer, right-click in thebottom right of the Protempis VTS screen and then select the required COM port andsettings.
5. Connect the Acutime 360 antenna to the Universal Interface Module (UIM) using theprovided antenna interface cable. Connect the 12-pin connector to the antenna, and theDB-25 connector to the UIM.
6. Connect one end of the USB cable to the USB port of the UIM.
7. Connect the other end of the cable to the USB port of your computer.
8. Turn on the DC power source or plug in the AC/DC converter and then turn on the power.
The Tx and Rx in the lower left of the status bar indicate the following:– If the Tx blinks, the computer is transmitting commands to the receiver.
– If the Rx blinks, the computer is receiving reports from the receiver.
9. The Acutime 360 antenna automatically begins its self-survey. When this is complete andthe receiver achieves a position fix, the following information appears:– position– time– satellites tracked– GPS receiver status
NOTE – The receiver sends a health report every few seconds, even if satellites are notbeing tracked.

Data fields
If the Protempis VTS software displays a question mark (?) in a data field, the receiver has notreported a status for this field. If the question mark stays in place, the Acutime 360 antenna may
not be communicating with the computer. Check the interface cable connections and verify theserial port selection and settings.
If the communication fails, contact the Protempis Technical Assistance Center or local reseller..

TSIP
The Protempis Standard Interface Protocol (TSIP) consists of command packets and reportpackets, see Appendix A Protempis Standard Interface Protocol.
The TSIP is installed by factory default.

NMEA-0813
To convert to the NMEA protocol, refer to and use the Protempis VTS software for serial port
protocol, Input/Output, message type output, and baud rate configuration.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 18

Setting up the Acutime Smart antenna

Acutime 360 starter kit

Acutime 360 Smart
Antenna

Power converter(AC to 24 VDC)

Universal Interface Module (RS-422 to USB converter)

Power pin adapters

USB cable

30 m (100 feet) of interface
cablewith DB-25 connector

Universal Interface Module (UIM)The UIM that is included with the starter kit makes it easy to evaluate and develop software
when it is connected to theAcutime 360 antenna. It has a Type 2 USB interface to the Acutime
360 antenna that is compatible with most computers.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 19

Setting up the Acutime Smart antennallNetwork power (+7 to +36 VDC) is supplied through the power connector on the front of themodule.
The USB connector and interface cable allows for easy connection to a PC USB port.
NOTE – The Acutime 360 requires power separate from the USB.

ll

The motherboard has a switching power supply, which converts the prime voltage input tothe 24 V that is required to power the receiver over most available cable lengths.
Connect the output device to the 1 PPS connector on the rear of the unit.

Power converter (AC/DC)The AC/DC power converter provides an alternative power source for the interface unit andenables you to run the module from network power.
It converts 110 or 220 VAC to a regulated +24 VDC that is compatible with the UIM. The
AC/DC power converter output cable is terminated with a standard DC power connector that iscompatible with the power connector on the metal enclosure.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 20

Setting up the Acutime Smart antenna

Setting up the starter kit

1. Mount the Acutime 360 antenna on a 1" OD marine pipe or 3/4” ID pipe, with 14 threads perinch.
2. Connect the antenna cable to the Acutime 360 antenna. Allow for the cable to maintain a"drip- loop" to prevent water intrusion and to allow for flex on the antenna to cableconnector.
3. Place the Acutime 360 antenna so that it has the fullest possible view of the sky to ensurethat the maximum number of satellites is available.
4. Use the DB-25 connector to connect the antenna cable to the rear of the UIM.
CAUTION – Be careful not to damage the cable. Take care to avoid sharp bends orkinks in the cable, hot surfaces (for example, exhaust manifolds or stacks), rotating or
reciprocating equipment, sharp or abrasive surfaces, door and window jambs, routing
near high EMI / EMF (Electro-Magnetic Induction / Field) transformers or equipment,
and corrosive fluids or gases.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 21

Setting up the Acutime Smart antenna

5. When using the TSIP protocol, connect one end of the USB interface cable to the USB portof the interface unit. Connect the other end of the cable to the USB port on a computer.
NOTE – The antenna supports the TSIP or NMEA protocols. Dual ports support
either the input/output of TSIP messages or the output of NMEA messages.
6. To connect the power connector to the UIM, do one of the following:ll

Use the DC power cable. Connect the terminated end of the power cable to the power
connector on the UIM. Connect the red lead to DC positive voltage (+12 VDC to +24
VDC) and the black power lead to DC ground. The yellow wire is not used.
Use the AC/DC power converter. Connect the output cable of the converter to thepower connector on the UIM. Use the appropriate 3-pin power adapters to connect theconverter to mains power (110 VAC or 220 VAC).

7. Switch on the DC power source or turn on the mains power.
To integrate the multi-GNSS smart antenna, into your system, see Integration.

Starter kit components
The Protempis® Acutime 360 antenna is available as part of the starter kit, or as an individual
item. The starter kit includes all the components necessary to quickly test and integrate thereceiver.
Product

Part Number

Acutime 360 multi-GNSS timing module (Default: GPS &GLO)

106406-00

100’ Acutime 360 cable

60155 (included in Starter kit)

Acutime 360 Universal Interface Module

Available with SK only

AC/DC power supply module

Available with SK onlyInterface cable (USB/USB)

Available with SK only

NOTE – Part numbers are subject to change. Confirm part numbers with your Protempis
representative when placing your order.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 22

3
Integration
The setup procedures for the Protempis® the Acutime 360 multi-GNSS Smart antenna aredescribed in Setting up the Acutime Smart antenna.
This chapter describes the hardware components, to assist you when you integrate the Acutime
360 antenna into a system.
To integrate the Acutime 360 multi-GNSS Smart antenna into your system you must:lConnect to a standard serial interface port on the host systemlDesign a circuit to read the electrical 1PPSlDevelop a software interface

The setup procedures for the Acutime 360 multi-GNSS Smart antenna starter kit are describedin Setting up the Acutime Smart antenna.
GNSS Error Correction: ITU-T technical paper GSTR-GNSS suggested different error
correction mechanisms for various physical and environmental condition that may impede
signal reception and processing. Protempis recommends that the those guideline are followed
for the implementation of error correction mechanisms.
Acutime Smart antenna
Interface cables
Power requirements

Acutime Smart antenna

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 23

Integration

Bottom view

Side view

Performance specifications
Parameter

Description

GeneralGPS, GLONASS, BeiDou frequencies, continuous
tracking receiver, static Over-determined Clock Mode

Update rate

1Hz

Event Update rate

5Hz / Second (max)Accuracy horizontal position<6 meters (50%)<9 meters (90%)

Accuracy altitude position<7 meters (50%) <10 meters (90%)

Velocity

0.06 m/sec

Time to first fix

No stored position: <46 s (50%), <50 s (90%)
Stationary with stored position (for example, recovery
after a power outage): <14 s (50%), <18 s (90%)

Reacquisition after 60s signal loss

<2 s (90%)

Dynamics

Velocity: 500 m/s maximum
Acceleration: 4 g (39.2 m/sec2) Jerk: 20 m/s3

PPS output

Physical interface: RS-422
Width: 10 milliseconds (default); user programmablefrom 1 millisecond to 500 milliseconds
On-time edge: Rising edge on time (default); user
programmable rising or falling resolution :<32
nanoseconds
Accuracy: UTC 15 nanoseconds (static), UTC 90
nanoseconds (dynamic, TDOP ≤ 3)

External event captureInterface: RS-422 Resolution: <500ns

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 24

Integration

Parameter

Description

Minimum pulse width

10 milliseconds, rising edge-on-edge

Reporting mechanism

TSIP packet

Environmental specifications
Parameter

Condition

Operating temperature-40° C to + 85° C (-40° F to 185° F)

Storage temperature-55° C to + 105° C (-67° F to 221° F)

Vibration

0.008 g2/Hz
0.05 g2/Hz-3 dB/octave

Operating humidity

95% RH, non-condensing at 60° C (140° F) EMC

EMC

CE, FCC Class B

Ingress protection

IP 67

5 Hz to 20 Hz
20 Hz to 100 Hz
100 Hz to 900 Hz

Physical characteristics
Power consumption

50 mA @ 12 V
0.6 W (typical), < 1 W maximum

Dimensions

95 mm (depth) x 72.5 mm (height) (3.74" x 2.85")

Connector

12-pin round, waterproof

Weight154 g (5.4 oz)

Mounting

1” - 14” straight thread or 3/4” pipe thread

Interface cables
The Acutime 360 smart antenna's interface cable is twisted-pair technology, 22 American Wire
Gauge (AWG), 6 pair/12 conductors, shielded, and protected with a PVC-U/V outer sheath.
The interface cables are available in the following standard lengths:l

15 m (50 feet)l

30 m (100 feet)l

60 m (200 feet)l

120 m (400 feet)

By following the RS-422 standard, also known as TIA/EIA-422, the maximum cable length canbe up to 1000 m (3280 feet)with a data rate of 115,200 Kbit/s.
For custom-length cables of up to 550 m (1800 feet), contact Protempis.
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 25

Integration

All cables are terminated on the antenna end.

Power requirements
The Protempis® Acutime 360 is designed for static timing applications and requires a nominal+12 VDC to +24 VDC input (a range of +5 VDC to +36 VDC is possible). You can apply power
to the Universal Interface Monitor using one of two options: the DC power cable, or the AC/DC
power converter.
TIP – Some voltage drop will occur over the cable run. If feed voltage is limited to +5 VDC,
the cable length is limited to 9 m (30 feet). When the cable is 30 m (100 feet) or longer, thefeed voltage must be at least +12 VDC. Protempis recommends +24 VDC for most runs.
The red wire (Acutime 360 pin 1) and the black wire (Acutime 360 pin 9) on the interface cable
support power and ground connections, respectively. The Acutime 360 smart antenna featuresa linear power supply, which supports +5 to +36 VDC. The antenna is protected against
reverse polarity and brief over voltage conditions, however, extended over-voltage conditions
may cause permanent damage.
Power consumption of the Acutime 360 smart antenna is less than 80 mA at 12 VDC.

Serial port interfaces
The pin-out descriptions and color codes for the standard un-terminated cables and DB-25
interface cable are as follows:
Accutime 360
Connector
Pin #Wire Color

Function

DB-25
Interface
Pin#

Protocol1

Red

DC Power

1+5 VDC to +36 VDC

2VioletPort B: Receive -25

TSIP RS-422

3

OrangePort B: Receive +13

TSIP RS-422

4

Brown

Port B: Transmit -11

TSIP RS-422

5

Yellow

Port B: Transmit +23

TSIP RS-422

6

White

Port A: Receive -24

Event Input

7

Gray

Port A: Receive +12

Event Input

8

Green

Port A: Transmit -10

NMEA / TSIP RS422

9

Black

DC Ground

7

Ground10

Blue

Port A: Transmit +22

NMEA / TSIP RS422

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 26

Integration

Accutime 360
Connector
Pin #Wire Color

Function

DB-25
Interface
Pin#

Protocol11

Orangew/white stripe

1 PPS Transmit +21

RS-42212Black w/white
stripe1PPS Transmit -9

RS-422

Pulse-Per-Second (PPS)The Acutime 360 smart antenna provides a 10 ms wide, RS-422, Pulse-Per-Second (PPS) on
antenna connector pins 11 and 12. The pulse is sent once per second and the leading edge ofthe pulse is synchronized to UTC, GPS, or GNSS time.
The pulse shape is affected by the distributed capacitance of the attached cabling and input
circuit. The pulse's trailing edge should not be used for timing applications. An accurate timing
pulse is available only when the Acutime 360 smart antenna is operating in the static.
Over-determined Clock Mode with a timing accuracy of <15 nanoseconds (one sigma) to UTC,
GPS, or GNSS time.
The PPS output can be programmed to provide an even-second output using TSIP packet
0x8F-4E.

Timing pulse connections
The Acutime 360 smart antenna outputs a timing pulse for timing and synchronization
applications. The timing pulse is generated using an RS-422 line driver circuit (connector pins
11 and 12). The leading edge of the PPS output pulse is synchronized to UTC. The width of thepulse's leading edge is 20 nanoseconds or less. The exact width and shape of the pulse
depends upon the distributed capacitance of the interface cable.

Serial ports
The Acutime 360 smart antenna has two RS-422 communication ports. The functions of these
ports (B and A) are described below.

Port B
Port B is the primary serial port for the Acutime 360 smart antenna. Using this port, you can:
l
l

l
l

l

Send commands and receive command responses.
Query for and receive satellite data (for example, ephemeris, tracking information, andsignal levels).
Receive timing packets that are synchronized with the PPS output.
Enable TSIP timing packets 0x8F-AB and 0x8F-AC (which output automatically after the
self-survey has been completed) or 0x8F-AD using command packet 0x8E-A5.
Configure Port B to transmit NMEA packets.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 27

Integration

The Acutime 360 smart antenna automatically sends a range of satellite data packets on Port B.
You may not need these data packets—to disable them, use command packet 0x8E-A5. This
ensures that only the timing packets are sent. You can also choose to receive the timing packets
on Port A, and use Port B to only send commands and receive satellite data.

Port APort A serves as a dedicated transmit port for timing packets and is also used by default toreceive external event inputs.
You can select NMEA output on port A, with TSIP in / TSIP out on port B.

Event input
The Acutime 360 smart antenna accepts an external event input in the shape of an RS-422
pulse. The external event pulse input is supported on Port A (pins 6 and 7). The Acutime 360
transmits a TSIP time packet (0x8F-0B or 0x8F-AD) in response to the event input. The TSIP
packet increments the event count field for each event received. The event time stamp is
generated within 500 ns of its arrival at the Acutime 360 interface connector.
NOTE – The event capture feature is design for low frequency events of 1 PPS or longer.
NOTE – When the event input on Port A is enabled the serial receive function on Port A is
disabled.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 28

4
System Operation
Startup
Timing receiver performance
Communicating with the receiver
Serial data communication
GNSS timing
Customizing operations

The Acutime 720 smart antenna receives the amplified GNSS signals through the antenna feedline connector and passes them to the RF down-converter. A highly stable crystal reference
oscillator is used by the down-converter to produce the signals used by the digital signal
processor (DSP). The DSP tracks the GNSS signals and extracts the carrier code information
as well as the navigation data at 50 bits per second.
Operation of the tracking channels is controlled by the navigation processor. The software
tracking channels track the highest twelve satellites above the horizon. The navigation
processor then uses the optimum satellite combination to compute a position. The navigation
processor also manages the ephemeris and almanac data for all of the satellites, and performs
the data I/O.

StartupOn startup, the receiver automatically runs a self-survey process and then provides an overdetermined timing solution.
The first time that the Acutime 360 smart antenna is turned on, it begins searching for satellites
from a cold start with no almanac, time, ephemeris, or stored position. The receiver starts
computing position and time solutions within the first 46 seconds, but the receiver must
continuously track satellites for approximately 15 minutes to download a complete almanac andephemeris. Do not interrupt the initialization process.
During the satellite acquisition phase, the Acutime 360 antenna outputs periodic TSIP
messages on Port B. These status messages confirm that the receiver is working.
NOTE – The Acutime 360 smart antenna has no provision for external backup power andalways begins operation from a cold start, unless a warm start is forced by uploading

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 29

System Operation

almanac data and time.

Timing receiver performance
The receiver and patch antenna contained in the Acutime 360 smart antenna are in a single
board format. The board has been adapted for timing applications where reliability,
performance, and ease of integration are required.
The receiver features Protempis's improved signal processing code, a high-gain RF section,
and RS-422 line drivers to deliver a differentially driven 1 PPS output for timing andsynchronization applications.
Timing applications are assumed to be static. The specialized timing software used within the
Acutime 360 smart antenna configures the unit into an automatic self-survey mode at start up.
The receiver will average position fixes for a specified time (one per second) and at the end of
this period, this reference location is used to solve for time. The receiver goes into an Overdetermined Clock Mode and no longer solves for position but only for clock error and clock bias
using all of the available satellites. This procedure will provide an accuracy of less than 15 ns(one sigma) to GPS, UTC, or GNSS time for the 1 PPS output.
To change the default port parameters and NMEA settings, issue the appropriate TSIP
command and then store the settings in the receiver's non-volatile (flash) memory. The settings
are retained when mains power is removed, without the need for battery backup. The factory
default setting for Port B, the primary I/O port, is bi-directional TSIP at 115,200 baud, 8 data
bits, odd parity, and 1 stop bit.
NOTE – When customizing port assignments or characteristics, confirm that yourchanges do not affect your ability to communicate with the receiver.

Communicating with the receiverCommunication with the receiver is through an RS-422 compatible serial port. The port
characteristics can be modified to accommodate your application requirements. Portparameters are stored in flash memory, which does not require back-up power. The default port
characteristics are:Parameter

Factory Default

Input baud rate

115,200

Output baud rate

115,200

ParityOdd

Data bits

8

Stop bits

1

Input protocol

TSIP input

Output protocol

TSIP output

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 30

System Operation

NOTE – The Acutime 360 smart antenna also supports the NMEA message protocol.

Port B configuration
The factory default protocol on Port B is TSIP in and out at 115,200-odd-8-1.
The serial port can be changed and stored in flash memory. The receiver protocol can bereconfigured using TSIP command packet 0xBC, Timing Receiver, Protempis VTS software, ora user-written serial interface program.
C-source code examples for TSIP commands are also provided in Appendix A Protempis
Standard Interface Protocol. When used as software design templates, this source code cansignificantly speed up code development.
The protocol settings and options are stored in Random Access Memory (RAM). They can besaved into the flash memory using command packet 0x8E-26.

Port A configuration
Port A is a dedicated port for outputting comprehensive timing packets. Messages are output
after the PPS and after external events. The factory default setting is TSIP, output only, at
115,200-8-odd-1.
NOTE – When the event input on Port A is enabled the serial receive function on Port A is
disabled.
The host system receives both the PPS and the time packet identifying each pulse. Use packet
0x8E-A5 to determine which Timing Superpacket to output on this port.
The information reported in the 0x8F-0B message relates to only the GPS constellation.
This packet is only valid for GPS satellites.

Automatic operation
When the Acutime 360 antenna has acquired and locked onto a set of satellites that pass themask criteria listed below, and has obtained a valid ephemeris for each tracked satellite, andthere is no stored position, or the position has changed from the last stored position by morethan 100 meters, then it performs a self-survey. After a number of valid position fixes, the selfsurvey is complete. At that time, the Acutime 360 antenna automatically switches to a time-onlymode (overdetermined clock mode).

Satellite masks
The Acutime 360 smart antenna continuously tracks and uses up to 32 satellites in an
overdetermined clock solution. The satellites must pass the mask criteria to be included in thesolution.
The following table lists the default satellite masks used by the Acutime 360 antenna. Thesemasks serve as the screening criteria for satellites used in fix computations and ensure that

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 31

System Operation

solutions meet a minimum level of accuracy. The satellite masks can be adjusted using the TSIP
protocol described in Appendix A, Protempis Standard Interface Protocol.
Mask
Elevation
C/N0[dBHz]PDOP

Default Setting
10°30

Description
Satellite elevation above horizon
Signal strength (carrier-to-noise power ratio)

6

Position Dilution of Precision (PDOP), used for self-survey only

Mask
Elevation
AMU
PDOP

Default Setting
10°
4
8

Description
Satellite elevation above horizon
Signal strength
Position Dilution of Precision (PDOP), used for self-survey only

Elevation mask
Generally, signals from low-elevation satellites are of poorer quality than signals from higher
elevation satellites. These signals travel farther through the ionospheric and tropospheric layers
and undergo distortion due to these atmospheric conditions. For example, an elevation mask of
10° excludes very low satellites from position fix computations and reduces the likelihood of
potential errors induced by using those signals.

SNR mask
Low SNR values can result from low-elevation satellites, partially obscured signals (forexample, dense foliage), or multi-reflected signals (multipath).
Multi-reflected signals, also known as multipath, can degrade the position and timing solution.
Multipath is most commonly found in urban environments with many tall buildings and a
preponderance of mirrored glass. Multi-reflected signals tend to be weak (low SNR value),since each reflection diminishes the signal.
If the Acutime 360 antenna has a clear view of the sky (outdoor antenna placement), an SNRmask of 35 is recommended for optimal results. However, for indoor use or operation with an
obscured view of the sky, the mask must be low enough to allow valid weak signals to be used.
For indoor operation, an SNR mask of 4 AMU is recommended.

PDOP mask
Position Dilution of Precision (PDOP) is a measure of the error caused by the geometric
relationship of the satellites used in the position solution. Satellite sets that are tightly clusteredor aligned in the sky have a high PDOP and contribute to lower position accuracy.
For most applications, a PDOP mask of 8 offers a satisfactory trade-off between accuracy andGPS coverage.
NOTE – PDOP is applicable only during self-survey or whenever the receiver isperforming position fixes.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 32

System Operation

Operating modes
The Acutime 360 smart antenna operates in one of the following main modes:lSelf-survey mode (position fix operating mode)lOverdetermined clock mode

After establishing a reference position in self-survey mode, the Acutime 360 antenna
automatically switches to overdetermined (OD) clock mode.

Self-survey modeAt power-on, the Acutime 360 smart antenna performs a self-survey by averaging position
fixes, default of 2,000 fixes will be averaged.
The number of position fixes until survey completion is configurable using the 8E-A9 command.
The default mode during self-survey is 3D Automatic, where the receiver must obtain a threedimensional (3D) position solution. The very first fix in 3D Automatic mode must include at least
five satellites. After a successful first fix, only four satellites are required. If fewer than therequired number of satellites are visible, the Acutime 360 antenna suspends the self-survey. 3Dmode may not be achieved when the receiver is subjected to frequent obscuration or when thegeometry is poor due to an incomplete constellation.

Overdetermined clock mode
Overdetermined clock mode is used only in stationary timing applications. This is the default
mode for the Acutime 360 antenna once a surveyed (or user input) position is determined. Afterthe receiver self-surveys its static reference position, it stores the surveyed reference position,
automatically and switches to overdetermined clock mode and determines the clock solution.
The timing solution is qualified by T-RAIM (Time Receiver Autonomous Integrity Monitoring)algorithm, which automatically detects and rejects faulty satellites from the solution.
Using the default anti-jamming setting, a minimum of two satellites is required for an initial PPS
fix in overdetermined clock mode. Once PPS alignment has been determined only a single
satellite is required to maintain that time. If all satellites are lost, then a minimum of two satellites
is again required to re-establish PPS alignment.
In this mode, the Acutime 360 antenna does not navigate or update positions and velocities, butmaintains the PPS output, solving only for the receiver clock error (bias) and error rate (biasrate). If the anti- jamming setting is disabled, only one satellite is required for a valid timing fix. To
set Anti Jamming, see Command packet 0xBB: Set Receiver Configuration.

PPS output options
The PPS (Pulse Per Second) output is the primary timing output generated by the Acutime 360
smart antenna and is provided through an RS-422 differential driver. Although an RS-422
differential receiver provides the best noise immunity, you can use only one side of thedifferential signal for single-ended applications.
To program the characteristics of the PPS, use the following TSIP packets:

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 33

System Operationl

To set an accuracy criterion for the generation of the PPS signal, based on the number ofusable satellites, use packet 0x8E-4E.
The accuracy of the pulse-per-second output depends to some degree on the number ofsatellites used in the solution. In some systems it is preferable to have the PPS generated
only when it meets the highest levels of accuracy and to leave it off if these accuracy levels
are not met.

l

To set the width of the PPS from 10 ms to 500 ms, use packet 0x8E-4F.

Serial data communication
The Acutime 360 smart antenna outputs TSIP superpackets or NMEA messages.
On start-up, the Acutime 360 antenna outputs TSIP packets 0x8F-AB, 0x8F-AC, and PPS. To
enable or disable timing packets and automatic output packets, use packet 0x8E-A5.
The factory default port setting is 115,200-odd-8-1 (in/out). To change the serial port setting andstore it in flash memory, use the appropriate TSIP command. The port can also be configured totransmit timing packets, using packet 0x8E-A5.

GNSS constellation configuration
The Acutime 360 smart antenna can be configured to use either just one GNSS system, suchas GPS, GLONASS, BeiDou, Galileo or QZSS, or a combination of these systems. The
receiver can use any combination of GNSS systems, except where GLONASS and BeiDou areenabled simultaneously. The receiver will automatically clear the BeiDou option when bothconstellations (BeiDou and GLONASS) are enabled.
The table below shows the Protempis recommended constellation options you can select.
GPS

Galileo

GLONASS

BeiDou

QZSS

√
√
√
√
√

√

√

√

√
√
√
√
√

√
√

√
√

√
√

√
√

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 34

System Operation

If a single constellation is chosen, then the PPS and Time alignment is automatically set to thesame constellation.
NOTE – QZSS can not be enabled by itself but it can be enabled any combinations withGPS as QZSS uses the same frequency band with GPS.

Timing operation
The Acutime 360 smart antenna automatically outputs a PPS and time tag. With an accurate
reference position, the receiver automatically switches to an overdetermined clock mode,
activates its T-RAIM algorithm and outputs precise PPS. Using a simple voting scheme basedon pseudo-range residuals, the Acutime 360 antenna's integrity algorithm automaticallyremoves the worst satellite with the highest residual from the solution set if that satellite's
residual is above a certain threshold.
In addition to T-RAIM, the smart antenna implements position integrity checking on startup, incase the receiver has been moved to a new location. When the receiver power-ups with asurveyed (or user input) position in memory, it compares fixes computed from the GNSS
satellites to the surveyed position. If it finds that the surveyed position is off by more than 100
meters horizontally or vertically in the first 60 consecutive GNSS fixes, it deletes the surveyed
position from memory (including non-volatile storage), and restarts the self-survey, provided theself-survey is enabled, and the "position save flag" is set to 1 using the 0x8E-A9 command (seepage 88).
The default configuration of the smart antenna provides optimal timing accuracy. The only item
under user or host control that can affect the receiver's absolute PPS accuracy is the delay
introduced by the antenna cable. For long cable runs, this delay can be significant (1.8 ns perfoot). TSIP packet 8Ex4A sets the cable delay parameter, which is stored in non-volatilememory. For the best absolute PPS accuracy, adjust the cable delay to match the installedcable length (check with your cable manufacturer for the delay for a specific cable type).
Generally, the cable delay is about 1.8 nanoseconds per foot of cable. To compensate for thecable delay, use a negative offset to advance the PPS output.
NOTE – GPS time differs from UTC (Universal Coordinated Time) by a small, submicrosecond offset and an integer-second offset. The small offset is the steering offset
between the GPS DoD clock ensemble and the UTC (NIST) clock ensemble. The large
offset is the cumulative number of leap seconds since 1 January 1980, which, on 1
January 2017 was increased from 17 to 18 seconds. Historically, the offset increases by
one second approximately every 18 to 24 months, usually just before midnight on 30 Juneor 31 December. System designers should note whether the output time is UTC or GPS
time.

Customizing operations
The Acutime 360 smart antenna provides a number of user configurable parameters tocustomize the operation of the unit. These parameters can be stored in non-volatile storage(NVS) to be retained during loss of power and through resets with TSIP command 0x91-02(see page 1). At reset or power-up, the receiver configures itself based on the parameters

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 35

System Operation

stored in the flash memory. You can change the value of these parameters to achieve thedesired operations using a variety of TSIP packets. The smart antenna configures itself basedon the new parameter immediately, but the new parameter value is not automatically saved to
flash. You must use the Save command to retain the parameters changed values in flash.
Send packet 0x91-02 to direct the smart antenna to save the current parameter values to the
flash. To save or delete the stored position, use command packet 0x8E-A6 (see page 87 ). You
can also direct the receiver to set the parameter values to their factory default settings (and toerase the stored position) with packet 0x1E.
In brief, to customize the smart antenna operations for your application:lll

Configure the receiver using TSIP command packets until the desired operation isachieved.
Use TSIP packet 0x91-02 to save the settings in nonvolatile storage (flash). Check for the
TSIP packet 0x91-02 response to verify the settings were saved successfully.
If the position was not automatically saved during the self-survey or if it was manuallyentered, the position can be saved to flash memory using TSIP packet 8E-A6.

The new settings will control receiver operations whenever it is reset or power cycled.

Configuration parameters
The following tables list the user configurable parameters. Each table lists the parameter name,its factory default value, and the TSIP packet that sets or reads the parameter value (typically,
one TSIP packet sets or reads several related parameters).
Parameter

Factory default

Operating dimension

4 (Full Position 3D)

Dynamic code

1 (land)Elevation mask

0.175 radians (10°)

Signal level mask

4.0 AMUPDOP mask

8.0

PDOP switch

6.0

Foliage mode

0 (never)Have reference altitude flag

False

Reference altitude (meters)

0.0

Datum index

WGS 84 Ellipsoid

Position

0x12

Velocity

0x02

Time

0x01

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 36

System Operation

Parameter

Factory default

Auxiliary

0x02

Superpackets output mask (byte 1)

0x32

Superpackets output mask (byte 2)

0x21

Auto TSIP output mask

0xFFFFFFFC0

Port A and B configuration
Parameter

Factory default

Input baud rate

115,200 bps

Output baud rate

115,200 bps

ParityOdd

Data bits

8 bitsStop bits

1 bit

Input protocol

TSIP input

Output protocol

TSIP output

PPS configuration
Parameter

Factory default

PPS enabled switch

EnabledPPS timebase

UTC

PolarityTrue

PPS offset

0.0 seconds

PPS width

10e-3 seconds

PPS driver switch

3 ( at least 1SV)

Position information
Parameter

Factory default

XYZ coordinates

Such that LLA coordinates are all zeros

Have position flag

False

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 37

System Operation

Self-survey configuration
Parameter

Factory default

Survey enable flag

True

Survey length

2000

Survey save flag

False

Survey operating dimension

Full Position 3D

NMEA 0183 protocol and data output options
The National Marine Electronics Association (NMEA) protocol is an industry standard data
protocol, which was developed for the marine industry. Protempis has chosen to adhere
stringently to the NMEA 0183 data specification as published by the NMEA. The Acutime 360
multi-GNSS smart antenna also adheres to the NMEA 0183, Version 3.0 specification.
NMEA data is output in standard ASCII sentence formats. Message identifiers signify what datais contained in each sentence. Commas within the NMEA sentence separate data fields. In the
Acutime 360 GNSS receiver, NMEA is an output-only protocol.
The receiver is shipped from the factory with the TSIP protocol configured on Port A and B. PortA can be reconfigured for NMEA output through Port B using TSIP command packet 0xBC, in
conjunction with the Protempis VTS software, or a user-written serial-interface program.
The NMEA output messages selection and message output rate can be set using TSIP
command packet 0x7A. The default setting is to output the ZDA message at a 1-second
interval, when the receiver output protocol is configured to NMEA, using packet 0xBC.
To use NMEA permanently, use TSIP command 0x8E-26 to store the protocol configuration(0xBC) and NMEA message output setting (0x7A) in the flash memory.
The industry standard port characteristics for NMEA are:l

Baud rate: 115.2 kbpslData bits: 8lParity: NonelStop bits: 1l

No flow control

Any standard serial communications program, such as Windows HyperTerminal or
PROCOMM, can be used to view the NMEA output messages.
TSIP is a binary protocol; it outputs raw binary serial data that cannot be read when using theWindows HyperTerminal or PROCOMM applications.
CAUTION – When you use the TSIP protocol to change port assignments or settings,
confirm that your changes do not affect the ability to communicate with the receiver. For
example, that you have not inadvertently selected PC COM port settings that do notmatch the receiver settings, or changed the output protocol to TSIP if you are not using

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 38

System Operation

the Protempis VTS software.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 39

A
Protempis Standard Interface
ProtocolThe Protempis Standard Interface Protocol (TSIP) provides commands that the systemdesigner can use to configure a GNSS receiver for optimum performance in a variety of
applications, and to customize the configuration of a GNSS module to meet the requirements ofa specific application.
TSIP is a simple bi-directional, binary packet protocol used in a wide variety of Protempis GNSS
receivers. TSIP offers a broad range of command packets and report packets that provide the
GNSS user with maximum control over the Acutime 360 receiver.
This appendix describes how to use the powerful TSIP features, enhance overall system
performance, and reduce the total development time. The reference tables help you determine
which packets apply to your application. For those applications requiring customization, see
Customizing receiver operations, for a detailed description of the key setup parameters.
Application guidelines are provided for each TSIP command packet.
Introduction to TSIP
TSIP packet structure
Physical interface characteristics
Packets output at startup
Receiver warm-start
Default background packets (Port B)
Default automatic position and velocity reports
Automatic primary and supplemental timing reports
Customizing receiver operations
Command Packets: User to Acutime 360 antenna
Report Packets: Acutime 360 to user
Packet Descriptions
TSIP superpackets
Unused or miscellaneous packets

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 40

Protempis Standard Interface Protocol

Introduction to TSIP
TSIP is a powerful and compact interface protocol which has been designed to allow the systemdeveloper a great deal of flexibility in interfacing to a Protempis product. Many TSIP data
packets are common to all products which use TSIP. An example would be a single precision
position output packet. Other packets may be unique to a product. Custom packets are onlyused in the products for which they have been created.

Interface scope
The Acutime 360 GNSS smart antenna has one configurable serial I/O communication port,
which is a bi-directional control and data port utilizing a Protempis Standard Interface Protocol(TSIP). The data I/O port characteristics and other options are user programmable and stored
in non-volatile memory (Flash memory).
The TSIP protocol is based on the transmission of packets of information between the user
equipment and the GPS receiver. Each packet includes an identification code (1 byte,
representing 2 hexadecimal digits) that identifies the meaning and format of the data that
follows. Each packet begins and ends with control characters.

TSIP packet structure
The basic structure of a TSIP packet is the same for both command and report packets.
The packet format is:<DLE> <id> <data string bytes> <DLE> <ETX>
Where:
<DLE>
<ETX>
<id>
<ETX>
<DLE>

is the byte 0x10
is the byte 0x03
is a packet identifier byte, which can have any value exceptingandThe bytes in the data string can have any value. To prevent confusion withthe frame sequences <DLE> <id> and <DLE> <ETX>, every <DLE> byte
in the data string is preceded by an extra <DLE> byte ('stuffing'). These
extra <DLE> bytes must be added ('stuffed') before sending a packet andremoved after receiving the packet.

NOTE – A simple <DLE> <ETX> sequence does not necessarily signify the end of thepacket, as these can be bytes in the middle of a data string. The end of a packet is <ETX>
preceded by an odd number of <DLE> bytes.
Multiple-byte numbers (integer, float, and double) follow the ANSI / IEEE Std. 754 IEEE
Standard for binary Floating-Point Arithmetic. They are sent most-significant byte first. You
must switch the byte order on Intel-based machines .
The data types used in the Acutime 360 smart antenna TSIP are as follows:

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 41

Protempis Standard Interface Protocol

Data Type

Description

UINT8

An 8- bit unsigned number (0 to 255)

SINT8

An 8-bit signed number (-128 to 127)

UINT16

A 16-bit unsigned number (0 to 65,535)

SINT16

A 16-bit signed number (-32,768 to 32,767)

UINT32A 32-bit unsigned number (0 to 4,294,967,295)

SINT32A 32-bit signed number (-2,147,483,648 to 2,147,483,647
Single - Float (4 bytes) (3.4x10-38 to 1.7x1038) (24 bit precision)
Double - Float (8 bytes) (1.7x10-308 to 3.4x10308) (53 bit precision)

NOTE – Default settings are 115,200-8-odd-1

Physical interface characteristics
The basic structure of a TSIP packet is the same for both command and report packets.
The Acutime 360 smart antenna uses high-quality serial I/O components to drive the available
serial transmit and receive channels.
The Acutime 360 antenna is available in an RS-422 configuration. This section explains thecapabilities of each receiver.

Nomenclature
As with previous Multi-GNSS Smart antennas by Protempis, including the Acutis™, Acutime,and Palisade™ products, the Acutime 360 ports are referenced as "A" and "B", and conform tostandards established by the Palisade product line.
Function

LabelInternal

TSIP

Port B

Port 0Timing

Port APort 1

Protocol capabilities
The I/O ports of the Acutime 360 smart antenna are highly configurable. Port settings are stored
in flash memory, and are retained after power failures.
For systems with minimal bandwidth for processing serial data streams, the receivers can be
configured as silent devices, which generate I/O only when polled. The Acutime 360 receivercan be configured to output various automatic report packets and protocols to satisfy
demanding real-time update requirements of complex monitoring systems.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 42

Protempis Standard Interface ProtocolPrimary port features – port B
The Acutime 360 smart antenna features a primary bi-directional port, which is factory
configured for TSIP input and output.

Secondary port features – port A
The Acutime 360 antenna has a bi-directional, programmable secondary port that is designatedas the Timing port.

Event Input
The Acutime 360 antenna features an event input, which can capture and report time stamps
with the same precision as the PPS signal.
Superpacket

LenghtDescription

0x8F-0B

74

Comprehensive time with LLA
position

0x8F-AD22

Primary UTC time with leap
information

The receivers can output the event reports on any available TSIP port.

Packets output at startup
The following messages are output by the receiver at startup. After completing its self- survey,
the receiver automatically outputs a series of packets that indicate the initial operating conditionof the receiver. Messages are output in the following order. Upon output of packet 0x84, thesequence is complete and the receiver is ready to accept commands.
Output ID

Description

Notes

0x46

Receiver health

0x4B

Machine code / status

0x45

Software version

0x83

Double precision XYZ position

If single precision is selected, packet
0x42 is output

0x84

Double precision LLA position

If single precision is selected, packet
0x4A is output

Receiver warm-startOnce the Acutime 360 smart antenna has completed its internal initialization and has output
packet 0x84 (see Packets output at startup), you can send the following commands to restart it.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 43

Protempis Standard Interface Protocol

Output ID

Description

0x2B/23

Initial position (LLA/ECEF)

0x38 (type 2)

GPS almanac (for each SV)

0x38 (type 3)

GPS almanac health

0x38 (type 4)

Ionosphere page

0x38 (type 5)

UTC correction

0x38 (type 6)

GPS ephemeris

0x38 (type 7)

GLONASS almanac

0x38 (type 8)

GLONASS ephemeris

Default background packets (Port B)
Output ID

Description

Notes

0x41

GPS time

Output approximately every 1.6 minutes if
the receiver's GNSS clock is set and thereceiver is not outputting positions.
Output approximately every 2.5 minutes if
the receiver is doing position fixes.

0x46

Receiver healthOutput every second, if the receiver is notdoing fixes.
Output approximately every 30 seconds if
the receiver is doing position fixes.
Whenever any bit in the health message
changes, receiver health is automatically
output.

0x6C

Mode packet

Output approximately every 30 seconds orwhen a constellation change occurs.

NOTE – The background packets listed in this table are automatically output.
Background packets can be turned off. See also Command packet 0x8E-4D: Automatic
Packet Output Mask.
NOTE – The packet 0x4B is always sent with report packet 0x46.

Default automatic position and velocity reports
The Acutime 360 smart antenna automatically outputs position and velocity reports at set
intervals. Report intervals are controlled by packet 0x35.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 44

Protempis Standard Interface Protocol

Output ID

Description

0x42

Single precision XYZ position

0x83

Double precision XYZ position

0x4A

Single precision LLA position

0x84

Double precision LLA position

0x43

Velocity fix (XYZ ECEF)

0x54

Bias and bias rate1

0x56

Velocity fix (ENU)

1When the receiver is in the Manual or Over-determined Clock Mode, it outputs packet 0x54 toprovide the computed clock-only solution.

Automatic primary and supplemental timing reports
Timing Packets 0x8F-AB and 0x8F-AC are automatically output at 1 Hz when enabled bypacket 0x8E-A5. These packets are part of the low-latency packet series 0x8F-AB/AC/AD/OB.

Low-latency timing packets
The Acutime 360 smart antenna features a sequence of high-priority Timing Superpackets,
which are output within a bounded period of time after the PPS.
The Superpackets that meet the LLTP criteria are shown below. Output of each packet can beturned on/off by using the mask in packet 0x8E-A5, but the output order cannot be changed.
The packets may also be requested; refer to the specific packet documentation for details.
LLT Packet ID

Description

Request packet ID

0x8F-ABPrimary Timing

0x8E-AB0x8F-AC

Supplemental Timing

0x8E-AC

0x8E-AD

Primary UTC

0x8E-AD

0x8F-0B

Comprehensive Time & Position

0x8E-0B

The receiver will output all other TSIP packets after the transmission of LLT packet sequence iscomplete.

Satellite data packets
Input ID

Description

Output ID

0x20

Request almanac

0x40

0x27

Request signal levels

0x47

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 45

Protempis Standard Interface Protocol

Input ID

Description

Output ID

0x28

Request GPS system message

0x48

0x29

Request almanac health page

0x49

0x2F

Request UTC parameters

0x4F

0x38

Request/load satellite system data

0x58

0x39

Set/request satellite disable or ignore health

0x59

0x3A

Request last raw measurement

0x5A

0x3B

Request satellite ephemeris status

0x5B

0x3C

Request tracking status

0x5D

Customizing receiver operations
Customizing receiver output for the application
Input ID

Description

Output ID

0x23

Set Initial position (XYZ Cartesian ECEF)

0x24

Request receiver position fix mode

0x6C

0x26

Request receiver health

0x46 and 0x4B

0x27

Request satellite signal levels

0x47

0x2B

Set Initial position (LLA)

0x35

Set input/output options

0x55

0x7A

Set/request NMEA interval and message mask

0x7B

0xBB

Set/request receiver configuration

0xBB

0xBC

Set/request port configuration

0xBC

0x8E-4A

Set/request PPS characteristics

0x8F-4A

0x8E-A5

Set/request packet broadcast mask

0x8F-A5

0x8E-A6

Issue self-survey command

0x8F-A6NOTE – Output is determined by packet 0x35 settings (see Command packet 0x35: Set
or Request I/O Options).

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 46

Protempis Standard Interface Protocol

Customizing receiver operation
Input ID

Description

Output ID

0x1E

Clear memory reset

1

0x2D

Request oscillator offset

0x4D

0x39

Satellite disable or ignore health

0x592

0xBB

Set receiver configuration parameters

0xBB

0x8E-4A

Set PPS characteristics

0x8F-4A

0x8E-4E

Set PPS output option

0x8F-4E

0x8E-4F

Set PPS width (Acutime 360 antenna only)

0x8F-4F

0x8E-20

Set Fixed Point Superpacket output

0x8F-20

1Output is determined by packet 35 settings. For packets 0x1E see Packets output at startup to

determine which packets are output at power-up.
2Not all modes of packet 0x39 cause a reply (see the description for packet 0x39).

Command Packets: User to Acutime 360 antenna
The table below summarizes the packets that can be input by the user. The table includes the
input packet ID, a short description of each packet, and the associated output packet.
Input ID

Description

Output ID

0x1C-01

Firmware version

0x1C-810x1C-03

Hardware component information

0x1C-83

0x1E

Initiate cold reset or factory reset

1

0x1F

Software version

0x45

0x21

Current GPS time

0x41

0x23

Set initial position (XYZ Cartesian ECEF)

0x24

Request GPS satellite selection

0x6C

0x26

Receiver health

0x46, 0x4B

0x27

Request signal levels

0x47

0x2B

Set approximate initial position (LLA)

0x2F

UTC parameters

0x30

Set UTC Date and Time for future roll over date

0x31

Accurate initial position (XYZ Cartesian ECEF)

0x4F

0x31

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 47

Protempis Standard Interface Protocol

Input ID

Description

Output ID

0x32

Set accurate initial position (LLA)

0x32

0x35

Set/Request I/O options

0x55

0x37

status and values of last position and velocity

0x572

0x38

Load or request satellite system data

0x58

0x39

Satellite enable/disable and health heed/ignore

0x593

0x3A

Request last raw measurement

0x5A

0x3B

Satellite ephemeris status

0x5B

0x3C

Request current satellite tracking status

0x5D

0x7A

NMEA Set/Request

0x7B

0xBB

Set receiver configuration

0xBB

0xBC

Set port configuration

0xBC

0x8E-02

Request UTC information

0x8F-020x8E-0B

Request or configure superpacket output

0x8F-0B/0x8F-A5

0x8E-20

Last fix (fixed point)

0x8F-20

0x8E-26

Save configuration

0x8E-41

Request manufacturing parameters

0x8F-410x8E-42

Request production parameters

0x8F-420x8E-4A

Set PPS characteristics

0x8F-4A

0x8E-4D

Packet Output Mask

0x8F-4D

0x8E-4E

PPS output option

0x8F-4E

0x8E-4F

Set PPS width

0x8F-4F

0x8E-A2

UTC/GPS timing

0x8F-A2

0x8E-A5

Packet broadcast mask

0x8F-A5

0x8E-A6

Self-survey commands

0x8F-A6

0x8E-A9

Self-survey parameters

0x8F-A90x8E-AB

Set/request primary timing packet

0x8F-AB

0x8E-AC

Set/Request supplemental timing packet

0x8F-AC

0x8E-AD

0x8F-AD output configuration

0x8F-A5 / 0x8F-AD

1Output is determined by packet 0x35 settings. See Packets output at startup to determine

which messages are output at power-up.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 48

Protempis Standard Interface Protocol

2Output is determined by packet 0x35 settings.
3 Not all packet 0x39 operations have a response. See packet 0x39 description

Report Packets: Acutime 360 to user
The table below summarizes the packets output by the Acutime 360 smart antenna. The table
includes the output packet ID, a short description of each packet, and the associated input
packet. In some cases, the response packets depend on user-selected options.

0x13

Unparsable packet

error

0x1C-81Firmware version

0x1C-01

0x1C-83

Hardware component information

0x1C-03

0x31

Accurate initial position (XYZ Cartesian ECEF)

0x31

0x32

Set accurate initial position (LLA)

0x32

0x41

GPS time

0x21

0x42

Single precision XYZ ECEF position fix

0x35

0x43

Velocity fix (XYZ ECEF)

0x37, auto

0x45

Software version

0x1E, 0x1F, power up

0x46

Health of receiver

0x26

0x47

Signal level for all satellites

0x27

0x4A

Single precision LLA position

0x37, auto

0x4B

Machine code/status

0x26

0x4F

UTC parameters

0x2F

0x54

One-satellite bias and bias rate

0x541

0x55

I/O options

0x35

0x56

Velocity fix (ENU)

0x37, auto

0x57

Status and values of last position and velocity

0x37

0x58

GPS system data acknowledge

0x38

0x59

Satellite enable/disable and health heed/ignore

0x39

0x5A

Last raw measurement

0x3A

0x5B

Satellite ephemeris status

0x3B

0x5D

Current satellite tracking status

0x3C

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 49

Protempis Standard Interface Protocol

0x6C

All-in-view satellite selection

0x24

0x7B

NMEA message output

0x7A

0x83

Double precision XYZ

0x37, auto

0x84

Double precision LLA

0x37, auto

0xBB

Receiver configuration

0xBB

0xBC

Port configuration

0xBC

0x8F-02

UTC information

0x8E-020x8F-0B

Comprehensive time

Auto / Event

0x8F-20

Last fix with extra information (fixed point)

0x8E-20

0x8F-26

Save configuration

0x8E-26

0x8F-41

Stored manufacturing parameters

0x8E-410x8F-42Stored production parameters

0x8E-420x8F-4A

Set PPS characteristics

0x8E-4A

0x8F-4D

Automatic packet output mask

0x8E-4D

0x8F-4E

PPS output option

0x8E-4E

0x8F-4F

Set PPS width

0x8E-4F

0x8F-A2

UTC/GPS timing

0x8E-A2

0x8F-A5

Packet broadcast mask

0x8E-A5

0x8F-A6

Self-survey commands

0x8E-A6

0x8F-A9

Self-survey parameters

0x8E-A9

0x8F-ABPrimary timing packet

Auto

0x8F-AC

Supplemental timing packet

Auto

0x8F-ADUTC event time

Auto / Event

1 Entering 1SV mode initiates automatic output of packet 0x54.

Packet Descriptions
Command packets are sent from an external device, such as a computer or terminal, to thereceiver when requesting report packets, setting receiver parameters, or performing receivercommand operations such as resetting the receiver. Many command packets have acorresponding report packet, which is sent to the external device in response to the command
packet. Some commands perform discrete operations and have no matching report packet.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 50

Protempis Standard Interface Protocol

Command packet 0x1C-01: Firmware version
Use the command packet 0x1C: 01 to obtain the firmware version. The product name is
Acutime360. The packet format is defined in the following table:
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x1C

Packet ID 0x1C1

Subpacket ID

UINT8

0x01

Subpacket 0x01 for software
component version information
requestReport packet 0x1C-81: Firmware component version information
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x1C

Packet ID 0x1C1

Subpacket

UINT8

0x81

Subpacket 0x81 for software
component version information
report2

Reserved

UINT8

Any

Reserved

3

Major version

UINT8

Any

Firmware major version

4

Minor version

UINT8

Any

Firmware minor version

5

Build number

UINT8

Any

Firmware build number

6

Month

UINT8

1-12

Firmware build month

7

Day

UINT8

1-31

Firmware build day

8…9

Year

INT16

Any

Firmware build year

10

Length of firstmodule name

UINT8

Any

The length of the product name
(L1)

11…
(10+L1)

Product name

UINT8StringProduct name in ASCII

Command packet 0x1C-03: Hardware component version information
Use the command packet 0x1C-03 to obtain the hardware component version information.
The report packet is of variable length, depending on the length of the hardware ID.
The serial number, build date fields, and the hardware ID are programmed into the Acutime 360
antenna at production.
The hardware information for Acutime 360 antenna:
Hardware Code:
Hardware ID:

3032
Acutime 360 (BD8)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 51

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x1C

Packet ID 0x1C1

Subpacket ID

UINT8

0x03

SubPacket ID 0x03 for hardware
component version information
requestReport packet 0x1C-83: Hardware component version information
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x1C

1

Subpacket ID

UINT8

0x83

SubPacket ID 0x83 for hardware
component version information
report2-5

Serial Number

UINT32

Any

Board serial number

6

Build day

UINT8

1-31

Day if the board’s build date

7

Build month

UINT8

1-12

Month of the board’s build date

8-9

Build year

UINT16

Any

Year of the board’s build date

10

Build hour

UINT8

0-23

Hour of the board’s build date

11-12

Hardware code

UINT160xBD8Hardware code associated withthe hardware ID

13

Length of
hardware ID

UINT8

Any

The length of the hardware ID (L)

14 (13+L) Hardware ID

UINT8StringHardware ID string in ASCII
Acutime 360

Command packet 0x1E: Initiate Cold, Warm, or Factory ResetThis packet commands the Acutime 360 smart antenna to perform either a cold reset, warm
reset or a factory reset.
ll

A cold reset will clear the GPS data (almanac, ephemeris, etc.) stored in RAM and isequivalent to a power cycle.
A factory reset will additionally restored the factory defaults of all configuration parameters
stored in flash memory. A warm reset clears ephemeris and oscillator uncertainty but
retains the last position, time and almanac. This packet contains one data byte.

The data format is shown below.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x1E

Description

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 52

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

1

Reset

UINT8

"K" (0x4B)

Cold reset"F" (0x46)

Factory reset"N" (0x4E)

Clear navigation data and cold reset

NOTE – The factory reset command will delete the stored position and cause a selfsurvey to restart.

Command packet 0x1F: Request Software Version
This packet requests information about the version of software in Acutime 360 smart antenna.
This packet contains no data. The Acutime 360 smart antenna returns packet 0x45.

Command Packet 0x21: Current Time Request
This packet requests current GNSS time. This packet contains no data. The Acutime 360 smart
antenna returns packet 0x41.

Command packet 0x23: Initial Position (XYZ Cartesian ECEF) command
This packet provides the GNSS receiver with an approximate initial position in XYZ coordinates.
This packet is useful if you have moved more than about 100 meters since the previous fix.
NOTE – The GNSS receiver can initialize without any data from the user; this packet
merely reduces the time required for initialization.
This packet is ignored if the receiver is already calculating positions.
The origin is the earth’s center. The X-axis points toward the intersection of the equator and theGreenwich meridian, the Y-axis points toward the intersection of the equator and the 90°
meridian, and the Z-axis points toward the North Pole. The cold-start default LLA (not XYZ)
position is 0, 0, 0.
Byte

Item

Type

Units

0-3

X

SingleMeters4-7

YSingleMeters

8-11

ZSingleMetersCommand packet 0x24: Request GNSS satellite selection
This packet requests a list of satellites used for the current position/time fix. This packet contains
no data. The Acutime 360 antenna returns packet 0x6C.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 53

Protempis Standard Interface Protocol

Command Packet 0x26: Health Request
This packet requests health and status information from the Acutime 360 antenna. This packet
contains no data. The Acutime 360 antenna returns packets 0x46 and 0x4B.

Command packet 0x27: Request Signal Levels
This packet requests signal levels for all satellites currently being tracked. This packet contains
no data. Acutime 360 smart antenna returns packet 0x47.

Command packet 0x2B: Initial Position (Latitude, Longitude, Altitude)
This packet is used for A-GPS (GPS only) to set and approximate initial WGS-84 position(Latitude, Longitude, and Altitude coordinates) for the receiver. This packet is useful when areceiver is moved more than 1,000 Km from the location of the last position fix. The GNSS
receiver returns report packet 0x2B, which indicates if the position was accepted by thereceiver.
NOTE – The GNSS receiver can initialize itself without any data from the user; thispacket merely reduces the time required for initialization.
This packet is ignored if the receiver is already calculating positions. The data format is shown in
the tables below.

Command Packet 0x2B Data Format (Double Precision)
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x2B

1-8

Latitude

DOUBLE

Radians+ for north, - for south

9-16

Longitude

DOUBLE

Radians+ for east, - for west

17-24

Altitude

DOUBLE

Meters25-28

Horizontal
Uncertainty

SINGLE

MetersDefault: 30,000 Range: 0 ~3,000 Km

29-32

VerticalUncertainty

SINGLE

MetersDefault: 500 Range: 0 ~ 500 m

Command Packet 0x2B Data Format (Single Precision)
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x2B

1-4

Latitude

SINGLE

Radians+ for north, - for south

5-8Longitude

SINGLE

Radians+ for east, - for west

9-12

Altitude

SINGLE

MetersProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 54

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

13-16

Horizontal
Uncertainty

SINGLE

MetersDefault: 30,000

17-20

VerticalUncertainty

SINGLE

MetersDefault: 500

Command packet 0x2F: UTC Parameters request
This packet requests the current UTC-GPS time offset (leap seconds). The packet has no data.
The receiver returns packet 0x4F.

Command packet 0x30: Set UTC Date and Time for future roll over dateThis packet changes the Base week, to extend out the last valid WNRO number which would
normally be based on the firmware build date.
Byte

Item

Type

Description

0

Packet ID

UINT8

30

1-2

Year

UINT16

Four Digits of the year

3

UTC:Month

UINT8

1-12

4

UTC:Day of Month

UINT8

1-31

5

UTC:Hour

UINT8

0-23

6

UTC:Min

UINT8

0-59

7

UTC:Sec

UINT8

0-59

NOTE – Do not use a date earlier than the current firmware date.

Command packet 0x31: Accurate Initial Position (XYZ Cartesian ECEF)
This packet is identical in content to packet 0x23; it provides an initial position to the Acutime 360
smart antenna in XYZ coordinates. However, the GNSS receiver assumes the position
provided in this packet to be accurate. This packet is used for satellite acquisition aiding insystems where another source of position is available and in time transfer (one-satellite mode)applications. For acquisition aiding, the position provided by the user to the Acutime 360
antenna in this packet should be accurate to a few kilometers. For high-accuracy time transfer,
position should be accurate to a few meters. T-RAIM flags come on if this position is notaccurate enough.
Entering an accurate position sets the self-survey completion state to 100%. The Acutime 360
antenna returns report packet 0x31, which indicates if the position was accepted by thereceiver. The uploaded position is not stored in flash memory unless it is stored with command
packet 0x8E-26. The input position is reported by packet 0x8F-AC.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 55

Protempis Standard Interface Protocol

Command Packet 0x31 Data Format (Single Precision)
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x31

1-4

X-axisSINGLE

Meters

5-8

Y-axisSINGLE

Meters9-12Z-axisSINGLE

MetersCommand Packet 0x31 Data Format (Double Precision)
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x31

1-8

X-axisDOUBLE

Meters

9-16

Y-axisDOUBLE

Meters17-24

Z-axisDOUBLE

MetersCommand packet 0x32: Accurate Initial Position (Latitude, Longitude,
Altitude)This packet provides an accurate initial position to the Acutime 360 smart antenna in latitude,
longitude, and altitude coordinates. Either the single precision or the double precision version ofthis packet may be used, however, we recommend using the double precision version for
greatest accuracy. The Acutime 360 antenna returns report packet 0x32, which indicates if theposition was accepted by the receiver.
The GPS receiver uses this position for performing time-only fixes. If a survey is in progress
when this command is issued, the survey is aborted, and this position data is used immediately.
The coordinates entered must be in the WGS-84 datum. The Acutime 360 antenna willautomatically switch to the overdetermined timing mode when this command is issued.
Note that this position is not automatically saved to flash memory. If you want to save thisposition, first set the position, wait at least 2 seconds and then use packet 8E-A6 to save theposition.
NOTE – When converting from degrees to radians use the following value for PI:
3.1415926535898

Command Packet 0x32 Data Format (Single Precision)
Byte

Item

Type

Units

0-3

Latitude

SINGLE

Radians, north

4-7Longitude

SINGLE

Radians, east

8-11

Altitude

SINGLE

MetersProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 56

Protempis Standard Interface Protocol

Command Packet 0x32 Data Format (Double Precision)
Byte

Item

Type

Units

0-7

Latitude

DOUBLE

Radians, north

8-15

Longitude

DOUBLE

Radians, east

16-23

Altitude

DOUBLE

MetersCommand packet 0x35: Set or Request I/O Options
This packet requests the current I/O option states and allows the I/O option states to be set as
desired.
To request the option states without changing them, send this packet with no data bytes. Tochange any option states, include 4 data bytes with the values. The I/O options, their default
states, and the byte values for all possible states are shown below.
These options can be set into non-volatile memory (flash ROM) with the 0x8E-26 command.
The Acutime 360 antenna returns packet 0x55.
The following abbreviations apply to the following table:l

ALT: Altitudel

ECEF: Earth-Centered, Earth-Fixedl

XYZ: Cartesian coordinatesl

LLA: Latitude, Longitude, Altitudel

HAE: Height Above Ellipsoidl

WGS-84: Earth model (ellipsoid)l

MSL geoid: Earth Mean Sea Level modelUTC: Universal coordinated Time

Byte

Data Type0

Packet ID

Bit

Value

Meaning

AssociatedPacket0x35

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 57

Protempis Standard Interface Protocol

Byte

Data Type

Bit

Value

Meaning

AssociatedPacket1

Position

00

ECEF off

0x42 or 0x83

1

ECEF on0

LLA off

1

LLA on0

HAE (datum)

1

MSL geoid (Note 1)

3

0

Reserved

40Single-precision position

1

Double-precision position 0x83/84

5-7

0Reserved

00

ECEF off

1

ECEF on0

ENU off

1

ENU on2-70Reserved

00Reserved

1

Now use 0x8E-A2

1

2

2

Velocity

1

3

Timing

0x4A or 0x84

0x4A or 0x84

0x42/4A

0x43

0x56

0x42, 0x43, 0x4A
0x83, 0x84, 0x56

4

Reserved

0-7

Reserved

NOTE – When using the MSL altitude output, the current datum must be set to WGS-84*Note that these should be enabled with great care because there can be a lot of data
generated and, unless the baud rate is increased above the default 115200 baud,
packets may be dropped.

Command packet 0x37: Request status and values of last position
This packet requests information regarding the last position fix (normally used when the GPS
receiver is not automatically outputting fixes). The Acutime 360 antenna returns the
position/velocity auto packets specified in the 0x35 message as well as message 0x57. This
packet contains no data.

Command packet 0x38: Request/load Satellite System Data
This packet is used for A-GPS (GPS only). This packet requests current satellite data (almanac,
ephemeris, and so on) or permits loading initialization data from an external source (forProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 58

Protempis Standard Interface Protocol

example, by extracting initialization data from an operating GNSS receiver unit through a datalogger or computer and then using that data to initialize a second GNSS receiver unit). The
Acutime 360 smart antenna returns packet 0x58.
NOTE – The Acutime 360 antenna can initialize itself without any data from the user; itmerely requires more time.
To request data without loading data, use only bytes 0 through 2; to load data, use all bytes.
Before loading data, observe the caution notice below. The data formats are located in Report
Packet 0x58.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x38

1

Operation

UINT8

1
2

Request data from GPS receiver
Load data into GPS receiver

2

Type of data

UINT8

2

Almanac3

Health page, t_oa, WN_oa

4

Ionosphere

5

UTC

6

Ephemeris

3

Sat PRN #UINT8Description

Selects an individual satellite or all
satellites
0: Data is not satellite specific1-32: Data is requested for a specificsatellite PRN (pseudorandom
number)4

Length (n)UINT8Number of bytes of data to be loaded

5 to
n+3

Data

UINT8

Satellite data

WARNING – Loading all satellite data at once sends a lot of bytes to the unit, which could
overwhelm the unit’s serial receive buffer. Always wait for the acknowledge packet
before sending the next data block.

Command packet 0x39: Satellite Attribute Database Command
Normally, the GNSS receiver selects only healthy satellites (based on transmitted values in theephemeris and almanac) that satisfy all mask values for use in the position solution. This packet
allows you to override the internal logic and force the receiver to either unconditionally disable aparticular satellite or to ignore a bad health flag. The GNSS receiver returns packet 0x59 for
operation modes 3 and 6 only.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 59

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

0

Operation

BYTE

1

Enable for selection (default)

2

Disable for selection

3

Request enable or disable status
on byte 1selection

4

Heed health on satellite

5

Ignore health on satellite

6

Request heed or ignore healthon byte 1 selection

0

All SVs

1

GPS

2

GLONASS

3

BeiDou4

Galileo

5

QZSS

6

SBAS

1

SV Type

2

SVID

BYTE

BYTE

If byte 1 value:
0 then 0

All SVs

1 then 1-32

GPS

2 then 65-96

GLONASS

3 then 201-237

BeiDou4 then 97-133

Galileo

5 then 193-195

QZSS

6 then 33-54

SBAS

NOTE – Send a WARM start command (0x1E 0x0E) after setting new values.

Command packet 0x3A: Request last raw measurement
This packet requests the most recent raw measurement data for one specified satellite. The
Acutime 360 smart antenna returns packet 0x5A if data is available.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x3A

Description

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 60

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

1

Satellite PRN

UINT8

0

All SV in current tracking set

1-32

GPS

65-96

GLONASS

97-133

Galileo

183,192,193,200

QZSS

201-237

BeiDouConvert values to
Hexadecimal

Command packet 0x3B: Satellite ephemeris status request (for GPS only)This packet requests the current status of satellite ephemeris data. The Acutime 360 antenna
returns packet 0x5B, if data is available.
Byte

Item

Type

Value

Description

1

Satellite #

BYTE

0

All satellites for which ephemeris data
is available

1-32

Required satellite

Command packet 0x3C: Request satellite tracking status
This packet requests the current satellite tracking status. The GNSS receiver returns packet
0x5D if data is available.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x3C

1

Satellite PRN

UINT8

0

All SV in current tracking set

1-32

GPS

65-96

GLONASS

97-133

Galileo

193,194,195

QZSS

201-237

BeiDouConvert values to
Hexadecimal

Description

Command packet 0x7A: NMEA Interval and Message Mask command
The NMEA message determines whether or not a given NMEA message will be output. If thebit for a message is set, the message will be sent every “interval” second. Use the values shown
below to determine the NEMA interval and message mask. While fixes are being generated theoutput order is: ZDA, GGA, GLL, VTG, GSA, GSV, RMC.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 61

Protempis Standard Interface Protocol

Byte

Item

Type

Value

0

Packet ID

UINT8

0x7A

1

Subcode

UINT8

0

2

Interval

UINT8

1-255

3

Reserved

UINT8

0

4

Reserved

UINT8

0

0

RMC

Bit

0
1

1-7

Reserved

Bit

0

0

GGA

Bit

0
1

Off
On

1

GGL

Bit

0
1

Off
On

2

VTG

Bit

0
1

Off

5

6

Bit

Description

Fix interval in seconds

Off
On

On

3

GSV

Bit

0
1

Off
On

4

GSA

Bit

0
1

Off
On

5

ZDA

Bit

0
1

Off
On

6-7

Reserved

Bit0

Report packet 0x31: Accurate Initial Position (XYZ Cartesian ECEF)
This packet is sent in response to command packet 0x31. The packet indicates if the receiveraccepted the accurate initial position.
Byte

Item

Type

Value

Description

0

StatusUINT801

Position accepted
Position not accepted1

Reserved

UINT80Reserved

Report packet 0x32: Accurate Initial Position (Latitude, Longitude, Altitude)
This packet is sent in response to command packet 0x32. The packet indicates if the receiveraccepted the accurate initial position.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 62

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

0

StatusUINT801

Position accepted
Position not accepted1

Reserved

UINT80Reserved

Report packet 0x41: GPS Time report
Legacy packet: Use 0x8F-AB or 0x8F-AC instead.
This packet provides the current GNSS time of week and the week number. The GNSS
receiver sends this packet in response to packet 0x21.
Byte

Item

Type

Units

0-3

GNSS time of week

SingleSeconds

4-5

GNSS week number

Integer

Weeks

6-9

UTC offset

SingleSeconds

Report packet 0x42: Single-precision position fix
This packet provides current GPS position fix in XYZ ECEF coordinates. If the I/O Position
option is set to “XYZ ECEF” and the I/O Precision-of-Position output is set to single-precision,then the GPS receiver sends this packet each time a fix is computed and at start-up. The data
format is shown below.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x42

1-4

X

SINGLEmeters

5-8

Y

SINGLEmeters

9-12

Z

SINGLEmeters13-16

time-of-fix

SINGLE

seconds

Desctiption

The time-of-fix is in GNSS time or UTC as selected by the I/O Timing option in command
packet 0x35. Packet 0x83 provides a double-precision version of this information.

Report packet 0x43: Velocity fix, XYZ ECEF
This packet provides current GNSS velocity fix in XYZ ECEF coordinates. If the I/O Velocity
option (packet 0x35) is set to “XYZ ECEF”, then the GNSS receiver sends this packet each timea fix is computed or in response to packet 0x37. The data format is shown below. The time-of-fix
is in GPS, GLONASS or UTC as selected by the I/O Timing option.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x43

Description

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 63

Protempis Standard Interface Protocol

Byte

Item

Type

Value/Unit

Description

1-4

X velocity

SINGLEmeters/second

5-8

Y velocity

SINGLEmeters/second

9-12

Z velocity

SINGLEmeters/second

13-16

bias rate

SINGLEmeters/second

17-20

time-of-fix

SINGLE

seconds

Report packet 0x45: Software version information
This packet provides information about the version of firmware running on the Acutime 360
smart antenna. The GNSS receiver sends this packet after power-on in response to packet
0x1F.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x45

1

Description

UINT8

Major version number of application

UINT8

Minor version number of application

UINT8

Month

4

UINT8

Day

5

UINT8

Year number minus 2000

6

UINT8

Major revision number of GNSS core

7

UINT8

Minor revision number of GNSS core

2
3

Application Layer ofthe firmware

9

GPS Core Layer of the
UINT8firmware
UINT8

10

UINT8

8

Month
Day
Year number minus 2000

Report packet 0x46: Health of Receiver report
This packet provides information about the satellite tracking status and the operational health of
the receiver. The receiver sends this packet after power-on or software-initiated resets, in
response to packet 0x26, during an update cycle, when a new satellite selection is attempted,
and when the receiver detects a change in its health. Packet 0x4B is always sent with thispacket. The data format is shown below:

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 64

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Meaning0

Status code

Byte

00 hex01 hex03 hex
08 hex
09 hex0A hex0B hex0C hexBB hexDoing position fixes
Do not have GPS time yet
PDOP is too highNo usable satellites
Only 1 usable satellite
Only 2 usable satellites
Only 3 usable satellites
The chosen satellite is unusable
Have GPS time fix (OD mode)

1

Error codes

Byte

See Report Packet 0x46, below

The error codes in Byte 1 of packet 0x46 are encoded into individual bits within the byte. The bit
positions and their meanings are shown below:
Error code bit position

Meaning if bit value = 10 (LSB)123456
7 (MSB)

Unused, always returned as ‘1’
UnusedUnusedUnusedAntenna feed line fault (open or short)
Antenna is shorted
UnusedUnusedReport packet 0x47: Signal level for all satellites tracked
This packet provides received signal levels for all satellites currently being tracked or on which
tracking is being attempted (i.e., above the elevation mask and healthy according to thealmanac). The receiver sends this packet in response to packet 0x27. The data format is shown
below. Up to 14 satellite number/signal level pairs may be sent, as indicated by the count field.
The signal level is normally positive. If it is zero then that satellite has not yet been acquired. The
absolute value of the signal level field is the last known signal level of that satellite.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x47

1

Count

UINT8

2

Satellite number 1

UINT8

3-6

Signal level 1

SINGLE

7

Satellite number 2

UINT8

8-11

Signal level 2

SINGLE(etc.)(etc.)(etc.)

Description

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 65

Protempis Standard Interface Protocol

NOTE – The signal level provided in this packet is a linear measure of the signal strength
after correlation or de-spreading. Units are dB-Hz.

Report packet 0x4A: Signal precision LLA position fix
This packet provides current GNSS position fix in LLA (latitude, longitude, and altitude)
coordinates. If the I/O position option is set to LLA and the I/O precision of position output is set
to single precision, then the receiver sends this packet each time a fix is computed. The data
format is shown below.
Byte

Item

Type

Value/Unit

Description

0-3

Latitude

SINGLE

radians+ for north, - for south

4-7

Longitude

SINGLE

radians+ for east, - for west

8-11

Altitude

SINGLEmeters

12-15

Clock bias

SINGLEmeters16-19

Time-of-fix

SINGLE

seconds

Always relative to GPS

The LLA conversion is done according to the datum selected; the default is WGS-84. Altitude isreferred to the datum or the MSL Geoid, depending on which I/O LLA altitude option is selectedwith packet 0x35. The time of fix is in GPS, GLONASS time or UTC, depending on which I/Otiming option is selected.
CAUTION – When converting from radians to degrees, significant and ready visible
errors will be introduced by use of an insufficiently precise approximation for the constant
π (pi). The value of a constant π as specified in ICD-GPS-200 is 3.1415926535898.
CAUTION – The MSL option is only valid with the WGS-84 datum. Do not use otherdatums.

Report packet 0x4B: Machine/Code ID and Additional status report
The Acutime 360 antenna transmits this packet in response to packet 0x26 and following achange in state. This packet identifies the receiver and may present error messages. Packet
0x46 is always sent with this packet. The machine ID can be used by equipment communicatingwith the receiver to determine the type of receiver to which the equipment is connected. Thenthe interpretation and use of packets can be adjusted accordingly.
Byte

Item

Type

Meaning0

Machine ID

BYTE

32

1

Status 1

BYTE

See below for the Status 1 codes

2

Status 2

BYTE

Superpackets are supported

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 66

Protempis Standard Interface Protocol

The status codes are encoded into individual bits within the bytes:
Status 1 bit position

Meaning if bit value = 10 (LSB)Not used1

Not used2

Not used

3

The Almanac stored in the receiver is not complete & current

4-7

Not used

Report packet 0x4F: UTC parameters report
This packet is sent in response to command packet 0x2F and contains 26 bytes. It reports the
UTC information broadcast by the GPS system. For details on the meanings of the following
parameters, consult ICD-200, Sections 20.3.3.5.2.4, 20.3.3.5.1.8, and Table 20-IX.
On the simplest level, to get UTC time from GPS time, subtract ΔTLS seconds. The otherinformation contained in this packet indicates when the next leap second is scheduled to occur.
Byte

Value

Type

0-7

A0

Double8-11

A1Single

12-13

ΔTLS

Integer

14-17

TOT

Single18-19

WNT

Integer

20-21

WNLSF

Integer

22-23

DN

Integer

24-25

ΔTLSF

Integer

Report packet 0x54: Bias and Bias rate report
The receiver sends this packet to provide the computed clock-only solution when the receiver isin the manual or automatic Over-determined Clock mode or Time Only (1-SV) mode.
Byte

Item

Type

Value

0-3

Bias

SINGLE

Meters4-7Bias rate

SINGLE

Meter/second

8-11

Time-of-fix

SINGLE

Seconds

The bias is the offset of the receiver internal time clock from GPS time. Bias is expressed asmeters of apparent range from the satellites, and corrects the 1 PPS output.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 67

Protempis Standard Interface Protocol

Bias rate is the frequency error of the receiver internal oscillator. It is expressed as apparent
range rate. Time-of-fix is in GNSS or UTC time as selected by the I/O Timing option in packet
0x35.
CAUTION – For accurate interpretation of the propagation delay, the precise constant forthe speed of light must be used. The ICD-200 value for the speed of light is 299,792,458m/s.

Report packet 0x55: I/O Options
This packet provides the current I/O option states in response to packet 0x35 request. The data
format is the same as for packet 0x35.

Report packet 0x56: Velocity Fix, East-North-Up (ENU)
If East-North-Up (ENU) coordinates have been selected for the I/O Velocity option, thereceiver sends this packet each time that a fix is computed or in response to packet 0x37 (lastknown fix). The data format for this packet is shown below.
Byte

Item

Type

Value/Unit

Description

0

Packet ID

UINT8

0x56

1-4

East velocity

SINGLEm/s+ for east, - for west

5-8

North velocity

SINGLEm/s+ for north, - for south

9-12

Up velocity

SINGLEm/s+ for up, - for down

13-16

Clock bias rate

SINGLE

m/s

17-20

Time-of-fix

SINGLE

seconds

NOTE – The time-of-fix is in GPS or UTC time as selected by the I/O timing option.

Report packet 0x57: Information about last computed fix
This packet provides information concerning the time and origin of the previous position fix. The
receiver sends this packet, among others, in response to packet 0x37. The data format is shown
below.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x57

1

Source of info

UINT8

0
1

Description

Old fix
New fix

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 68

Protempis Standard Interface Protocol

Byte

Item

Type

Value/Unit

Description

2

Tracking mode

UINT8

0
1
2
3
4
5
6

No previous fix
Time only -SV
Not used
2D
3D
Over-determined clock
Not used

3-6

Time of last fix

SINGLE

Seconds

7-8

Week of last fix

UINT16weeks

Report packet 0x58: Satellite System Data/Acknowledge from ReceiverThis packet provides GPS data (almanac, ephemeris, and so on). The receiver sends thispacket in response to packet 0x38 (acknowledging the loading of data). The data format isshown below. The table and section numbers referred to in the “Meaning” column reference the
ICD-GPS-200.

Data format
Byte

Item

Type

Value/Unit

Description

0

Packet ID

UINT8

0x58

1

Operation

UINT8

2
3

Data out
No data on SV

2Type of data

UINT8

1
2
3
4
5
6

Not used
Almanac
Health page, t_oa, WN_oa
IonosphereUTC
GPS Ephemeris

3

Sat PRN #

UINT8

0
1-32

Data is not satellite specificData is requested for a specificsatellite PRN (pseudorandom
number)4

Length (n)

UINT8

5 to
(n+4)

Data

nBytesNumber of data bytes to load

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 69

Protempis Standard Interface Protocol

Almanac parameters
Byte

Item

Type

Definition/ ICD-GPS-200

5t_oa_raw

UINT8

Sec 20.3.3.5.1.2

6

SV_HEALTHUINT8

Sec 20.3.3.5.1.2

7-10

e

SingleSec 20.3.3.5.1.2

11-14

t_oa

SingleSec 20.3.3.5.1.2

15-18

i_o

SingleSec 20.3.3.5.1.2

19-22

OMEGADOT

SingleSec 20.3.3.5.1.2

23-26

sqrt_A

SingleSec 20.3.3.5.1.2

27-30

OMEGA_0

SingleSec 20.3.3.5.1.2

31-34

OMEGA

SingleSec 20.3.3.5.1.2

35-38

M_0

SingleSec 20.3.3.5.1.2

39-42

a_f0

SingleSec 20.3.3.5.1.2

43-46

a_f1

SingleSec 20.3.3.5.1.2

47-50

Axis

SingleSec 20.3.3.5.1.2

51-54

n

SingleSec 20.3.3.5.1.2

55-58

OMEGA_nSingleSec 20.3.3.5.1.2

59-62

ODOT_nSingleSec 20.3.3.5.1.2

63-66

t_zs

UINT16

Sec 20.3.3.5.1.2, see Note 2.

67-68

weeknum

UINT16

Sec 20.3.3.5.1.2

69-70

WN_oa

UINT16

Sec 20.3.3.5.1.2

NOTE – All angles are in radians. If data is not available, t_zc is set to -1.0.

Satelite health
Byte

Item

Type

Definition/ ICD-GPS-200

5week number for
healthUINT8

Sec 20.3.3.5.1.3

6-37

SV health

UINT8

Sec 20.3.3.5.1.3

38

t_oa for health

UINT8

Sec 20.3.3.5.1.3

39

current t_oa

UINT8units = seconds/2048

40-41

current week #UINT16

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 70

Protempis Standard Interface Protocol

Ionosphere parameters
Byte

Item

Type

Definition/ ICD-GPS-200

5-12

not used

13-16

α0

SingleSec 20.3.3.5.1.9

17-20

α1

SingleSec 20.3.3.5.1.9

21-24

α2

SingleSec 20.3.3.5.1.9

25-28

α3

SingleSec 20.3.3.5.1.9

29-32

β0

SingleSec 20.3.3.5.1.9

33-36

β1

SingleSec 20.3.3.5.1.9

37-40

β2

SingleSec 20.3.3.5.1.9

41-44

β3

SingleSec 20.3.3.5.1.9

TypeMeaning

UTC parameters
Byte

Item

5-17

Not used

18-25

A0

DoubleSec 20.3.3.5.1.8

26-29

A1
ΔtLS

SingleS16

Sec 20.3.3.5.1.8
Sec 20.3.3.5.1.8

30-31

tot

SingleSec 20.3.3.5.1.8

32-35

WNt

UINT16

Sec 20.3.3.5.1.8

36-37

WNLSF

UINT16

Sec 20.3.3.5.1.8

38-39

DN

UINT16

Sec 20.3.3.5.1.8

40-41

ΔtLSf

S16

Sec 20.3.3.5.1.8

TypeMeaning

Ephemeris data
Byte

Item

5

SV number UINT8 SV
PRN number

6-9t_ephemSingleTime of collection (note, if data is missing orinvalid, t_ephem will be negative)

10-11

week number

UINT16

GPS week number 0 thru 1023

12

codeL2Sec 20.3.3.3, Table 20-I

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 71

Protempis Standard Interface Protocol

Byte

Item

Type

Meaning

13

L2Pdata14

SV accuracy raw

UINT8

Sec 20.3.3.3, Table 20-I

15

SV health

UINT8

Sec 20.3.3.3, Table 20-I

16-17

IODC

UINT16

Sec 20.3.3.3, Table 20-I

18-21

tGD

SingleSec 20.3.3.3, Table 20-I

22-25

toc

SingleSec 20.3.3.3, Table 20-I

26-29

af2

SingleSec 20.3.3.3, Table 20-I

30-33

af1

SingleSec 20.3.3.3, Table 20-I

34-37

afo

SingleSec 20.3.3.3, Table 20-I

38-41

SV accuracy

SingleSec 20.3.3.3, Table 20-I

42

IODE

UINT8

Sec 20.3.3.4

43

fit_interval

UINT8

Sec 20.3.3.4

44-47

Crs

SingleSec 20.3.3.4

48-51

Δn

SingleSec 20.3.3.4

52-59

M0

DoubleSec 20.3.3.4

60-63

Cuc

SingleSec 20.3.3.4, radians

64-71

e

DoubleSec 20.3.3.4

72-75

CUS

SingleSec 20.3.3.4, radians76-83

sqrt(A)

DoubleSec 20.3.3.4

84-87

toe

SingleSec 20.3.3.4

88-91

Cic

SingleSec 20.3.3.4

92-99

OMEGA_0

DoubleSec 20.3.3.4

100-103 Cis

SingleSec 20.3.3.4

104-111 io

DoubleSec 20.3.3.4

112-115 Crc

SingleSec 20.3.3.4

116-123 OMEGA

DoubleSec 20.3.3.4

124-127 OMEGADOT

SingleSec 20.3.3.4

128-131 IDOT

SingleSec 20.3.3.4

132-139 Axis

Double= (sqrt_A)2

Sec 20.3.3.3, Table 20-I

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 72

Protempis Standard Interface Protocol

Byte

Item

Type

Meaning140-147 n

Doublederived from delta_n148-155 r1me2

Double= sqrt (1.0-e2)

156-163 OMEGA_n

Doublederived from OMEGA_0, OMEGADOT

163-171 ODOT_n

Doublederived from OMEGADOT

Report packet 0x59: Satellite Attributes Database Report
This packet is returned in response to packet 0x39 if operation mode 3 or 6 is used with packet
0x39.
Normally the GNSS receiver selects only healthy satellites (based on transmitted values in theephemeris and almanac) that satisfy all mask values, for use in the position solution.
Packet 0x59 indicates whether or not each satellite is allowed to be selected for use in theposition solution, and whether each satellite’s health is to be heeded or ignored.
NOTE – When viewing the satellite disabled list, the satellites are not numbered but are in
numerical order. The disabled satellites are signified by a 1 and enabled satellites are
signified by a 0.
Byte

Item

Type

Value

Description

0

Operation

BYTE

3

Request enable or disable status onbyte 1 selection

6

Request heed or ignore health onbyte 1 selection
1

2~38

SV Type

SVID

BYTE

BYTE

1 then 1-32

GPS

2 then 65-96

GLONASS

3 then 201-237

BeiDou4 then 97-133

Galileo

5 then 193-1956
then 33-54

QZSS
SBAS

1 byte per SV(depends on byte 0
value)
0
1

Enable SV selection or head SV
healthDisable SV selection or ignore SV
healthProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 73

Protempis Standard Interface Protocol

Report packet 0x5A: Raw Data Measurement Data
This packet provides raw GNSS measurement data. If the packet 0x35 auxiliary option byte bit
1 is set, this packet is sent automatically as measurements are taken.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x5A

1

SV PRN #SINGLE

2-5

Sample length

SINGLE

milliseconds

6-9

Signal level

SINGLE

dB-Hz

10-13

Code phase

SINGLE

1/16th chip

14-17

Doppler

SINGLE

Hertz @ L1

18-25

Time of measurement

DOUBLE

seconds

Description

NOTE – The sample length is the number of milliseconds over which the sample wasaveraged.
NOTE – The code phase value is the average delay over the sample interval of thereceived C/A code, and is measured with respect to the receiver’s millisecond timingreference.

Signal level
The Signal Level (byte 6) is a linear approximation of C/N0 which is stated in antenna amplitude
measurement units (AMUs), a Protempis devised unit.
The C/N0 is affected by five basic parameters:lsignal strength from the GPS satellitelreceiver/antenna gainl

pre-amplifier noise figurelreceiver noise bandwidthlaccumulator sample rate and statistics

Codephase
The codephase (byte 10) value is the average delay over the sample interval of the received
C/A code and is measured with respect to the receiver's millisecond timing reference. Thus, it
includes all receiver, satellite, and propagation biases and errors. It is expressed in 1/16th of a
C/A code chip.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 74

Protempis Standard Interface Protocol

Doppler
The Doppler (byte 14) value is apparent carrier frequency offset averaged over the sample
interval. It is measured with respect to the nominal GPS L1 frequency of 1575.42 MHz,
referenced to the receiver's internal oscillator. Thus, it includes all receiver and satellite clock
frequency errors. It is expressed in Hertz at the L1 carrier.

Time of measurement
The time of measurement (Byte 18) is the center of the sample interval adjusted by adding thereceiver-supplied codephase (modulo mS) to a user-determined integer number of mS
between receiver and satellite.
The receiver codephase resolution is 1/16th of a C/A code chip. This corresponds to:
1/16 × C/A code chip ≈ 977.517ns/16 ≈ 61.0948 ns≈ 61.0948 × speed of light, m/s≈ 18.3158 meters
The integer millisecond portion of the pseudo-range must then be derived by utilizing theapproximate receiver and satellite positions. Rough receiver position (within a few hundred
kilometers) must be known; the satellite position can be found in its almanac/ephemeris data.
Each mS integer corresponds to:
C/A code epoch × speed of light = 1 ms × speed of light m/s≈ 300 km (approximate)≈ 299.792458 km (precise)
The satellite time-of-transmission for a measurement can be reconstructed using the code
phase, the time of measurement, and the user-determined integer number of milliseconds.

Report packet 0x5B: Satellite Ephemeris Status Report (GPS only)This packet is sent in response to packet 0x3B and optionally, when a new ephemeris (basedon IODE) is received. It contains information on the status of the ephemeris in the receiver for agiven satellite.
Byte

Item

Type

Units

0

Packet ID

U8

0x5B

1

Satellite PRN number

Byte

2-5

Time of Collection

Single6

Health

Byte

7

IODE

Byte

8-11

toe

Single12

Fit Interval Flag

Byte

seconds

seconds

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 75

Protempis Standard Interface Protocol

Byte

Item

Type

Units

13-16

SV Accuracy (URA)

Singlemeters

The satellite PRN number is in the range 1–32. Time of Collection is the GPS time when thisephemeris data was collected from the satellite. Health is the 6-bit ephemeris health. IODE, toe,and Fit Interval Flag are as described in ICD-GPS-200. SV Accuracy (URA) is converted tometers from the 4-bit code as described in ICD-GPS-200.

Report packet 0x5D: Satellite Tracking Status
The receiver sends this packet in response to command packet 0x3C.
Byte

Bit

Item

Type

Value

Description

0

Packet ID

UINT8

0x5D

1

SV PRN number

UINT8

See table in 0x3C description

2

Channel number

UINT8

Channel number minus 1

3

Acquisition flag

UINT8

0
1
2

Never acquired
AcquiredRe-opened search4

SV used in Position
or Time calculation

UINT8

0
1

Not Used
Used

5-8

Signal level

SINGLE

9-12

Time of lastmeasurement

SINGLE

seconds

13-16

Elevation angle

SINGLE

radians

17-20

Azimuth angle

SINGLE

radians

21

Old measurement
flag

UINT8

0
>0

Flag not set
Measurement is old

22

Integer msec flag

UINT8

0
1
2
3
4

Don’t know msec
Known from subframe
Verified by bit crossing
Verified by good fix
Suspect msec error

23

Bad data flag

UINT8

0
1
2

Flag not set
Bad parity
Bad ephemeris health

24

Data collection flag

UINT8

0
>0

Flag not set
Collection in progressdB-Hz
GPS TOW

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 76

Protempis Standard Interface Protocol

Byte

Bit

Item

Type

Value

Description

25

Used flags

Bit field

Bit 0
Bit 1
Bit 2-7

Satellite used in timing fix
Satellite used in position fix
Reserved

26

SV Type

UINT8

0
1
2
3
4
5
6
7

GPS
GLONASS
BeiDouGalileo
Reserved
QZSS
Reserved
Reserved

Report packet 0x6C: All-in-View Satelite selection
This packet provides a list of satellites used for position or time-only fixes by the GNSS receiver.
The packet also provides the PDOP, HDOP, VDOP and TDOP of that set and provides thecurrent mode (automatic or manual, 3D or 2D, overdetermined clock, etc.) This packet hasvariable length equal to 17+nsvs where nsvs is the number of satellites used in the solution.
The GNSS receiver sends this packet in response to packet 0x24 when the selection list is
updated. If enabled with packet 8E-A5, the receiver will send this packet whenever the selection
is updated. The data format is shown below.
Byte

Bit

0
1

0-2

3

Item

Type

Value

Packet ID

UINT8

0x6C

Fix dimension

Bit field

Description

3
4
5

2D fix3D fixOD clock fix

0
1

Auto
ManualFix mode

Bit field

2-5

PDOP

SINGLE

PDOP

6-9

HDOP

SINGLE

HDOP

10-13

VDOP

SINGLE

VDOP

14-17

TDOP

SINGLE

TDOP

18

No. of SVs in fix

UINT8

Count

19-n

SV PRN

UINT8(1-224)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 77

Protempis Standard Interface Protocol

Report packet 0x7B: Set NMEA Message Output
This packet is sent in response to command packet 7A and has the same data format as packet
7A.

Report packet 0x83: Double Precision XYZThis packet provides current GNSS position fix in XYZ ECEF coordinates. If the I/O “position”
option is set to “XYZ ECEF” and the I/O double position option is selected, the receiver sends
this packet each time a fix is computed.
Byte

Item

Type

Units

0

Packet ID

1-8

X

DOUBLEmeters

9-16

Y

DOUBLEmeters

17-24

Z

DOUBLEmeters25-32

clock bias

DOUBLEmeters33-36

time-of-fix

SINGLE

seconds

0x83

NOTE – The time-of-fix is in GPS, GLONASS or UTC time, as selected by the I/O“timing” option. Packet 0x42 provides a single-precision version of this information.

Report packet 0x84: Double precision LLA position (Fix and Bias
information)
This packet provides current GNSS position fix in LLA coordinates. If the I/O “position” option is
set to “LLA” and the double position option is selected (see packet 0x35), the receiver sends thispacket each time a fix is computed.
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x84

1-8

latitude

DOUBLE

radians

9-16

longituda

DOUBLE

radians+ for north, - for south

17-24

altitude

DOUBLEmeters+ for east, - for west

25-32

clock bias

DOUBLEmeters33-36

time-of-fix

SINGLE

seconds

NOTE – The time-of-fix is in GPS, GLONASS, or UTC time, as selected by the I/O“timing” option.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 78

Protempis Standard Interface Protocol

CAUTION – When converting from radians to degrees, significant and readily visible
errors will be introduced by use of an insufficiently precise approximation for the constantp (PI). The value of the constant PI as specified in ICDGPS-200 is 3.1415926535898.

Command packet 0xBB: Set Receiver Configuration
In query mode, packet 0xBB is sent with a single data byte and returns report packet 0xBB in
the format shown below.
Data Format (Query Only)
Byte

Item

Type

Value

0

Packet ID

UINT8

0xBB

1

Subpacket ID

UINT8

0x00

Description

Query mode

TSIP packet 0xBB is used to set the GNSS Processing options. The table below lists theindividual fields within the 0xBB packet.
Byte

Item

Type

Value

Description

Default

0

Packet ID

UINT8

0xBB

1

Subpacket ID

UINT8

0x00

Receiverconfiguration block2

Receiver mode

UINT8

0
1
3
4
5
6
7

Automatic
Time only (1SV)
Horizontal (2D)
Full position (3D)Reserved
Reserved
Over-determined
clock

3

Reserved

UINT8

N/A

4

Reserved

UINT8

N/A

5

Reserved

UINT8

N/A

6-9

Elevation mask

SINGLE0- π/2Lowest satellite
elevation for fixes

0 degrees

10-13

AMU Mask

SINGLE

0-55

Minimum signal levelfor fixes

4.0

14-17

PDOP mask

SINGLE

Maximum PDOP for
position fixes, only
active during selfsurvey and in PVT
mode

6

#0

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 79

Protempis Standard Interface Protocol

Byte

Item

Type

Value

18-21

PDOP switch

SINGLE

Unused, value
ignored

22

Reserved

UINT8

N/A

23

Anti-Jam Mode

UINT8

0
1

Description

Disabled
EnabledDefault

1

24-25

Reserved

UINT8

N/A

26

Measurement
rate

UINT8

0

1 Hertz

1Hz

27

Position Fix rate

UINT8

0

1 Hertz

1Hz

28

Constellation

Bit

0
1
2
3
4
5
6
7

GPS
GLONASS
Reserved
BeiDouGalileo
QZSSReserved
Reserved

29-40

Reserved

UINT8

N/A

NOTE – Byte 28 is used for enabling/disabling use of a constellation. For GPS only modethe 1st bit position is set to 1 (0001), for GLONASS only mode the 2nd bit position is set to
1 (e.g., 0010) and for GPS & GLONASS mode both 1st and 2nd bits are set to 1 (0011).
NOTE – The only limitation on satellite selection is that both GLONASS and BeiDoucannot be enabled at the same time. If they are both enabled then the unit will disable
BeiDou and use GLONASS only.
CAUTION – The operation of the Acutime 360 antenna can be affected adversely if
incorrect data is entered in the fields associated with packet 0xBB.
NOTE – When sending packet 0xBB, fields that are specified as “N/A” or if you do notwant to alter a specified field, send a value of 0xFF for UINT8 types and a value of -1.0 for
floating point types. The Acutime 360 antennawill ignore these values.

Command packet 0xBC: Set Port Configuration
TSIP packet 0xBC is used to set and query the port characteristics. In query mode, packet
0xBC is sent with a single data byte and returns report packet 0xBC.
NOTE – The input and output baud rates must be the same.
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 80

Protempis Standard Interface Protocol

Command packet 0xBC Data Format (Query Mode)
Byte

Item

Type

Value

0

Packet ID

UINT8

0xBC

1

Port Number

UINT8

0
1
FF

Description

Port
Port B
Current port

The table below lists the individual fields within the packet 0xBC when used in the set mode andwhen read in the query mode.
Command and Report packet 0xBC Field Data Format
Byte

Item

Type

Value

0

Packet ID

UINT8

0xBC

1

Port to Change

UINT8

0
1
0xFF

Port
Port B
Current port

2

Input Baud Rate

UINT8

6
7
8
9
10
11

4800 baud
9600 baud
19200 baud
38400 baud
57600 baud
115200 baud3

Output Baud Rate UINT8As above

As above

4# Data bits

UINT8

2
3

7 bits8 bits5

Parity

UINT8

0
1
2

None
Odd
Even

6

# Stop bits

UINT8

0
1

1 bit
2 bits7

Flow Control

UINT8

0

8

Input Protocols

UINT8

9

10

Output Protocols

Reserved

Description

2
4

TSIP
NMEA

2
4

TSIP
NMEA

UINT8

UINT8

0

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 81

Protempis Standard Interface Protocol

TSIP superpackets
Several packets have been added to the core TSIP protocol to provide additional capability forthe receivers. In packets 0x8E and their 0x8F responses, the first data byte is a subcode whichindicates the superpacket type. For example, in packet 0x8E-A6, A6 is the subcode thatindicates the superpacket type. Therefore the ID code for these packets is 2 bytes long followedby the data.

Command packet 0x8E-02: Request UTC Information
This packet allows the user to query UTC Information. The module responds to a query withpacket 0x8F-02
Byte

Item

Type

Value

0

Packet ID

UINT8

8E

1

Subpacket ID

UNIT8

02

2

Type of data

UNIT8

01
02
03

Description

GPS
BeiDouGalileo

Command packet 0x8E-0B: Request or configure superpacket output
The 0x8E-0B packet is identical in function to the 0x8E-AD packet. If the 0x8E-0B byte
sequence is sent with no data, the receiver will return a 0x8F-0B packet on Port B. The timereported by the 0x8F-0B packet on Port B is always the beginning of the current second.

Command packet 0x8E-20: Request Last Fix with Extra Information
This packet requests packet 0x8F-20 or marks it for automatic output. If only the first byte (20) issent, a 0x8F-20 report containing the last available fix will be sent immediately. If two bytes aresent, the packet is marked / unmarked for auto report according to the value of the second byte.
Byte

Item

Type

Units

0

Packet ID

UINT8

0x8E

1

Subpacket ID

BYTE

0x20

2

Mark for Auto-report

BYTE

0 = do not auto-report
1 = auto-report

NOTE – Auto-report requires that Superpacket output is enabled. See Command packet
0x35: Set or Request I/O Options. This packet must also be enabled with packet 0x8EA5.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 82

Protempis Standard Interface Protocol

Command packet 0x8E-26: Write Receiver Configuration to Non-volatile
Memory (Flash)This command packet causes the current configuration settings to be written to non-volatilestorage. This packet contains only a single byte: the sub-packet ID. Upon receiving thecommand, the receiver will write the configuration and send a report packet 0x8F-26 when theoperation is completed. It typically takes about one second to write the user configuration.
CAUTION – If the user application needs to power down the receiver after issuing thiscommand, it must wait until 0x8F-26 report packet is received.

Command packet 0x8E-41: Request Manufacturing Parameters
This packet is used to request the manufacturing parameters stored in non-volatile memory.
Send this packet with no data (don’t forget the subpacket ID) to request packet 0x8F-41.

Command packet 0x8E-42: Stored Production Parameters
This packet is used to request the production parameters stored in non-volatile memory. Send
this packet with no data (don’t forget the subpacket ID) to request packet 0x8F-42.

Command packet 0x8E-4A: Set PPS characteristics
This packet allows you to query (by sending the packet with no data bytes) or set Acutime 360
antenna PPS characteristics. Acutime 360 antenna responds to a query or set command withpacket 0x8F-4A.
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x8E

1

Subcode

UINT8

0x4A

Always2

PPS driver switch

UINT8

0
1

off
on

3

Reserved

UINT8

4

PPS polarity

UINT8

5–12

PPS offset ofcable delay (seenote)

DOUBLE

13–16

Reserved

Reserved
01

positive
negativeseconds

Reserved

NOTE – Negative offset values advance the PPS, and are normally used to compensate
for cable delay

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 83

Protempis Standard Interface Protocol

Command packet 0x8E-4D: Automatic Packet Output Mask
This packet is used to disable automatic output of packets on Port B.
ll

To request the current mask, send this packet with no data bytes except the subcode byte.
The receiver returns packet 0x8F-4D.
To set the automatic packet output mask , send this packet with 4 data bytes. This mask
only disables automatic packet output. Packets generated in response to TSIP set or querycommands will always be output by the receiver.

Bit

Output packet

Default
A2K

When output

Description

0 (LSB)

0x40

0After Decode

Almanac data collected fromsatellite.

10x58, 0x5B

0After Decode

Ephemeris data collected fromsatellite.

2

0x4F

0

After Decode

UTC data collected from satellite.

23

0x58

0

After Decode

Ionospheric data collected fromsatellite.

4

0x48

0

After Decode

GPS Message.

5

0x49

0

After Decode

Almanac health page collectedfrom satellite.

6

Reserved

1

Reserved

7

Reserved

1

Reserved

8

0x41

1

9

Reserved

1

Reserved

10

Reserved

1

Reserved

11

6D, 46, 4B, 82

1

12-29

Reserved

130

42, 43, 4A, 54,
56, 83, 84, 8F-20

1

New Fix Update

Kinetic and Timing information.
Output must be enabled using I/O
options

31

5A

1

New Fix

Raw Measurement Data Output
must be enabled using I/O options

New Fix

Constellation

Partial and full fix complete andpacket output timer has expired.

New satellite selection
Reserved

Command packet 0x8E-4E: Set PPS output option
This command packet sets the PPS driver switch to one of the values listed in Table A-52. The
current driver switch value can be requested by sending the packet with no data bytes except

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 84

Protempis Standard Interface Protocol

the subcode byte.The response packet is 0x8F-4E.
Driver switch values 3 and 4 only make sense in overdetermined timing mode. In any position fix
mode, the effective choices are always on, or during fixes which you get if you set the driverswitch to 3 or 4.
The Acutime 360 smart antenna can also be configured to generate an Even Second pulse inplace of the PPS pulse by setting the value as shown in the table below.
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x8E

0

Subpacket ID

UINT8

0x4E

1

PPS Driver Switch

UINT8

2

PPS is always on. PPS is generated
every second.

3

PPS is output when at least one
satellite is tracking. PPS is generated
every second.

4

PPS is output when at least threesatellites are tracking. PPS isgenerated every second.

130

PPS is always on. PPS is generated
every even second PPS is output
when at least one satellite is tracking.
PPS is generated every evensecond.

131

PPS is output when at least threesatellites are tracking.

132

PPS is generated every even second

Command packet 0x8E-4F: Set PPS widthThis command packet sets the PPS width to a value in the range of 10 milliseconds to 500
milliseconds. The receiver returns packet 0x8F-4F. The current PPS width can be requested bysending this packet with no data bytes except the subpacket byte.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x8E

1

Subcode

UINT8

0x4F

2-9

PPS width

UINT16

Description

seconds

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 85

Protempis Standard Interface Protocol

Command packet 0x8E-A2: UTC/GNSS TimingThis command packet sets the UTC/GNSS timing mode (time and data fields) in packet
0x8F-AB, and the temporal location of the Acutime 360 antenna output PPS. Send packet
0x8E-A2 with no data to request the current settings. The Acutime 360 antenna replies withresponse packet 0x8F-A2.
Byte

Item

Type

Bit

Value

Description

0

Packet ID

UINT8

0x8E

1

Subpacket ID

UINT8

0xA2

Subpacket ID

2Time Flag

Bit field

001

GPS time (Default)
UTC or GNSS time1

0
1

GPS PPS (Default)
UTC or GNSS PPS

2Reserved

3

Reserved

4-5

0
1
2
3

UTC (USNO) time
GLONASS time
BeiDou time
Galileo time

6-7

0
1
2
3

UTC (USNO) PPSGLONASS PPS
BeiDou PPS
Galileo PPS

Command packet 0x8E-A5: Packet Broadcast Mask
Use command packet 0x8E-A5 to set the packet broadcast masks or to request the current
mask settings. The Acutime 360 antenna replies to request with response packet 0x8F-A5. The
broadcast mask is bitwise encoded to enable turning on and off the broadcast of certain
packets.
For those broadcast packets that have multiple format, the Acutime 360 antenna will broadcast
only one of the formats. If more than one of the formats is masked on for broadcast, then theformat with the greatest precision of content masked on will be sent and the rest will not.
For each bit in the mask that is used, the coding is as follows:
0: Turn off broadcast of this packet
1: Turn on broadcast of this packet
Byte

Item

Type

0

Subpacket ID

UINT8

Bit

Value

Description

0xA5

Subpacket ID

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 86

Protempis Standard Interface Protocol

Byte

Item

Type

Bit

Value

Description

1-2

Mask 0

Bit field

018F-20 on Port B

1

0

Reserved

20

Reserved

30

Reserved

40

Reserved

51

Enable auto TSIP outputs

0x8F-AB

6

0

0x8F-AB Primary timing packet output

0x8F-AC

700x8F-AC Supplemental timing packet
output0x8F-0B

8

0Synchronous 0x8F-0B (1Hz) on PortA

0x8F-0B

9

1

Event output of 0x8F-0B on Port A

0x8F-0B

10

0Event output of 0x8F-0B on Port B

0x8F-AD

11

0

Synchronous 0x8F-0B (1Hz) on PortB

0x8F-AD

12

1

Synchronous 0x8F-AD (1Hz) on PortA

0x8F-AD

13

1

Event output of 0x8F-AD on Port A

0x8F-AD14

Event output of 0x8F-AD on Port B

0x8F-AD

15

Synchronous 0x8F-AD (1Hz) on PortB

3-4

Mask 2Bit field

Reserved

Command packet 0x8E-A6: Self-Survey Command
Use command packet 8E-A6 to issue a self-survey command, to save the current position in
flash or to delete the position saved in flash. The GNSS receiver returns report packet 0x8F-A6,
which indicates the result of the requested operation.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x8E

1

Subpacket ID

UINT8

0xA6

2

Self-survey
command

UINT8

0
1
2

Description

Restart self-survey
Save position to Flash
Delete position from Flash

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 87

Protempis Standard Interface Protocol

Command packet 0x8E-A9: Self-Survey parameters
Use command packet 8E-A9 to set the self-survey parameters or to request the current
settings. The Acutime 360 replies to requests with response packet 8F-A9.

Data fieldslSelf-Survey Enable: Use this field to enabled or disabled the self-survey mechanism.
0: Disable the self-survey mechanism
1: Enable the self-survey mechanismlPosition Save Flag: Use this field to tell the self-survey mechanism to automatically save(or to not save) the self-surveyed position at the end of the self-survey procedure.
0: Don't automatically save the surveyed position when the self-survey is complete.
1: Automatically save the surveyed position when the self-survey is complete.

l

Self-Survey Length: Use this field to specify the number of position fixes that are to beaveraged together to form the self-surveyed position used for clock-only fixes.
Limits: 1 to (232 - 1) fixeslUncertainty threshold. An index from 1 to 100. The smaller the number the higher degreeof certainty of the self-survey fix will be used to fix the position of the unit for OD mode.
Depending on the constellation and position of the satellites a small index number can leadto survey times of many hours as the unit may only qualify a small rate of fixes to complete
the designated survey length (default 2000).

Byte

Item

Type

Value

Description

0

Subcode

UINT8

0xA9

1

Self-Survey Enable

UINT8

0
1

Disabled
Enabled2

Position Save Flag

UINT8

0
1

Don't save position
Save self-surveyed position at theend of the survey

3-6

Self-Survey Length

UINT32see
above

Number of fixes

7-10

Horizontal
Uncertainty

Float>0<=100 Horizontal position uncertainty.
Default: 100

11-14

Vertical Uncertainty

Float>0<=100 Vertical position uncertainty. Default:
100

Command packet 0x8E-AB: Request Primary Timing packet
Use this command packet to request the Primary Timing packet 0x8F-AB. By default, theAcutime 360 antenna automatically sends packet 0x8F-AB once per second so it is notProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 88

Protempis Standard Interface Protocolnecessary to request it. To receive 0x8F-AB information by request only, use packet 0x8E-A5 todisable the automatic output.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x8E

1

Subpacket ID

UINT8

0xAB

2

Request Type

UINT8

0
1
2

Description

Send 0x8F-AB immediately
Send 0x8F-AB on-time next second
Send 0x8F-AB and 0x8F-AC on-time
next second

The Request Type item determines how the Acutime 360 antenna will reply to this command:Type

Description0

The most current primary timing values will be sent in packet 0x8F-AB immediately.

1

The response is not sent immediately. Instead packet 0x8F-AB is sent after the
next PPS output. This is the same time that the packet would be automatically sent
if enabled.

2

Same as type 1 except that both 0x8F-AB and 0x8F-AC are sent after the next
PPS output.

Command packet 0x8E-AC: Request Supplemental Timing packet
Use command packet 0x8E-AC to request the Supplemental Timing packet 0x8F-AC. By
default, the Acutime 360 antenna automatically sends packet 0x8F-AC once per second so it is
not necessary to request it. To receive 0x8F-AC information by request only, use packet 0x8EA5 to disable the automatic output.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x8E

1

Subpacket ID

UINT8

0xAC

2

Request Type

UINT8

0
1
2

Description

Send 0x8F-AC immediately
Send 0x8F-AC on-time next second
Send 0x8F-AB and 0x8F-AC on-time
next second

The Request Type item determines how the Acutime 360 antenna will reply to this command:Type

Description0

The most current primary timing values will be sent in packet 0x8F-AC
immediately.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 89

Protempis Standard Interface Protocol

Type

Description

1

The response is not sent immediately. Instead packet 0x8F-AC is sent after the
next PPS output. This is the same time that the packet would be automatically sent
if enabled.

2

Same as type 1 except that both 0x8F-AB and 0x8F-AC are sent after the next
PPS output.

Command packet 0x8E-AD: Request or Configure Superpacket Output
If the 0x8E-AD byte sequence is sent with no data, the receiver generates an 0x8F-AD packet
on port B. The time reported by the 0x8F-AD packet on port B is always the beginning of thecurrent second.
Output of the 0x8F-AD Primary UTC timing packet on Port A is configured by sending a 3- byte
message 0x8E-AD n, where n ranges from 0 to 3, as defined below. The receiver returns the
0x8F-A5 Superpacket Output Mask.
Byte

Item

Type

Value

Default

Description

0

SubcodeByte

AD

RequiredSuperpacket ID

1

Flag

Byte

0

3

Disable packet output on port A

1

Output packet on port A only at
PPS

2

Output packet on port A only at
event input

3

Output at both event input and
PPS

Report packet 0x8F-02: UTC information
This packet is sent in response to 0x8E-02.
Byte

Item

Type

Value

GPS

BeiDouGalileo0

Packet ID

UINT8

8F

1

Subpacket ID

UINT8

02

2

Constellation

UINT8

1

2

3

3-10

A_0

Double11-14

A_1

Single

21-22

WN_t

UINT16

NA / 023-24

WN_LSFUINT16

NA / 0Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 90

Protempis Standard Interface Protocol

Byte

Item

Type

Value

25-26

DN

UINT1627-28

Delta_t_LSF

SINT16GPS

BeiDouGalileo

Report packet 0x8F-0B: Comprehensive Time
The output of the packet is synchronized with the PPS. Report packet 0x8F-0B provides easy
identification of each timing pulse and contains all the information required for most timing andsynchronization applications. Output of this packet can be disabled and configured using the
0x8E-A5 packet on Port B. If output of the 0x8F-AD packet is also enabled, the 0x8F-0B packet
will always be output after the 0x8F-AD packet.
Byte

Item

Type

Units

0

Packet ID

UINT8

1

Subpacket ID

UINT8Subcode 0x0B

2-3

Event CountINTEGER

Zero for PPS.

4 -11

UTC/GPS TOWDOUBLE

UTC/GPS time of week (seconds)

12

Date

BYTE

Date of PPS or event

13

Month

BYTE

Month of PPS or event

14 -15Year

INTEGERYear of PPS or event

16

Receiver Mode

BYTE

Receiver operating dimensions
0: Horizontal (2D)
1: Full Position (3D)
2: Single Satellite (OD)
3: Automatic (2D/3D)
4: N/A 5: Clock hold (2D)
6: OD clock mode (default)

17-18

UTC Offset

INTEGERUTC offset value (seconds)

19-26

Reserved

DOUBLE

Reserved

27-34

Reserved

DOUBLE

Reserved

35-38

Reserved

SINGLE

Reserved

39-42

Reserved

SINGLE

Reserved

43-50

Latitude

DOUBLE

Latitude in radians

51-58

Longitude

DOUBLE

Longitude in radians

59-66

Altitude

DOUBLE

Altitude according to current datum, meters

67-74

Satellite ID

8 BYTES

Identification numbers of tracking andusable satellites

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 91

Protempis Standard Interface Protocol

Bytes 67 through 74 identify the tracking and usable satellites. A tracked satellite isdistinguished from a usable satellite by a negative sign (−) appended to its PRN number.
In this Superpacket, time is referenced to UTC to correspond to the default PPS timebase. To
configure the receiver to output time relative to GPS, the PPS must be characterizedaccordingly. Command packet 0x8E-4A enables the PPS to be re-defined at run-time andstores the new settings in flash memory.
NOTE – Leap seconds cannot be predicted in advance using only the 0x8F-0B packet. A
leap second can be identified by observing that the date does not increment once 86400
seconds have elapsed in the current day. The date rollover is delayed for the duration of
the leap second, and the day/month/year count reported does not increment to the next
day until the beginning of the second following the leap event. Decoding of the 0x8F-AD
packet provides complete leap status information.
NOTE- The information reported in the 0x8F-0B message relates to only the GPS constellation.
This message should no longer be used and considered obsolete for future projects.
The UTC offset is incremented at the beginning of the first second following the leap second.

Report packet 0x8F-20: Last Fix with Extra Information (binary fixed point)
This packet provides information about the time and origin of the previous position fix. This is thelast-calculated fix; it could be quite old. The receiver sends this packet in response to Packet
0x8E-20; it also can replace automatic reporting of position and velocity packets. Automatic
output of 0x8F-20 must also be enabled by setting bit 5 of byte 0 in command packet 0x0x35
and bit 0 of bytes 1-2 in command packet 0x8E-A5.
Byte

Item

Type

Description0

Subpacket ID

Byte

ID for this subpacket (always 0x20)

1

Key Byte

Byte

N/A

2-3

east velocity

IntegerUnits 0.005m/s or 0.020m/s (see Byte 24).
Overflow =0x8000

4 -5

north velocity

IntegerUnits 0.005m/s or 0.020m/s (see Byte 24).
Overflow =0x8000

6-7

up velocity

IntegerUnits 0.005m/s or 0.020m/s (see Byte 24).
Overflow = 0x8000

8-11Time of Week

Unsignedlong

GPS Time in milliseconds

12-15

LatitudeLong
integer

Latitude, units = 2^31 semicircle, according tocurrent datum. Range = -2^30 to 2^32

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 92

Protempis Standard Interface Protocol

Byte

Item

Type

Description

16-19

Longitude

Unsignedlong

Longitude east of meridian, units = 2^31
semicircle, according to current datum. Range = 0
to 2^32

20-23

AltitudeLong
integer

Altitude above ellipsoid, mm, according current
datum.

24

Velocity scaling

When bit 0 is set to 1, velocities in bytes 2-7 havebeen scaled by 4

25

Reserved

0

26

Datum

Datum index + 1

27

Fix Type

Byte

Type of fix. This is a set of flags.
0 (LSB) 0: Fix was available
1: No fix available
1 0: Fix is autonomous
1: N/A
2 0: 3D fix
1: 2D fix
3 0: 2D fix used last-circulated altitude
1: 2D fix used entered altitude
4 0: Unfiltered
1: Position or altitude filter on
5-7 Unused (always 0)

28

Num SVs

Byte

Number of SV used for fix. Zero if no fix wasavailable.

29

UTC Offset

Byte

Number of leap seconds between UTC time andGPS time.

30-31

Week

Integer

GPS time of fix (weeks)32-115Fix SVsFix SVs

Repeated groups of 2 bytes, one for each satellite.
The bytes are 0 if group N/A.

Byte 0: PRNX

Byte

Satellite number and IODC-IODE. PRN = lower
six bits of PRNX

Byte 1: IODE

Byte

IODC = (PRNX/64)x256 + IODE

8 Bytes

The broadcast ionospheric parameters116-123 Iono Param

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 93

Protempis Standard Interface Protocol

Report packet 0x8F-26: Save Receiver Configuration to Non-volatile
Storage Memory
This packet is returned in response to save configuration to flash memory packet 0x8F-26.
The packet indicates whether the receiver configuration has been successfully saved to nonvolatile memory.
Byte

Item

Type

Value

Description

0

Subcode

UINT8

0x26

Packet subpacket

1-4

StatusUINT320
1successfully stored receiver
failed to store receiver configuration

Report packet 0x8F-41: Stored manufacturing operating parameters
This packet is sent in response to a command 0x8E-41.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x8F

1

Subpacket ID

UINT8

0x41

2-3

Board serial number prefix

UINT16

4-7

Board serial number

UINT328

Year of build

UINT8

9

Month of build

UINT8

10

Day of build

UINT8

11

Hour of build

UINT8

12-15

Reserved

SINGLE

16-17

Reserved

UINT16

Report packet 0x8F-42: Stored Production parameters
This packet is sent in response to 0x8E-42.
Byte

Item

Type

Value/Unit

0

Packet ID

UINT8

0x8F

1

Subpacket ID

UINT8

0x42

2

Production options prefix

UINT8

3

Production number extension UINT8

4-5

Case serial number prefix

UINT16

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 94

Protempis Standard Interface Protocol

Byte

Item

Type

6-9

Case serial number

UINT32

10-13

Production number

UINT32

14-15

Reserved

UINT1616-17

Machine identification
numberUINT16

18-19

Reserved

UINT16

Value/Unit

Report packet 0x8F-4A: Set PPS characteristics
This packet is sent in response to a query by packet 0x8E-4A. See the corresponding command
packet for information about the data format.
Byte

Item

Type

Units

0

Packet ID

UINT8

0x8F

1

Subpacket ID

Byte

0x42

2

PPS Driver Switch

Byte

0: Off
1: On

3Time Base

Byte

0: GPS
1: UTC (default)

4

PPS Polarity

Byte

0: Positive (default)
1: Negative

5-12

PPS Offset or Cable Delay

DoubleSeconds

13-16

Reserved

Reserved

Report packet 0x8F-4D: Automatic Packet Output Mask
This packet provides information on the automatic packets that may be output by the receiver.
This packet is sent in response to 0x8E-4D query, or is set.
Byte

Item

Type

Meaning0

Packet ID

UINT8

0x8F

1

Subpacket ID

Byte

ID for this sub-packet is always
0x4D

2-5

Bit Mask

ULONG

Bits in the mask enable output
packetsl

A “0” in the bit position means that automatic output of the associated packets is disabled.

l

A “1” in the bit positions means that the associated packets can be automatically output.

The meaning and packets output by each set bit is as follows:
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 95

Protempis Standard Interface Protocol

Bit

Output packet

When output

Meaning00x40

After Decode

Almanac data collected fromsatellite

10x58, 0x5B

After Decode

Ephemeris data collectedfrom satellite

2

0x4F

After Decode

UTC data collected fromsatellite

30x58

After Decode

Ionospheric data collectedfrom satellite

4

0x48

After Decode

GPS Message

5

0x49

Almanac health page
collected from satellite

6

Reserved

7

Reserved

80x41

New Fix

Partial & full fix complete andpacket output timer has
expired

9

Reserved

10

Reserved

11

0x6C

Constellation
changeNew satellite selection

12

Reserved

13-29

Reserved

30

4A, 8F-20, 42, 43, 54, 56,
83, 84

New fix update

311

0x5A

New Fix

1A 1 in the bit mask indicates that output for the associated packets is ON; a 0 indicates that theoutput is turned OFF.

Report packet 0x8F-4E: PPS output
This report packet is output after the command packet 0x8E-4E has been executed. See thecorresponding command packet for information about the data format.

Report packet 0x8F-4F: PPS widthThis report packet is output after the command packet 0x8E-4F has been executed. See Report
Packet 0x8F-4A: PPS Characteristics.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 96

Protempis Standard Interface Protocol

Report packet 0x8F-A2: UTC/GPS TimingThis packet is sent in response to command packet 0x8E-A2. See the corresponding command
packet for information about the data format.

Report packet 0x8F-A5: Packet Broadcast Mask
This packet is sent in response to 0x8E-A5 command and describes which packets are
currently automatically broadcast. A ‘0’ in a bit field turns off broadcast, and a ‘1’ in a bit fieldenables broadcast. See the corresponding command packet for information about the data
format.

Report packet 0x8F-A6: Self-Survey Command
This packet is sent in response to command packet 0x8E-A6. The packet indicates the result of
the requested self-survey operation.
Byte

Item

Type

Value

0

Packet ID

UINT8

0x8F

1

Sub-code

UINT8

0xA6

Packet sub-code

UINT8

0
1
2

Restart self-survey
Save position to Flash memory
Delete position from Flash memory

UINT8

0
1

Requested command successful
Requested command failed

2

3

StatusDescription

Report packet 0x8F-A9: Self-Survey Parameters
Packet 0x8F-A9 is sent in response to command packet 0x8E-A9 and describes the current
self-survey parameters. See the corresponding command packet for information about the data
format.

Report packet 0x8F-AB: Primary Timing Packet
This packet provides time information once per second if enabled with command packet 0x8EA5. GPS week number, GPS time-of-week (TOW), UTC integer offset, time flags, data andtime-of-delay (TOD) information is provided. This packet can be requested with packet 0x8EAB. If enabled, this packet will begin transmission within 30 ms after the PPS pulse to which it
refers.
Byte

Item

Type

Bit

Value

0

Packet ID

UINT8

0x8F

1

Subpacket ID

UNIT8

0xAB

2-5

Time of week

UINT32

Description

GPS seconds of week or from
0x8E-A2 time selection

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 97

Protempis Standard Interface Protocol

Byte

Item

Type

Bit

Value

Description

6-7

Week Number

UINT16

GPS Week Number or from
0x8E-A2 time selection

8-9

UTC Offset

SINT16UTC Offset (seconds) fromchosen constellation timereference. Always = 0 when
GLONASS time is selected.

10Time Flag

Bit field

001

GPS time (Default)
UTC or GNSS time1

0
1

GPS PPS (Default)
UTC or GNSS PPS

2

0
1

Time is set
Time is not set

3

0
1

Have UTC info
No UTC info

4-5

0
1
2
3

UTC time
GLONASS time
BeiDou time
Galileo time

6-7

0
1
2
3

UTC PPSGLONASS PPS
BeiDou PPS
Galileo PPS

11

Seconds

UINT8

0-59

Seconds

12

Minutes

UINT8

0-59

Minutes

13

Hours

UINT8

0-23

Hours

14

Day of Month

UINT8

1-31

Day of Month

15

Month

UINT8

1-12

Month of Year

16-17

Year

UINT16

Data
Field

Description

Time
of
Week

This field represents the number of seconds since Sunday at 00:00:00 GPS,GLONASS and Galileo time for the current week. For BeiDou it is for the number of
seconds since Monday at 00:00:00. Time of week is often abbreviated as TOW.

Four digits of Year

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 98

Protempis Standard Interface Protocol

Data
Field

Description

Week
Numb
er

This field represents the current GNSS week number.

UTC
Offset*UTC (USNO) offset = GPS time - UTC (USNO) time
UTC (INRIM) offset = Galileo time - UTC (INRIM) time
UTC (NTSC) offset = BeiDou time - UTC (NTSC) time
UTC (SU) offset = 0

Timing This field is bitwise encoded to provide information about the timing outputs.
Flags Unused bits should be ignored.
Bit 0:
0 – the date and time fields broadcast in packet 8F-AB (Primary
Timing Message) are in the GPS time scale
1 – these fields are in the UTC time scale and are adjusted for leap
seconds
Use command packet 8E-A2 to select either GPS or UTC timescales.
Bit 1:
0 – the PPS output is aligned to GPS.
1 – the PPS output is aligned to UTC.
Use command packet 8E-A2 to select either GPS or UTC PPSalignment.
Bit 2:
0 – time has been set.
1 – time has not yet been set
Bit 3:
0 – UTC offset information has been received
1 – UTC offset information is not yet known
Bit 4:
0 – time is coming from GPS/UTC
1 – the Acutime 360 antenna time is coming from GLONASS
Bit 5:
0 – PPS output is aligned to GPS/UTC
1 – the PPS output is aligned to GLONASSTime Time of Day is sent in hours-minutes-seconds format and varies from 00:00:00 toof Day 23:59:59, except when time is in UTC and a leap second insertion occur. In this casethe time will transition from 23:59:59 to 23:59:60 to 00:00:00.
Date

The date is sent in day-month-year format.

*NOTE: Due to limitations in the GLONASS signal generation the unit will drop satellites during
a leap second event if using GLONASS only.

Report packet 0x8F-AC: Supplemental Timing Packet
This packet provides supplemental timing information once per second. Information regarding
position, unit status and health, and the operational state of the unit.This packet cannot berequested.
When enabled, this packet is transmitted once per seconds shortly after packet 0x8F-AB.
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 99

Protempis Standard Interface Protocol

The position sent in packet 8F-AC depends on the Receiver Operating Mode and on self-survey
activity. When a self-survey is in progress, the position sent is the running average of all of theposition fixes collected so far. When the self-survey ends or whenever the receiver is using atime-only operating mode, then the position sent is the accurate position the receiver is using toperform time-only fixes. When the self- survey is disabled or otherwise inactive and the receiveris using a position fix operating mode, then the position sent is the position fix computed on thelast second.
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x8F

1

Subpacket ID

UINT8

0xAC

2

Receiver Mode

UINT8

0
1
3
4
5
6
7

Automatic (2D/3D)
Single Satellite (Time)
Horizontal (2D)
Full Position (3D)
Not usedNot usedOver-determined Clock3

Reserved

UINT8

Reserved

Reserved

4

Self-Survey
Progress

UINT80-100%

Percent complete

5-8

Reserved

UINT320

Reserved

9-10

Reserved

UINT16

0Reserved

11-12

Minor Alarms

UINT16

Bit field

Bit 0 :Not used
Bit 1 : Antenna OpenBit 2 : Antenna shorted
Bit 3 : Not tracking satellites
Bit 4 :Not used
Bit 5 : Survey-in progress
Bit 6 : No stored position
Bit 7 : Leap second pending *Bit 8 : In test mode
Bit 9 : Position is questionableBit 10 : Not used
Bit 11 : Almanac not complete
Bit 12 : PPS not generated

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 100

Protempis Standard Interface Protocol

Byte

Item

Type

Value

Description

13

GNSS Decoding
Status

UINT8

0x00
0x01
0x02
0x08
0x09
0x0A
0x0B
0x0C

Doing fixes
Don’t have GPS time
No FixNo usable satellites
Only 1 usable satellite
Only 2 usable satellites
Only 3 usable satellites
The chosen satellite is unusable

14

Reserved

UINT8

Reserved

Reserved

15

PPS indication

UINT8

0
1

PPS Good indication
PPS Not Good indication

16

Reserved

UINT8

Reserved

17-20

PPS Offset

SINGLE

ns

21-24

Clock Offset

SINGLE

ppb

25-28

Reserved

UINT32

Reserved

29-32

Reserved

SINGLE

Reserved

33-36

Temperature

SINGLE

Degrees C

37-44

Latitude

DOUBLE

Radians

45-52

Longitude

DOUBLE

Radians

53-60

Altitude

DOUBLE

Meters61-64

Reserved

65-68

Reserved

Data
Field

Description

0

Always 0
Reserved

Receive This field shows the fix mode that the GNSS receiver is currently configured for.
r ModeSelfWhen a self-survey procedure is in progress, this field shows the progress of theSurvey survey as a percentage of fixes collected so far. The self-survey will be complete
Progres when the self-survey progress reaches 100%.
sProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 101

Protempis Standard Interface Protocol

Data
Field

Description

Minor
AlarmsThis field is bitwise encoded with several minor alarm indicators. A minor alarmindicates a condition that the user should be alerted to, but does not indicate an
immediate (or necessarily any) impairment of functionality. For each bit, a valueof 0 means that the condition is not indicated. Bits not described below should be
ignored. A value of 1 indicates the following:
Bit 1:
The antenna input connection is open. More precisely, this bit
indicates that the antenna input is not drawing sufficient current.
Bit 2:
The antenna input is shorted. More precisely, this bit indicates thatthe antenna input is drawing too much current.
Bit 3:
No satellites are yet usable.For a satellite to be usable, it must be
tracked long enough to obtain ephemeris and health data.
Bit 5:
A self-survey procedure is in progress.
Bit 6:
There is no accurate position stored in Flash ROM.
Bit 7:The GNSS system has alerted theAcutime 360 antennathat a leap
second transition is pending.*
Bit 8:
TheAcutime 360 antennais operating in one of its test modes.
Bit 9:
The accuracy of the position used for time only fixes isquestionable.This alarm may indicate that the unit has been moved
since the unit completed the last self-survey. If this alarm persists,
resurvey the position of the unit.
Bit 11:The Almanac is not current or complete.
Bit 12:The PPS was not generated this second. This could mean there
wasn’t enough usable satellites to generate an accurate PPS
output.It could also mean that the unit is generating an Even
Second output (see Packet 8E-4E) and the unit did not output a
PPS on the odd second.

GNSS This field indicates the decoding status of theGNSSreceiver.
Decoding
Status
Local
Clock
OffsetCarries the offset of the local clock relative to UTC or GPS as reported by the GPS
receiver in nanoseconds. Positive values indicate that the receiver’s local clock is laterelative to GPS or UTC. Also known as “bias”.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 102

Protempis Standard Interface Protocol

Data
Field

Description

The "PPS good" indicator is composed of:
PPS
Indicati 1. Unit has achieved a 'first fix'.
on
2. Unit has resolved the millisecond ambiguity. This is done with a proprietaryalgorithm.
3. The unit has at least one satellite that is has passed all Protempis proprietarytiming integrity checks (TRAIM). These include, but are not limited to:lSatellite is in the constellation list of allowed timing sourceslSatellite millisecond ambiguity has been establishedlSatellite signal strength is above the user setting for signal strengthlSatellite elevation is above the elevation masklSatellite tracking filter has settled

4. PPS has been generated for at least 4 seconds after GNSS system restart
Latitude This field carries the latitude of the position being shown. The units are in radiansand vary from -pi/2 to +pi/2. Negative values represent southern latitudes. Positive
values represent northern latitudes.
LongitudeThis field carries the longitude of the position being shown. The units are in radiansand vary from -pi to +pi. Negative values represent western longitudes. Positive
values represent eastern longitudes.

Altitude This field carries the altitude of the position being shown. The units are in meters(WGS-84.)*NOTE: Due to limitations in the GLONASS signal generation the unit will drop satellites during
a leap second event if using GLONASS only.

Report packet 0x8F-AD: Primary UTC Time
The output of the 0x8F-AD packet is synchronized with the PPS. This packet provides accurate
time and date information for time stamping and time transfer. The leap flag provides complete
UTC event information, allowing implementation of sophisticated distributed systems intended
to operate synchronously with UTC time. This packet is always output first in a possible
sequence of up to four synchronous packets. Output of this packet can be disabled andconfigured using the 0x8E-AD packet.
Byte

Item

Type

Units

0

Packet ID

UINT8

0x8F

1

Subpacket ID

Byte

0xAD

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 103

Protempis Standard Interface Protocol

Byte

Item

Type

Units

2-3

Event Count

Integer

Zero for PPS.

4-11

Fractional Second

DoubleTime elapsed incurrent second(seconds)

12

Hour

Byte

UTC Hour13

MinuteByte

UTC Minute

14

SecondByte

Second (0-59;
60 = leap)

15

Day

Byte

Date (1-31)

16

Month

Byte

Month (1-12)

17-18

Year

IntegerYear (4 digit)

19

Receiver Status

Byte

Tracking Status(see definition
below)

20

UTC Flags

Byte

Leap Second
Flags (seedefinition below)

21

Reserved

Byte

Contains 0xFF

22

Reserved

Byte

Contains 0xFF

Tracking status flag
This flag allows precise monitoring of receiver tracking status and allows a host system todetermine whether the time output by the receiver is valid. After self-survey has completed, thereceiver only needs to track one satellite to maintain precise synchronization with UTC. The
definitions are as follows:
Flag value

StatusDescription

0

DOING_FIXES

Receiver is navigating.

1

GOOD_1SV

Receiver is timing using one satellite

2

APPX_1SVApproximate time3

NEED_TIME

Start-up

4

NEED_
INITALIZATION

Start-up

5

PDOP_HIGH

Dilution of Precision too High6

BAD_1SV

Satellite is unusable

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 104

Protempis Standard Interface Protocol

Flag value

StatusDescription

7

0SVs

No satellites usable

8

1SV

Only 1 satellite usable

9

2SVs

Only 2 satellites usable

10

3SVs

Only 3 satellites usable

11

NO_INTEGRITY

Invalid solution

12

DCORR_GEN

Differential corrections

13

OVERDET_CLK

Over-determined fixes

Leap second flag
Leap seconds are inserted into the UTC timescale to counter the effect of gradual slowing of theearth’s rotation due to friction. The 0x8F-AD packet provides extensive UTC leap second
information to the user application. The definitions are as follows
Bit #

Name

Meaning if set to 1

0

UTC Flag

UTC Time is available

1-3

Reserved

N/A

4

Leap Scheduled

Leap second date is not in the past

5

Leap Pending

24-hour warning

6

Leap Warning

Set ± 6 hours before/after leap event

7

Leap in Progress

Leap second is now being inserted

l

l

l

l

The Leap Scheduled bit is set by the receiver, when the leap second has been scheduled by
the GPS control segment. The Control segment may schedule the leap second several
weeks before the leap second takes place.
The Leap Pending bit indicates that the leap second will be inserted at the end of the currentday.
The Leap Warning bit is set while GPS is operating in the leap exception mode specified in
ICD-200.
The Leap in Progress bit is set to 1 at the beginning of the leap second, and cleared at the
beginning of the second following the leap event. The date rollover is delayed by one
second on the day the leap second is inserted. The date will not increment until the
beginning of the first second following the leap second

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 105

Protempis Standard Interface Protocol

Unused or miscellaneous packets
Report packet 0x13: Unparsable packet
This packet is sent in response to a received packet that was unparsable. A packet is
unparsable if the packet ID is not recognized or if the length or content of the packet is notcorrect for the packet ID.
Data format:
Byte

Item

Type

Value

Description

0

Packet ID

UINT8

0x13

Packet ID of unparsable packet

Data

UINT8

1-N

Packet data bytes of unparsable
packetProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 106

B
NMEA 0183 Protocol
This appendix provides a brief overview of the NMEA 0183 protocol, and describes both thestandard and optional messages offered by the Acutime 360 antenna.
Introduction
NMEA 0183 communication interface
NMEA 0183 message structure
Field definitions
NMEA 0183 message options
NMEA 0183 message formats
Exception behavior

Introduction
The National Marine Electronics Association (NMEA) protocol is an industry standard data
protocol which was developed for the marine industry.
NMEA 0183 is a simple, yet comprehensive ASCII protocol which defines both thecommunication interface and the data format. The NMEA 0183 protocol was originallyestablished to allow marine navigation equipment to share information. Since it is a wellestablished industry standard, NMEA 0183 has also gained popularity for use in applications
other than marine electronics.
For those applications requiring output only from the GNSS receiver, NMEA 0183 is a popular
choice since, in many cases, an NMEA 0183 software application code already exists. The
Acutime 360 antenna is available with firmware that supports a subset of the NMEA 0183
messages: GGA, GLL, GSA, GSV, RMC, VTC, and ZDA. For a nominal fee, Protempis canoffer custom firmware with a different selection of messages to meet your application
requirements.
For a complete copy of the NMEA 0183 standard, contact:
NMEA National Office
Seven Riggs Avenue, Severna Park, MD 21146
Phone: +1-410-975-9425 or 800-808-6632 (NMEA)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 107

NMEA 0183 Protocol

Fax: +1-410-975-9450

NMEA 0183 communication interface
The NMEA 0183 protocol allows a single source (talker) to transmit serial data over a single
twisted wire pair to one or more receivers (listeners). The table below lists the standard
characteristics of the NMEA 0183 data transmissions.
SignalNMEA Standard

Baud rate

115 kbps

Data bits

8

ParityNone

Stop bits

1

NMEA 0183 message structure
The NMEA 0183 protocol covers a broad array of navigation data. This broad array of
information is separated into discrete messages which convey a specific set of information. The
entire protocol encompasses over 50 messages, but only a sub-set of these messages apply toa GPS receiver like the Acutime 360. The NMEA message structure is described below.

$IDMSG,D1,D2,D3,D4,.......,Dn*CS[CR][LF]
Where:
$
ID

MSG

,
Dn
*
CS

[CR][LF]

Signifies the start of a message
The talker identification is a two letter mnemonic
which describes the source of the navigation
information. The GP identification signifies a GPS
source while GL will signify a GLONASS source. In
the event that the information in the sentence isagnostic the ID will be GP.
The message identification is a three letter mnemonic
which describes the message content and the number
and order of the data fields.
Commas serve as delimiters for the data fields.
Each message contains multiple data fields (Dn)which are delimited by commas.
The asterisk serves as a checksum delimiter.
The checksum field contains two ASCII characterswhich indicate the hexadecimal value of thechecksum.
The carriage return [CR] and line feed [LF]
combination terminate the message.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 108

NMEA 0183 Protocol

NMEA-0183 messages vary in length, but each message is limited to 79 characters or less. This
length limitation excludes the "$" and the [CR][LF]. The data field block, including delimiters, islimited to 74 characters or less.

Talker IDs
The message talker ID, which is the two characters immediately following the starting marker($) in a standard NMEA message, describes the source of data in a particular message.
Specifically, it indicates the GNSS constellation to which the data is applicable. The following
table lists talker IDs.
Talker ID

Constellation

Description

GN

ALL

GP
BD
GA
GL

GPS
BEIDOUGALILEOGLONASS

Data combines all supported and enabled constellations on agiven device.
Data from GPS
Data from BEIDOU
Data from GALILEO
Data from GLONASS

Field definitions
Many of the NMEA date fields are of variable length, and the user should always use thecomma delineators to parse the NMEA message date field. The following table specifies thedefinitions of all field types in the NMEA messages supported by Protempis:
Type

SymbolDefinition

StatusA

Single character field: A=Yes, data valid, warning flagclear V=No, data invalid, warning flag set.

Special Format Fields
Latitudellll.lll

Fixed/variable length field: Degreesminutes.decimal-2
fixed digits of degrees, 2 fixed digits of minutes and avariable number of digits for decimal-fraction ofminutes. Leading zeroes always included for degrees
and minutes to maintain fixed length. The decimal
point and associated decimal- fraction are optional if
full resolution is not required.

Longitude

yyyyy.yyy

Fixed/Variable length field: Degreesminutes.decimal3 fixed digits of degrees, 2 fixed digits of minutes and avariable number of digits for decimal-fraction ofminutes. Leading zeroes always included for degrees
and minutes to maintain fixed length. The decimal
point and associated decimal- fraction are optional if
full resolution is not required.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 109

NMEA 0183 Protocol

Type

SymbolDefinitionTimehhmmss.ss

Fixed/Variable length field:
hoursminutesseconds.decimal-2 fixed digits ofminutes, 2 fixed digits of seconds and a variable
number of digits for decimal-fraction of seconds.
Leading zeroes always included for hours, minutes,
and seconds to maintain fixed length. The decimal
point and associated decimal-fraction are optional if
full resolution is not required.

DefinedSome fields are specified to contain pre-definedconstants, most often alpha characters. Such a field isindicated in this standard by the presence of one ormore valid characters. Excluded from the list ofallowable characters are the following, that are used
to indicated field types within this standard: "A", "a","c", "hh", "hhmmss.ss", "llll.ll", "x", "yyyyy.yy".

Numeric Value fields
Variablex.x

Variable length integer or floating numeric field.
Optional leading and trailing zeros. The decimal point
and associated decimal-fraction are optional if full
resolution is not required (example:
73.10=73.1=073.1=73).

Fixed HEXhh

Fixed length HEX numbers only, MSB on the left.

Fixed Alphaaa

Fixed length field of upper-case or lower-case alphacharacters.

Fixed Number

xx

Fixed length field of numeric characters.

Information fields

NOTE –lllSpaces are only to be used in variable text fields.
Units of measure fields are appropriate characters from the Symbol column, unless a
specified unit of measure is indicated.
Fixed length field definitions show the actual number of characters. For example, afield defined to have a fixed length of 5 HEX characters is represented as hhhhh
between delimiters in a sentence definition.

NMEA 0183 message options
The Protempis® Acutime 360 antenna can output any or all of the messages listed in the tablebelow. In its default configuration (as shipped from the factory), the Acutime 360 antenna
outputs only TSIP messages. Typically, NMEA messages are output at a one second interval
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 110

NMEA 0183 Protocol

with the "GP" talker ID and checksums. These messages are output at all times during
operation, with or without a fix. If a different set of messages has been selected (using Packet
0x7A), and this setting has been stored in flash memory (using Packet 0x8E-26), the default
messages are permanently replaced until the receiver is returned to the factory default settings.
NOTE – You can configure a custom mix of the messages listed in the following table.
CAUTION – If too many messages are specified for output, you may need to increase theunit's baud rate.
Message

Description

GGA

GPS fix data

GLL

Geographic position Latitude/LongitudeGSA

GPS DOP and active satellites

GSV

GPS satellites in view

RMC

Recommended minimum specific GPS/Transit data

VTG

Track made good and ground speed

ZDA

Time and date

Acutime 360 antenna proprietary NMEA messages
Message

Description

AH

Query or set almanac health

AL

Query or set almanac data for a specific satellite

AS

Query or set almanac status

BA

Query and response to antenna status

CR

Query or set GPS receiver configuration information.

EM

Set receiver into Monitor Mode. Set only.

EP

Query or set ephemeris data for a specific satellite.

IO

Query or set ionosphere data.

KG

Set initial position and time info data for to aid navigation startup.

NM

Query or set NMEA automatic message output control.

PS

Query or set PPS configuration.

PT

Query or set serial port configuration.

RT

Set Reset Type (cold)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 111

NMEA 0183 Protocol

Message

Description

TF

Query or set receiver status and position fix information.

UT

Query or set UTC data

VR

Query and response to version information

ZD

Extended Time and Date

NMEA 0183 message formats
GGA - GPS Fix Data
The GGA message includes time, position and fix related data for the GNSS receiver.
$aaGGA,hhmmss.s,llll.lllx,d,yyyyy.yyyx,d,q,s,xh.hx,xaaaaa,M,xggg,M,xxx,xxxx*hh<CR><LF>
Field

DescriptionaaTalker ID

hhmmss.s

Hours, minutes, seconds, sub-seconds of position in UTC.

llll.lllx

LatitudedN|Syyyy,yyyx

Longitude

d

E|W

q

Quality indicator (see Section 3.1 for more info):
0 = fix not available
1 = autonomous GNSS mode, fix valid
2 = differential/SBAS-aided GNSS mode, fix valid
4 = RTK (fixed) or RTX
5 = RTK (float)
6 = estimated/dead reckoning mode (DR)s

Number of satellites in use

xh.hx

HDOP

xaaaaaAntenna altitude, meters MSL

xggg

Geoidal separation, meters. This is the difference between the earth
ellipsoid and mean-sea-level (geoid) defined by the reference datum usedin the position solution. A negative value indicates the mean-sea-level isbelow ellipsoid.

xxx

Age of differential corrections data

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 112

NMEA 0183 Protocol

Field

Description

xxxx

Differential reference station ID

hhchecksum

GLL - Geographic Position - Latitude/Longitude
The GLL message contains the latitude and longitude of the present vessel position, the time ofthe position fix and the status.
$aaGLL,llll.lllx,d,yyyyy.yyyx,d,hhmmss.s,s,a*hh<CR><LF>
Field

DescriptionaaTalker ID

llll.lllx

LatitudedN|S

yyyyy.yyyx

Longituded

E|W

hhmmss.s

Hours, minutes, seconds, sub-seconds of position in UTC.

s

Status:A = data valid
V = data invalidaMode indicator:
N = data not valid
A = autonomous modeD = differential/SBAS-aided mode
F = RTK (float)
R = RTK (fixed)
P = RTX or PPP
E = estimated/DR
M = manual modehhchecksum

GSA - GPS DOP and Active Satellites
The GSA messages indicate the GNSS receiver's operating mode and lists the satellites used
for navigation and the DOP values of the position solution.

$idGSA,a,v,ww,ww,ww,ww,ww,ww,ww,ww,ww,ww, ,,x.xx,y.yy,z.zz*hh<CR><LF>

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 113

NMEA 0183 Protocol

Where id is GP, GL or GN, dependent on if the sentence contains GPS, GLONASS or bothconstellations respectively.
Field

Description

1

Mode: M = Manual, A = Automatic. In manual mode, the receiver is forced tooperate in either 2D or 3D mode. In automatic mode, the receiver is allowed
to switch between 2D and 3D modes subject to the PDOP and satellitemasks.

2

Current Mode: 1 = fix not available, 2 = 2D, 3 = 3D

3 - 14

PRN numbers of the satellites used in the position solution. When less than
12 satellites are used, the unused fields are null.

15

Position dilution of precision (PDOP)

16

Horizontal dilution of precision (HDOP) 17 Vertical dilution of precision(VDOP)

hh

Checksum

GSV - GPS Satellites in View
The GSV message identifies the GNSS satellites in view, including their PRN number,elevation, azimuth and SNR value. Each message contains data for four satellites. Second andthird messages are sent when more than 4 satellites are in view. Fields #1 and #2 indicate thetotal number of messages being sent and the number of each message respectively.

$idGSV,t,u,vv,ww,ww,www,ww,xx,xx,xxx,xx,yy,yy,
yyy,yy,zz,zz,zzz,zz*hh<CR><LF>

Where id is GP or GL, dependent on if the sentence contains GPS or GLONASS satellites.
Field

Description

1

Total number of GSV messages

2

Message number: 1 to 3

3

Total number of satellites in view

4

Satellite PRN number

5

Satellite elevation in degrees (90° Maximum)

6

Satellite azimuth in degrees true (000 to 359)

7

Satellite SNR (C/N0), null when not tracking

8, 9, 10, 11

PRN, elevation, azimuth and SNR for second satellite

12, 13, 14, 15

PRN, elevation, azimuth and SNR for third satellite

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 114

NMEA 0183 Protocol

Field

Description

16, 17, 18, 19

PRN, elevation, azimuth and SNR for fourth satellite

hh

Checksum

RMC - Recommended Minimum Specific GPS/Transit Data
The RMC message contains the time, date, position, course, and speed data provided by the
GNSS navigation receiver. A checksum is mandatory for this message and the transmissioninterval may not exceed 2 seconds. All data fields must be provided unless the data is
temporarily unavailable. Null fields may be used when data is temporarily unavailable. Thismessage is output automatically if selected in the NMEA message output mask.
$aaRMC,hhmmss.s,s,llll.lllx,d,yyyyy.yyyx,d,xs.sx,xc.cx,ddmmyy,xm.vx,d,a*hh<CR><LF>
Field

DescriptionaaTalker ID

hhmmss.s

Hours, minutes, seconds, sub-seconds of position in UTC.

s

Status (see Section 3.1 for more info):
A = data valid
V = data invalid

llll.lllx

LatitudedN|S

yyyyy,yyyx

Longitude

d

E|W

xs.sx

Speed Over Ground in Knots

xc.cx

Course Over Ground in Degrees TrueddmmyyDay, month, year of datexm.vx

Magnetic Variation in Degreesd

E|W

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 115

NMEA 0183 Protocol

Field

DescriptionaMode indicator:
N = data not valid
A = autonomous modeD = differential/SBAS-aided mode
F = RTK (float)
R = RTK (fixed)
P = RTX or PPP
E = estimated/DR
M = manual modehh

Checksum (mandatory for RMC)

VTG - Track Made Good and Ground Speed
The VTG message conveys the actual track made good (COG) and the speed relative to theground (SOG).
This message is output automatically if selected in the NMEA message output mask.
$aaVTG,xc.cx,T,xc.cx,M,xs.sx,N,xs.sx,K,a*hh<CR><LF>
Field

DescriptionaaTalker ID

xc.cx

Course Over Ground in Degrees Truexc.cx

Course Over Ground in Degrees Magnetic

xs.sx

Speed Over Ground in knots

xs.sx

Speed Over Ground in km/hr

aMode indicator:
N = data not valid
A = autonomous modeD = differential/SBAS-aided mode
F = RTK (float)
R = RTK (fixed)
P = RTX or PPP
E = estimated/DR
M = manual modehh

Checksum

ZDA - Time & Date
The ZDA message contains UTC time, the day, the month, the year and the local time zone.
This message is output automatically if selected in the NMEA message output mask.
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 116

NMEA 0183 Protocol$aaZDA,hhmmss.s,dd,mm,yyyy,zh,zm*hh<CR><LF>
Field

DescriptionaaTalker ID

hhmmss.s

Hours, minutes, seconds, sub-seconds of position in UTC.

dd

Day (01 to 31)

mm

Month (01 to 12)

yyyy

Year

zh

Local Zone Hour, offset from UTC to obtain Local timezm

Local Zone Minutehh

Checksum
NOTE – Fields #5 and #6 are null fields in the Acutime 360Acutime 720 output. A GNSS
receiver cannot independently identify the local time zone offsets.
CAUTION – If UTC offset is not available, time output will be in GPS time until the UTC
offset value is collected from the GPS satellites. When the offset becomes available, thetime will update to UTC time.
NOTE – GPS time can be used as a time tag for the 1PPS. The ZDA message comes out
100–500 msec after the PPS.

AH - Almanac Health
Use this message to query or set almanac health data. Since the maximum number of bytes
that can be contained in a single NMEA sentence is less than the total almanac health length,
the almanac health must be sent in two parts that have to be sent or received together in thecorrect sequence. After receiving the query, the receiver sends out two messages.

Message 1$PTNLaAH,1,hh,hhhhhhhh,hhhhhhhh,hhhhhhhh,hhhhhhhh,hh*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – Response

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 117

NMEA 0183 Protocol

Field

DescriptionhhWeek number for health, variable length integer, 4 digits maximum

hhhhhhhh

Satellite 1 - 4 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 5 - 8 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 9 - 12 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 13 - 16 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hh

Checksum

Message 2$PTNLaAH,2,hh,hhhhhhhh,hhhhhhhh,hhhhhhhh,hhhhhhhh,hh*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – ResponsehhWeek number for health, variable length integer, 4 digits maximum

hhhhhhhh

Satellite 17 - 20 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 21 - 24 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 25 - 28 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hhhhhhhh

Satellite 29 - 32 health, one byte for each satellite, HEX data conforming to
GPS ICD 200

hh

ChecksumAL - Almanac Page
Use this message to query or set almanac data for a specific satellite. The query format is:$PTNLQAL,xx*hh<CR><LF>

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 118

NMEA 0183 Protocol

Field

Descriptionxx

Satellite ID

The set or response format is as follows:
Field

Description

a

Mode:
S – SetR – Responsexx

Satellite ID, 01-32

x.x

GPS week number, variable length integer, 4 digits maximum.

hh

SV health, HEX data conforming to GPS ICD 200

hhhh

Eccentricity, HEX data conforming to GPS ICD 200hht_oa, almanac reference time, HEX data conforming to GPS ICD 200

hhhh

sigma_I,HEX data conforming to GPS ICD 200

hhhh

OMEGADOT, HEX data conforming to GPS ICD 200

hhhhhhroot_a, HEX data conforming to GPS ICD 200

hhhhhhOmega, HEX data conforming to GPS ICD 200

hhhhhhOmega_0, HEX data conforming to GPS ICD 200

hhhhhhM_O, HEX data conforming to GPS ICD 200

hhh

a_fO, HEX data conforming to GPS ICD 200

hhh

a_fl, HEX data conforming to GPS ICD 200

hh

ChecksumAS - Almanac Status
Use this sentence to query or set almanac status. The query format is:$PTNLaAS,hh,xxxx,hh,hh,hh,hh,hh*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – ResponsehhTime of almanacxxxx

Week of number of almanac

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 119

NMEA 0183 Protocol

Field

DescriptionhhReservedhhReservedhhReservedhhReservedhh

Almanac Status
0 – almanac incomplete
1 – almanac complete and current

hhChecksum

The corresponding response for the set is:$PTNLRAS,a*hh<CR><LF>
Where “a” is the action status: A = success; V= failure.

CR - Configure Receiver
Use this sentence to query or set receiver configuration information.
The Query sentence format is:$PTNLQCR*hh<CR><LF>
The Response to query or Set sentence format is:$PTNLaCR,x.x,x.x,x.x,x.x,x.x,a,a,a,a,*hh<CR><LF>
Field

DescriptionaMode (S = set; R = response)x.x

Signal Level Mask (default = 0.6 AMU)

x.x

Elevation mask in degrees (default = 5 degrees)

x.x

PDOP mask (default = 12)

x.x

PDOP switch (default = 6) (unused in Onix)x.x

Max Oscillator Offset (unused in Onix)aConstellation Mode, default is 0
0 – AUTO

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 120

NMEA 0183 Protocol

Field

DescriptionaDynamics, default is 0
1 – Land2 – Sea
3 – AiraReserved, set to 1.

a

SBAS mode, default is 0a

Bitmap of Constellation track/use mask:
Bit 0 - GPS L1C
Bit 1 - GPS L2 (Not supported, for future use)
Bit 2 - GPS L5
Bit 3 - Reserved
Bit 4 - Glonass G1
Bit 5 - Glonass G2 (Not supported, for future use)
Bit 6,7 - Reserved
Bit 8 - SBAS
Bit 9 - Reserved
Bit 10 - Reserved
Bit 11 - Reserved
Bit 12 - Beidou B1
Bit 13 - Beidou B2i (Not supported, for future use)
Bit 14 - Beidou B2a
Bit 15 - Reserved
Bit 16 - Galileo E1
Bit 17 - Galileo E5a
Bit 18 - Galileo E5b (Not supported, for future use)
Bit 19 - Galileo E6 (Not supported, for future use)
Bit 20 - Reserved
Bit 21 - QZSS L1C
Bit 22 - QZSS L2C (Not supported, for future use)
Bit 23 - QZSS L5
Bit 24 - Reserved
Bit 25 - Reserved
Bit 26 - Navic L5
Bit 27 - Reserved
Bit 28 - Reserved
Bits 29-31 - ReservedaJamming enable/disable (1 default):
0 - disable
1 - enablehh

ChecksumProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 121

NMEA 0183 Protocol

The Response to set format is:$PTNLRCR,a*hh<CR><LF>
Field

DescriptionaStatus (A – success; V – failure)hh

ChecksumEM - Enter Monitor modeThis sentence is used to set the Acutime 360 antenna multi-GNSS timing module into Monitor
mode. This is Set only, no query supported. The sentence format is:$PTNLSEM*hh<CR><LF>
This sentence is used by the Firmware Uploading Program.

EP - Ephemeris
Use this sentence to query or set ephemeris data for a specific satellite. Since the maximum
number of bytes that can be contained in a single NMEA sentence is less than the total
ephemeris data length, the ephemeris data must be sent in three sentences. The threesentences have to be sent or received together in correct sequence. The query format is:$PTNLQEP,xx*hh<CR><LF>
Field

Description

Q

Query

xx

Satellite ID

After receiving the query, the receiver sends out three messages.

Message 1$PTNLaEP,1,xx,x.x,x.x,hh,hh,hh,hh,hhh,hh,hhhh,hh,hhhh,hhhhhh,x .x*hh<CR><LF>
Field

Description

a

Mode:
S – SetR – Response

1

Message number for EP, message 1 must be sent or received before
message 2, and message 2 must be sent or received before message 3. All
three messages must be sent together in the correct sequence.

xx

Satellite id

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 122

NMEA 0183 Protocol

Field

Descriptionx.x

T_ephem, This is a double-precision floating point number.

x.x

Week number for health, variable length integer, 4 digits maximum.

hh

CodeL2, HEX data conforming to GPS ICD 200

hh

L2Pdata, HEX data conforming to GPS ICD 200

hh

Svacc_raw, HEX data conforming to GPS ICD 200

hh

SV_health, HEX data conforming to GPS ICD 200

hhh

IODC, HEX data conforming to GPS ICD 200

hh

T_GD, HEX data conforming to GPS ICD 200

hhhh

T_oc, HEX data conforming to GPS ICD 200

hh

A_f2, HEX data conforming to GPS ICD 200

hhhh

A_f1, HEX data conforming to GPS ICD 200

hhhhhhA_f0, HEX data conforming to GPS ICD 200

Message 2$PTNLaEP,2,xx,hh,hh,hhhh,hhhh,hhhhhhhh,hhhh,hhhhhhhh,hhh
h,hhhhhhhh,hhhh* hh<CR><LF>
Field

Description

a

Mode:
S – SetR – Response

2

Sentence number for EP, sentence 1 must be sent or received before
sentence 2, and sentence 2 must be sent or received before sentence 3. All
three sentences must be sent together.

xx

Satellite id

hh

IODE, Hex data conforming to GPS ICD 200

hh

Fit_interval, Hex data conforming to GPS ICD 200

hhhh

C_rs, Hex data conforming to GPS ICD 200

hhhh

Delta_n, Hex data conforming to GPS ICD 200

hhhhhhhh

M_0, Hex data conforming to GPS ICD 200

hhhh

C_uc, Hex data conforming to GPS ICD 200

hhhhhhhh

E, Hex data conforming to GPS ICD 200

hhhh

C_us, Hex data conforming to GPS ICD 200
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 123

NMEA 0183 Protocol

Message 3$PTNLaEP,3,xx,hhhh,hhhhhhhh,hhhh,hhhhhhhh,hhhh,hhhhhhhh,
hhhhhh,hhhh*hh< CR><LF>
Field

Description

a

Mode:
S – SetR – Response

3

Sentence number for EP, sentence 1 must be sent or received before
sentence 2, and sentence 2 must be sent or received before sentence 3. All
three sentences must be sent together.

xx

Satellite idhh

C_ic, Hex data conforming to GPS ICD 200

hh

OMEGA_0, Hex data conforming to GPS ICD 200

hhhh

C_ri, Hex data conforming to GPS ICD 200

hhhh

I_O, Hex data conforming to GPS ICD 200

hhhhhhhh

C_rc, Hex data conforming to GPS ICD 200

hhhh

OMEGA, Hex data conforming to GPS ICD 200

hhhhhhhh

OMEGA_DOT, Hex data conforming to GPS ICD 200

hhhh

IDOT, Hex data conforming to GPS ICD 200

IO - IonosphereThis sentence can be used to query or set ionosphere data.

$PTNLaIO,hh,hh,hh,hh,hh,hh,hh,hh*hh,<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – ResponsehhAlpha_0, HEX data conforming to GPS ICD 200

hhAlpha_1, HEX data conforming to GPS ICD 200

hhAlpha_2, HEX data conforming to GPS ICD 200

hhAlpha_3, HEX data conforming to GPS ICD 200

hh

Beta_0, HEX data conforming to GPS ICD 200

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 124

NMEA 0183 Protocol

Field

Description

hh

Beta_1, HEX data conforming to GPS ICD 200

hh

Beta_2, HEX data conforming to GPS ICD 200

hh

Beta_3, HEX data conforming to GPS ICD 200

KG - Set Initial Position
Use this sentence to set initial position or time info data or both for accelerating navigation
startup:l

To set time only, send valid time fields and NULL position fields.

l

To set position only, send valid position fields and NULL time fields. Query is not supported.

$PTNLaKG,x.x,x.x,llll.lllll,a,yyyyy.yyyyy,a,x.x*hh<CR><LF>
NOTE – When uploading a position, it should be within 100 Km of the actual position andtime within 5 minutes of UTC.
Field

Description

a

Mode:
S – SetR – Responsex.x

GPS week number, maximum 4 digits

x.x

GPS time of week in milliseconds llll.lllll Latitudea

N|S

yyyyy.yyyyy

Longitude

a

E|W

x.x

Altitude from the sea level in meters (maximum 5 digits)

NM - NMEA Configuration
This sentence may be issued by the user to configure NMEA message output. The Querysentence format is:$PTNLQNM,x*hh<CR><LF>
Field

DescriptionxPort, default is current port if field is left null.
0 – Port A
1 – Port B
255 – Current port
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 125

NMEA 0183 Protocol

The Response sentence to query or Set sentence format is:$PTNLaNM,hhhhhhhh,x.x,x,x*hh<CR><LF>
Field

DescriptionaMode (S = set; R = response)

hhhhhhhh

Message Flags (32 bits maximum), one bit for each message:
Bit 0 – GGA
Bit 1 – GLL
Bit 2 – VTG
Bit 3 – GSV
Bit 4 – GSA
Bit 5 – ZDA
Bits 6,7 – Reserved
Bit 8 – RMC
Default is 0x3D

x.x

Automatic Report Interval (1 – 255 seconds), default is 1 if field is left null.
Default is 1 secondxPosition fix data source.
This field indicates the source of fix data in messages containing position fix
information (GGA, RMC).
255 – position fix data source not supported (fix data always comes from DR
for DR-capable products or from GNSS for non-DR products)
This is output by default. Users can set any values or null.

xPort, default is current port if field is left null.
0 – Port A
1 – Port B
255 – Current port

The Response sentence to set format is:$PTNLRNM,a*hh<CR><LF>
Field

DescriptionaStatus (A – success; V – failure)hh

ChecksumProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 126

NMEA 0183 Protocol

PS - PPS Configuration
This sentence can query or set PPS configuration data.

$PTNLaPS,b,x...x,c,x...x*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – Responseb

PPS mode, default is 1
0 – PPS_OFF (Always Off)1 – PPS_ON (Always On or Early PPS)
2 – Reserved
3 – Reserved

x…xReservedc

Output pulse polarity, default is 1
0 – Output pulse is active low
1 – Output pulse is active highx…x

Antenna Cable Length Compensation. Default = 0, Units in nanoseconds.
Can be positive or negative.
Negative value will mean PPS comes out earlier, for example, to compensate
for cable delay.
Field value range is -100000000...100000000 (±100 milliseconds)

PT - Serial Port Configuration
Use this sentence to configure the current serial port. The Query sentence format is:$PTNLQPT*hh<CR><LF>
The Response sentence to query or Set sentence format is:$PTNLaPT,xxxxxx,a,a,a*hh<CR><LF>
In the case of Set, the Response message with new parameters is sent using the oldparameters first, and then the switch to the new parameters is made.
If the switch fails for any reason, an NMEA error response is sent. If the switch succeeds, noadditional response is sent.
Field

DescriptionaMode (S = set, R = response)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 127

NMEA 0183 Protocol

Field

Description

xxxxxxBaud rate (4800, 9600, 19200, 38400, 57600, 115200). Default baud rate is4800

a

Number of data bits (7 or 8)aParity (N = None, O = Odd, E = Even)a

Number of stop bits (1 or 2)hInput protocol. This is a hex bit-map but only one protocol in use. This field
may not be 0.
Bit 0: NONE (TBD)
Bit 1: TSIP
Bit 2: NMEAh

Output protocol. This is a hex bit-map (same as input).
Bit 0: NONE (TBD)
Bit 1: TSIP
Bit 2: NMEAhh

Checksum

The Response sentence to set format is:$PTNLRPT,a*hh<CR><LF>
Field

DescriptionaStatus (A – success; V – failure)hh

Checksum

RT - Reset
Use this sentence to Set the reset type. No query is supported.

$PTNLaRT,b,c*hh<CR><LF>
Field

Description

a

Mode:
S – SetR – Response

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 128

NMEA 0183 Protocol

Field

DescriptionbCommandC = Cold software reset, Erases RAM (including the customer configurationin RAM) and restarts
F = Factory software reset. Erases the customer configuration, the almanac,
ephemeris and last position in Flash Memory and in SRAMc (decimal
integer)Flash operation
0 - Do not do any Flash operation
1 - Reserved
2 - Store user configuration to Flash Memory
3 - Reserved
4 - Reserved
5 - Erase user configuration from Flash Memory
6 – ReservedhhChecksum
NOTE – A successful command is followed by a $PTNLRRT,A*3F response. An incorrectcommand will be followed by a $PTNLRRT,V*28 response.
NOTE – To save the user configuration to flash memory, send command$PTNLSRT,C,2*22.

TF - Receiver Status and Position Fix
Use this sentence to get the receiver status and position fix. The Query sentence format is:$PTNLQTF*hh<CR><LF>
The Response to query sentence format is:$PTNLaTF,b,c,xxxxxx,xx,x,llll.lllll,d,yyyyy.yyyyy,e,xxxx
x,x.x,x.x,x.x*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – Responseb

BBRAM status on startup (A = valid; V = invalid)c

Almanac completion status (A = complete; V = incomplete)

xxxxxxGPS time of week (in seconds)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 129

NMEA 0183 Protocol

Field

Descriptionxx

Number of satellites in use, 00 - 12, may be different from the number in
view.

x

Position fix source (0 = no fix; 1 = Stationary Mode, 2 = 2D fix; 3 = 3D fix)

llll.lllll

Latitude of the current position fix dyyyyy.yyyyy

Longitude of the current position fix

e

E|W

xxxxx

Antenna altitude re: mean-sea-level (MSL geoid, meters)

x.x'East' component of ENU velocity (m/s)

x.x'North' component of ENU velocity (m/s)

x.x'Up' component of ENU velocity (m/s)

hhChecksum

UT - UTC data
Use this sentence to query or set UTC data.

$PTNLaUT,hhhhhhhh,hhhhhh,hh,hh,hhhh,hhhh,hh,hh*hh<CR><LF>
Field

Description

a

Mode:
Q – QueryS – SetR – Response

hhhhhhhh

A_0, HEX data conforming to GPS ICD 200

hhhhhhA_1, HEX data conforming to GPS ICD 200

hh

Delta_t_ls, HEX data conforming to GPS ICD 200hh

T_oa, HEX data conforming to GPS ICD 200

hhhh

Wn_t, HEX data conforming to GPS ICD 200

hhhh

Wn_LSF, HEX data conforming to GPS ICD 200

hh

DN, HEX data conforming to GPS ICD 200

hh

Delta_t_LSF, HEX data conforming to GPS ICD 200

hh

ChecksumVR - Version
This sentence may be issued by the user to get application version information.
Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 130

NMEA 0183 Protocol

The Query sentence format is:$PTNLQVR,a*hh<CR><LF>
Field

DescriptionaComponent ID for which to query the version:S – system (application firmware) version
H – hardware info

hhChecksum

The Response to query sentence format for all components versions except the hardware (H).
$PTNLRVR,a,a..a,b…b,xx,xx,xxxx*hh<CR><LF>

Application firmware
Field

DescriptionaComponent ID (same as in Query format)

a..aComponent name (variable length character string)b...bVersion number in the format xx.yy.zz where
xx – major version number (2 digits, prepend 0 if the number is less than 10)
yy – minor version number (2 digits, prepend 0 if the number is less than 10)
zz – build version number (2 digits, prepend 0 if the number is less than 10)
NOTE – There must be a period character separating the major/minor
and minor/build numbers.

xx

Month (1-12)xx

Day (1-31)

xxxx

Year

hh

Checksum

The Response to query sentence format for the Hardware version (H)information is:$PTNLRVR,H,xxxx,a..a,xxxxxxxx,xx,xx,xxxx,xx*hh<CR><LF>
Field

Description

xxxx

Hardware codea..aHardware ID (variable length character string)

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 131

NMEA 0183 Protocol

Field

Description

xxxxxxxx

Serial numberxx

Build month (1-12)xx

Build day (1-31)

xxxx

Build yearxx

Build hour (0-23)

hh

Checksum

ZD - Extended Time and Date
This message reports extended time and date information - UTC, day, month, year, local timezone and UTC to GPS leap second.
Setting the data is not supported.
This message is output automatically if selected in the NMEA message output mask.
Query format:$PTNLQZD*hh<CR><LF>
Response to query format:$PTNLRZD, hhmmss.s,dd,mm,yyyy,zh,zm,ls,lsp*hh<CR><LF>
Field

Description

hhmmss.s

Hours, minutes, seconds, sub-seconds of position in UTC.

dd

Day (01 to 31)

mm

Month (01 to 12)

yyyy

Year

zh

Local Zone Hour, offset from UTC to obtain Local timezm

Local Zone MinutelsCurrent leap second offset between GPS and UTC timelsp

Pending leap second. If non-zero (+/- 1) then a leap second is scheduled tooccur at the end of the day. The sign indicates the direction of the leap
second.

hh

ChecksumProtempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 132

NMEA 0183 Protocol

Exception behavior
When no position fix is available, some of the data fields in the NMEA messages will be blank. A
blank field has no characters between the commas.

Interruption of GNSS signal
If the GNSS signal is interrupted temporarily, the NMEA will continue to be output according to
the user-specified message list and output rate. Position and velocity fields will be blank until thenext fix, but most other fields will be filled.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 133

CAcutime 360 Antenna GPS-only
Variant
This appendix describes the difference between the GPS-only and the standard Acutime 360
product.
Introduction
Default communication interface
PPS pulse width
Default constellations
Default messages

Introduction
The Acutime 360 antenna provides the user with the ability to track multiple constellations. Thisability meant that some existing messages had to be modified and extra messages added todeal with the new constellation options. The default baud rate also had to be increased from
9600 to 115200 to allow for the extra data.
A “GPS-only” version of the Acutime 360 antenna is made available to customers who require a
replacement for the legacy Acutime Gold.
A user may need the “GPS-only” variant if:a) The customer host computer cannot be reprogrammed with the new message structureb) The customer has to use a default baud rate of 9600 and cannot change either the host or the
standard Acutime 360 antenna baud settings.
c) The customer hardware cannot use the faster communication baud rate.
Note that both the standard and GPS-only Acutime 360 antenna use identical hardware andfirmware. The differences described in this section are enabled at the factory. Once
programmed the user cannot change the parameter values of the default settings.

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 134

Acutime 360 Antenna GPS-only Variant

Default communication interface
Acutime 360 standard

Acutime 360 GPS-only Acutime Gold

106406-00

106406-05

55238-00

Port B

115200, 8, odd,1

9600, 8, odd, 1

9600, 8, odd, 1

Port A

115200, 8, odd,1

9600, 8, odd, 1

9600, 8, odd, 1

You can still change the communication settings to other values and save them for later use,after a power cycle for instance. However, after a factory reset the unit will return to the defaults
listed in the table above.

PPS pulse width

Minimum pulse
width

Acutime 360 standard

Acutime 360 GPSonly

Acutime Gold

106406-00

106406-05

55238-00

10ms

10ms

10us (micro seconds)

Acutime 360 standard

Acutime 360 GPSonly

Acutime Gold

106406-00

106406-05

55238-00

GPS and GLONASSGPS only

GPS only

Default constellations

Default
constellation

The user can still change the constellation settings to other values and save them for later use,after a power cycle for instance. However after a factory reset the unit will return to the defaults
listed in the table above.

Default messages
The messages in the table below are fixed to the part number of Acutime 360 antenna that theuser possesses. For instance a GPS-only Acutime 360 antenna will only output the 0x5C and
0x6D messages no matter what constellation is selected.
Acutime 360
standard

Acutime 360 GPSonly

Acutime Gold

106406-00

106406-05

55238-00

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 135

Acutime 360 Antenna GPS-only Variant

Acutime 360
standard

Acutime 360 GPSonly

Acutime Gold

Satellite Tracking Status
request/response

0x3C/0x5D

0x3C/0x5C

0x3C/0x5C

Satellite Selection List
request/response

0x24/0x6C

0x24/0x6D

0x24/0x6D

Protempis Acutime 360 Multi-GNSS Smart Antenna User Guide | 136