This morning I installed TBC 5.20 (had been using 5.10). I added two stations to an existing network, reprocessed it all, and the results were horrible, several meters of residuals. I started looking at the results, and it was using anywhere from 1 satellite up to 6, mostly 3 or under. I re-installed 5.10, and everything is back to normal.?ÿ
Anyone else ever seen this pathological behaviour??ÿ
Do you want to post your .T02 or VCE files for others to corroborate?
I just checked for updates and there is a patch "which fixes a number of issues."?ÿ I don't have enough time to install it right now.?ÿ It updates TBC 5.20.0.0 to 5.20.2
I was in a rush to get some work out, so I didn't have time to investigate more, easiest thing to do at the time was to go back to V5.10. I didn't save anything.?ÿ
I had assumed that a TBC full install file would have the most up-to-date patches, but that is probably a wrong assumption. Once I get sometime where I am not under deadline pressure I will try again and install any patches.?ÿ
5.10 has a patch too I think or maybe I skipped that one and it is 5.00 that has a patch, fixes the invalid leap seconds error
I am running 5.20.7286.17026 (GNSS 2.20.2.18137), which was just installed on Wednesday by our IT folks, so I assume it is what they mean by 5.20.2 - nothing comes up when I run "check for updates". I just ran a quick test project using some data that was collected in 2016 and some data collected a few weeks ago and it performed with no issue.
I am going to give it another try after vacation. I wish I would have saved it, but I was in a rush.?ÿ
