ASHTECH Gurus,
So with the TGO bug that has recently come to light, I have been playing with GNSS Solutions for post-processing static data from my 2 Hiper Lite + receivers and a Promark3. I have processed the data successfully in both TGO and TOPCON Tools as well as OPUS on the Hipers, so the data itself is good.
There seems to be some issue with the RINEX data or the way I am importing it into GNSS Solutions. The vectors process with very near similar results as the other two packages, but there seems to be an issue with antenna heights? I am working with a simple three-point loop (2 knowns, 1 unknown)and can replicate the resultant unknown coordinates with a single vector from either base (one Hiper, one Promark3), but when looped together, the elevations and loop closures bust by what appears to be 2m in the vertical and 3'+/- in the easting only.
In am converting the .TPS files (TOPCON) with Link version 8 and have also tried editing the raw data for antenna type and height prior to conversion with the same result.
It looks like this topic was discussed before [msg=44165]here[/msg], but I am a bit miffed at the moment.
Any ideas are appreciated in advance. I will be away from the PC tonight at a Society Chapter meeting, but will check in later.
Thanks,
Matt
Matthew,
Welcome to the madness! I have seen that same error happen again, on a different project, and cannot figure out what the heck is going on. I would always try to set one of the Hipers on your main points, and use OPUS as a rough check. I would also try to fix only one point at a time and see how your results are.
Paul in PA is a guru with GNSS Solutions, and has helped me on more than one occasion. He is a nice guy, and very helpful.
Please keep us posted on your experience. I am sure that I am not the only one other than you that has run into this. The Hipers and PM3's are pretty popular receivers.
Thanks, and good luck,
Jimmy
Truth Be Told, I Am Not A GNSS Solutions Guru
My weapon of choice is still my old Ashtech Solutions.
Quite a few years ago I bought and paid for the first GNSS Solutions with an L2 key sold as a stand alone program in the USA. With every update it seems to be moving away from me, possibly because the amount of my GPS work has declined. As CORS have increased I have found certain Trimble CORS that my GNSS Solutions pukes on, while other CORS with apparently the same setup work just dandy. I no longer try to figure it out, just mosey on down the road to the next CORS.
A few years ago I and a few others beat certain Topcon CORS submission files to death as Topcon Tools and Solutions consistently agreed on vertical positions that OPUS disagreed with. With unmatched Topcon receivers especially, there was an antenna file problem that I never saw was satisfactorily solved. In some cases the points were reoccupied with switched receivers and the difference error swapped points. With the plethora of antennas it is hard to keep up any longer and I now accept the downloaded defaults rather than editing my antenna files as in the past.
Your problem does sound like an antenna files issue, so start by peering into the Solutions antenna.inf file. Compare the offsets to your Topcon and to NGS information.
Paul in PA
