I'm in need of a little help from my fellow beer legers.?ÿ I'm working on a remote tower project adjacent to one I did back in 2000.?ÿ All of my original control is long gone and a fence builder has wiped out the only property monuments on the mountain top.?ÿ I'm trying reprocess my old control to get into the current realization of NAD83 but have run into a bit of a snag.?ÿ The original data was collected when I was still a Trimble shop and I can not convert the old DAT files using Trimble's 'Convert to RINEX' program.?ÿ I'm sure it is Windows issue based on the type of error message I'm getting.?ÿ Can anyone out there convert these for me??ÿ If so shoot me a message.
Thanks
As far as I know this is a free utility
https://geospatial.trimble.com/trimble-rinex-converter
?ÿ
Watch out
The latest version of the Trimble Configuration Utility must be installed prior to operation of this utility.
If you are just looking to submit to OPUS, I think maybe it just accepts the .dat files without conversion. It did at one time, anyway.
Use teqc. It is a command line program.?ÿ
teqc -tr d xxxxddds.dat>xxxxDDDS.YYo where xxxxddds.dat is the file name and YY is the year of observation.?ÿ
If you want to send to OPUS you might want to include a +C2 after the d.?ÿ
It took a little fooling around to get the "Convert to RINEX" program downloaded and working. Very simple to use. It unpacks the .T02 file into several files. You send the larger file to OPUS.
If you're only going to use it once send it to me and I'll run it through the Convert to RINEX program.
@christ-lambrecht thanks for configuration utility tip.?ÿ That is probably the issue. I'll try to download it from my hotel later on tonight. I've been working on this while on holiday.
Well, Christ's tip on the configuration utility worked and the RINEX files have been imported into Infinity.
Thanks for the input everyone.?ÿ Now back to looking out over the Canadian Rockies.
@john-hamilton There is Winteqc these days, too, a Windows wrapper on teqc https://teqc.silkwerks.com/
Moving from Leica world to Trimble world, I was surprised to find that I had to use the Convert to Rinex widget to convert Trimble files to Rinex, AND THEN had to use a 3rd party application (Winteqc) to decimate my Rinex file to send to OPUS.?ÿ (It was a 1-second base for PPK--that's why I had to decimate).
I like a lot of things about Trimble hardware and field software, but not loving TBC so far...?ÿ?ÿ
Why use Opus at all?
You could use TBC for the processing - you just need to include the base station orbit?ÿ files, no need for Rinex, no need for decimation
?ÿ
@john-hamilton There is Winteqc these days, too, a Windows wrapper on teqc https://teqc.silkwerks.com/
Moving from Leica world to Trimble world, I was surprised to find that I had to use the Convert to Rinex widget to convert Trimble files to Rinex, AND THEN had to use a 3rd party application (Winteqc) to decimate my Rinex file to send to OPUS.?ÿ (It was a 1-second base for PPK--that's why I had to decimate).
I like a lot of things about Trimble hardware and field software, but not loving TBC so far...?ÿ?ÿ
Why not just submit to OPUS directly through TBC? No need to mess around with RINEX or decimation at all:
Although as @jimcox suggested, why not ditch OPUS entirely and process with RTX or process baselines within TBC? Then you can leverage full GNSS and faster logging rates.
?ÿ
@rover83 Yeah, I have submitted to OPUS directly from TBC before, but a long base session at 1-sec interval seemed to be too big for OPUS.?ÿ I received an error message in return.?ÿ I also do process static networks a lot in TBC, but I like to have a Basis of Coordinates from OPUS (usually the average of 2 or 3 days of OPUS results)--it's "official".?ÿ I have to admit I'm pretty unfamiliar with RTX, I'll have to look into it.
That's a good point, I've seen OPUS get overwhelmed before too.
Honestly it's a big reason (alongside the GPS-only requirement) why I switched to processing with RTX on import. Since Trimble implemented HTDP in TBC, I don't have to add another step, and it takes all of 1-2 minutes to get an RTX solution back right inside of TBC.
I've done so many comparisons between manual processing, OPUS, and RTX (also CSRS-PPP and AusPos) that I don't see enough of a difference to make me worry about it.
That's a good point, I've seen OPUS get overwhelmed before too.
Honestly it's a big reason (alongside the GPS-only requirement) why I switched to processing with RTX on import. Since Trimble implemented HTDP in TBC, I don't have to add another step, and it takes all of 1-2 minutes to get an RTX solution back right inside of TBC.
I've done so many comparisons between manual processing, OPUS, and RTX (also CSRS-PPP and AusPos) that I don't see enough of a difference to make me worry about it.
I haven't tried a .dat file with RTX but if it's supported by TBC and RTX I would use it exclusively for .dat files.