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

RTO
•	RTCM Message #5 was being encoded incorrectly if it contained satellite 32. Its ID was not encoded as 0 which is now fixed to fully meet the RTCM standard. Certain rovers could possibly not fully decode this message.
•	RTCM Messages #5 and #43 contained as C/N (carrier-to-noise ratio) values those of the L2 frequency instead of the L1 frequency.
•	The PRC (pseudo-range correction) values in RTCM correction messages could possibly “drift” away for GLONASS if letting the system run for a long time, like for multiple months. Eventually this could have the effect of the values getting too big and thus getting outside the valid range in the RTCM message, leading to satellites being dropped in the DGNSS position calculation.

DGNSS Engine
The Raven demodulator was reset when the DGNSS Engine did not receive RTCM correction data within a specific time. This could occur for example when bigger RTCM messages like the #5 or the #7 were transmitted or multiple non-correction messages were scheduled to be sent out at the same time. The effect of the issue was that the displayed signal strength would temporarily go to 0 while the message error ratio would go up for a few seconds and the DGNSS position could have a jump or a small data gap.

Beacon RS/IM
•	Several properties could not be modified from TCC and some properties were not read correctly from the registry so that after a reload /restart those properties contained default values.
•	Some RSIM messages were not sent from the RS or IM to TCC if they were queried by TCC or under certain circumstances. This could lead to views in TCC not correctly being populated and timeout messages or other warning messages in the Status Messages view of TCC.
•	Some RSIM messages could occasionally have an invalid timestamp. Those messages were discarded by the receiver (RS, IM or TCC) and possibly answered with a NAK message. The effect would be negligible as most of those messages being affected were sent every second.