Trimble static data and OPUS issues
I'm hoping to find a higher survey nerd to assist with this issue. Our DOT mandates primary control is submitted to OPUS for a solution. (Fine, sure, I still process the network myself to check, I digress)
I'm having an incredibly difficult issue with a file from a R6-2 receiver. Every time I submit the file to OPUS, it states: "The file xxxx seems to have a collection interval of 257 seconds!
The collection interval must be 1,2,3,5,10,15 or 30 seconds to be processed by OPUS."
First, I tried multiple different options with Trimble's convert to RINEX utility. No luck, same error every time. Then I fell back to 'ol reliable, teqc. Using teqc, I attempted to force different intervals directly from the DAT file. -O.dec or -O.int and trying various, OPUS accepted, intervals. Again, the same error.
I couldn't figure out the issue. The crew was going back onsite a week later, so they collected another 3+hr session, this time with a R8-4 receiver.
OPUS is giving me a similar issue except stating it detects a 51 second interval. Again, I used convert to RINEX and teqc with no resolution. We collect @ 1 second intervals (so we can decimate later, if needed). The files were downloaded directly to my desktop from the receivers using data transfer. All Trimble software was updated to the latest version two weeks ago.
Thanks for your assistance,
I would suggest that you examine the Rinex file to see if the time interval between the first and second data epoch. Sometimes there can be an epoch that does not get recorded and can mess up OPUS. I think OPUS determines the recording interval by examining only the first tow epochs!
Are you using the most recent version of Trimble's RINEX utility?
Send me the files at ldrennan AT mphinc DOT com and I'll be happy to look at them.
This worked flawlessly. I deleted the first epoch of any files that were experiencing the error and OPUS was able to process them.
Cliff, thanks for the insight!
p.s. I did find this nice page on the RINEX 2.11 format: RINEX v2.11
Lee, see the comment above. Simply deleted the first epoch of the RINEX file resolved the issue. If you would still like to see the files, I will gladly send them.