GNSS Receiver Properties - Receiver Data

When you add the GNSS Receiver module, the GNSS Receiver Properties dialog appears with this tab.

If you select the module in the Tree view after you have added the module, the categories and settings of this tab appear in the Properties view.

Use the Receiver Data categories and settings to view and select the tracking settings.

Receiver Control category

Note – Depending on the connection type established between Trimble 4D Control Server and the receiver, the settings of the Receiver Control category control the receiver (if a bi-directional connection is established) or not (GNSS Receiver module in passive mode). In the latter case, the values displayed here are only used for data filtering in the system.

The Receiver Control category lets you set a basic elevation cutoff angle in degrees (Elevation cutoff, default: 5 degrees) and a tracking interval (Tracking interval, default: 1Hz, selectable values are between 10 minutes and up to 20 Hz, depending on the selected receiver type). Based on these two settings, the GNSS Receiver module filters the data and passes the filtered data on to its depending modules, even if the receiver provides observations with lower elevation or higher tracking rate.

In contrast to the Elevation cutoff and Tracking interval settings, the settings of Azimuth dependent cutoff property will only be used for realtime processing. They will not be applied when receiver data is stored to data files for post processing. The Azimuth dependent cutoff property displays whether azimuth-dependent elevation cutoffs have been set or not. To view or change the details of the cutoff settings, set the focus onto the Azimuth dependent cutoff value field and click the browse button. This opens the Azimuth Dependent Elevation Cutoff dialog with the current settings for elevation cutoffs. Per default, no such cutoff is set.

More settings are available in the Remote Access and Advanced sub-categories.

Remote Access sub-category

For controlling a receiver directly (for example, to connect to the receiver's Web UI or to perform a receiver firmware update), Trimble 4D Control Server must know its address and credentials. Use the Remote Access sub-category to provide both.

The Receiver name is the host name or IP address of the receiver itself. If the receiver is directly connected to Trimble 4D Control Server using the TCP/IP Client connection, that is without any intermediate router, this address is identical to the Server name in the Connection settings. In other cases, the address may be different. The HTTP port is set to 80 per default, but a different HTTP port can be set.

Modern Trimble network receiver types (for example, NetR3, NetR9) support firmware update by remote access from the Trimble 4D Control Server system. Only for these receiver types, the User name and Password properties are available. Use them to set the access credentials for the receiver.

Tip - The receiver firmware update is started from the Device Manager Firmware Update module-view.

Advanced sub-category

Newer reference station receivers provide many advanced settings for internal receiver configuration, such as carrier phase smoothing of the raw observation data or the observation of the new civil signal on the L2 carrier phase, L2C. With active connections, you can configure these settings in the Trimble receiver by external commands from the Advanced category.

• Using the Active - waiting for response communication mode type (in combination with the Alarm Manager module), Trimble 4D Control Server administrators have full control on the receiver reaction. If the connected receiver does not acknowledge the settings, the GNSS Receiver module will issue a warning message (see the Status Messages view). If the receiver does not respond at all, the communication mode will additionally be set to Active - "fire and forget" .
• With the Active - "fire and forget" communication mode type, the GNSS Receiver module will not know whether the receiver has acknowledged the command and has changed its settings accordingly.

With passive connections, configuring the receiver is not possible. Therefore, some of the advanced settings will not be available for those connections.

The system passes the improved observations on to the depending modules, such as the data storage modules or the Processing Engines.

Note - Make sure to configure all receivers in your system to comply with the frequency and tracking types you have specified using the System Properties. If the receiver is configured to send a different observation than that one expected, the observation will not be used for processing.

Phase smoothing: Enables carrier phase smoothing at the receiver, if set to Yes. By default: not enabled (No).

Note - Phase smoothing cannot be enabled with tracking intervals higher than 1 Hz.

Clock steering: As the internal time at the receiver is not perfectly stable with respect to the GPS time standard, this drifting effect will cause receiver time and GPS time to slowly diverge. Trimble receivers such as the NetRS and later can compensate for this drift by periodically re-synchronizing the receiver time with GPS time using the estimated receiver clock offset. This periodic resynchronization is referred to as clock steering. To enable clock steering, make sure the Enable Clock Steering setting is set to Yes / Enabled (default).

L2 tracking: Use the setting to view or select the tracking mode on the L2 frequency. For available L2 tracking modes see the following table. For Trimble receivers not supporting one or several of these tracking modes, these are not displayed for selection.

L2C code: The L2C code selection applies for the civil signal on L2: With CM / CL, the default selection, the receiver tracks both the Moderate length code (CM) and the Long length code (CL); to track only the Long length code, select CL.

Enable L5: Only available for receivers capable of tracking the new L5 signal. If set to Yes (default selection), the additional L5 code setting lets you select the code to be tracked. To disable L5 tracking and usage, select No.

L5 code: Specifies the code tracked on L5, one of IQ (combination of I and Q), I (I code), or Q (Q code)."

Note - With an active connection the Enable L5 setting commands the receiver to track or track not the L5 frequency. With a passive connection, L5 data arriving at the GNSS Receiver module will be rejected, if Enable L5 is set to No. However, if Enable L5 is set to Yes for a passive connection, any L5 code arriving will be accepted and used.

Note for the Trimble receivers previous to the NetR9 receiver - These receiver types can track only two of the three frequencies L2C, L2 Legacy and L5. Therefore, to use the L2C and Legacy combination, you should set the Enable L5 setting to No. If one wants to use L5, one should select L2 Legacy as L2 tracking setting. Trimble NetR9 and later receivers do not have this limitation.

GLONASS tracking: Lets you select which code to track for GLONASS or if to track GLONASS not at all (Disable). To only track the CA code on the first GLONASS frequency, select CA, to track both CA and P keep the default selection CA and P. If GLONASS tracking is not disabled, the second GLONASS frequency is tracked anyway.

Enable Galileo: Only available for receivers capable of tracking Galileo satellites. By default, set toYes . To disable Galileo tracking and usage, select No.

Note - Observations from tracked Galileo satellites will currently not be forwarded to the Synchronizer modules. They will be written, however, into storage files, such as RINEX v3 files.

Enable SBAS: SBAS satellites (such as WAAS, or EGNOS satellites) augment the GNSS systems for accuracy, reliability, and availability. If Enable SBAS is set to Yes, the receiver tracks signals sent by SBAS satellites and passes their correction messages into the system. The Satellite Tracking, Skyplot, Receiving Info, and Raw Data Analysis views will show the results for these satellites. If data storage is enabled, the raw data of these satellites will be stored, too, into RINEX v3 files with the extension .??b. Default value: No.

Enable QZSS: Only available for receivers capable of tracking the QZSS (Quazi Zenith Satellite System) satellites. If set to Yes (default selection), receiver tracks signals sent by QZSS satellites and passes the observations into the system. The Satellite Tracking, Skyplot, Receiving Info, and Raw Data Analysis views will show the results for these satellites. If data storage is enabled, the raw data of these satellites will be stored, too, into T01, T02, TGD, and RINEX v3 files. To disable QZSS tracking and usage, select No.

Enable BeiDou: Only available for receivers capable of tracking the Chinese BeiDou satellites. If set to Yes (default selection), the receiver tracks signals sent by BeiDou satellites and passes their correction messages into the system. The Satellite Tracking, Skyplot, and Receiving Info views will show the results for these satellites. If data storage is enabled, the raw data of these satellites will be stored, too, into T01, T02, TGD, and RINEX v3 files. To disable BeiDou tracking and usage, select No.

Receiver Internal RTX sub-category

Newer reference station receivers provide the option to internally process their corrected position by connecting to Trimble CenterPoint™ RTX™, the Trimble server of corrected orbit and clock values. With active connections, you can configure the Trimble receiver to use internal RTX positioning by external commands available with the Receiver Internal RTX sub-category.

Note - The communication mode status influences the receiver behavior in the same way as it does for the settings of the Advanced sub-category.

With passive connections, configuring the receiver is not possible. Therefore, the Receiver Internal RTX sub-category of settings will not be available for those connections.

Control receiver internal RTX: Specifies, whether or not the GNSS Receiver module controls the instrument with respect to its internal RTX processing capabilities. If set to Yes, the receiver is controlled externally and additional settings become available. By default: not enabled (No).

Connect receiver to Centerpoint RTX: Only available, if the Control receiver internal RTX property is set to Yes. When you set this property to Yes, it commands the receiver to start an internal, pre-defined NtripClient connection to the Trimble Global data server, which provides the corrected data for RTX processing.

Note - Using the Web UI of the receiver one can specify additional settings with respect to its internal RTX processing.