What version of TBC, and what model/firmware receivers? There was a leap second update in 2016, and just last year another GPS week rollover.
@shelby-h-griggs-pls I was able to force some non-CORS data to process using GLONASS only just now. ~15?? static work utilizing R10-1s sucking up signal from 4 constellations.?ÿ
Of course some of the solutions weren??t ideal (and some were horrible), but that??s to be expected using GLO only.
I think you have to run "update office software" or something like that to fix the leap second error. Maybe this link...
https://www.trimble.com/trimble_configuration_utitlity.aspx
?ÿ
I had the same problem in TBC:
Rinex observation files for CORS (including GPS and Glonass) and precise MGEX sp3 orbit file for the day (including all constellations)
No Glonass satellite used in the baseline processing...
The solution is to import the broadcast ephemeris for Glonass for the day?ÿon top of the precise (the official Glonass site has a repository- easy to access and navigate). This way it processes Glonnass as well, I am now in the process of trying to find out how it is used in the processing why it's required in the first place.
@gnssinthetunnel That seems... odd. I'll give it a shot- thanks.
@steinhoff you tell me, lol!
If anyone's got insight about this I would appreciate it, seems like a rabbithole ready to devour precious manhours...