I have found that if I convert my data file to rinex using teqc (my standard operating procedure), and sent it in, it only processes GPS, none of the other constellations. But, if I convert to rinex using the trimble utility, then it processes all of the constellations, which results in better solutions with lower sigmas. I just did a file from yesterday (147 minutes), the difference was 4 cm in height.?ÿ
Also, I have found very minor differences depending on whether I send in a .t02, .tgd, or rinex (trimble converter) file. In the couple of millimeter range.?ÿ
The reason for sending in as rinex rather than native .t02 or .tgd is that I can edit the file to get the correct HI. But I would like to know why the slightly different results???ÿ
?ÿ
From what I've seen the TBC?ÿroutine takes care of the HI for you, I've never converted anything to send to RTX and even measuring to the lever arm produces the correct HI for processing. Same with OPUS.
?ÿ
I am not sending it from inside TBC, why is it rejecting other constellations if teqc is used??ÿ
Trimble's response was that maybe teqc is producing a non-standard rinex file....
Got it, I only send it as it's loaded into TBC, made it all a bunch simpler.
I can imagine doing it "longhand" would take a lot more editing.
Not really, I have always done it on the web page (trimblertx.com/UploadForm.aspx) and that way I get a nice pdf and xml file returned. The pdf is a one page summary of the results, the xml has all the info, I scan that to load the info into a database. Typically I just upload the raw file, even if the HI is not correct. I have a routine which will correct everything using the actual HI. It is just a rotation/translation of the ECEF coordinates, and then convert to lat/long/hgt.?ÿ?ÿ
One annoyance is every time you upload using the web page you have to enter in the stupid captcha characters. I would much prefer that they require you to register and you put in your login and password (which can of course be automated in chrome)
?ÿ
After corresponding with Lou Estey (teqc person), the solution is to use +CA_L1 as an option when running teqc. This creates a rinex file that RTX will use GLONASS. I am collecting data right now with all constellations to make sure that it uses all of the when a rinex is submitted, same as when a .t02 is submitted.?ÿ
I seem to use RTX and OPUS for more of a check to my own processing of CORS data. It isn't very often where any CORS sites are "close" and I like to look at each vector one at a time before processing the entire batch.
A good match with the three results gives me the warm and fuzzys, I tend to see RTX match elevations closer?ÿto my adjustment, but those results continue to get closer. The automation of RTX and?ÿOPUS in TBC has made it so quick there really isn't any reason to not do it.
But doing RTX my way doesn't give out a detailed report.
+