I use teqc to convert trimble dat files to rinex, but that only gets the GPS satellites, which normally is all that I want. Now, I want to convert a .T01 file to rinex, so that it will have glonass also. TEQC does not convert .T01 files, I assume because Trimble does not let them have the file format for that, only for .dat.
I downloaded the Trimble ConvertToRINEX program (v2.21.0), but it immediately blows up when I try to run it (windows 7 64 bit machine). Any thoughts on that? No error message, just blows up.
I have also tried to use runpkr00.exe to convert the .T01 file to something else, but it only seems to work to create a .dat file.
On a related note, I have recently been using the RTX PPP post processed service from Trimble (which is free, but must be certain receivers). The processor works very well with enough data. If I send the .dat file, the results are not as good as when I send the .t01 file, because the extra satellites result in a better solution. But, the .t01 file has a zero HI. Hence the need to create a rinex file with glonass. Not that it really matters now, i wrote a program to parse the returned xml file and create records in a database with the pertinent information, and also I correct the results for the missing HI.
John,
I have been running ConvertoRinex ver. 2.1.7.0 on T01 & T02 files on my Windoz 7-64 bit since I got the machine (last year some time), without any problems.
BTW, the HI, Antenna Model, etc. come across to the RINEX file just fine, along with the GLONASS (etc) observations (T02 anyway, the T01 files that I have converted were NOT GNSS).
If you want to, shoot me the T01 file, and I'll give it a shot.
Loyal
I, also, ran ConverttoRinex on W7 64x with no problems.
John -
I'm also running Convert To RINEX 2.1.7.0 on Win 7 64-bit and haven't had any problems with T01 files. If you're not getting HI, etc. in your file I assume it's because you're running an older receiver or pushing the blue button on an R7; if you use fixed height tripods you could use Configuration Toolbox or GPS Configurator to create a boot file that contains HI, antenna type, etc. If you're starting it with Survey Controller or Access all that should be in the T01.
I second Loyal's comments. 64 bit, windows 7 machine with no issues running the converter. Also, all of the appropriate header information will be filled in the RINEX file.
Strange issue. Have you tried running it in XP compatibility mode? (right-click the program -> properties -> compatibility, Service pack 3)
~Raybies
Just for grins I just updated to 2.2.2.1 - no problems - and converted a T01 file from an R7GNSS - no problems. GLONASS was there, HI and antenna were there, all good.
The issues about the antenna HI, point name, etc are separate from this. I do not run any data collector when doing static, but then I put this info into the dat file in the office. However, I cannot do the same with the .t01 file because I do not have the file format info from Trimble. That is why I want to convert to Rinex.
My program that reads the .xml from the Trimble RTX service automatically puts in the station name (by looking up the dat file name in another database, as well as the correct ARP height from the other database). I then correct the X, Y, Z vector components to reflect the true HI by the following formulas, because the RTX processor is using an ARP height of 0.000 (rather than the actual 2.000):
DeltaX=cos(latitude)*cos(longitude)*deltaH
DeltaY=cos(latitude)*sin(longitude)*deltaH
DeltaZ=sin(latitude)*deltaH
In this case, deltaH is -2.000
I tried uninstalling and reinstalling the rinex converter, same problem. I then tried it on my laptop (which is also windows 7 64 bit). Installed fine, runs fine, and it created the rinex file(s) with GPS and glonass, and the two ephemeris files. So something is !@#$-up with my desktop.
I have always tried to steer clear of the Trimble rinex converter and use teqc instead, as that seems more "standard". But, of course there is the problem of not recognizing .t01 files.
Proprietary formats...
I know Trimble isn't the only one, but why do the manufacturers insist on storing data in proprietary formats that they keep as a secret? I do have the old format specs for dat files, as apparently unavco does, but I think no one has the .t01 (or .t02, etc) formats. What really is the problem with releasing that?