I am not a Trimble user (I do process a lot of brands of data in my workflow), I am trying to troubleshoot some data from a Trimble board (BD982) that outputs data that is then converted to the RT27 format. I am trying to determine if my RT27 converter is bad or if there is an issue with Trimble's "Convert To RINEX" utility in the handling of the RT27 file format. Issue is I am not getting correct GAL ephemeris data.
So, I understand that newer Trimble survey receivers can output RT27 format data (per the R12 sales literature) and am wondering if any users have output that format file they could share with me or even record a short file for me to work with? This is not likely something you would get without configuring something on the receiver since I believe in the survey world newer Trimble receivers still default to *.Txx files. I have converted *.Txx files successfully with Convert To RINEX Ver. 3.1.4, so if the converter has an issue, it might just be with the RT27 input files, or it could be my method of getting the RT27 file from the Trimble board. Like I said, trying to troubleshoot a data file and there are about three moving pieces at the moment.
Anyone help in this regard would be appreciated.
SHG
I haven't convert any RT27 files but Trimble's states:
ConvertToRINEX v3.14.0?ÿ(1633 KB)
This utility converts Trimble GNSS measurement files in DAT, T00, T01, T02, T04, RT17, RT27 or .cap format to RINEX version 2.10, 2.11, 3.02, 3.03, and 3.04 formats.
Maybe your RT27 converter.
@r-s-mayer Thanks for comment. Yes it might be my converter to RT27. I failed to mention that with GPS/GLONASS only data the converter has been working fine for years. So either my converter is choking on full GNSS data or the Trimble utility is. Like I said, the Trimble utility converts full GNSS Txx files OK, so I doubt it is the converter, but whole purpose of post was to confirm that piece of the puzzle 1st.
SHG
I had a version of 'Convert to RINEX' that I used for years, then with a new Trimble firmware update, it would crash on generated files. Updating to the very-very-latest version fixed it. I am using 3.14.0 now.
However, I also use TEQC for doing streamed RT27 conversions all the time (like daily files on 20-stations) and I found that if I check this box:
'FLL Measurements' I can not process the resulting files. No matter what I do.
So I don't check it. I don't know what it does, so I guess no big deal.
@mark-silver Thanks for your comments. Do you find that RT27 MULTI constellation files convert correctly in Convert To RINEX? Any chance you have a MULTI constellation RT27 file you could provide for me to run though Convert To RINEX? Our process seemed to work when ONLY GPS/GLONASS, but now that we add MULTI constellation data we seem to be getting incorrect GAL ephemeris data with wrong times.
SHG
If there is an issue with the converter, I would uninstall it using the Trimble Office Cleanup utility.?ÿ That utility will completely remove the Convert to RINEX utility.?ÿ You will want to use the advanced tab to choose Convert to RINEX.?ÿ The program can be downloaded at https://drive.google.com/a/trimble.com/file/d/1vlYZAGLW6jW_ktGXMitpmkDkXw9n1g9W/view?usp=sharing
@fairleywell thanks for suggestion. How will that fix an issue with coding within Convert To RINEX, assuming the issue is that utility? We are currently running Ver 3.1.4 which is the current version.
SHG
Back to report success by taking a different path. I am still untested on the RT27 (multi-constellation) file format to RINEX via Trimble's Convert To RINEX utility, but starting with a *.DAT file of the same data does work. Either our extraction routine for RT27 data format is broken (with multi-constellations) or the Trimble utility breaks when feed RT27 data (with multi-constellations), unsure which at this point, but I do have a workaround using the DAT format. Our procedures have worked for a number of years (with GPS/GLO) until we added Galileo to the mix, so I think that broke something in one of the two steps.
SHG
Another update. I have confirmed that the issue with the GAL EPH is caused by the Trimble Convert To RINEX utility itself and have a support ticket open at Trimble. Anyone trying to convert RT27 to RINEX with GAL data present should be aware that the resulting *.yyL RINEX broadcast navigation file will be incorrect. Hoping for a fix to be released.
SHG
Quoted below is the resolution form Trimble. This might be useful info for anyone in the future in trying to convert RT27 format data to RINEX.
RT272DAT Instructions
The BD982 and BX982 log the satellite observables for both the position and vector antennas into the
same RT27 data stream. In order to split these combined files into single files for the position and/or
vector antennas which can then be converted to RINEX, a software utility named RT272DAT is available,
which can be downloaded here https://drive.google.com/file/d/1rsEfx2GpIG1plmnMtWimN7K1d8O5YkMD/view?usp=sharing.
This will extract only the desired antenna??s data and convert the file to a DAT file. These DAT files can be converted to RINEX using the ConvertToRINEX software.
From a DOS command window or with a DOS batch file, this command will extract the position antenna??s
data: RT272DAT -n0 log.r27 position.dat
From a DOS command window or with a DOS batch file, this command will extract the vector antenna??s
data: RT272DAT -n1 log.r27 vector.dat
Note that: The switch ??n0 or -n1 controls which antenna??s data will be extracted.
log.r27 is the name of the file containing the logged binary RT27 stream.
position.dat or vector.dat is the DAT file that the extracted data will be stored in.
Also note that the RT27 stream only includes position records for the position antenna. Because the
RINEX conversion requires an approximate position, these are included in the vector antenna??s DAT file,
but they are not positions for the vector antenna.
Finally, if there are spaces in the file name(s) these will need to have quotes around them, such as:
RT272DAT -n0 ??input file.r27? ??output position antenna file.dat?
SHG
The BD982 and BX982 log the satellite observables for both the position and vector antennas
What's the difference between a position antenna and a vector antenna?
@jim-frame No Idea. This seems like a convoluted solution, but maybe that is the way it needs to be. With a little more manual work on my end, I don't need the RT27 files, instead I can start with the DAT files. Our processes were semi automated with the RT27 input, and maybe we can incorporate this RT272DAT routine into the automated script?
I just wanted to have the info posted in case someone in future runs into same issue.
SHG
I would guess that they are talking about receivers with dual antenna inputs for computing trajectories, for example machine control. One antenna is the position and velocity that is being used, the other antenna is used to solve for the direction that the vehicle is moving