Trimble Business Center

I processed some GNSS data from yesterday (July 7, 2020; day 189) in TBC 5.20. I use the baseline processing report in my workflow, it is a critical link between the processing in TBC and everything I do with the data. 

All of the baselines show up in the report as processed, but all of the times (start/stop, and when processed) show up as "invalid leap seconds". The data consists of 6 .dat files, and 4 rinex files. All of the rinex files have a leap seconds record in the header. 

By not having the start/stop times, it breaks my workflow. 

I was able to get around the problem by changing the time units to "GPS Time". But I would still like to know what the problem is. 

Which receiver are you using?  Do you have any updates when you have TBC check for updates? (aside from v5.3, though if you have a valid license for v5.2 you'll be able to use v5.21 too).

This happened on all of the solutions. There was an Alloy, three R10's, two R8's, a 5700, and three CORS (one 5700, one Leica R10, and one Net R5). It is happening when TBC is trying to display local times. Once I changed the time units to be GPS (i.e. no leap seconds), everything was fine. I have not yet upgraded past V5.20, although I am eligible. I will add that the 5700 that I deployed does have the issue with the incorrect week number. I use a program that updates the week number in the .dat file to the correct week. We use this all of the time, and have not seen this behaviour before when using dat files that have been week corrected. 

The 5700 is old. Did it get the leap second firmware update? I'm assuming there was one for it as there was for the 5800. I think just one receiver without the update could affect all baseline calculations.

That may be the issue, that is why I mentioned it, but it has never happened before. We have several older receivers with older firmware, but this issue never manifested itself. 

I will try to create a new job without that data file and see what happens. 

We had the same issue on 2 machines last week.  Our solution was to run the Office configuration file utility update; all vectors and baselines were reporting correctly after that.

Trimble Configuration Utility 

Thanks, John. I am going to update to 5.30 and run the config utility. The reason I hesitate to update to a new version is that it always resets the excel baseline report format, I have to go back in and reconfigure to match my workflow. I wish they would just leave those setting as they are when an update takes place.