User Guide: Trimble Netr9 Gnss Reference Receiver
User Guide: Trimble Netr9 Gnss Reference Receiver
Version 4.15
Revision A
May 2010 F
Corporate Office How to Obtain Warranty Service
Survey Business Area To obtain warranty service for the Product, please contact your Trimble
Trimble Navigation Limited dealer. Alternatively, you may contact Trimble to request warranty
Survey Business Area service at +1-408-481-6940 (24 hours a day) or e-mail your request to
5475 Kellenburger Road trimble_support@trimble.com. Please be prepared to provide:
Dayton, Ohio 45424-1099 – - your name, address, and telephone numbers
USA – - proof of purchase
800-538-7800 (toll free in USA) – - this Trimble warranty card
+1-937-245-5600 Phone – - a description of the nonconforming Product including the model
+1-937-233-9004 Fax number
www.trimble.com – - an explanation of the problem.
Email: trimble_support@trimble.com The customer service representative may need additional information
from you depending on the nature of the problem.
Legal Notices
© 2010, Trimble Navigation Limited. All rights reserved. Warranty Exclusions and Disclaimer
Trimble and the Globe & Triangle logo are trademarks of Trimble This Product limited warranty shall only apply in the event and to the
Navigation Limited, registered in the United States and in other extent that (i) the Product is properly and correctly installed, configured,
countries. CMR+, Maxwell, NetR9, R-Track, TRIMMARK, VRS, and interfaced, maintained, stored, and operated in accordance with
Zephyr Geodetic are trademarks of Trimble Navigation Limited. Trimble's applicable operator's manual and specifications, and; (ii) the
Product is not modified or misused. This Product limited warranty shall
The Bluetooth word mark and logos are owned by the Bluetooth SIG, not apply to, and Trimble shall not be responsible for defects or
Inc. and any use of such marks by Trimble Navigation Limited is under performance problems resulting from
license.
(i) the combination or utilization of the Product with hardware or
Microsoft, Windows, and Internet Explorer are either registered software products, information, data, systems, interfaces or devices not
trademarks or trademarks of Microsoft Corporation in the United States made, supplied or specified by Trimble; (ii) the operation of the Product
and/or other countries. under any specification other than, or in addition to, Trimble's standard
All other trademarks are the property of their respective owners. specifications for its products; (iii) the unauthorized, installation,
modification, or use of the Product; (iv) damage caused by: accident,
Release Notice lightning or other electrical discharge, fresh or salt water immersion or
This is the January 2010 release (Revision A) of the NetR9 GNSS spray; or exposure to environmental conditions for which the Product is
reference receiver User Guide. It applies to version 4.15 of the NetR9 not intended; or (v) normal wear and tear on consumable parts (e.g.,
GNSS reference receiver firmware. batteries). Trimble does not warrant or guarantee the results obtained
through the use of the Product. NOTICE REGARDING PRODUCTS
Limited Warranty Terms and Conditions EQUIPPED WITH TECHNOLOGY CAPABLE OF TRACKING
SATELLITE SIGNALS FROM SATELLITE BASED AUGMENTATION
Product Limited Warranty SYSTEMS (SBAS) (WAAS/EGNOS, AND MSAS), OMNISTAR, GPS,
Subject to the terms and conditions set forth herein, Trimble Navigation MODERNIZED GPS, OR GLONASS SATELLITES, OR FROM IALA
Limited ("Trimble") warrants that for a period of (1) year from date of BEACON SOURCES: TRIMBLE IS NOT RESPONSIBLE FOR THE
purchase this Trimble product (the "Product") will substantially conform OPERATION OR FAILURE OF OPERATION OF ANY SATELLITE BASED
to Trimble's publicly available specifications for the Product and that the POSITIONING SYSTEM OR THE AVAILABILITY OF ANY SATELLITE
hardware and any storage media components of the Product will be BASED POSITIONING SIGNALS.
substantially free from defects in materials and workmanship. THE FOREGOING LIMITED WARRANTY TERMS STATE TRIMBLE'S
Product Software ENTIRE LIABILITY, AND YOUR EXCLUSIVE REMEDIES, RELATING
TO PERFORMANCE OF THE TRIMBLE PRODUCT. EXCEPT AS
Product software, whether built into hardware circuitry as firmware, OTHERWISE EXPRESSLY PROVIDED HEREIN, THE PRODUCT AND
provided as a standalone computer software product, embedded in flash ACCOMPANYING DOCUMENTATION AND MATERIALS ARE
memory, or stored on magnetic or other media, is licensed and not sold. PROVIDED "AS-IS" AND WITHOUT EXPRESS OR IMPLIED
If accompanied by a separate end user license agreement, use of any WARRANTY OF ANY KIND, BY EITHER TRIMBLE OR ANYONE WHO
such software will be subject to the terms of such end user license HAS BEEN INVOLVED IN ITS CREATION, PRODUCTION,
agreement (including any differing limited warranty terms, exclusions INSTALLATION, OR DISTRIBUTION, INCLUDING, BUT NOT LIMITED
and limitations), which shall control over the terms and conditions set TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
forth in this limited warranty). FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND
Software Updates NONINFRINGEMENT. THE STATED EXPRESS WARRANTIES ARE IN
LIEU OF ALL OBLIGATIONS OR LIABILITIES ON THE PART OF
During the limited warranty period you will be entitled to receive such TRIMBLE ARISING OUT OF, OR IN CONNECTION WITH, ANY
Fix Updates and Minor Updates to the Product software that Trimble PRODUCT.
releases and makes commercially available and for which it does not
charge separately, subject to the procedures for delivery to purchasers of SOME STATES AND JURISDICTIONS DO NOT ALLOW LIMITATIONS
Trimble products generally. If you have purchased the Product from an ON DURATION OR THE EXCLUSION OF AN IMPLIED WARRANTY, SO
authorized Trimble distributor rather than from Trimble directly, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
Trimble may, at its option, forward the software Fix Update or Minor Limitation of Liability
Update to the Trimble distributor for final distribution to you. Major
Upgrades, new products, or substantially new software releases, as TRIMBLE'S ENTIRE LIABILITY UNDER ANY PROVISION HEREIN
identified by Trimble are expressly excluded from this update process SHALL BE LIMITED TO THE AMOUNT PAID BY YOU FOR THE
and limited warranty. Receipt of software updates shall not serve to PRODUCT. TO THE MAXIMUM EXTENT PERMITTED BY
extend the limited warranty period. APPLICABLE LAW, IN NO EVENT SHALL TRIMBLE OR ITS SUPPLIERS
BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL OR
For purposes of this warranty the following definitions shall apply: CONSEQUENTIAL DAMAGE WHATSOEVER UNDER ANY
(1) "Fix Update" means an error correction or other update created to fix CIRCUMSTANCE OR LEGAL THEORY RELATING IN ANYWAY TO THE
a previous software version that does not substantially conform to its PRODUCTS, SOFTWARE AND ACCOMPANYING DOCUMENTATION
published specifications; (2) "Minor Update" occurs when AND MATERIALS, (INCLUDING, WITHOUT LIMITATION, DAMAGES
enhancements are made to current features in a software program; and FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS
(3) "Major Upgrade" occurs when significant new features are added to OF DATA, OR ANY OTHER PECUNIARY LOSS), REGARDLESS OF
software, or when a new product containing new features replaces the WHETHER TRIMBLE HAS BEEN ADVISED OF THE POSSIBILITY OF
further development of a current product line. Trimble reserves the right ANY SUCH LOSS AND REGARDLESS OF THE COURSE OF DEALING
to determine, in its sole discretion, what constitutes a significant new WHICH DEVELOPS OR HAS DEVELOPED BETWEEN YOU AND
feature and Major Upgrade. TRIMBLE. BECAUSE SOME STATES AND JURISDICTIONS DO NOT
ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
Warranty Remedies CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE
If the Trimble Product fails during the warranty period for reasons LIMITATION MAY NOT APPLY TO YOU.
covered by this Limited Warranty and you notify Trimble of such failure PLEASE NOTE: THE ABOVE TRIMBLE LIMITED WARRANTY
during the warranty period, Trimble at its option will repair OR replace PROVISIONS WILL NOT APPLY TO PRODUCTS PURCHASED IN
the nonconforming Product, OR refund the purchase price paid by you THOSE JURISDICTIONS, SUCH AS COUNTRIES OF THE
for the Product, upon your return of the Product to Trimble in EUROPEAN ECONOMIC COMMUNITY, IN WHICH PRODUCT
accordance with Trimble's standard return material authorization
procedures.
Type approval
Type approval, or acceptance, covers technical parameters of the equipment related to
emissions that can cause interference. Type approval is granted to the manufacturer of
the transmission equipment, independent from the operation or licensing of the units.
Some countries have unique technical requirements for operation in particular radio-
modem frequency bands. To comply with those requirements, Trimble may have
modified your equipment to be granted Type approval. Unauthorized modification of
the units voids the Type approval, the warranty, and the operational license of the
equipment.
Battery safety
C WARNING – Charge and use the rechargeable Lithium-ion battery only in strict
accordance with the instructions. Charging or using the battery in unauthorized
equipment can cause an explosion or fire, and can result in personal injury and/or
equipment damage.To prevent injury or damage:
C WARNING – When this receiver is connected to a Power over Ethernet (PoE) connection,
the source of the Ethernet power must meet IEEE 802.11af. The receiver DC output
(Ethernet power source) must be completely isolated from earth ground (floating).
Otherwise, a shock hazard may exist.
C WARNING – When this reeiver is connected to a PoE connection, the DC voltage must be
limited to no more than 57 V DC +0% under both normal and single fault conditions. If
the recommended input voltage is exceeded, the receiver may present an electrical
hazard.
C WARNING – This receiver is not intended to be used in a wet location, or a location that
may become wet, when it is powered by the PoE interface, or by the external DC power
supply. Use the receiver in a wet location only when operating it on its own internal
battery.
C WARNING – The external power adapter and its associated power cord and plug are not
intended to be installed outdoors, or in a wet location.
C WARNING – Do not power the receiver through external power when operating in a wet
environment or an environment that may become wet. The power input connections
must be sheltered.
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
About the receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Technical support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Your comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Receiver framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
The network appliance concept. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Receiver services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Receiver features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Use and care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Electronic interference. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
COCOM limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Keypad and display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Rear connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
8 Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
A NMEA-0183 Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
NMEA-0183 message overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Common message elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
C Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Receiver issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
1
Introduction 1
Related information
Sources of related information include the following:
• Release notes: The release notes describe new features of the product,
information not included in the manuals, and any changes to the manuals. They
are provided as a PDF file on the Trimble website.
• Trimble training courses: Consider a training course to help you use your GNSS
system to its fullest potential.
For more information, go to www.trimble.com/training.html.
Technical support
If you have a problem and cannot find the information you need in the product
documentation, contact your local Infrastructure dealer. Alternatively, go to the
Support area of the Trimble website (www.trimble.com/support.shtml) and then select
the product you need information on. Product updates, documentation, and any
support issues are available for download.
If you need to contact Trimble technical support, complete the online inquiry form at
www.trimble.com/support_form.asp.
Your comments
Your feedback about the supporting documentation helps us to improve it with each
revision. Email your comments to ReaderFeedback@trimble.com.
2
Overview 2
Receiver framework
The receiver integrates the latest multi-frequency GNSS technology into a specialized
processing and communications framework. The receiver can operate as a standalone
reference station or it can be integrated into a scalable network.
With an Internet Protocol (IP) as the primary communications method, you can use
public domain tools, such as a web browser and FTP client, to configure the receiver
and access logged data files.
Note – All references to the Internet refer to either a Wide Area Network (WAN) or a Local
Area Network (LAN) connection.
You can enforce multiple levels of security, from a completely open system that allows
anonymous access to all features, to a secured system that requires a password
protected login for configuration changes and/or file access.
Use the network management features to create a base configuration with a variety of
operating modes. You can then enable those modes as necessary instead of switching
the global state of the receiver from one mode to another. For example, you can
configure a number of streaming services with different configurations (such as
measurement intervals or smoothing controls) on different TCP or UDP ports. To
activate one or more modes, open the connection to the specific port. This allows
multiple clients to access any given streaming service.
These features and many more, shift the model of a GNSS receiver toward the concept
of a "network appliance".
The receiver provides the following standard configuration and data logging services:
Use... To perform...
HTTP all manual and automated configuration operations manual operations to
manage the logged data file space
FTP remote manual and/or automated operations to manage the logged data file
space
Receiver services
The receiver can provide one or more streaming or query services over a RS-232 serial
port or a TCP/IP port:
• Streaming service
Anyone with authorized access can obtain streamed information, such as GNSS
measurements or RTCM corrections, without having to control or issue
commands to the receiver. The client simply connects to the port that is
streaming the required information. Normally the port should be set to Output
only mode so multiple users can connect to receive correction data.
• Query service
This allows bi-directional communications between the receiver and another
application. All ports act as query ports unless Output-only mode is selected.
When Output-only mode is selected, it also means the receiver is more secure;
especially if it is on the Internet. Multiple users can connect simultaneously to a
single port as long as it is set to Output-only mode.
Multiple users can connect simultaneously to a single port as long as it is set to Output
only mode.
Receiver features
• 440-channels
– GPS: L1/L2/L2C/L5
– GLONASS: L1 C/A and unencrypted P code, L2 C/A, and unencrypted P
code
– Galileo: GIOVE-A and GIOVE-B
– SBAS: L1C/A and L5 supporting WAAS, EGNOS, and MSAS
– L-Band: OmniSTAR VBS/HP/XP
• 8 GB on-board storage
• External USB drive support
• Integrated battery, provides over 15 hours operation
C CAUTION – Operating or storing the receiver outside the specified temperature range can
damage it. For more information, see Chapter 8, Specifications.
Electronic interference
High-power signals from a nearby radio or radar transmitter can overwhelm the
receiver circuits. This does not harm the instrument, but it can prevent the receiver
electronics from functioning correctly.
Avoid locating the receiver or antenna within 400 meters of powerful radar, television,
or other transmitters or GNSS antennas. Low-power transmitters, such as those in cell
phones and two-way radios, normally do not interfere with receiver operations.
COCOM limits
The U.S.A. Department of Commerce requires that all exportable GNNS products
contain performance limitations so that they cannot be used in a manner that could
threaten the security of the United States of America.
On the NetR9 GNSS reference receiver, immediate access to satellite measurements
and navigation results is disabled when the receiver velocity is computed to be greater
than 1000 knots, or its altitude is computed to be above 18 000 meters. The receiver
GNSS subsystem resets until the COCOM situation clears. As a result, all logging and
stream configurations stop until the GNSS subsystem is cleared.
1
4
2 3 2
Feature Description
1 Power LED Shows if the power is on or off.
2 Buttons Use to turn on and turn off the receiver, and to configure it. See Button functions,
page 32.
3 Display This Vacuum Fluorescent display enables you view the receiver operations the
configuration settings. See Home screen, page 33.
4 Blutooth logo Location of the Blutooth antenna.
Rear connectors
1 2 3 4
5 6 7
3
Batteries and Power 3
External power
The receiver uses an external power source in preference to its internal battery. If the
receiver is not connected to an external power source, or if the external power supply
fails, the internal battery is used.
The applied external power must offer between 9.5 V DC and 28 V DC and must be
able to supply at least 5 W of power. The receiver's internal battery charges only when
the external voltage is above 12 V DC. Trimble recommends that external supply
voltage be above 12 V DC for long-term installations. This ensures that the internal
battery is charged and ready to compensate for power supply disruptions.
While carrying out static measurements for postprocessed computations using the
internal memory, if no external power is supplied and the internal battery is drained,
the receiver shuts down. No data is lost; when power is restored, the receiver restarts in
the same status as it was when power was lost.
If you prefer not to use the internal battery as an uninterruptable power supply, you
can disable this feature in the Web user interface. For more information, see Chapter 6,
Configuring the Receiver: Other Than Keypad and Display.
C WARNING – The external AC power adapter and its associated power cord and plug are
not intended to be installed outdoors, nor in a wet location. Do not power the receiver
through external power when operating in a wet environment or an environment that
may become wet. The power input connections must be sheltered.
C WARNING – When you apply DC voltage to this product through the Lemo connector, the
DC voltage must be limited to 28 V DC +0% under both normal and single fault
conditions. This product may present an electrical hazard if the recommended input
voltage is exceeded
Battery safety
The receiver is powered by a rechargeable internal Lithium-ion battery. Charge and use
the battery only in strict accordance with the following instructions.
Battery performance
To optimize battery performance and extend battery life:
• Fully charge all new batteries before use.
• Do not use at extreme temperatures. The receiver is designed to operate at
-40 °C to +65 °C (-40 °F to +149 °F). However, operation at temperatures of less
than 0 °C (32 °F) can cause a rapid drop in battery life.
• Do not allow a battery that is in storage to discharge to below 5 V.
C WARNING – Charge and use the rechargeable Lithium-ion battery only in strict
accordance with the instructions. Charging or using the battery in unauthorized
equipment can cause an explosion or fire, and can result in personal injury and/or
equipment damage.
To prevent injury or damage:
- Do not charge or use the battery if it appears to be damaged or leaking.
- Charge the Lithium-ion battery only within the NetR9 receiver. The battery can only be
removed by an authorized Trimble Service Center.
4
Setting Up the Receiver 4
Guidelines
When you set up the receiver, follow these guidelines.
Environmental conditions
The receiver has a waterproof housing but you must take reasonable care to keep the
unit dry.
To improve the performance and long-term reliability of the receiver, do not expose the
receiver to extreme environmental conditions, such as:
• Water
• Heat greater than 65 °C (149 °F)
• Cold less than -40 °C (-40 °F)
• Corrosive fluids and gases
For additional information on this topic, research the reference antenna installation
guidelines published by the:
• US National Geodetic Survey
(http://www.ngs.noaa.gov/PUBS_LIB/CORS_guidelines.pdf )
• International GNSS Service
(http://igscb.jpl.nasa.gov/network/guidelines/guidelines.html)
GNSS antenna
The receiver provides a TNC-type female connector for connecting to an antenna. The
receiver is intended for use with a Zephyr Geodetic™ Model 2 antenna or a Trimble
GNSS Choke Ring antenna.
Antenna cabling
Many permanent GPS installations have unique cabling requirements. Depending on
the available infrastructure, you may need to mount the antenna a substantial distance
from the receiver.
The receiver can withstand a loss of 12 dB between the antenna and the receiver. The
degree of loss in a coaxial cable depends on the frequency of the signal passing through
it. Some common types of cable are shown below.
Dial-up modem
The receiver can make automated dial-out connections to an Internet service provider.
To set up the receiver to do this, select Network Configuration/PPP in the Web interface.
You can set up a streaming service, such as RT17/RT27 raw GNSS data, CMR, or RTCM
corrections over a serial port. When using a modem on the serial port, the modem
itself must perform the auto-answer function.
Radio modem
You can connect the receiver to an external radio through the Lemo ports or the 9-pin
serial port, whether or not the Ethernet port is in use. Trimble radios are supplied with
the required cables to connect to the Lemo ports. The receiver supports the following
Trimble base radios:
• TRIMMARK™ 3 ( firmware 1.26 or later)
• Trimble HPB450
• Trimble PDL450
To use an external radio with the receiver, you must have an external power source for
the radio. Use the configuration program for the external radio to configure it
separately.
To configure the receiver for RTK operation, do the following:
1. Enable the RTCM or CMR RTK corrector stream on the selected serial port.
2. Use the receiver front panel or the Web user interface to set the reference station
coordinates and broadcast ID.
5
Configuring the Receiver: Keypad
and Display 5
Button functions
Use the buttons on the front panel to turn on or turn off the receiver and to check or
change the receiver settings.
Power Turn on or turn off the receiver.
To turn off the receiver, hold down for two seconds.
Escape Return to the previous screen or cancel changes you make on a screen.
Enter Advance to the next screen or accept changes you make on a screen.
Down Move the cursor between multiple fields on a screen, or make changes.
Home screen
This is the main receiver screen. The receiver always returns to this screen if any other
screen is left idle for 60 seconds.
The Home screen shows:
• The number of satellites being tracked.
• The internal battery power remaining.
• The current operation mode.
• If the receiver is logging data. If logging is enabled, the operating mode field
shows Logging every three seconds.
As a power-saving feature, the front panel goes dark after a short period of inactivity .
If the display is not lit and the receiver is on, press to reactivate the display. If
required, you can disable this power-saving feature in the Web interface.
Status screens
To review the receiver's current settings in the status screens, press or in the
Home screen. The status screens show the following information:
• Position solution
• CMR and RTCM IDs
• Base name and code
• Latitude, longitude, and height
• Antenna type
• Antenna height and measurement point
• Receiver firmware version and date
• Receiver serial number
• Current IP address
• Current subnet mask
Setting the reference latitude, longitude, and height of the base station
In the Base Latitude screen:
1. Press to edit the reference latitude of the base station.
2. Press or to select the character to edit and then press or to
change it.
3. When finished, press .
4. Press to move to the next screen.
In the Base Longitude screen:
1. Press to edit the reference longitude of the base station.
2. Press or to select the character to edit and then press or to
change it.
3. When finished, press .
4. Press to move to the next screen.
In the Point Height screen:
1. Press to edit the ellipsoidal height of the base station.
2. Press or to select the character to edit and then press or to
change it.
3. When finished, press .
4. Press to move to the next screen.
Outputting corrections
1. Press to edit the name of the port that will output corrections.
2. Press or to select the port (1, 2, or 3).
3. When finished, press .
4. Press to select the Format field and then press to edit this field.
5. Press until the required format choics flashes
6. Press to move to the next screen.
Data logging
In the Logging screen:
1. Once you configure the output corrections, press to set up internal logging
on the receiver.
2. Press or to select the logging rate.
3. Press to accept.
4. Press to select files and then press to edit them.
5. Press or to select the appropriate length of time to log data for.
6. When finished, press .
7. Press to move to the next screen.
Outputting observations
In the RT27 screen:
1. Once you configure data logging, press to set up RT27 message output from
the receiver.
2. Press or to select the output port.
3. Press to accept.
4. Press to move the cursor to the output rate then press to edit it.
5. Press or to select the rate at which RT27 message will be output.
6
Configuring the Receiver: Other Than
Keypad and Display 6
c. Click Next.
6. From the Operation Selection screen, select Configure Ethernet settings and then
click Next:
Once the WinFlash utility connects to the receiver, the Ethernet Configuration
dialog appears:
2. If security is enabled on the receiver (by default, it is disabled), the web browser
prompts you to enter a username and password:
• Identity
Shows a list of unique receiver items, including the Ethernet MAC address and
the Bluetooth MAC address. It also lists variable items, including the current
Ethernet IP address and the firmware version:
• Receiver Options
Lists the installed options and limits of the receiver platform. In addition, this
page shows the current firmware warranty date and enables you to upload new
codes to the receiver so that you can enter new firmware warranty date codes
• Activity
Lists several important items to help you understand how the receiver is being
used and its current operating condition. Items include the identities of
currently tracked satellites, files being logged, data streams being input and
output, the receiver's internal temperature, how long the receiver has been
operational, power source voltages, and the state of the internal battery. With
this information, it is easy to tell exactly what functions the receiver is
performing:
• Position
Shows all relevant information about the receiver's position solution. If the
receiver is operating as a reference station, this information may be of minimal
concern. However, if the receiver is acting as a Rover Integrity Monitor, this
menu provides all the information needed to assess the quality of the receiver's
RTK position and therefore, the quality of network correctors:
• Position (Graph)
Graphically shows the receiver's position and fix status. These plots show the
values of Height, East, North, East/North, and PDOP/# SVs. The operator can
choose from 10-second or high-rate updates:
• Vector
Provides information on the vector between the NetR9 GNSS reference receiver
and its RTK reference station.
• Google Earth
Enables you to request a Google Earth position marker file for the reference
receiver position. You can easily import this KMZ file into Google Earth for that
software to show the receiver's location on a map or aerial view.
Satellites menu
Use the Satellites menu to view satellite tracking details and enable/disable GPS,
GLONASS, Galileo, and SBAS (WAAS/EGNOS/MSAS) satellites. These menus include
tabular and graphical displays to provide all required information on satellite tracking
status.
• General
Provides an overview of the satellite tracking status:
• Summary
Shows the files that are currently being stored, including their schedules, names,
whether they are using memory pooling, and in which directory they are stored:
– To create a new session, click New Session. The Data Logging Configuration
screen appears:
In this screen, you can set all logging parameters, and determine whether
the session files will be affected by the FTP Push, Email Push, and any
format conversions.
• Data Files
View, download, graph, and/or convert the files currently stored on the receiver:
– To download a file, double-click the file name or its icon and then follow
the standard procedures to complete the download.
– To select a group of files for download, select the check box to the right of
the required file names before double-clicking to start the download. To
select all files, click Select All.
– To delete files, select the check box to the right of all files to be deleted and
then click Delete Selected Files.
The following file naming options are available in the receiver:
• File Protection
Use this screen configure the protection of stored data files when an event signal
is received. This feature allows important data to be protected from the
standard memory pool automatic deletion function. The idea is that an event
input from an external sensor, such as a seismic detector, will protect data from
automatic deletion for a time period before and after the event, which ensures
that this data is available for later study:
To remove protected data from the system memory, you must manually delete
it.
• FTP Push
Use this screen to configure the receiver to push stored files to the FTP server of
your choice. Only files that are configured to use FTP push are transmitted:
• Summary
Gives an overview of the status of many of the important configuration items:
• Antenna
Use this screen to configure all of the items relating to the GNSS antenna. You
must enter the correct values for all antenna-related fields, as the choices you
make significantly affect the accuracy for logged data and broadcast RTK
correctors:
• Reference Station
Use this screen to configure settings such as the station coordinates and the
broadcast station identifiers. You must enter accurate information in these
fields, as this data significantly affects the accuracy of logged data files and
broadcast RTK correctors:
• Tracking
Use this screen to determine whether Everest™ technology and clock steering
are used. This screen also enables you to select which signals relating to
particular satellites are to be stored:
• Position
Use this screen to configure settings relating to using the receiver as a Rover
Integrity Monitor:
• General
Use this screen to:
– Determine whether event signals and an external frequency source will be
used.
– Choose to output a one-pulse-per-second signal (1 PPS).
– Disable the use of the internal battery as an uninterruptable power supply.
– Enable Power over Ethernet.
– Configure power on and shutdown voltages.
– Configure VFD settings.
• Application Files
Use this screen to configure all of the settings that make up an application file, to
save that file, and to select an application file for use:
• Reset
Use this screen to completely or partially reset the receiver:
• Default Language
Use this screen to select the language that the receiver uses when it starts:
You can use the receiver USB port to access the receiver in USB Device mode.
This enables you to cable your computer to the receiver and then browse the
receiver internal memory as an external USB device. USB drivers are available
from www.trimble.com.
• Bluetooth menu
Use this menu to configure Bluetooth settings. The following figure shows an
example of the screen that appears when you select Bluetooth/Info:
OmniSTAR menu
Use this menu to configure OmniSTAR settings.
The following figure shows an example of the screen that appears when you select
OmniSTAR/Summary:
The following figure shows an example of the screen that appears when you select
Network Configuration / Ethernet:
Security menu
Use this menu to configure the login accounts for all users who will be permitted to
configure the receiver through a web browser. Each account consists of a username,
password, and permissions. Administrators can use this feature to limit access to other
users. By default, security is disabled to make it easier to configure the receiver.
However, Trimble encourages administrators to enable security to avoid unwanted
changes. If security is enabled with anonymous access, it allows users to browse the
receiver settings but they cannot make changes.
The following figure shows an example of the screen that appears when you select
Security/Configuration:
Firmware menu
Use this menu to verify the current firmware and to load new firmware to the receiver.
You can upgrade firmware across a network or from a remote location without having
to connect to the receiver with a serial cable.
The following figure shows an example of the screen that appears when you select
Firmware:
7
Default Settings and Application
Files 7
Select Receiver Configuration/Application Files to access the required tools to use these
features. There are two variable fields:
• Filename: Enter a unique name for a stored configuration file.
• Operation: Select a particular operation from a drop-down list.
Operation Description
Start Now Applies the selected application file.
Enable Timer Determines at what time and date the receiver will automatically power-up (wake
up) and at what interval it will automatically power-up thereafter.
Operation Description
Generate Clone File Allows you to create a named xml file including the receiver configuration items of
your choice.
Install Clone File Tells the receiver to accept the clone file settings in a particular file.
Upload Clone File Allows you to move a clone file from your browsing computer to the target receiver.
Download Clone File Allows you to move a clone file from the receiver to your browsing computer.
Delete Clone File Allows you to delete a clone file stored on the receiver.
Upload&Install Clone Sends a clone file to the target receiver while telling the receiver to accept and apply
File these settings.
FTP
• FTP Server Enable switch
• FTP Server Port
• FTP Push Controls
- FTP Server Address
- Remote Directory (at server)
- Path Style
- Rename setting
You must enter the username and password.
NTP server
• External Time Servers
• NTP Port
• Enable switch
8
Specifications 8
General
Feature Specification
Keyboard and display Vacuum Fluorescent Display (VFD), 16 characters by 2 rows
Escape and Enter key for menu navigation
4 arrow keys (up, down, left, right) to scroll options and for data entry
Receiver type GNSS reference receiver
Antenna type Zephyr Geodetic Model 2 or Trimble GNSS Choke Ring antenna preferred.
Other models supported.
Physical
Feature Specification
Dimensions 26.5 cm x 13.0 cm x 5.5 cm (10.43 in x 5.12 in x 2.16 in)
Weight 1.75 kg (3.85 lb)
Temperature1
• Operating -40 °C to +65 °C (-40 °F to +149 °F)
• Storage -40 °C to +80 °C (-40 °F to +176 °F)
Humidity 100% condensing
Ingress protection Tested to IP67; waterproof for temporary immersion to a depth of 1 m (3.28 ft);
dustproof
Shock and vibration Designed to survive a 1 m (3.28 ft) drop onto a hard surface.
• Shock: non-operating Survival to 75 g, 6 mS
• Shock: operating Survival to 25 g, 10 msec, saw-tooth
• Vibration 10 Hz to 300 Hz 0.04 g2 / Hz; 300 Hz to 1000 Hz -6 dB/Octave
Tracking • Two advanced Trimble Maxwell™ 6 GNSS chipsets for a total of
440_channels
• Trimble EVEREST multipath signal rejection
• Trimble R-Track™ technology
• High precision multiple correlator for GNSS pseudorange measurements
• Unfiltered, unsmoothed pseudorange measurements data for low noise,
low multipath error, low time domain correlation and high dynamic
response
• Very low noise GNSS carrier phase measurements with <1 mm precision in a
1 Hz bandwidth
• Signal-to-noise ratios reported in dB-Hz
• Proven Trimble low elevation tracking technology
• Current satellite signals tracked simultaneously:
- GPS: L1 C/A, L2C, L2E (Trimble method for tracking L2P), L5
- GLONASS: L1 C/A and unencrypted P code, L2 C/A1 and unencrypted P
code
- Galileo GIOVE-A and GIOVE-B
- SBAS: L1 C/A, L5 supporting WAAS, EGNOS and MSAS
- L-Band OmniSTAR VBS, HP and XP
Feature Specification
Code Differential GNSS
Positioning2
• Horizontal 0.25 m + 1 ppm RMS
• Vertical 0.50 m + 1 ppm RMS
• WAAS differential Typically, <5 m 3DRMS
positioning3
Static GNSS Surveying2
Baseline <30 km
• Horizontal 3 mm + 0.1 ppm RMS
• Vertical 4 mm + 0.4 ppm RMS
Baseline >30 km
• Horizontal 4 mm + 0 ppm RMS
• Vertical 9 mm + 0 ppm RMS
Real Time Kinematic
Surveying2, 4
Single Baseline <30 km
• Horizontal 8 mm + 1 ppm RMS
• Vertical 15 mm + 1 ppm RMS
Networked RTK5
• Horizontal 8 mm + 0.5 ppm RMS
• Vertical 15 mm + 0.5 ppm RMS
Initialization time Typically <10 seconds
Initialization reliability Typically >99.9%
1. The internal battery will operate from -20 °C to +50 °C (-4 °F to +122 °F). The internal battery charger will
operate from 0 °C to 40 °C (32 °F to 104 °F).
2. Accuracy may be subject to degradation by multipath interference, obstructions, satellite geometry and
atmospheric conditions. Always follow recommended survey practices.
3. Depends on WAAS/EGNOS system performance.
4. NetR9 limited to 1,000 m RTK baseline length.
5. Networked RTK PPM values are referenced to the closest physical base station.
Electrical
Feature Specification
Power
Internal Integrated internal battery 7.4 V, 7800 mA-hr, Lithium-ion
Internal battery can operate as a UPS in the event of external power source outage
Internal battery will charge from external power source when input voltage is >12 V
or via Power over Ethernet supply
External Power input on Lemo 7P0S has a user-defined cut off threshold of 9.5 V or higher.
Power source supply (Internal / External) is hot swap capable in the event of power
source removal or cut-off
Power input on Lemo ports is 9.5 V DC to 28 V DC external power input with
over-voltage protection
Receiver will auto power on when connected to external power of a user-defined
voltage. The default value is 15 V.
Power over Ethernet Requires a Class 3 Ethernet power supply.
Power consumption 3.8 W nominal, dependent upon user settings.
Reference station Up to 15 hours.
operation time on
internal battery
Regulatory RoHS
China RoHS
FCC Part 15.247 FCC certifications
Class B Device FCC Part 15 and ICES-003 compliance
RSS-310 and RSS-210 Industry Canada compliance
CE mark compliance
C-Tick mark compliance
UN ST/SG/AC.10.11/Rev. 3, Amend. 1 (Li-Ion battery)
UN ST/SG/AC.10/27/Add. 2 (Li-Ion battery)
WEEE
Communication
Feature Specification
Communications
• Port 1 (D9 male) Full 9-wire RS-232
• Port 2 (OS 7P Lemo) 3-wire RS-232, 1PPS output, event input, DC power input
• Port 3 (USB) 5 pin Mini-B USB, operates in Device or Host modes
• RJ45 Jack Ethernet, PoE
• Bluetooth Fully integrated, fully sealed 2.4 GHz Bluetooth wireless technology.
Note – Bluetooth type approvals are country-specific. For more information, contact
your local Trimble office or representative.
Receiver position 1 Hz, 2 Hz, 5 Hz, 10 Hz, 20 Hz, and 50 Hz positioning
update rate
Data Input and Output CMR, CMR+™, CMRx, RTCM 2.1, 2.3, 2.3, 3.0, 3.1
Outputs NMEA, GSOF, RT17, RT27, BINEX
A
NMEA-0183 Output A
• Report max DQI=2 NMEA GGA string: When enabled, the Quality Indicator
field in the GGA output message will never be greater than 2 (Differential GPS).
Only to be used with legacy systems that do not fully support the NMEA
standard.
• Report max correction age 9 sec in NMEA GGA string: When enabled, the Age of
differential data field in the GGA message will never be greater than 9 sec. Only
to be used with legacy systems that do not fully support the NMEA standard.
• Report extended information in NMEA GGA and RMC strings: By default this
check box is enabled to provide high precision position data in the NMEA
messages. You should clear this check box to conform to the NMEA standard
message length of 82 characters. However, if you do, the precision of the position
and altitude data is reduced by truncating the number of decimal places.
Message values
NMEA messages that the receiver generates contains the following values.
Direction
Direction (north, south, east, or west) is represented by a single character: N, S, E, or W.
Time
Time values are presented in Universal Time Coordinated (UTC) and are represented
as hhmmss.cc, where:
• hh is hours, from 00 through 23
• mm is minutes
• ss is seconds
• cc is hundredths of seconds
NMEA messages
When NMEA-0183 output is enabled, the following messages can be generated.
Field Meaning
0 message ID $PPGPADV
1 Message sub-type 110
2 Latitude
3 Longitude
4 Ellipsoid height
6 Elevation of second satellite, in degrees, 90° maximum
7 Azimuth of second satellite, degrees from True North, 000° through 359°
8 The checksum data, always begins with *
$PGPPADV,120,21,76.82,68.51,29,20.66,317.47,28,52.38,276.81,22,42.26,198.96*5D
ADV subtype 120 message fields
Field Meaning
0 message ID $PPGPADV
1 Message sub-type 120
2 First SV PRN number
3 Elevation of first satellite, in degrees, 90° maximum
4 Azimuth of first satellite, degrees from True North, 000° through 359°
5 Second SV PRN number
6 Elevation of second satellite, in degrees, 90° maximum
7 Azimuth of second satellite, degrees from True North, 000° through 359°
8 The checksum data, always begins with *
Field Meaning
0 message ID $GPGGA
1 UTC of position fix
2 Latitude
3 Direction of latitude:
N: North
S: South
4 Longitude
5 Direction of longitude:
E: East
W: West
6 GPS Quality indicator:
0: Fix not valid
1: GPS fix
2: Differential GPS fix
4: Real Time Kinematic, fixed integers
5: Real Time Kinematic, float integers
7 Number of SVs in use, range from 00 through 12
8 HDOP
9 Orthometric height (MSL reference)
10 M: unit of measure for orthometric height is meters
11 Geoid separation
12 M: geoid separation is measured in meters
13 Age of differential GPS data record, Type 1 or Type 9. Null field when DGPS is
not used.
14 Reference station ID, ranging from 0000 through 1023. A null field when any
reference station ID is selected and no corrections are received.
15 The checksum data, always begins with *
Field Meaning
0 message ID $GPGSA
1 Mode 1, M = manual, A = automatic
2 Mode 2, Fix type, 1 = not available, 2 = 2D, 3 = 3D
3 PRN number, 01 through 32, of satellite used in solution, up to 12 transmitted
4 PDOP-Position dilution of precision, 0.5 through 99.9
5 HDOP-Horizontal dilution of precision, 0.5 through 99.9
6 VDOP-Vertical dilution of precision, 0.5 through 99.9
7 The checksum data, always begins with *
Field Meaning
0 message ID $GPGST
1 UTC of position fix
2 RMS value of the pseudorange residuals; includes carrier phase residuals during
periods of RTK(float) and RTK(fixed) processing
3 Error ellipse semi-major axis 1 sigma error, in meters
4 Error ellipse semi-minor axis 1 sigma error, in meters
5 Error ellipse orientation, degrees from true north
6 Latitude 1 sigma error, in meters
7 Longitude 1 sigma error, in meters
8 Height 1 sigma error, in meters
9 The checksum data, always begins with *
Field Meaning
0 message ID $GPGSV
1 Total number of messages of this type in this cycle
2 Message number
3 Total number of SVs visible
4 SV PRN number
5 Elevation, in degrees, 90° maximum
6 Azimuth, degrees from True North, 000° through 359°
7 SNR, 00–99 dB (null when not tracking)
8–11 Information about second SV, same format as fields 4 through 7
12–15 Information about third SV, same format as fields 4 through 7
16–19 Information about fourth SV, same format as fields 4 through 7
20 The checksum data, always begins with *
Field Meaning
0 message ID $GPHDT
1 Heading in degrees
2 T: Indicates heading relative to True North
3 The checksum data, always begins with *
PTNL,AVR
Time, Yaw, Tilt, Range for Moving Baseline RTK
The PTNL,AVR message string is shown below, with a description of the message
fields.
$PTNL,AVR,181059.6,+149.4688,Yaw,+0.0134,Tilt,,,60.191,3,2.5,6*00
Field Meaning
0 message ID $PTNL,AVR
1 UTC of vector fix
2 Yaw angle in degrees
3 Yaw
4 Tilt angle in degrees
5 Tilt
6 Reserved
7 Reserved
8 Range in meters
9 GPS quality indicator:
0: Fix not available or invalid
1: Autonomous GPS fix
2: Differential carrier phase solution RTK (Float)
3: Differential carrier phase solution RTK (Fix)
4: Differential code-based solution, DGPS
10 PDOP
11 Number of satellites used in solution
12 The checksum data, always begins with *
PTNL,GGK
Time, Position, Position Type, DOP
An example of the PTNL,GGK message string is shown below, with a description of the
message fields.
$PTNL,GGK,172814.00,071296,3723.46587704,N,12202.26957864,W,3,06,1.7,EHT-
6.777,M*48
Field Meaning
0 message ID $PTNL,GGA
1 UTC of position fix
2 Date
3 Latitude
4 Direction of latitude:
N: North
S: South
5 Longitude
Field Meaning
6 Direction of Longitude:
E: East
W: West
7 GPS Quality indicator:
0: Fix not available or invalid
1: Autonomous GPS fix
2: Differential, floating carrier phase integer-based solution, RTK(float)
3: Differential, fixed carrier phase integer-based solution, RTK(fixed)
4: Differential, code phase only solution (DGPS). Also, OmniSTAR XP/HP
converging
5: SBAS solution – WAAS, EGNOS
6: RTK Float 3D in a VRS/Network. Also OmniSTAR XP/HP converged
7: RTK Fixed 3D in a VRS/Network
8: RTK Float 2D in a VRS/Network
8 Number of satellites in fix
9 DOP of fix
10 Ellipsoidal height of fix
11 M: ellipsoidal height is measured in meters
12 The checksum data, always begins with *
Note – The PTNL,GGK message is longer than the NMEA-0183 standard of 80 characters.
PTNL,PJK
Local Coordinate Position Output
An example of the PTNL,PJK message string is shown below, with a description of the
message fields.
$PTNL,PJK,010717.00,081796,+732646.511,N,+1731051.091,E,1,05,2.7,EHT-
28.345,M*7C
Field Meaning
0 message ID $PTNL,PJK
1 UTC of position fix
2 Date
3 Northing, in meters
4 Direction of Northing will always be N (North)
5 Easting, in meters
6 Direction of Easting will always be E (East)
Field Meaning
7 GPS Quality indicator:
0: Fix not available or invalid
1: Autonomous GPS fix
2: Differential, floating carrier phase integer-based solution, RTK(float)
3: Differential, fixed carrier phase integer-based solution, RTK(fixed)
4: Differential, code phase only solution (DGPS). Also, OmniSTAR XP/HP
converging
5: SBAS solution – WAAS, EGNOS
6: RTK Float 3D in a VRS/Network. Also OmniSTAR XP/HP converged
7: RTK Fixed 3D in a VRS/Network
8: RTK Float 2D in a VRS/Network
8 Number of satellites in fix
9 DOP of fix
10 Ellipsoidal height of fix
11 M: ellipsoidal height is measured in meters
12 The checksum data, always begins with *
Note – The PTNL,PJK message is longer than the NMEA-0183 standard of 80 characters.
PTNL,VGK
Vector Information
An example of the PTNL,VGK message string is shown below, with a description of the
message fields.
$PTNL,VGK,160159.00,010997,-0000.161,00009.985,-0000.002,3,07,1,4,M*0B
Field Meaning
0 message ID $PTNL,VGK
1 UTC of vector in hhmmss.ss format
2 Date in mmddyy format
3 East component of vector, in meters
4 North component of vector, in meters
5 Up component of vector, in meters
6 GPS Quality indicator:
0: Fix not available or invalid
1: Autonomous GPS fix
2: Differential, floating carrier phase integer-based solution, RTK(float)
3: Differential, fixed carrier phase integer-based solution, RTK(fixed)
4: Differential, code phase only solution (DGPS). Also, OmniSTAR XP/HP
converging
5: SBAS solution – WAAS, EGNOS
6: RTK Float 3D in a VRS/Network. Also OmniSTAR XP/HP converged
7: RTK Fixed 3D in a VRS/Network
8: RTK Float 2D in a VRS/Network
7 Number of satellites if fix solution
8 DOP of fix
Field Meaning
9 M: Vector components are in meters
10 The checksum data, always begins with *
PTNL,VHD
Heading Information
An example of the PTNL,VHD message string is shown below, with a description of the
message fields.
$PTNL,VHD,030556.00,093098,187.718,-22.138,-76.929,-
5.015,0.033,0.006,3,07,2.4,M*22
Field Meaning
0 message ID $PTNL,VHD
1 UTC of position in hhmmss.ss format
2 Date in mmddyy format
3 Azimuth
4 ΔAzimuth/ΔTime
5 Vertical Angle
6 ΔVertical/ΔTime
7 Range
8 ΔRange/ΔTime
9 GPS Quality indicator:
0: Fix not available or invalid
1: Autonomous GPS fix
2: Differential, floating carrier phase integer-based solution, RTK(float)
3: Differential, fixed carrier phase integer-based solution, RTK(fixed)
4: Differential, code phase only solution (DGPS). Also, OmniSTAR XP/HP
converging
5: SBAS solution – WAAS, EGNOS
6: RTK Float 3D in a VRS/Network. Also OmniSTAR XP/HP converged
7: RTK Fixed 3D in a VRS/Network
8: RTK Float 2D in a VRS/Network
10 Number of satellites used in solution
11 PDOP
12 The checksum data, always begins with *
Field Meaning
0 message ID $GPRMC
1 UTC of position fix
Field Meaning
2 Status A=active or V=void
3 Latitude
4 Longitude
5 Speed over the ground in knots
6 Track angle in degrees (True)
7 Date
8 Magnetic variation in degrees
9 The checksum data, always begins with *
Field Meaning
0 message ID $GPROT
1 Rate of turn, degrees/minutes, "–" indicates bow turns to port
2 A: Valid data
V: Invalid data
3 The checksum data, always begins with *
VTG Speed Over Ground or Track Made Good and Speed Over Ground
An example of the VTG message string is shown below, with a description of the
message fields.
$GPVTG,,T,,M,0.00,N,0.00,K*4E
Field Meaning
0 message ID $GPVTG
1 Track made good (degrees true)
2 T: track made good is relative to true north
3 Track made good (degrees magnetic)
4 M: track made good is relative to magnetic north
5 Speed, in knots
6 N: speed is measured in knots
7 Speed over ground in kilometers/hour (kph)
8 K: speed over ground is measured in kph
9 The checksum data, always begins with *
ZDA UTC Day, Month, And Year, and Local Time Zone Offset
An example of the ZDA message string is shown below, with a description of the
message fields.
$GPZDA,172809,12,07,1996,00,00*45
Field Meaning
0 message ID $GPZDA
1 UTC
2 Day, ranging between 01 and 31
3 Month, ranging between 01 and 12
4 Year
5 Local time zone offset from GMT, ranging from 00 through ±13 hours
6 Local time zone offset from GMT, ranging from 00 through 59 minutes
7 The checksum data, always begins with *
Fields 5 and 6 together yield the total offset. For example, if field 5 is –5 and field 6 is
+15, local time is 5 hours and 15 minutes earlier than GMT.
B
Upgrading the Receiver Firmware B
C
Troubleshooting C
Receiver issues
This section describes some possible receiver issues, possible causes, and how to solve
them.
D
Programmatic Interface D
Overview
Programmatic commands are submitted to the GNSS receiver using the same TCP/IP
channels used by the GUI-browser interface. They both use the HTTP or HTTPS
protocol to submit CGI requests encoded in URLs. Response documents are then
returned to the remote computer using the same channels. The only differences
between GUI requests and Programmatic requests are the exact URLs used and the
types of responses returned.
Secure operations using the Programmatic Interface are available in two ways:
• The interface can be accessed through the HTTPS protocol, which encrypts all
transactions. This prevents anyone from observing the interactions. Note that
the commands can be accessed over the unencrypted HTTP port as well, which
is not encrypted.
• The second level of security is provided by the HTTP Security mechanism. All
programmatic commands are handled through the web server inside the GNSS
Receiver. This security has three levels:
State Access
Disabled Any user can execute any programmatic command.
Enabled A valid user account must be supplied with each Programmatic Interface request. The
capabilities for that account may limit the types of requests that the user can make.
Enabled With Many commands can be executed without providing a username and account. These
Anonymous Access would be primarily "show" commands that will not alter the configuration of the
system. The capabilities of the anonymous user can be customized to include file
download and file deletion. However, Programmatic Commands beyond that limited
scope are not allowed unless an authorized account name and password are used.
Note – By default, HTTP Security is not enabled. You must set Enabled or Enabled-With-
Anonymous-Access restrictions before accounts and passwords will be required for the
Programmatic Interface. See sample code later in this document for examples of how you
can encode your requests when a Security mode is enabled.
Variable Description
http: The protocol to use, either 'http:' or 'https:'
//NETR9-7332
The name or IP address of the GNSS receiver that is the target of the command.
or
Must be preceded by two slashes, '//'.
//10.1.150.72
/prog Indicator to the GNSS receiver web server that this is a programmatic request. This
triggers the command parser to interpret the command.
/enable The Verb. This is the action requested. Verbs can be one of:
• Show
• Set
• Reset
• Enable
• Disable
• Delete
• Download
• Upload
In this example, the Verb is 'enable'.
?session This is an Object type on which the action is to be performed. Objects can be:
• A state or characteristic of the system, such as the Serial Number.
• A function control, such as ElevationMask or data logging Session.
• A file object, like a logged data file, or a firmware file.
In this example, the Object is a data logging Session.
&name=HiRate A parameter that picks one of several objects, or describes characteristics that
qualify the command request.
In this sample, the 'name' parameter gives the name of the specific data logging
Session that is to be enabled.
Parameters are usually in the form paramname=value. Multiple parameters can be
given for a single command. They all must be separated by an ampersand (&).
As far as is possible, Verbs, Objects, parameter names, and parameter values are not
case sensitive. That is, you can use any combination of upper and lower case
characters, anywhere in the commands. The exceptions are items such as
SystemName, file names, session names, account names, passwords, and so on. These
exceptions are called out in the parameter descriptions for each command.
In such cases, the parameter listing in the command description shows the acceptable
formats.
Some parameters define an arbitrary string of characters that can include spaces,
ampersands, or other punctuation character. These characters may cause problems
when encoded in URLs. It is best to express them as "%xx" values, where 'xx' is the
hexadecimal equivalent of the ASCII character. Common values that need encoding
are:
Hex ASCII
%20 Space
%25 Percent (%)
%26 Ampersand (&)
%3F QuestionMark (?)
Most other characters do not require encoding but, if in doubt, you can do so.
Uploading files
A small number of commands are used to transfer a file from an external computer
into the GNSS receiver. These commands all use the verb Upload. The process for
uploading a file is more complex than a simple URL/CGI submission. Instead of an http
GET request, you use a POST request. Programming with Upload commands requires
special techniques. See the following examples in Using Curl, page 108, Using Perl,
page 109, and Firmware commands, page 113.
Responses to commands
Programmatic Interface requests trigger a response from the GNSS receiver. The
response is usually a plain-text ASCII document that is returned using the HTTP or
HTTPS protocol. The response can take one of several forms:
• Single line data response, page 105
• Multi-line data response, page 105
• Single line action response: OK, page 106
• A single line error message, page 106
• Binary file response, page 107
SerialNumber sn=1234A56789
Single-line responses can be arbitrary text, but most often they are similar to a Set
command format, showing an object name with parameters. For example, Show
GpsSatControls returns:
This string is exactly what you must be append to the Set verb, in order to restore the
controls to the current state.
<Show Sessions>
Note –
- A multi-line response may have zero lines of data inside the frame.
- There is no way of determining the length of the response other than counting lines until
the end-of-response line is found.
- Any command that can return a multi-line response will always do so, even if the
information could fit in a single line response.
Some commands allow partial parameter lists, and then use defaults for the
unspecified values. In these cases, the OK response always shows the complete list of
settings that the affected object now has.
In other cases the descriptive text shows an appropriate description of what action
was taken. For example:
Delete IoPort port=TcpPort5066
OK: IoPort TcpPort5066 is deleted.
Reset GnssData
OK: Clearing GnssData and restarting system.
Shw System
ERROR: Invalid verb 'Shw'
Show Serial
ERROR: Unknown command : 'show?serial'
Show SerialNumber
SerialNumber sn=60350239BF
One exception to this process is the case of uploading a file to the GNSS receiver.
Upload commands use a POST request instead of GET. For more information, see
Uploading files, page 104.
Using Curl
A simple method of testing out Programmatic commands is to manually feed the URLs
into Curl, a commonly available command line tool. Here is a sample Unix session that
shows the usage.
$ curl 'http://NetR9.Trimble.com/prog/show?serialNumber'
SerialNumber sn=60350239BF
$ curl 'http://NetR9.Trimble.com/prog/show?gpstime'
GpsTime gpsweek=1244 weekseconds=437597
$ curl 'http://NetR9.Trimble.com/prog/badcommand?abc'
ERROR: invalid verb 'badcommand'
$ curl 'http://NetR9.Trimble.com/prog/set?elevationmask&mask=10'
OK: ElevationMask mask=10
$ curl 'http://NetR9.Trimble.com/prog/show?position'
<Show Position>
GpsWeek 1244
WeekSeconds 498154.0
Latitude 37.3891271874 deg
Longitude -122.0368443968 deg
Altitude -4.898 meters
....
<end of Show Position>
You can assemble multiple Curl commands into a shell script to implement a basic
form of remote control.
If the GNSS receiver has security enabled, you need an account name and password to
use the programmatic interface commands. Curl accepts these in a '-u' command line
argument. For example:
$ curl -u admin:adminpw 'http://NetR9.trimble.com/prog/show?serialNumber'
SerialNumber sn=60350239BF
That submits the request, using account name 'admin' and password 'adminpw'.
Binary file downloads with Curl simply require directing the output to a file.
$ path=/Internal
$ name=60350239BF200906181935.T01
$ curl "http://NetR9/prog/download?file&path=$path/$name" > $name
$
File upload commands require Curl to format a POST request, with a binary
attachment. Curl implements this with a -F option:
$ f=/tmp/fina_V401.timg
$ curl 'http://NetR9/prog/upload?firmwareFile' -F firmwareFile=@$f
That command uploads a new firmware image file to the GNSS receiver, and triggers
an installation of the new firmware.
Using Perl
Perl is a powerful scripting language. The language comes with numerous library
packages that allow it to automate many complex tasks. It is also available on most
operating systems, which makes it good for cross-platform applications.
Perl can easily be used to control a GNSS receiver using the Programmatic Interface
commands. A simple method uses LWP—a library for web access in Perl. On a Linux
system, use man LWP for overview documentation. This is a powerful and complex
package, which cannot be documented here. Some sample programs show the basic
techniques needed. The first shows how to encode basic URL requests:
#!/usr/bin/perl -w
use strict;
use LWP::Simple;
print get( "http://fbtc/prog/show?systemname" ) ;
print get( "http://fbtc/prog/show?gpstime" ) ;
print get( "http://fbtc/prog/badCommand?abc" ) ;
print get( "http://fbtc/prog/set?elevationMask&mask=10" ) ;
print get( "http://fbtc/prog/show?position" ) ;
File downloads are more complex than just redirecting a get() request to a file, mainly
because the files can be arbitrarily large. A more complex syntax allows Perl to
download and put the results directly into a file.
#!/usr/bin/perl -w
use LWP::UserAgent;
my $f = '60350239BF200906181935.T01' ;
my $path = '/Internal' ;
my $ua = LWP::UserAgent->new ;
my $req = HTTP::Request->new(GET=>
"http://NetR9/prog/download?file&path=$path/$f" ) ;
my $res = $ua->request( $req, $f ) ;
When this is run, the logged file on the GNSS receiver is copied to an identically named
file in the local computer. No text comes to standard output.
File uploads use a similar technique.
#!/usr/bin/perl -w
use strict ;
use HTTP::Request::Common qw(POST) ;
use LWP::UserAgent ;
print "OKAY\n" ;
my $fname = '/tmp/fina_V401.timg' ;
my $ua = LWP::UserAgent->new ;
my $command = 'http://fbtc/prog/Upload?FirmwareFile' ;
my $response = $ua->request( POST( $command ,
Content_Type => 'form-data',
Content => [ 'firmwareFile'
=> [ $fname ]
]
)
);
print $response->content ;
Running that program produces
OK: Failsafe Firmware Installation Started.
Other techniques
You can use other methods to transmit the Programmatic Commands to the target
system. For example, you could write C or C++ programs to directly open socket
connections to the GNSS receiver and then directly transmit the requests over those
channels. This is moderately advanced programming and the details are beyond the
scope of this document.
Programmatic commands
Below is a complete list of the Action-Object commands accepted by the
programmatic interface. Click an individual command to go to the specific
information on that command.
• Status commands, page 111
• Satellite commands, page 111
• Configuration commands, page 112
• Input/Output commands, page 112
• Firmware commands, page 113
Status commands
All of these commands display some information from the GNSS receiver. The
information can be a static item, such as a serial number, or dynamic, such as the
current time or receiver position.
Command Description
Show SerialNumber Returns the Serial Number of this GNSS receiver.
Show UtcTime Returns the current UTC date and time.
Show GpsTime Returns the current GPS week number and time.
Show Position Returns the currently measured position and associated values.
Show Voltages Returns the voltages on all power or battery inputs.
Show Temperature Returns the internal temperature of the GNSS receiver.
Show Commands Returns a list of all supported commands.
Satellite commands
These commands are associated with satellite tracking and data.
Command Description
Show TrackingStatus Returns information on all tracked satellites.
Show Tracking Returns signal tracking settings.
Set Tracking Modifies signal tracking settings.
Show GpsSatControls Returns the Enable/Disable/IgnoreHealth settings for all GPS
satellites.values.
Set GpsSatControls Modifies the Enable/Disable/IgnoreHealth settings for GPS
satellites.
Show SbasSatControls Returns the Enable/Disable/IgnoreHealth settings for all SBAS
satellites.
Set SbasSatControls Modifies the Enable/Disable/IgnoreHealth settings for SBAS
satellites.
Show GlonassSatControls Returns the Enable/Disable/IgnoreHealth settings for all
GLONASS satellites.
Command Description
Set GlonassSatControls Modifies the Enable/Disable/IgnoreHealth settings for GLONASS
satellites.
Show Ephemeris Returns ephemeris data for a GNSS Satellite.
Show Almanac Returns the Almanac data for a GNSS satellite.
Show GpsHealth Returns the health status of all GPS satellites.
Show GpsUtcData Returns the UTC data decoded from GPS satellites.
Show GpsIonoData Returns the Ionospheric Model data decoded from GPS satellites.
Reset GnssData Clears all decoded GNSS Ephemeris and Almanac data.
Configuration commands
These commands show or modify the state of various of system functions:
Command Description
Reset System Restarts (reboots) the GNSS Receiver
Show ReferenceFrequency Returns the current source for the 10MHz reference clock.
Set ReferenceFrequency Modifies the source for the 10MHz reference clock.
Show ElevationMask Returns the current Elevation Mask control setting.
Set ElevationMask Modifies the Elevation Mask control setting.
Show PdopMask Returns the current PDOP Mask control setting.
Set PdopMask Modifies the PDOP Mask control setting.
Show ClockSteering Returns the current Clock Steering control setting.
Set ClockSteering Modifies the Clock Steering control setting.
Show MultipathReject Returns the current Multipath Rejection control setting.
Set MultipathReject Modifies the Multipath Rejection control setting.
Show PPS Returns the current settings of the Pulse-Per-Second controls.
Set PPS Modifies the settings of the Pulse-Per-Second controls.
Show AntennaTypes Returns a list of supported antenna types.
Show Antenna Clears Returns the current Antenna specifications.
Set Antenna Modifies the Antenna specifications
Input/Output commands
These sections show how Input/Output ports are configured to stream data, and so on:
Command Description
Show IoPorts Returns a list of all I/O ports and their settings
Show IoPort Returns the settings for a single I/O port.
Set IoPort Modifies the controls for an I/O port.
Delete IoPort Removes a TCP/IP port definition.
Show RefStation Returns the current Reference Station control settings.
Set RefStation Modifies the Reference Station control settings.
Command Description
PortParameters Port specification parameters.
StreamParameters Stream specification parameters.
Firmware commands
These commands are associated with updating firmware in the GNSS receiver.
Command Description
Show FirmwareVersion Returns the current running firmware version.
Show FirmwareWarranty Returns the firmware warranty date set in the receiver.
Set FirmwareWarranty Sends option code to update firmware warranty date.
Upload FirmwareFile Loads new firmware file to receiver
almanac A file that contains orbit information on all the satellites, clock corrections, and
atmospheric delay parameters. The almanac is transmitted by a GPS satellite to a GPS
receiver, where it facilitates rapid acquisition of GPS signals when you start collecting
data, or when you have lost track of satellites and are trying to regain GPS signals.
The orbit information is a subset of the emphemeris / ephemerides data.
base station Also called reference station. A base station in construction, is a receiver placed at a
known point on a jobsite that tracks the same satellites as an RTK rover, and provides
a real-time differential correction message stream through radio to the rover, to obtain
centimeter level positions on a continuous real-time basis. A base station can also be a
part of a virtual reference station network, or a location at which GPS observations are
collected over a period of time, for subsequent postprocessing to obtain the most
accurate position for the location.
BINEX BInary EXchange format. BINEX is an operational binary format standard for
GPS/GLONASS/SBAS research purposes. It has been designed to grow and allow
encapsulation of all (or most) of the information currently allowed for in a range of
other formats.
broadcast server An Internet server that manages authentication and password control for a network of
VRS servers, and relays VRS corrections from the VRS server that you select.
carrier A radio wave having at least one characteristic (such as frequency, amplitude, or phase)
that can be varied from a known reference value by modulation.
carrier frequency The frequency of the unmodulated fundamental output of a radio transmitter. The GPS
L1 carrier frequency is 1575.42 MHz.
carrier phase The time taken for the L1 or L2 carrier signal generated by the satellite to reach the
GPS receiver. Measuring the number of carrier waves between the satellite and receiver
is a very accurate method of calculating the distance between them.
cellular modems A wireless adaptor that connects a laptop computer to a cellular phone system for data
transfer. Cellular modems, which contain their own antennas, plug into a PC Card slot
or into the USB port of the computer and are available for a variety of wireless data
services such as GPRS.
CMR Compact Measurement Record. A real-time message format developed by Trimble for
CMR+ broadcasting corrections to other Trimble receivers. CMR is a more efficient
alternative to RTCM.
covariance The mean value.
datum Also called geodetic datum. A mathematical model designed to best fit the geoid,
defined by the relationship between an ellipsoid and, a point on the topographic
surface, established as the origin of the datum. World geodetic datums are typically
defined by the size and shape of an ellipsoid and the relationship between the center of
the ellipsoid and the center of the earth.
Because the earth is not a perfect ellipsoid, any single datum will provide a better
model in some locations than in others. Therefore, various datums have been
established to suit particular regions.
For example, maps in Europe are often based on the European datum of 1950 (ED-50).
Maps in the United States are often based on the North American datum of 1927
(NAD-27) or 1983 (NAD-83).
All GPS coordinates are based on the WGS-84 datum surface.
deep discharge Withdrawal of all electrical energy to the end-point voltage before the cell or battery is
recharged.
DGPS See real-time differential GPS.
differential Differential correction is the process of correcting GPS data collected on a rover with
correction data collected simultaneously at a base station. Because the base station is on a
known location, any errors in data collected at the base station can be measured, and
the necessary corrections applied to the rover data.
Differential correction can be done in real-time, or after the data has been collected by
postprocessing.
differential GPS See real-time differential GPS.
DOP Dilution of Precision. A measure of the quality of GPS positions, based on the geometry
of the satellites used to compute the positions. When satellites are widely spaced
relative to each other, the DOP value is lower, and position accuracy is greater. When
satellites are close together in the sky, the DOP is higher and GPS positions may
contain a greater level of error.
PDOP (Position DOP) indicates the three-dimensional geometry of the satellites. Other
DOP values include HDOP (Horizontal DOP) and VDOP (Vertical DOP), which
indicate the accuracy of horizontal measurements (latitude and longitude) and
vertical measurements respectively. PDOP is related to HDOP and VDOP as follows:
PDOP2 = HDOP2 + VDOP2
dual-frequency GPS A type of receiver that uses both L1 and L2 signals from GPS satellites. A
dual-frequency receiver can compute more precise position fixes over longer distances
and under more adverse conditions because it compensates for ionospheric delays.
EGNOS European Geostationary Navigation Overlay Service. A satellite-based augmentation
system (SBAS) that provides a free-to-air differential correction service for GPS.
EGNOS is the European equivalent of WAAS, which is available in the United States.
elevation mask The angle below which the receiver will not track satellites. Normally set to 10 degrees
to avoid interference problems caused by buildings and trees, and multipath errors.
ellipsoid An ellipsoid is the three-dimensional shape that is used as the basis for mathematically
modeling the earth’s surface. The ellipsoid is defined by the lengths of the minor and
major axes. The earth’s minor axis is the polar axis and the major axis is the equatorial
axis.
emphemeris / A list of predicted (accurate) positions or locations of satellites as a function of time. A
ephemerides set of numerical parameters that can be used to determine a satellite’s position.
Available as broadcast ephemeris or as postprocessed precise ephemeris.
epoch The measurement interval of a GPS receiver. The epoch varies according to the
measurement type: for real-time measurement it is set at one second; for
postprocessed measurement it can be set to a rate of between one second and one
minute. For example, if data is measured every 15 seconds, loading data using
30-second epochs means loading every alternate measurement.
feature A feature is a physical object or event that has a location in the real world, which you
want to collect position and/or descriptive information (attributes) about. Features
can be classified as surface or non-surface features, and again as points,
lines/breaklines, or boundaries/areas.
firmware The program inside the receiver that controls receiver operations and hardware.
GLONASS Global Orbiting Navigation Satellite System. GLONASS is a Soviet space-based
navigation system comparable to the American GPS system. The operational system
consists of 21 operational and 3 non-operational satellites in 3 orbit planes.
GNSS Global Navigation Satellite System.
GSOF General Serial Output Format. A Trimble proprietary message format.
HDOP Horizontal Dilution of Precision. HDOP is a DOP value that indicates the accuracy of
horizontal measurements. Other DOP values include VDOP (vertical DOP) and PDOP
(Position DOP).
Using a maximum HDOP is ideal for situations where vertical precision is not
particularly important, and your position yield would be decreased by the vertical
component of the PDOP ( for example, if you are collecting data under canopy).
L1 The primary L-band carrier used by GPS satellites to transmit satellite data.
L2 The secondary L-band carrier used by GPS satellites to transmit satellite data.
L5 The third L-band carrier used by GPS satellites to transmit satellite data. L5 will
provide a higher power level than the other carriers. As a result, acquiring and tracking
weak signals will be easier.
MSAS MTSAT Satellite-Based Augmentation System. A satellite-based augmentation system
(SBAS) that provides a free-to-air differential correction service for GPS. MSAS is the
Japanese equivalent of WAAS, which is available in the United States.
multi-frequency GPS A type of receiver that uses multiple carrier phase measurements (L1, L2, and L5) from
different satellite frequencies.
multipath Interference, similar to ghosts on a television screen, that occurs when GPS signals
arrive at an antenna having traversed different paths. The signal traversing the longer
path yields a larger pseudorange estimate and increases the error. Multiple paths can
arise from reflections off the ground or off structures near the antenna.
NMEA National Marine Electronics Association. NMEA 0183 defines the standard for
interfacing marine electronic navigational devices. This standard defines a number of
'strings' referred to as NMEA strings that contain navigational details such as positions.
Most Trimble GPS receivers can output positions as NMEA strings.
OmniSTAR The OmniSTAR HP/XP service allows the use of new generation dual-frequency
receivers with the OmniSTAR service. The HP/XP service does not rely on local
reference stations for its signal, but utilizes a global satellite monitoring network.
Additionally, while most current dual-frequency GPS systems are accurate to within a
meter or so, OmniSTAR with XP is accurate in 3D to better than 30 cm.
PDOP Position Dilution of Precision. PDOP is a DOP value that indicates the accuracy of
three-dimensional measurements. Other DOP values include VDOP (vertical DOP) and
HDOP (Horizontal Dilution of Precision).
Using a maximum PDOP value is ideal for situations where both vertical and
horizontal precision are important.
postprocessing Postprocessing is the processing of satellite data after it has been collected, in order to
eliminate error. This involves using computer software to compare data from the rover
with data collected at the base station.
real-time differential Also known as real-time differential correction or DGPS. Real-time differential GPS is the
GPS process of correcting GPS data as you collect it. Corrections are calculated at a base
station and then sent to the receiver through a radio link. As the rover receives the
position it applies the corrections to give you a very accurate position in the field.
Most real-time differential correction methods apply corrections to code phase
positions. RTK uses carrier phase measurements.
While DGPS is a generic term, its common interpretation is that it entails the use of
single-frequency code phase data sent from a GPS base station to a rover GPS receiver
to provide sub-meter position accuracy. The rover receiver can be at a long range
(greater than 100 kms (62 miles)) from the base station.
reference station See base station.
rover A rover is any mobile GPS receiver that is used to collect or update data in the field,
typically at an unknown location.
Roving mode Roving mode applies to the use of a rover receiver to collect data, stakeout, or control
earthmoving machinery in real time using RTK techniques.
RTCM Radio Technical Commission for Maritime Services. A commission established to
define a differential data link for the real-time differential correction of roving GPS
receivers. There are three versions of RTCM correction messages. All Trimble GPS
receivers use Version 2 protocol for single-frequency DGPS type corrections. Carrier
phase corrections are available on Version 2, or on the newer Version 3 RTCM protocol,
which is available on certain Trimble dual-frequency receivers. The Version 3 RTCM
protocol is more compact but is not as widely supported as Version 2.
RTK real-time kinematic. A real-time differential GPS method that uses carrier phase
measurements for greater accuracy.
SBAS Satellite-Based Augmentation System. SBAS is based on differential GPS, but applies to
wide area (WAAS/EGNOS and MSAS) networks of reference stations. Corrections and
additional information are broadcast via geostationary satellites.
signal-to-noise ratio SNR. The signal strength of a satellite is a measure of the information content of the
signal, relative to the signal’s noise. The typical SNR of a satellite at 30° elevation is
between 47 and 50 dBHz. The quality of a GPS position is degraded if the SNR of one or
more satellites in the constellation falls below 39.
skyplot The satellite skyplot confirms reception of a differentially corrected GPS signal and
displays the number of satellites tracked by the GPS receiver, as well as their relative
positions.
SNR See signal-to-noise ratio.
UTC Universal Time Coordinated. A time standard based on local solar mean time at the
Greenwich meridian.
VRS Virtual Reference Station. A VRS system consists of GNSS hardware, software, and
communication links. It uses data from a network of reference stations to provide
corrections to each rover that are more accurate than corrections from a single base
station.
To start using VRS corrections, the rover sends its position to the VRS server. The VRS
server uses the reference station data to model systematic errors (such as ionospheric
noise) at the rover position. It then sends RTCM or CMR correction messages back to
the rover.
WAAS Wide Area Augmentation System. WAAS was established by the Federal Aviation
Administration (FAA) for flight and approach navigation for civil aviation. WAAS
improves the accuracy and availability of the basic GPS signals over its coverage area,
which includes the continental United States and outlying parts of Canada and
Mexico.
The WAAS system provides correction data for visible satellites. Corrections are
computed from ground station observations and then uploaded to two geostationary
satellites. This data is then broadcast on the L1 frequency, and is tracked using a
channel on the GPS receiver, exactly like a GPS satellite.
Use WAAS when other correction sources are unavailable, to obtain greater accuracy
than autonomous positions. For more information on WAAS, refer to the FAA website
at http://gps.faa.gov.
The EGNOS service is the European equivalent and MSAS is the Japanese equivalent of
WAAS.
WGS-84 World Geodetic System 1984. Since January 1987, WGS-84 has superseded WGS-72 as
the datum used by GPS.
The WGS-84 datum is based on the ellipsoid of the same name.
www.trimble.com