This manual reflects Software Versions 4.503 and 4.52
Proprietary Notice
Information in this document is subject to change without notice and does not rep resent a comm itmen t on th e part
of NovAtel Inc.. The software d escribed in this document is furnished under a licence agreement or non- disclosu re
agreement. The software may be used or copied only in accordance with the terms of the agreement. It is against
the law to copy the software on any medium except as specifically allowed in the license or non-disclosure
agreement.
No part of this manual may be reproduced or transmitted in any fo rm or by any means, electronic or mechanical,
including photocopying an d recording, for any purpose withou t the express written permission o f a duly author ized
representative of NovAtel Inc.
The information contained within this manual is believed to be true and correct at the time of publication.
MiLLennium, NovAtel, Narrow Correlator, RT-20 and RT-2 are registered trademarks of NovAtel Inc.
GPSCard, GPSAntenna, GPSolution and Pinwheel are trademarks of NovAtel Inc.
All other brand names are trademarks of their respective holders.
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 29
Software License
SOFTWARE LICENSE
SOFTWARE LICENSE
BY OPENING THE SEALED DISK PACKAGE YOU ARE AGREEING TO BE BOUND BY THE TERMS OF
THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT PROMPTLY
RETURN THE UNOPENED DISK PACKAGE AND THE ACCOMPANYING ITEMS TO NOVATEL INC.
1. License: NovAtel Inc. (“NovAtel”) grants you a non-exclusive license (not a sale) to use one copy of the enclosed NovAtel
software on a single computer, and only with the product whose model number and serial number appear on the en velope.
2. Copyright: NovAt el owns, or has the right to sub license, a ll copy right, tra de secret, p atent an d other p ropriet ary righ ts in the
software and the software is protected by national copyright laws, international treaty provisions and all other applicable
national laws. You must treat the software like any other copyrighted material except that you may either (a) make one copy
of the software solely for ba ckup or archiv al pur poses , or (b) tran sfer t he softwar e to a single hard disk pr ovi ded yo u kee p the
original solely for backup or a rc hi val p urp ose s. Yo u ma y not c op y the p r od uct m a nu al o r written mate ria ls a cco mpa n yin g the
software.
3. Restrictions: You may not: (1) copy (other than as provided for in paragraph 2), distribute, rent, lease or sublicense all or
any portion of the software; (2) modify or prepare derivative works of the software; (3) use the software in connection with
computer-based services business or public ly display visual ou tput of the software ; (4) transmit the soft ware over a network, by
telephone or elec tronical ly using any me ans; or (5) r everse eng ineer, deco mpile or dis assemble the software . You agree to ke ep
confidential and use your best efforts to prevent and protect the conten t s of th e soft ware from unauthorized disclosure or us e.
4. Term and Termination: This Agreement is effective until terminated. You may terminate it at any time by destroying the
software, including all computer programs and documentation, and erasing any copies residing on computer equipment. If you
do so, you should inform NovAtel in writing immediately. This Agreement also will terminate if you do not comply with any
of its terms or conditions. Upo n such termination you are obligate d to destroy the softwa re and erase all cop ies residing on
computer equipment. NovAtel reserves the right to terminate this Agreement for reason of misuse or abuse of this software.
5. Warranty: For 90 days from the date of shipment, NovAtel warrants that the media (for example, diskette) on which the
software is contained will be free from de fe cts in ma te rials and work man ship . Th is wa rranty do e s no t c over dam age cau sed by
improper use or neglect. NovAtel does not warrant the contents of the software or that it will be error free. The software is
furnished "AS IS" and without warranty as to the performance or results you may obtain by using the software. The entire risk
as to the results and performance of the software is assumed by you.
6. For software UPDATES and UPGRADES, and regular customer support, contact the NovAtel GPS Hotline at
1-800-NOVATEL (Canada and the U.S.A. only), or directly for International Customers 1-403-295-4900, Fax 1-403-2954901, e-mail to support@novatel.ca, visit out world wide web site at http://www.novatel.ca, or write to:
NovAtel Inc.
Customer Service Dept.
1120 - 68th Avenue NE
Calgary, Alberta,
Canada
T2E 8S5
7. Disclaimer of Warranty and Limitation of Liability:
a.THE WARRANTIES IN THIS AGREEMENT REPLACE ALL OTHER WARRANTIES, EXPRESS OR
IMPLIED, INCLUDING ANY WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
NOVATEL DISCLAIMS AND EXCLUDES ALL OTHER WARRANTIES. IN NO EVENT WILL NOVATEL'S
LIABILITY OF ANY KIND INCLUDE ANY SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING
LOST PROFITS, EVEN IF NOVATEL HAS KNOWLEDGE OF THE POTENTIAL LOSS OR DAMAGE.
b.NovAtel will not be liable for any loss or damag e caused by delay in fur nishing the software or a ny other performan ce
under this Agreement.
c.NovAtel's entire liability a nd your e xclusive remedie s for our liab ility of any kind (inc luding li abilit y for negli gence)
for the software covered by this Agreement and all other performance o r non performance by NovAtel un der or related to this
Agreement are limited to the remedies specified by this Agreement.
This Agreement is governe d by the laws of the Provinc e of Alberta, Canada. Each of the parties hereto irrevocably
attorns to the jurisdiction of the courts of the Province of Alberta.
10MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
Software Support
SOFTWARE SUPPORT
SOFTWARE SUPPORT
Software updates are software revisions to an existing model which improves (but does not increase) basic
functionality of the GPS receiver. During the one year warranty coverage following initial purchase, software
updates are supplied free of charge. After the warranty has expi red, software up dates and updated manuals may be
subject to a nominal charge.
Software upgrades are software releases which increase basic functionality of the receiver from one model to a
higher level model type. When available, upgrades can be pu rchased at a pr ice which is the d ifference between the
two model types on the current NovAtel GPS Price List plus a nominal service charge.
Software updates and upgrades are obtained through NovAtel authorized dealers or NovAtel Customer Support.
Contact your local NovAtel dealer for more information.
To locate a dealer in your area, contact NovAtel in any of the following ways:
• GPS Hotline at 1-800-NOVATEL (1-800-668-2835)
(U.S.A. and Canada only; 8 a.m. - 4:30 p.m. Mountain Standard Time)
Thank you for purchasing a NovAtel GPSCard product.
Whether you have bought a stand alone GPSCard or a packaged receiver you will have also received companion
documents to this manual. They will help you get the hardware operational. Afterwards, this text will be your
primary MiLLennium GPSCard command and logging reference source.
Scope
The MiLLennium Command Descriptions Manual describes each command and log that the MiLLennium
GPSCard is capable of accepting or outputting. Sufficient detail is provided so that you can understand the purpose,
syntax, and structure of each command or log and be able to effectively communicate with the GPSCard, thus
enabling the developer to effectively use and write custom interfacing softwar e for specific n eeds and applications .
The manual is organized into chapters which allow easy access to appropriate information about the GPSCard.
This manual does not address in detail any of the GPSC ard hardware attributes or installation information. Please
consult the appropriate companion manual for hardware or system technical specifications information.
Furthermore, should you encounter any functional, operational, or interfacing difficulties with the GPSCard,
consult the appropriate hardware manual for NovAtel warranty and customer support information.
Prerequisites
As this reference manual is focused on the GPSCard commands and logging protocol, it is necessary to ensure that
the GPSCard has been properly installed and powered up according to the instructions outlined in the companion
hardware manual before proceeding.
To use your NovAtel GPS receiver effectively, you should be familiar with the Global Positioning System (GPS)
as it applies to positioning, navigation, and surveying applications. For your reference Appendix A of this manual
provides an overview of the Global Positioning System.
This manual covers the full performance capabilities of all MiLLennium GPSCards. Every MiLLenn ium can be
upgraded through a family of firmware models, each having unique features. Ther efore, depending on the software
configuration of your MiLLennium, certain commands and logs may not be accessible. Feature-tagging symbols
have been created to help clarify which commands and logs are only available with a certain option:
RTKFeatures available only with MiLLennium GPSCards equipped with the RT-20 or RT-2 option
WAASFeatures available only on MiLLennium GP SCard s equipped with the WAAS/EGNOS option
What’s New In This Manual?
This manual includes enhancements that apply to both Firmware 4.503 and 4.52 (Points #1 and #2 below). Points
#3 to #6 are enhancements that apply only to Firmware 4.52.
1. Further WAAS/EGNOS capabilities with the additions to the WAASCORRECTION and IONOMODEL
commands.
2. New WEPA/B and WUTCA/B logs.
3. Aircraft & Rapid Kinematic Applicatio n Optimization. Enhanced satellite tracking ability unde r demanding
high velocity and rapidly changing altitude circumstances, especially applications involving aircraft and
photogrammetry.
4. Improvements to L1 / L2 AGC Po wer Calculations. MiLLen nium GPS Cards are now bet ter equipped to handle
increased ionospheric activity and atmospheric disturbances caused by the increasing solar activity of the
approaching solar maximus.
5. Fixed TM1 log to correctly display the week field.
6. Decreased Sensitivity to RF Interference and Jamming. MiLLennium GPS Cards will now more accurately
track L1 and L2 GPS signals through high levels of external RF interference. Examples of RF interference
sources include intentional or accidental RF jamming and increased solar activity.
12MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
1 Quick Start
1QUICK START
1 QUICK START
This chapter will help you get started quickly regardless of whether you wish to carry out real-time kinematic
(RTK) positioning, operate in differential modes or simply log data. Each section references additional sources of
information.
1.1 INSTALLATION
For more detailed instructions on the installation and set up of your GPSCard please refer to the accompanying
MiLLennium GPSCardGuide to Installation and Operation.
The MiLLennium receiver is designed for flexibility of integration and configuration. You are free to select an
appropriate data and signal interface, power supply system and mounting structure. This concept allows OEM
purchasers to custom-design their own GPS-based positioning system around the MiLLennium GPSCard.
Installing the MiLLennium GPSCard typically consists of the followin g:
•Mount the GPSCard in a secure enclosure to reduce environmental exposure, RF
interference and vibration effects
•Pre-wire the I/O harness and the 64-pin DIN female connector for power and
communications, then connecting them to the OEM series GPSCard
•Install the GPSAntenna, then connect to the GPSCard
•(Optional) Install an external oscillator if additional precision and stability is required
OPERATION
Once the hardware and software installations ha ve been completed, you are now read y to beg in initial operation of
the GPSCard receiver.
Communication with the MiLLennium GPSCard consists of issuing commands through the COM1 or COM2 port
from an external serial communications device. This could be either a terminal or an IBM-compatible PC that is
directly connected to a MiLLennium GPSCard COM port using a null modem cable.
TURNING ON
The initial operating software and firmware of th e MiLLennium GPSCard resides in its read-only m emory. As
such, the unit “self-boots” upon power- up. The green LED indicato r should b link ab out once per secon d if t he unit
is operating normally. The red one lights up if an error is detected during a self-test. The self-test status word can
be viewed in the RGEA/B/D and RVSA/B data output logs.
If a persistent error develops please con tact the Nov Atel GPS Customer Service Departm ent fo r fu rther assistance
COMMUNICATION DEFAULT SETTINGS
COM1 and COM2 for the MiLLennium GPSCards are defaulted to the following RS232 protocol:
•9600 bps, no parity, 8 data bits, 1stop bit, no handshake, echo off
Graphical Interface
Your GPSCard comes with a disk containing NovAtel’s graphical interface software GPSolution, a Microsoft
Windows-based program , enabling you to us e your GP SCard w ithout s truggl ing wit h commun ications protoc ol or
writing make-do software.
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 213
1 Quick Start
The View menu options allow you to select or de-select various visual aids and display screens. Take a look at all
of the options and keep open those you wish to display. To send commands and log data the Command Console
screen should be visible. ASCII format logs can be monitored on the ASCII Record screen.
e.g. On the command line of the Command Console screen type:
After you hit the <Enter> key the ASCII Record screen will display the output for your current position. The
POSA/B log is described on Page 180.
log com1 posa once
1.2 DATA LOGGING
The GPSCard has four major logging formats:
•NovAtel Format Data Logs (ASCII/Binary)
•NMEA Standard Format Data Logs (ASCII)
•RTCM Standard Format Data Logs (Binary)
•RTCA Standard Format Data Logs (Binary)
All data types can be logged using several methods of triggering each log event. Each log is initiated using the LOG
command. The LOG command and syntax are listed following.
14MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
LOGLOG
portCOM1 or COM2 Defaults to the port that the command was entered on.COM1
datatypeEnter one of the valid ASCII or Binary Data Logs (see Chapter 4, Page 35 and Appendix D, Page 138)POSA
triggerEnter one of the following triggers.ONTIME
ONCEImmediately logs the selected data to the selected port once. Default if trigger field is left
ONMARKLogs the selected data when a MARKIN electrical event is detected. Outputs internal buffers
ONNEWLogs the selected data each time the data is new even if the data is unchanged.
ONCHANGEDLogs the selected data only when the data has changed.
ONTIME
[period], [offset]
CONTINUOUSLYWill log the data all the time. The GPSCard will generate a new log when the output buffer
periodUse only with the ONTIME trigger. Units for this parameter are seconds. The selected period may be any of the
following values: 0.05, 0.10, 0.20, 0.25, 0.50, 1, 2, 3, ... , 3600 seconds but may be limited by the GPSCard model
and previously requested logs. Selected data is logged immediately and then periodic logging of the data will start
at the next even multiple of the period. If a period of 0.20 sec is chosen, then data will be logged when the receiver
time is at the 0.20, 0.40, 0.60 and the next (0.80) second marks. If the period is 15 seconds, then the logger will
log the data when the receiver time is at even 1/4 minute marks. The same rule applies even if the chosen period
is not divisible into its next second or minute marks. If a period of 7 seconds is chosen, then the logger will log at
the multiples of 7 seconds less than 60, that is, 7, 14, 21, 28, 35, 42, 49, 56 and every 7 seconds thereafter.
offsetUse only with the ONTIME trigger. Units for this parameter are seconds. It provides the ability to offset the logging
events from the above startup rule. If you wished to log data at 1 second after every minute you would set the period
to 60 seconds and the offset to 1 second (Default is 0).
holdWill prevent a log from being removed when the UNLOGALL command is issuedHOLD
blank.
at time of mark - does not extrapolate to mark time. Use MKPA/B for extrapolated position
at time of mark.
Immediately logs the selected data and then periodically logs the selected data at a
frequency determined by the period and offset parameters. The logging will continue until an
UNLOG command pertaining to the selected data item is received (see the UNLOG
command, Page 134).
associated with the chosen port becomes empty. The continuously option was designed for
use with differential corrections over low bit rate data links. This will provide optimal record
generation rates. The next record will not be generated until the last byte of the previous
record is loaded into the output buffer of the UART.
60
1
NOTE: The syntax for a command can contain option al parameters (OPT1, OP T2, ...). OPT2 may only be us ed if
it is preceded by OPT1. OPT3 may only be used if it is preceded by OPT2 and so on. Parameters after and
including OPT1 will be surrounded by square brackets.
An optional parameter such as {hold} surrounded by braces may be used with the log command without
any preceding optional parameters.
Example:
log com1 posa 60 1 hold
log com1 posa hold
Example:
log com1,posa,ontime,60,1
If the LOG syntax does not include a trigger type, it will be output only once following execution of the LOG
command. If trigger type is specified in the LOG syntax, the log will continu e to be output based on the trigger
specification. Specific logs can be disabled using the UNLOG command, whereas all enabled logs will be disabled
by using the UNLOGALL command (see Chapter 2, Page 24 and Appendix C, Page 81). All activated logs will
be listed in the receiver configuration status log (RCCA), Page 192.
The [port] parameter is optional. If [port] is not specified, [port] is defaulted to the port that the command was
received on.
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 215
1 Quick Start
COMMONLY USED LOGS
Type LogsTrigger
PositioningPRTKA/B
POSA/B
Post ProcessingRGEA/B/D
REPA/B, ALMA/B
NMEA PositionGPGLL
GPGGA
Other useful logs are
•RCCA to list the default command settings
•ETSA to monitor the channel tracking status
•SATA to obser ve the satellite specific data
•DOPA to monitor the dilution of precision of the current satellite constellation
•RVSA to monitor the receiver status
For further information on output logging see Chapter 4, Page 35 and the individual logs listed alphabetically in
Appendix D, Page 138.
Use the HELP command to list all available commands. For more info rmation on sending comm ands s ee Chapter
2, Page 24 and the individual commands listed alphabetically in Appendix C, Page 81.
ontime or onmark
ontime
onchanged
ontime or onmark
1.3 DIFFERENTIAL OPERATION
The MiLLennium GPSCard is ideal for design into DGPS systems because it is capable of operating as either a
reference station or a rover station.
The GPSCard is capable of utilizing various formats of differential corrections. These formats are divided into two
primary groups RTCM and RTCA.
For detailed data structure concerning these logs, please see:
Operating the GPSCard with a DGPS system requires that the reference station broadcast differential correction
data messages to one or more rover receivers. As there are many methods by which this can be achieved, it is up
to you to establish an appropriate data link that best suits your user requirements.
Whatever data link is chosen, the operator of the reference station will want to ensure that the bit rate of data
transmission is suitable for the an ticipated data lin k and remote u sers. Use the GPS Card COMn comm and to the
COM port default bit rate (default is 9600 bps, no parity, 8 data bits, 1 stop bit, no handshake, echo off).
Note that the GPSCard COMn_DTR and COMn_RTS commands are available for remote device keying (such as
a radio transmitter). These commands allow for flexible control of the DTR and RTS lines to be precisely timed
with log transmissions.
Further information may be found in Appendix A.Table 1-1, following, is a GPSCard pseudorange differential initialization summary.
16MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
Differential mode of operation is established at the reference station through a two step process: fix position and
logging observation and correction data.
FIX POSITION
The reference station must initialize the precise position of its reference antenna phase centre (lat/lon/hgt). This is
accomplished by utilizing the GPSCard FIX POSITION command. The syntax is as follows:
Syntax:
FIX POSITIONlat lonheightstation idhealth
Example:
fix position 51.3455323,-114.2895345,1201.123,555,0
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 217
1 Quick Start
NOTE 1: Entry of the station ID and health are optional. For a CMR correction type the station ID mu st b e < 31 .
NOTE 2: The accuracy of the reference station’s FIX POSITION setting will directly affect the accuracy of its
computed differential corrections. Good results at the rover station are dependent on the reference
station’s combined position errors being kept to a minimum (e.g., fix position error + multipath errors).
NOTE 3: The GPSCard performs all computations based on WGS84 and is defaulted as such, regardless of
DATUM command setting. The datum in which you choose to operate is converted from WGS84;
therefore, all differential corrections are based on WGS84. Ensure that any change in your operating
datum is set prior to FIX POSITION.
NOTE 4: When transmitting RTCM type data, the GPSCard has various options for assigning the number of data
bits per byte. Please see the GPSCard command RTCMRULE, Page 116 for further information
concerning RTCM data bit rule settings.
NOTE 5: The FIX POSITION “health” field entered will be reported in word 2 of the RTCM message frame
header.
Once the GPSCard has its position data fixed and is tracking th ree or more satellites, it is now ready to trans mit
differential correction and observation data to the rover stations.
LOG BROADCAST DATA
Assuming that a data link has been establi shed, use the GPSCard log command to send observation and di fferential
corrections data for broadcast to the rover stations.
Syntax:
LOGport dataontimeseconds
Example:
log com1 rtcm ontime 5
NOTE:Ensure that the bit rate of the data link is suitable for the differential type, logging rate and maximum
message length of the data type being logged.
1.4 RTK MODE
NovAtel’s RTK system utilizes proprietary messaging as well as RTCM Types 18 and 19, and can also receive
CMR messages from a non-NovAtel base station. For more information on specific message formats please see
Chapter 4, Page 46.
NOTE:No guarantee is made that the MiLLennium will meet its performance specifications if non-NovAtel
accessories (e.g. antennas, RF cable) are used.
Data Communications Link
It is the user’s responsibility to provide a data communicatio ns link between the reference station and remote
station. The data transfer rate must be high enough to ensure that sufficient reference station messages reach the
remote station to keep extrapolation errors from growing too large; see Table 1-2.
Table 1-2 Latency-Induced Extrapolation Error
Time since last reference station observationTypical extrapolation error (CEP)
18MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
1 Quick Start
Generally, a communications link capable of data throughput at a rate of 4800 bits per second or higher is
sufficient. However, it is possible to satisfactorily use a lower rate (e.g. 2400 bps) with the RTC A, RTCM 59 and
CMR formats. RTCM Types 18 and 19 may require a higher rate; see Chapter 4, Message Formats, Page 46 for
additional information. The minimum data transfer rate is based on the following :
1. RT-2 requires th at the reference station periodically transmit two RTCA Standard Type 7 messages:
•An RTCAOBS message contains reference station satellite observation information, and
should be se nt once every 1 or 2 seconds.
•An RTCAREF message contains reference station position information, and should be
sent once every 10 seconds.
OR periodically transmit an R TCM Type 18 and RTCM Type 19 (R TCM1819) me ssage together with an
RTCM Type 3 message:
•A Type 3 message contains reference station position information , and shou ld be sent
once every 10 seconds (although it is possible to send it as infrequently as once every 30
seconds).
•RTCM1819 gives raw measurement information (Type 18 provides carrier phase
measurements, while Type 19 provides pseudorange measurements) and should be sent
once every 1 or 2 seconds.
NOTE: This message can be sent in RT CM Version 2. 1 or Vers ion 2.2 fo rmat, contro lled with the RTKMODE
command.
and, optionally, also periodically transmit an RTCM Type 22 message together with an RTCM Type 3
message:
•A Type 3 message contains reference station position information , and shou ld be sent
once every 10 seconds (although it is possible to send it as infrequently as once every 30
seconds).
•A Type 22 message gives extended reference station parameters and should be sent once
every 10 seconds.
OR periodically transmit two CMR messages where the station ID, see Page 100, must be
transmitting CMR corrections:
•A CMROBS message contains reference station satellite observation information, and
should be se nt once every 1 or 2 seconds.
•A CMRREF message contains reference station position information, and should be sent
once every 10 seconds.
2. RT-20 requires that the reference station periodically transmit either the RTCA messages listed above (the
recommended option), or RTCM 1819 or CMR messages or the RTCM SC-104 Type 3 & 59N messages:
•A Type 3 message contains reference station position information , and shou ld be sent
once every 10 seconds (although it is possible to send it as infrequently as once every 30
seconds).
•A Type 59N message contains reference station satellite observ ation information, and
should be sent once every 2 seconds.
≤ 31 when
Further information on RTCA, RTCM and CMR message formats is contained in Chapter 6.
System Initiali za t ion
The RTK system is designed for ease of use: you set up the remote station, enter a command so that it accepts RT2 or RT-20 messages from the reference station, and are ready to go. There are options, however, which can be
used to adapt the system to a specific application. Some options apply only to the reference station, while others
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 219
1 Quick Start
apply only to the remote station. Detailed descriptions can be found in Appendix C, CommandsSummary.
In the following sections, keep the following in mind:
•Dynamics modes. For reliable performance the antenna should not move more than 1-2
cm when in static mode. See the RTKMODE commands in Chapter 2, Page 24 and
Appendix C, Page 117 for more information.
•When using the FIX POSITION command, the height entered must be in metres above
mean sea level; it will be converted to ellipsoidal height inside the receiver. You can enter
an undulation value, if desired, using the UNDULATION command; if none is entered,
the receiver estimates an undulation with its internal table. The format of the optional
station ID field depends on whether RTCM or R TC A mes sages ar e being us ed: if RTCM,
any number from 0 - 1023 is valid, while if RTCA, any 4-character string of numbers and
upper-case letters, enclosed in quotation marks, is valid. See Appendix C, Page 100 for
additional information on the station id field.
• The COMn field refers to the se rial por t (eit her COM1 or COM2) to which data
communications equipment is connected. The serial port assignment at the reference and
remote stations need not be the same; e.g. a radio transmitter might be connected to
COM1 at the reference station, and a radio receiver to COM2 at the remote station.
INITIALIZATION FOR RTCA-FORMAT MESSAGING (RT-2 OR RT-20)
The following commands will enable RTCA-format messaging and allow RT-2 or RT-20 to operate with the
remote station either at rest or in motion. Note that the optional station health field in the existing FIX POSITION
command is not currently implemented in NovAtel’s RTCA messages, though it will be in the future.
1. At the reference station:
fix position lat,lon,height,station id
log comn,rtcaref,ontime,interval
log comn,rtcaobs,ontime,interval
Example:
fix position 51.11358042,-114.04358013,1059.4105,”RW34”
log com1,rtcaref,ontime,10
log com1,rtcaobs,ontime,2
2. At the remote station:
accept comn,rtca
Example:
accept com2,rtca
Congratulations! Your RTK system is now in operation!
INITIALIZATION FOR RTCM59-FORMAT MESSAGING (RT-20 ONLY)
Although RT-20 can operate with either RTCA or RTCM-format messaging, the use of RTCA-format messages is
recommended (see Chapter 4, Page 46 for further information on this topic). Nevertheless, the following
commands will enable RTCM59-format messaging and allow RT-20 to operate with the remote station either at
rest or in motion:
1. At the reference station:
fix position lat,lon,height,station id,station health
log comn,rtcm3,ontime,interval
log comn,rtcm59,ontime,interval
20MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
1 Quick Start
Example:
fix position 51.11358042,-114.04358013,1059.4105,119,0
log com1,rtcm3,ontime,10
log com1,rtcm59,ontime,2
2. At the remote station:
accept comn,rtcm
Example:
accept com2,rtcm
Congratulations! Your RT-20 system is now in operation!
Monitoring Your RTK Output Data
At the remote station, you could now select any or all of these output logs for positioning information:
•BSLA/BBaseline Measurement
•NMEA-format logs
•POSA/BComputed Position
•PRTKA/B Best Position
•RPSA/BReference Station Position & Health
•RTKA/B RTK Output - Time Matched Positions
The POSA/B, PRTKA/B and NMEA-format logs contain the low-latency position; the RTKA/B logs co ntain the
matched position. The low-latency solution is the recommended one for kinematic users, while the matched
solution is the one recommended for stationary users. Fo r a discussion on low-latency and matched positions, see
the Differential Positioning section of Appendix A, Page 67.
Options for Logging Differential Corrections
SET DGPSTIMEOUT
The DGPSTIMEOUT command allows the reference station to set the delay by which it wil l inhibit utilization of
new ephemeris data in its differential corrections. This delay ensures that the remote receivers have had sufficient
time to collect updated ephemeris data as well.
A delay of 120 to 130 seconds will typically ensure that the rover stations have collected updated ephemeris. After
the delay period is pas sed, t he r eferen ce st at ion wi ll b egi n us ing n e w ephem eri s dat a. To ent er an ephemeris delay
value, you must first enter a numeric placeholder in the DGPS delay field (e.g., 2). When operating as a reference
station, DGPS delay will be ignored (see the DGPSTIMEOUT command found in Chapter 2, Page 24 and
Appendix C, Page 92 for further information on using this command at rover stations.)
Syntax:
DGPSTIMEOUTdgps delayephem delay
Command OptionDescriptionDefault
DGPSTIMEOUTCommand
dgps delaymin. 2
max.1000
ephem delaymin.0
max. 600
Maximum age in seconds60
Minimum time delay in seconds120
Example:
dgpstimeout 2,300
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 221
1 Quick Start
USING RTCM SC-104 LOG TYPES
RTCM SC-104 is a standard for transmitting differential corrections between equipment from different
manufacturers. The NovAtel GPSCard is capable of transmitting or receiving RTCM data.
To facilitate transmitting the RTCM data over shared data links, the GPSCard is also capable of sending the RTCM
log in NovAtel ASCII format (R TCMA) or with the NovA tel binary header (R TCMB) added to allow s ynchronous
transmission and reception along with other data types.
NOTE:When sending or receiving RTCM log types, it is important to ensure that all connected equipment are
using the same RTCMRULE for compatibility.
The easiest method to send RTCM standard lo gs is from the COM1 o r COM2 ports of the referen ce GPSCard. The
easiest method to receive the RTCM data is through the COM1 or COM2 port of the rover GPSCard. The rover
GPSCard must issue the “ACCEPT port RTCM” command to dedicate a port before it will accept the RTCM data
into that port.
The RTCMA log can be intermix ed with othe r NovAtel A SCII data over a common communication port. It will
be directly interpreted by a rover GPSCard as a special data input command ($RTCM). “ACCEPT port
COMMANDS” must be used with this input command. A non-NovAtel rover station will need to strip off the
header ($RTCM) and terminator (*xx), then con vert the hexadecimal data to binary befo re the RTCM standard data
can be retrieved.
The RTCMB log can be intermixed with other NovAtel binary data over a common communication port.
REMEMBER: Use the CDSA/B logs to monitor the COM port activity, success, and decoding errors.
USING RTCA LOG TYPES
The RTCA (Radio Technical Commission for Aviation Services) Standard is being designed to support
Differential Global Navigation Satellite System (DGNSS) aviation applications. The perceived advantage to using
RTCA type messages for transmitting and receiving differential corrections versus using RTCM type messages is
that RTCM transmits 30-bit words, and the data is difficult to decode and process because of the parity algorithm
and irregular word sizes used. RTCA is transmitted in 8-bit words, which are easier to generate, process and
decode. The RTCA messages are therefore smaller, they have a 24 bit CRC that is much more robust than RTCM
messages, and they permit the use of a four-alpha-character station ID.
RTCA standard logs can be received through the COM1 or COM2 port of the rover GPSCard. The remote
GPSCard must issue the “ACCEPT port RTCA” command to dedicate a port before it will accept the RTCA data
input to that port. The RTCA logs cannot be intermixed with other logs.
The RTCAA log can be intermixed with other NovAtel ASCII data over a common communications port. It will
be directly interpreted by a rover GPSCard as a special data input comman d ($RTCA). “ACCEPT po rt commands”
must be used with this input command. A non-NovAtel rover station will need to strip off the header ($RTCA) and
terminator (*xx), then convert the hexadecimal data to binary before the RTCA standard can be retrieved.
The RTCAB log can be intermixed with other NovAtel binary data. Th e remote GPSCard identifies the RTCAB
log by the message block identifier contained in the message, and will interpret only the RTCA data portion of the
log.
NOTE: The CDSA/B logs may be used to monitor the COM port activity and differential data decode success.
Initialization - Rover Station
It is necessary to initialize the rover receiver to accept observation data from the reference station. If the receiver
is not correctly initialized, it will proceed to compute solutions in single point positioning mode.
22MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
1 Quick Start
Before initializing, ensure that the data link with the reference station has been properly set up. As well, ensure that
the COM port which is to receive the differential data is s et up to match th e bit rate and pr otocol settings of the
reference station broadcast data.
Establishing differential mode of operation at the rov er receiver is primarily a one- step process whereb y the accept
command is used to enable reception of observation data from the reference station.
ACCEPT COMMAND
The accept command is primarily used to set the GPSCard’s COM port command interpreter for acceptance of
various data formats (see the ACCEPT command in Chapter 2, Page 24 and Appendix C, Page 81).
Syntax
ACCEPTportmode
Example:
accept com2 rtcm
Once intitialized, the rover GPSCard receiver will operate in single point mode until the differential messages are
received. If the data messages are lost, the GPSCard will revert to single point positioning until the pseudorange
correction messages are restored.
NOTE:Ensure that the GPSCard RTCMRULE settings agree with the bit rule being transmitted by the RTCM
Range ValueDefault
reference station. Unless otherwise set, all GPSCards default to 6CR.
LOG POSITION DATA AND OTHER USEFUL DATA
The GPSCard remote receiver has many options for information data logging. To monitor position status, the user
may find the PRTKA/B logs to be the most informative. Other options exist, such as POSA/B and GPGGA. As
well, velocity data can be found in the VLHA/B, SPHA/B and GPVTG logs. It is really up to your specific
applications as to the full range of logs you require.
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 223
2 Command Descriptions
2COMMAND DESCRIPTIONS
2 COMMAND DESCRIPTIONS
2.1 GENERAL
This section describes all commands accepted by the GPSCard with the exception of the "Special Data Input
Commands". They are listed in alphabetical order. For descriptions of output logs using the LOG command, seeChapter 3.
The GPSCard is capable of responding to over 50 different input commands. You will find that once you become
familiar with these commands, the GPSCard offers a wide range in operational f lexibility. All commands are
accepted through the COM1 and COM2 serial ports. See Table 2-1, Page 26 for a complete command listing.
NOTE: You will find the HELP command a useful tool for inquiring about the various commands available.
The following rules apply when entering commands from a terminal keyboard:
•The commands are not case sensitive (
e.g.
e.g.
HELP or help
FIXPOSITION or fix position
COMMAND or command).
•All commands and required entries can be separated by a space or a comma
(command,variable
ORcommand variable).
e.g.datum,tokyo
e.g.datum tokyo
e.g.fix,position,51.3455323,-117.289534,1002
e.g.fix position 51.3455323 -117.289534 1002
e.g.com1,9600,n,8,1,n,off
e.g.com1 9600 n 8 1 n off
e.g.log,com1,posa,onchanged
e.g.log com1 posa unchanged
•At the end of a command or comm and strin g, p res s th e <CR> key. A carriage return is what
the card is looking for and is usually the same as pressing the <Enter> key.
•Most command entries do not provide a response to the entered command. Exceptions to
this statement are the VERSION and HELP commands. Otherwise, successful entry of a
command is verified by receipt of the COM port prompt (i.e. COM1> or COM2>).
The syntax for a command can contain optional parameters (OPT1, OPT2, ...). OPT2 may only be used if it
is preceded by OPT1. OPT3 may only be used if it is preceded by OPT2 and so on. Parameters after and
including OPT1 will be surrounded by square brackets.
An optional parameter such as {hold} surrounded by braces may be used with the log without any preceding
optional parameters
Example:
log com1 posa 60 1 hold
log com1 posa hold
When the GPSCard is first powered up, or after a FRESET command, all commands will rev ert to the factory
default settings. An example is shown below. The SAVECONFIG command can be used to modify the power-on
defaults. Use the RCCA log to reference stati on comm a nd and log settings.
24MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
2 Command Descriptions
NOTE:All previously stored configurations that were saved to non-volatile memory are erased (including
Saved Config, Saved Almanac, and Channel Config).
Example:
Optional Calculation Of The Checksum
When an input command is followed by an optional checksum, the checksum will be verified before the command
is executed. The checksum is the result of the logical exclusive-OR operation on all the bits in the message. So, the
checksum of a command with parameters will change if the parameters are modified.
NOTE: The command must be typed in uppercase for the proper checksum to be calculated.
As an example, it may be essential to ensure that a receiver has received and executed the correct command from
a host computer. If the checksum were calculated by the sender and attached to the command, the receiver would
be able to recognize if errors had been introduced and if so, alert the sender to this with an “Invalid Command
CRC” message.
Both are acceptable, but only the second one would trigger the verification function.
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 225
2 Command Descriptions
2.2 STANDARD COMMAND TABLES
Table 2-1 lists the commands by function while Table 2-2 is an alphabetical listing of commands. Please see
Appendix C, Page 81 for a more detailed description of individual commands which are listed alphabetically.
Table 2-1 Commands By Function Table
COMMUNICATIONS, CONTROL AND STATUS
CommandsDescriptions
ANTENNAPOWERPower to the low-noise amplifier of an active antenna
COMnCOMn port configuration control
COMn_DTRDTR handshaking control
COMn_RTSRTS handshaking control
DIFF_PROTOCOL
FREQUENCY_OUTVariable frequency output (programmable )
LOGLogging control
MESSAGESDisable error reporting fro m comm an d in terpre te r
RINEXConfigure the user defined fiel ds in t he file header
RTCMRULESets up RTCM bit rule
RTCM16TEnters an ASCII message
SENDSends ASCII message to COM port
SENDHEXSends non-printable characters
SETL1OFFSET
1Intended for advanced users of GPS only
1
1
Differential Protocol Control
Add an offset to the L1 pseudorange to compensate for
signal delays
GENERAL RECEIVER CONTROL AND STATUS
CommandsDescriptions
$ALMADownload almanac data file
CRESETReset receiver to factory default
DYNAMICSSet correlator tracking bandwidth
HELPOn-line command help
RESETPerforms a hardware reset (OEM only)
SAVEALMASaves the latest almana c in NVM
SAVECONFIGSav es current configuration (OEM onl y)
$TM1AInjects receiver time of 1PP S
VERSIONSoftware/hardware information
26MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
Table 2-1 Commands By Function Table (continued)
POSITION, PARAMETERS, AND SOLUTION FILTERING CONTROL
CommandsDescriptions
CSMOOTH
DATUMChoose a DATUM na me type
ECUTOFFSatellite elevation cut-off for solutions
FIX HEIGHTC onstrains to fixed height (2D mode)
FIX POSITIONConstrains to fixed lat, lon, height
FRESETClears all data which is stored in NVM
$IONADownload ion osphe ric correction data
IONOMODEL
LOCKOUTDeweights a satellite in solutions
$PVAA
RTKMODESetup the RTK mode
UNDULATIONEllipsoid-geoid separation
USERDATUMUser-customized datum
WAASCORRECTIONControls handling of WAAS/EGNOS corrections.
1 Intended for advanced users of GPS only.
1
1
Sets amount of carrier smoot hi ng
What ionospheric correction to use (MiLLennium with the
WAAS option)
Position, velocity and accel e rat ion in ECEF coordinates
2 Command Descriptions
SATELLITE TRACKING AND CHANNEL CONTROL
CommandsDescriptions
$ALMADownload almanac data file
ASSIGNSatellite channel assignment
CONFIGSwitc hes the channel configuratio n of th e G PSCard
DYNAMICSSets correlator tracking band w idth
FIX VELOCITYAids high ve l ocity reacqu i s ition
RESETHEALTHReset PRN health
SETHEALTHOverrides broadcast satellite health
DGPSTIMEOUTSets ephemeris del ay
FIX POSITIONConstrain to fixed (reference)
LOGSelects required differential-output log
POSAVEImplements position averagi ng for reference station
RTCMRULESelects RTCM bit rule
SETDGPSIDSet reference station ID
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 227
2 Command Descriptions
Table 2-1 Commands By Function Table (continued)
DIFFERENTIAL REMOTE STATION
CommandsDescriptions
ACCEPTAccepts RTCM1, RTCA or RTCA B di fferential inputs
$ALMAInput almanac data
DGPSTIMEOUTSet maximum age of differential data accepted
RESETPerforms a hardware reset
$RTCARTCA differential correct io n input (ASCII)
$RTCMRTCM differential correction in put (A SCII)
RTCMRULESelects RTCM bit rule
SETDGPSIDSelect differential referen ce stat io n ID to rec ei ve
CLOCK INFORMATION, STATUS, AND TIME
CommandsDescriptions
CLOCKADJUSTEnable clock modelling & 1PPS adjust
1
DIFF_PROTOCOL
EXTERNALCLOCKSets default parameters of an optional external oscillator
EXTERNALCLOCK FREQUENCYSets clock rate
SETTIMESYNC
$UTCADownload UTC data
Differential protocol control
1
Enable or disable time syn ch ronization
1Intended for advanced users of GPS only
Table 2-2 GPSCard Command Summary
CommandDescriptionSyntax
$ALMAInjects almanac(follows NovAtel ASCII log format)
$IONAInjects ionospheric refract ion corrections(follows NovAtel ASCII log format)
$PVAAInjects latest computed position, velocity and acceleration(follows NovAtel ASCII log format)
$REPAInjects raw GPS ephemeris data(follows NovAtel ASCII log format)
$RTCAInjects RTCA format DGPS corrections in ASCII (Type 1)(follows NovAtel ASCII log format)
$RTCMInjects RTCM format differential corrections in ASCII (Type 1)(follows NovAtel ASCII log format)
$TM1AInjects receiver time of 1 PPS(follows NovAtel ASCII log format)
$UTCAInjects UTC information(follows NovAtel ASCII log format)
ACCEPTPort input control (set command interpreter)accept port,option
ANTENNAPOWERPower to the low-noise amplifier of an active antennaantennapowerflag
ASSIGNAssign a prn to a channel #assign channel,prn,doppler, search window
UNASSIGNUn-assign a channelunassign channel
UNASSIGNALLUn-assign all channelsunassignall
CLOCKADJUSTDisable clock steering mechanismclockadjustswitch
COMnInitialize Serial Port (1 or 2)comn bps,parity,databits,stopbits, handshake,echo
COMn_DTRProgrammable DTR lead/tail timecomn_dtrcontrol,active,lead,tail
COMn_RTSProgrammable RTS lead/tail timecomn_rtscontrol,active,lead,tail
CONFIGSwitches the channel configuration of the GPSCardconfigcfgtype
CRESETConfiguration reset to factory defaultcreset
CSMOOTHSets carr ier smo oth ingcsmooth value
DATUMChoose a DATUM name typedatumoption
USERDATUMUser defined DATUMuserdatumsemi-major,flattening,dx,dy,dz, rx,ry,rz,
DGPSTIMEOUTSets maximum age of differential data to be accepted and ephemeris
delay
scale
dgpstimeout value value
28MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
2 Command Descriptions
DIFF_PROTOCOLDiffe ren tial cor rect ion messa ge enc odi ng and decod ing for
DYNAMICSSet receiver dyna micsdynamicsoption [user_dynamics]
ECUTOFFSet elevation cutoff angleecutoffangle
EXTERNALCLOCKSets default parameters of an optional external oscillatorexternalclock option
EXTERNALCLOCK
FREQUENCY
FIX HEIGHTSets height for 2D navigationfix height height [auto]
FIX POSITIONSet antenna coordinates for reference stationfix position lat,lon,height [station id] [health]
FIX VELOCITYAccepts INS xyz (ECEF) input to aid in high velocity reacquisition of
UNFIXRemove all receiver FIX constraintsunfix
FREQUENCY_OUTVariable frequency output (programmable)frequency_outn,k
FRESETClears all data which is stored in non-volatile memoryfreset
HELP or ?On-line command helphelp option or ? option
IONOMODELInfluences what ionospheric corrections the card usesionomodelkeyword
LOCKOUTLock out satellitelockoutprn
UNLOCKOUTRestore satelliteunlockoutprn
UNLOCKOUTALLRestore all satellitesunlockoutall
LOGChoose data logging typelog [port],datatype,[trigger],[period],[offset],{hold}
UNLOGDisable a data logunlog [port],data type
UNLOGALLDisable all data logsunlogall [port]
MAGVARSet magnetic variation correctionmagvar value
MESSAGESDisable error reporting from command inte rpre termessages port,option
POSAVEImplements position averaging for reference stationposavemaxtime, maxhorstd, maxverstd
RESETPerforms a hardware reset (OEM only)reset
RINEXConfigure the user defined fields in the file headersrinex cfgtype
RTCM16TEnter an ASCII text message to be sent out in the RTCM data streamrtcm16t ascii message
RTCMRULESet variations of the RTCM bit rulertcmrule rule
RTKMODESet up the RTK moderrtkmode argument, data range
SAVEALMASave the latest almanac in non-volatile memorysavealmaoption
SAVECONFIGSave current configuration in non-volatile memory (OEM only)saveconfig
SENDSend an ASCII message to any of the communications portssend port ascii-message
SENDHEXSends non-printable characters in hexadecimal pairssendhex port data
SETDGPSIDEnter in a reference station ID setdgpsid option
SETHEALTHOverride PRN healthsethealth prn,health
RESETHEALTHReset PRN healthresethealth prn
RESETHEALTHALLReset all PRN healthresethealthall
SETL1OFFSETAdd an offset to the L1 pseudorange to compensate for signal delayssetL1offsetdistance
SETNAVSet a destination waypointsetnavfrom lat,from lon,to lat, to lon,track offset, from
SETTIMESYNCEnable or disable ti me synchronizationsettimesync flag
UNDULATIONChoose undulationundulation separation
VERSIONCurrent software and hardware informationversion
WAASCORRECTIONDictates how the card handles WAAS/EGNOS correctionswaascorrectionkeyword [prn] [mode]
implementation in the GPS card firmware
Sets clock rateexternal frequency clock rate
SVs
diff_protocoltype key
or diff_protocol disable
or diff_protocol
fix velocity vx,vy,vz
port,to port
MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 229
2 Command Descriptions
Gro
u
S
Integrity data,differential corrections
,
time control, and statu
s
PS Satellit
eConstellationIntegrity da
ta,differential
c
and ranging
C-ban
d
tio
n
2.3 WAAS
The Wide Area Augmentation System (WAAS) is a safety-critical system that provides a quality of positioning
information previously unavailable. The WAAS improves the accuracy, integrity, and availability of the basic GPS
signals. In the future, the wide area of coverage for this system will include the entire United States and some
outlying areas. At the time of publication, there are two WAAS satellites over the western Atlantic Ocean and the
Pacific (PRN 122 and PRN 134 respectively) and one EGNOS satellite over the eastern Atlantic Ocean (PRN 120).
WAAS data is available from any of these satellites and more satellites will b e available in the fu ture.
The primary functions of WAAS include:
•data collection
•determining ionospheric corrections
•determining satellite orbits
•determining satellite clock corrections
•determining satellite integrity
•independent data verification
•WAAS message broadcast and ranging
•system operations & maintenance
As shown in Figure 2-1, the WAAS is made up of a series of Wide Area Reference Stations, Wide Area Master
Stations, Ground Uplink Stations and Geostationary Satellites (GEOs). The Wide Area Reference Stations, which
are geographically distributed, pick up GPS satellite data and route it to the Wide Area Master Stations where wide
area corrections are generated. These corrections are sent to the Ground Uplink Stations which up-link them to the
GEOs for re-transmission on the GPS L1 frequency. These GEOs transmit signals which carry accuracy and
integrity messages, and which also provide additional ranging signals for added availability, continuity and
accuracy. These GEO signals are available over a wide area and can be received and processed by ordinary GPS
receivers. GPS user receivers are thus able to receive WAAS data in-band and use not only differential corrections,
but also integrity, residual errors and ionospheric information for each monitored satellite.
GPS User
Figure 2-1 The WAAS Concept
Geostationary
Satellite (GEO)
L1
Wide-area
Refere nce Sta t ion
(WRS)
L1 & C-band
Wide-area
Refere nce Sta t ion
(WRS)
Wide-area
Master Station
(WMS)
L1 & L2
Wide-area
Reference Sta
(WRS)
G
orrections,
control
nd Uplink
tation
(GUS)
30MiLLennium GPSCard SW Version 4.503/4.52 Command Descriptions Manual Rev 2
Loading...
+ 255 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.