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

Real-Time Output
Updating the current epoch position of reference station coordinates resulted in rover disconnects at 0:00 UTC. After applying this software update RTO clients will remain connected in case of this regular update process (daily, weekly, monthly or yearly).

Ephemeris Manager 
The Ephemeris Manager allows writing hourly or daily RINEX orbit data into specified folders. Having this feature enabled both the week number and the Ionospheric/Delta-UTC values in the RINEX file header now show values of the time in accordance to when the file has been written.

NMEA Decoder
The handling of NMEA strings in GGA format has been improved. If the time stamp comes with three decimal digits the NMEA sentence is still accepted as valid.

Trimble PivotTM Platform, version 3.1.6

GNSS Receiver 

This software update introduces changes in the geostationary BeiDou satellite signal decoding. It ensures the correct decoding of BeiDou observables of Trimble receivers having the latest firmware version 4.93 or later installed. 

Note:
If station data are exchanged via RTCM 3.2 MSM between different installations Trimble Pivot Platform needs to run on version 3.5.5 or later on both sides. Only this way geostationary BeiDou satellite signals can successfully be processed at the client side(s). 

Router/GNSS Receiver

The use of the “Dynamic port number” setting by Router and GNSS Receiver modules has been adjusted to accommodate the reload of a system configuration. Trimble Pivot Platform now verifies that all modules using this feature are properly reloaded. 

Real-Time Output

The setting “verbose logging” of an RTONet module has been reworked to display detailed information on network and station determination at the Status History view more effective. 

Ephemeris Manager

The optional feature of writing almanac data as almanac files has been reworked to the effect that a continuous storage is guaranteed. 

Network Processor
The Network Processor has been stabilized under conditions where the ionosphere activity is high. This means no station is excluded anymore from network processing because its position is mistakenly considered as inaccurate. 	
		
Reference Data Shop

The zipping mechanism of the Reference Data Shop in advance of an order delivery has been revised for a smoother workflow.  

Trimble PivotTM Platform, version 3.1.5

User Interface
The User Interface has been enhanced to reduce its response time and to run smoother on large systems consisting of several servers.

Trimble PivotTM Platform, version 3.1.4
RTO Net
The RTO Net module is now coming with an additional property setting that also allows accepting NMEA strings with 00:00:00 as time stamp.

RTO Net/ RTO Single Station/ RTO Multi Station
The message type 1013 of the RTCM 3.1 and RTCM 3.2 MSM real-time data format has been enhanced to include all system messages. In addition the output setting of message type 4094 is no longer dependent on other message types.

Storage
The file storage of Trimble Pivot Platform has been enhanced regarding DAT/TGD/T01/T02 files in combination with stations using the antenna types TRM29659.00 TCWD, JNSCR_C146-22-1 NONE and LEIAR25 NONE. These files are now being accepted by dependent functionalities like the Reference Data Shop as well.

Trimble PivotTM Platform, version 3.1.3
Trimble Ntrip Caster
The number of simultaneous Trimble Ntrip Caster (TNC) users might have reached its limit even with less connected users than available in the license due to multiple counting of connections. This potential issue has been fixed.

Trimble PivotTM Platform, version 3.1.2
GNSS Receiver
Improved handling of NULLANTENNA information for incoming RTXM3.x data streams. ADVNULLANTENNA, ADVNULLANTENNA NONE GPPNULLANTENNA AND GPPNULLANTENNA NONE will be handled equally and will all be accepted. 

RTK-Engine PP
Processing with post-processing VRS observation files might have introduced a height offset if the vrs file contained other antenna information than ADVNULLANTENNA. Antenna information will now be applied accordingly. 

Trimble Pivot Web / Accounting 
The handling of expiration dates of subscriptions has been improved. Expiration dates might have not been set correctly if a contract of a follow-up subscription has been changed. 

Post Processing Engine
Improved handling of zipped observations files in Post Processing Engine. Potential issues regarding duplicate files in scan folders, handling of station IDs higher than 1024 and the file scanning process have been fixed.

RTO Net
A registry setting might have created a misinterpretation of weighting values, depending on regional Windows settings. This issue would have resulted in an inability to load RTO Net modules. It has been fixed.

Trimble PivotTM Platform, version 3.1.1
RTO (Single Station)
Nullantenna output in RTCM 3.2 format has caused a height offset in TPP version 3.1. This issue has been fixed. 

RTCM 3.2 MSM 
Improved handling of RTCM 3.2 messages 6 and 7 throughout all modules that create respective RTCM messages or make use of them. 

Atmosphere Watch
Surface met data
Improved handling of "Surface met data model" when being selected as weather model type. 
Network Processor Storage
Typing error in Network Processor Storage has been corrected. File type name is now corrected to "GRIB".
Header information issue for elevation and azimuth angles in network processor storage in Atmosphere Watch module has been fixed. 

GNSS Receiver
The Leica GR25 receiver has been referred to a wrong receiver noise model in TPP version 3.1. This issue has been fixed.

RTK Engine PP 
Antenna height handling
The antenna height is being reduced from antenna phase center to antenna reference point before being processed in the processing engines. The RTK Engine PP did not apply this reduction in TPP version 3.1. This issue has been resolved. 
Rover Integrity support
Improved handling of large RTK PP processing sessions when RTK Engine PP is being used in Rover Integrity. Large session might have created a conflict with Rover Integrity data base. This potential conflict from version 3.1 has been fixed.