This software update for Trimble® Pivot™ Platform (TPP) contains all changes since the release of version 3.8.0. The following document gives you an overview of the changes. For any questions please contact Trimble Advanced Positioning Support using the known phone numbers or email email@example.com.
3D Interpolation is an option for the RTO Net module that makes use of a new modelling method for tropospheric delays. It significantly improves the vertical component for rover positioning where the rover height is very different compared to the height of the surrounding reference stations. We have identified that the 3D Interpolation option might result in poor rover fixing performance caused by an insufficient number of satellites in the correction data stream if (both must apply):
The activation of 3D Interpolation is recommended in environments with height differences between reference stations and rovers of 500 meters or more. However, an effective interpolation can be derived only if reference stations are located on high and low elevation. Extrapolation can work seamlessly if height differences between reference stations and rovers are 500 meters or more and if the rover’s vertical position is close to the highest or lowest surrounding reference station.
In previous versions 3D Interpolation was automatically enabled for all RTONet modules by default. With this patch we change the default setting so that 3D Interpolation is disabled for all new RTONet configurations. Existing configurations are not changed and we still recommend to disabling 3D Interpolation.
Dynamic Station Coordinates
The “Dynamic Station Coordinates (DSC) approach” uses “Trimble RTX™” technology to compute the so-called “Dynamic Station Coordinates” for each reference station. These coordinates are dynamically re-computed and updated to best fit the reference stations’ position. DSC is designed to automatically avoid the influence of biased position information during Network-RTK positioning.
With the Dynamic Station Coordinates (DSC) approach, local coordinates are not used to initialize the network processor. Reference Station Coordinates in ITRF2008 Current Epoch are directly estimated by using GNSS data with Trimble RTX™ technology. For each epoch, the internally computed RTX position is fed into two Kalman filters, one configured to expect no movement (static) and the other for sudden movement. The static filter outputs the highest accuracy position, but has a substantial reaction delay to position changes. The sudden movement filter has a fair accuracy and reaction time to movement. By comparing the position from the static and sudden movement filters, unexpected movements of the station can be determined. Converged position information from the static filter will only be forwarded into the processors. In case of movement detection, no data from the affected station will be processed until the accuracy of the position is below the default thresholds
It has been identified that the sudden movement filter in DSC might falsely flag CORS data as compromised and remove the data from the processors when thresholds are passed even with non-moving CORS.
Consequently, the thresholds for the allowable differences between the static and sudden movement filter are significantly increased. This allows the system to estimate and use high accurate coordinates based on the static filter even in areas with tectonic movement ensuring correction data with the highest quality. The system continues to disable stations in the processors if significant sudden movement is detected. In the event of movement below the defined threshold the static filter converges to the new position with some delay.
Trimble PivotTM Platform, version 3.8.3
New Support Bulletins
Please see the newly created Support Note section on the Trimble web page <http://www.trimble.com/Infrastructure/Trimble-Pivot-Platform.aspx> (Product Resources -> Support Note) for two new support bulletins that might provide you with useful information in respect to the operation of Trimble Pivot Platform. The topics are:
- Reducing CPU load
- Google maps support (for sensor map in Trimble Pivot Web)
Assignment to sub network
If a network consists of two or more sub networks, a rover will be assigned to one or the other sub network based upon a quality indicator for each sub network and the distance of the rover to the sub networks. The processing of the quality indicator in conjunction with the distance to the sub networks has been improved in order to avoid faulty rover assignments.
RTO status message output
In case of CMRx output, CMRx encoding messages might have been output in the RTO status history view as error messages, even though CMRx messages output worked seamlessly. Such potential and misleading output has been stopped.
Ntrip Version 2.0 standard introduces Server and Client authentication with Transport Level Security (TLS; its predecessor known as Secure Socket Layer, SSL). The Trimble Ntrip Caster module offers the use of SSL/TLS connections. SSL/TLS transmits data that can be encrypted and therefore is more secure as it cannot be read or manipulated during transmission. Moreover, the Ntrip Server provides a certificate to the clients that ensures its identity.
This software update introduces the possibility of using Ntrip Server and Client authentication with SSL/TLS for:
- Setting up an Ntrip Caster for SSL/TLS security and server authentication.
- Setting up an Ntrip Caster for SSL/TLS security with respect to client authentication.
- Setting up a mountpoint on the Ntrip Caster for SSL/TLS security and server with respect to the connection to data sources.
- Setting up the data source for SSL/TLS security and authentication.
A new option is available in the Ntrip Caster settings that will enable authentication and allow the selection of a respective certificate.
The firmware version information of Trimble reference station receivers with firmware version 5.10 might have been misinterpreted as version 5.1. This misinterpretation might have caused unnecessary and disruptive CPU load peaks as well as multiple entries of the "last modification time" of the station properties. This issue has been fixed.
The number of processed Glonass satellites might have decreased for some stations during course of a few days and would not be at full performance until the network processor has been re-initialized. This behavior might have occurred in case a station sent reduced number of Glonass observations. The network processer then missed to process all observations once they were available again. This issue has been fixed.
Loading Pivot with a very large number of modules (e.g. 750 and more modules per Pivot instance) might have caused an exception error message. The effect would have been that Pivot has not been completely loaded. This potential bottleneck has been removed and Pivot can now load a significantly larger number of modules during start-up routine.
The event time of an alarm in the history view had an offset of 17 seconds compared to the actual time of the event (based on UTC time). This offset has been resolved; event time of alarms is now UTC time.
Trimble Pivot Web 2
It has not been possible to create subscriptions if the respective organization name started with a "0" (zero). This issue has been fixed.
The automated patch mechanism will update the respective files for Trimble Pivot Web 2 if Trimble Pivot Web 2 runs on the same computer as where Trimble Service Administrator is running. In case Trimble Pivot 2 runs on a separate computer, please copy manually the following file:
Copy NewSubscriptionController.js from the in the 3.8.3 software update files (found in: \TPP-Update-3.8.3\CustomPatchFolder_AdminWeb\Plugins\Accounts\Scripts\app\controllers\Subscriptions) to:
<Pivot Web 2 Root>\Plugins\Accounts\Scripts\app\controllers\Subscriptions\
Trimble PivotTM Platform, version 3.8.2
Correction data output in CMRx format might have resulted in not letting rovers to fix. This issue exists in versions 3.8 and 3.8.1 (not in versions 3.5.8 and lower). This issue has been fixed with the software update 3.8.2.
Trimble PivotTM Platform, version 3.8.1
Network processing of QZSS signals failed in previous versions if BINEX was being used as GNSS observation data input format. This issue has been fixed.
The network processor's status view might have indicated a performance percentage higher than 100% (number of processed satellites in relation to number of solved satellites) while the number of solved satellites cannot be higher than the number of processed satellites. This potential issue has been fixed.
In the unlikely event that the computation of local transformation parameters fails, transformation messages with values set to zero were sent out without further notification in previous versions. This software update introduces error messages in the Trimble Pivot Platform status view in case no transformation parameters can be provided while the user will be disconnected from the RTO (in case of RTO Net and multi-station RTO; in case of single-station RTO, the data stream will be stopped).
Trimble Ntrip Caster
0 bytes connections
Ntrip connections might hold connections with no data being sent without clearing these connections. This behavior could have resulted in a license limit exceeds or might have forced the Ntrip Caster to stop working. This potential issue has been resolved.
Mounpoint format data
Trimble Ntrip Caster allows the creation of new mointpoints by copying existing mountpoints (parent). When using a copied mountpoint (child) and if the data format settings of the child get changed, the parent's data format settings get changed as well unintentionally, and vice-versa. This issue has been fixed.
When using RTCM 3.2 MSM as GNSS observation data input format in Trimble Pivot Platform version 3.8, stored RINEX files have showed unrealistically high numbers of cycle slips. This issue has been resolved with this software update.
The output of correction data in RTO Net with CMR+ format might have stopped and showed an error message in the status messages view in Trimble Pivot Platform version 3.8.0. This software update fixes this potential issue.
Moving a large number of modules from one container to another might have resulted in no progress of the "Moving Modules" dialogue and in an unresponsive Trimble Pivot Platform User Interface. These potential issues have been resolved. A "Cancel" button has been added to the "Moving Modules" dialogue and the number of moved modules will be indicated.
Improved handling of CMRx input data.
TCP/IP communication to Trimble NetRx GNSS receivers allows using IP authentication. The authentication password requires at least 7 characters. This requirement will be shown as information in the module information section with this software update. Once, a password of at least seven characters is set in Trimble Pivot Platform, the receiver connects as soon as the receiver's properties are adapted to the new password.