Trimble PivotTM Platform, version 4.3.2
July 2020
This software update for Trimble® Pivot™ Platform (TPP) contains all changes since the release of version 4.3. The following document gives you an overview of the changes.

Trimble Ntrip Caster / Accounting 
Various software code and accounting database (DB) have been implemented to improve the handling of a large number of simultaneous users. These changes and enhancements include improved handling of accounting calls for correction data output, PBS info updates in iScope live, minimization of AccountingLogging, improvements regarding indices to the Accounting DB and improved emergency access handling.
All these updates will extend the upper end of simultaneous user support. 
Please note: 
The highest available number of simultaneous users in a Trimble Pivot Platform environment highly depends on - besides sufficient software licenses - various factors like server specifications and IT communication bandwidth. 

Trimble Online Processing
The TPP Online Post Processing status messages and report might have shown the use of broadcast ephemeris for processing, although precise orbits were used (if available). This issue has been corrected, the use of precise orbits will be shown in status messages and reports if they were used for processing. 

RINEX Storage
RINEX storage (any RINEX format type) used to show incorrect Doppler values if stored from a Leica GR30/50 or Septentrio PolaRx4/5 receiver. This issue has been fixed.
Please note: Doppler values stored from Trimble receivers were not affected. 

Network/RTXNet Processor
TPP did not process QZSS satellites from non-Trimble receivers if QZSS L2C frequency type was set to L2C CM or L2C CL. This issue has been resolved, TPP can process QZSS from non-Trimble receivers with frequency type L2C CM, CL and CM+CL.
Please note:
QZSS L2C CM+CL processing requires sufficient data availability on the CBC Server. Calculation of respective values has started, full availability might take a few days after release of this patch though.

Real-Time Output
1)	Geofence regions caching has been changed with the release of Trimble Pivot Platform 4.3. Regions are being cached in the Real-Time Output (RTO) module instead of the DBServer since that release. However, until this software update, RTO’s with regions did not allow new users if DBServer became unavailable if more than one source has been available. This issue has been fixed. Region caching and RTO availability is independent from DBServer availability. 
2)	Glonass processing might have been reduced in the very rare event of too large residual interpolation results for Glonass satellites, even though tracked data was sufficient for processing. This potential behavior has been corrected, Glonass satellites will be processed and solved if sufficient data is available. 
3)	RTO output might have experienced delay in outputting correction data in times with a large number of users connected (depends on individual system and IT setup, typically refers to numbers larger than 1000 simultaneous users) and while DB Cleaner is running. The performance of the RTO output and respective database handling has been improved in order to avoid output delays.  

Reference Data Shop
Submitting an order for two or more separate VRS positions, but for the same time period, could have resulted in creating only one of the two VRS files. This potential issue has been fixed. 

Storage Integrity
In very rare events, Storage Integrity might not have downloaded missing epochs at the beginning of a new storage interval. This issue has been fixed.

Trimble PivotTM Platform, version 4.3.1
Trimble Pivot Platform 4.3 Release Notes Update
Trimble RTX Clocks and Orbits bridging has been introduced with Trimble Pivot Platform version 4.3 in August 2019 (see Trimble Pivot Platform version 4.3 release notes). 
It has been mentioned that “Full-GNSS corrections will remain available for up to one hour”. While this statement remains true for GPS, Galileo, BeiDou and QZSS corrections, please note that Glonass corrections would not be available anymore after 30 minutes. Glonass sends new ephemeris information every 30 minutes which will make old ephemeris not usable anymore while other constellations will be bridged for 60 minutes.

Network Processor
The number of fixed satellites in the Network Processor might have decreased to zero over time in network setups with RTCM input data and inconsistent settings for GPS L2 frequency observations. This issue has been fixed. 
Please note: The RTXNet Processor has not been affected by this issue.

Real-Time Output
1)	RTCM message 1033 will be output by default and will not be optional any longer. The property will allow to output either 1033 only or with a respective antenna descriptor (RTCM message 1007 or 1008). This is needed in order to send the physical base station’s firmware version for optimized QZSS L2C phase adjustment handling with RTCM output.  
2)	For optimized QZSS L2C phase adjustment handling, Trimble Pivot Platform version 4.3.1 will include a check on the physical base stations’ firmware version. With Trimble reference stations operating on firmware lower than version 5.43, QZSS corrections will not be sent out. 

Please note: 
-	This applies only to RTCM corrections. CMRx corrections will include QZSS, independently from the reference station’s firmware version. 
-	No implications or firmware version requirements for non-Trimble reference station receivers. 

RINEX Storage
1)	Updating the QZSS L2C phase adjustment handling in the observations, records and header info in order to comply with the RINEX standard. 

Please note: 
-	It is recommended to disable QZSS processing in Trimble Pivot Platform’s post-processing engines if it includes RINEX files that were stored with versions older than 4.3.1.
-	No restrictions for processing with T02 files.

2)	RINEX long name files being created by Trimble Pivot Platform contained the epoch rate in the file name for observation files as well as for navigation files. The file naming for the navigation file will be changed to the more commonly used nomenclature which does not contain the epoch rate. 

Example:	
-	Old (until Pivot 4.3): ZAPR0123_S_20191120000_01D_30S_CN.rnx
-	New (Pivot 4.3.1 onwards): ZAPR0123_S_20191120000_01D_CN.rnx (please note: does not longer contain “30S_” in the file name.

Please note:
1)	Reference Data Shop, Post-Processing Engines, Trimble Online Processing and storage zipping will work with files according to the new naming nomenclature only. 
2)	In case you need to convert to the previously used nomenclature, please contact our Technical Support Team (rtns_support@trimble.com) for receiving a script that can convert from new to old nomenclature.

Trimble Ntrip Caster 
Ntrip client info strings can be more than 100 characters long. However, iScope Live does not allow strings longer than 100 characters and would have created exceptions in previous versions. With this update, strings longer than 100 characters will be cut for the use in iScope Live and will become usable.