Trimble Business Center

Updated the fix needed as I did have a typo. There seems to be an issue for old versions that has come up and updating the Office Configuration File doesn't resolve it. Our engineering team are aware of this and we will look at whether we need to update the Office Config file to address this issue.

A quick fix on your PC is as follows:

Open the LeapSeconds.xml file in C:\ProgramData\Trimble\LeapSecondsConfig

Edit the date to 2024-07-01

Updating the GPS Configuration Files Utility solved the issue.

Thank you!

Its baaaack.  "Invalid leap seconds" on a January 13, 2025 T04 file collected on a R12i, current version of Access. Processing in TBC v. 2024.01with installed version GPS Configuration Files Utility (v. 24.6.16.0.)   

The fix, recommended by Ismael Koch does work (editing the XML file).

Joel- I believe there have been some updates to the GPS configuration file since 24.6.16.0. You will likely want to run the "Check For Updates" command and confirm you are using the latest version. 

I thought invalid leap second errors required a firmware fix for the receiver, or has Trimble chosen to address adjustments to data files through TBC processing? And yes there is an updated GPS config file to install.

Yes, following Robert Hoy here, that would be interesting to know, especially for static data.

For RTK I have to assume it needs a FW fix, but for static data it should be possible to apply those seconds afterwards as long as some flags are set/checked.

Occasionally we have subcontractors rocking up with old 5800 or R8 type of receivers, which are long out of software warranty. I can't find the support webpage with those old FW's anymore, so I have to assume it was shut down.

What I also don't like is that we have to pay for this kind of updates for the geospatial receivers.

For the machine control receiver line the FW warranty was thankfully abolished years ago. Even a 10-year-old machine receiver can get the latest FW without costs. 

From what I understand, firmware updates for this issue are required for years where leap seconds are introduced. There have been no leap second updates for the most recent period, therefore TBC can interpolate. I'm not sure if I can speak to additional fixes that might be included in these firmware updates.

thanks Jonas,

Correct.  constellation leap seconds do not occur every year, so this issue were seeing on a Julian calendar turn over makes no sense that a file collected after Jan 1 requires updates in TBC.  This is TBC.  Wouldn't it be prudent that a simple edit on the XML a user has to do is fixed on the production cycle of TBC release?    Really shouldn't have to do this every year.   And if the conf. utility fixes it, as we know, thats a SIDE utility that many of us get banged on ability to install - since its a MSI file.  Increasing security issues on us as customers is making installing utilities even harder and harder.  Fixt the XML embedded in the TBC new release and were done!

Recommend this small fix on the leap_seconds.xml is simply updated out to some date.  And if you can, make it out to December instead of July as the instructions here indicate.

Here is a file collected yesterday on a R980.  

Joel - I am doing some testing for the next update as Trimble was recently notified (by International Earth Rotation and Reference Systems Service (IERS))  there would be no seconds added again for this period. Out of curiosity, are you simply trying to see what time frame the data was collected? If so, why simply update the time to reflect GPS time, or offset from GPS time? The test below is based of a fictitious measurement from 3/5/2045. 

Hi Jonas,

Personally, I'm a fan of viewing my data in TBC set to local time.  With an 8 hour offset up here, you can understand the gyrations involved.  Setting to local time is just logical.  From your tests, I think I understand we won't need to see this crazy error (which is in fact wrong "no leap second has been engaged), again.  Thanks for the update.!

This invalid leap second issue is back once again.  The bug is now a much bigger issue now since users in many agencies (e.g. NPS) have no capacity to edit the XML file without admin privileges.    This is an issue that stops us from processing data after this July deadline, which has a counter set to July 01.   Users have contacted me with TBC version 2024.1 or 2024.1x that this has re-appeared.   

Request some method to ensure this issue is resolved.  Updating to most current version of TBC is not possible for all users in this time of disruption that is occurring all over agencies in the Feds.

*************************

Per Brandon's response:

There seems to be an issue for old versions that has come up and updating the Office Configuration File doesn't resolve it. Our engineering team are aware of this and we will look at whether we need to update the Office Config file to address this issue.

A quick fix on your PC is as follows:

Open the LeapSeconds.xml file in C:\ProgramData\Trimble\LeapSecondsConfig

Edit the date to 2024-07-01