-
OPUS doesn't like my R10 RINEX files
Let me start by saying that I’m very new to Trimble Access and the R10.
Yesterday I was playing around with my new R10 receivers in FastStatic mode, in order to ultimately generate OPUS solutions. I ran both base and rover for about two hours in the back yard, and stored .T02 files no problem. When I attempted to convert to RINEX, only one of my .T02 files would convert. This may or may not be because my RINEX conversion program is at least a few years old.
When I submitted the one RINEX file that successfully converted to OPUS, I got this error message:
1017 The RINEX data file that was submitted is not formatted correctly and
1017 therefore is not standard RINEX. You may have several errors in the file.
1017 Run “teqc +v filename” to check the formatting. TEQC is available through
1017 our CORS Utilities/Software tab
1017 ** See the exact formatting error message from teqc below.
1017Are there any tricks to successfully generating OPUS solutions from R10 data? Maybe a specific RINEX conversion program that works well?
Any advice would be much appreciated. Thanks!
-
7 Replies
-
If you like…
Shoot me your .T02 (and RINEX) files, and I’ll take a look at them.
Loyal
ldogeo AT aol DOT com -
It is far better to run into these problems on a practice run, than on the job and facing a deadline.
Paul in PA
-
use teqc.
-
algallop, post: 352498, member: 8394 wrote: Let me start by saying that I’m very new to Trimble Access and the R10.
Yesterday I was playing around with my new R10 receivers in FastStatic mode, in order to ultimately generate OPUS solutions. I ran both base and rover for about two hours in the back yard, and stored .T02 files no problem. When I attempted to convert to RINEX, only one of my .T02 files would convert. This may or may not be because my RINEX conversion program is at least a few years old.
When I submitted the one RINEX file that successfully converted to OPUS, I got this error message:
1017 The RINEX data file that was submitted is not formatted correctly and
1017 therefore is not standard RINEX. You may have several errors in the file.
1017 Run “teqc +v filename” to check the formatting. TEQC is available through
1017 our CORS Utilities/Software tab
1017 ** See the exact formatting error message from teqc below.
1017Are there any tricks to successfully generating OPUS solutions from R10 data? Maybe a specific RINEX conversion program that works well?
Any advice would be much appreciated. Thanks!
Let Trimble calculate it with RTX-PP if you have TBC, it will do it automatically, I’ve not seen a bit of horizontal difference between OPUS and Trimble. Elevations so far tend to be better referenced to NAD88 with RTX-pp
-
algallop, post: 352498, member: 8394 wrote: Let me start by saying that I’m very new to Trimble Access and the R10.
Yesterday I was playing around with my new R10 receivers in FastStatic mode, in order to ultimately generate OPUS solutions. I ran both base and rover for about two hours in the back yard, and stored .T02 files no problem. When I attempted to convert to RINEX, only one of my .T02 files would convert. This may or may not be because my RINEX conversion program is at least a few years old.
When I submitted the one RINEX file that successfully converted to OPUS, I got this error message:
1017 The RINEX data file that was submitted is not formatted correctly and
1017 therefore is not standard RINEX. You may have several errors in the file.
1017 Run “teqc +v filename” to check the formatting. TEQC is available through
1017 our CORS Utilities/Software tab
1017 ** See the exact formatting error message from teqc below.
1017Are there any tricks to successfully generating OPUS solutions from R10 data? Maybe a specific RINEX conversion program that works well?
Any advice would be much appreciated. Thanks!
I would download a newer version of Covert To RINEX. The R10 tracks a lot of modern sats, and you might have some stuff that OPUS can figure out.
-
We got it sorted out late Saturday night.
Basically the RINEX file created by Trimble Access was nonsensical (13 OBS including stuff like C0 L0 P0 D0 S0, all of which were blank), and a scattering of REAL obs data. TEQC verify gagged on it (the weird obs types) and crashed, which is probably what happened when OPUS tried TEQC on it.
I ran his T02 files through “Convert to Rinex,” and they both processed fine.
Loyal
-
As long as you have the latest version of Convert to RINEX you won’t have any issues:
http://www.trimble.com/support_trl.aspx?Nav=Collection-40773&pt=Trimble%20RINEX
Log in to reply.