OPUS Error 1020

Something you are using is not up to date, but you can easily fix it.

Open your RINEX "O" file in WordPad and do a "replace all". Replace 2000 11?ÿ 8 with 2020?ÿ 6 24, or it might be replace 00 11?ÿ 8 with 20?ÿ 6 24, since I am not sure how every line reads. It may be neccessary to do the same with your RINEX?ÿ "N" file.

I just had to do it with a GPS observation I did today. My problem is the internal battery in the GPS receiver needs to be replaced and I have not gotten around to having that done, since I am not doing GPS every day or even week. I think today was the first time since May 6 and the second time since January.

Paul in PA

Posted by: @chazb

0220326010 R7 2.21 REC # / TYPE / VERS
TRM41249.00 ANT # / TYPE

I agree with Paul, there is something going on with the receiver itself.

If that is truly v2.21 of the R7 firmware, that is around 15 years old. At the very least it does not account for the latest GPS week rollover of last year, not to mention leap seconds. I would get the warranty up to date and download the latest firmware.

Thanks for the input guys. Yes the receiver appears to be very out of date. Its not a setup we use often but in this case we thought it would be nice to do 3 static observations at the same time. And now here I am having to manipulate the data to work... I attempted to replace the date string with a new string. It appears to have worked fine but when I submit it to OPUS it now thinks the data set is less than 7.5 minutes long and will not process it.?ÿ

?ÿ

EDIT: Added another space between the date and time strings and it has been submitted just fine. We will see what OPUS gives me.

?ÿ

EDIT2: Opus came back and the redundant ties to each point line up great. Thanks again for the help!

A friend of mine has a Hemisphere GPS receiver. The native binary files appear to be correct. But when he exports to rinex theyƒ??re 1020 weeks retarded. And the Nav too. A simple TextPad search replace and opus is completely happy. Itƒ??s a software fail probably not a receiver fail, but I donƒ??t know for sure. The manufacturer probably knows all about it by now.

All of my receivers are week rollover afflicted. Z12s. I have a fixer app that with 2 clicks and done. Knowing the issue, I have no fear using them in all applications. But I always use static, kinematic (aerial mapping) post process kind of guy.?ÿ

@larry-scott

What software is he using to generate the RINEX from the BIN file?  What antenna is he using?  We use the S320 weekly and have not had any issues uploading to NRCAN's PPP.  The software is a bit fussy on making sure you select the correct antenna.  I tested OPUS about a month ago for giggles and it worked fine for us.

@jaccen

It’s a bit more odd than that. (I misspoke in my earlier comment.)

We were measuring a typical static line and he sent me his data in Rinex. The obs file was 100% ok. Opus returned no error.

however the nav file he sent had incorrect date; week rollover effected. Gnss would not process our differential observation. I inspected his rinex obs saw proper date: 20  5  8

however the nav file that he sent had: 00  9 23

He re-extracted and the same mismatched dates: obs file correct, nav file retarded. In the header:

RINEXSKX2 2.9.3  HEMISPHERE PGM

HEMS320   ANT # / TYPE

He rarely uses rinex, so he had no idea, and it took me quite awhile to realize ONLY his nav was wrong.

(I have fix my Ashtech ZSurveyor and Z-XII all of the time.)

@larry-scott

Easiest fix for a wrong nav file is to go to NGS CORS RINEX site, pick the broadcast nav file and rename it to match your Observation file. You can also use any other nav file for that day from your own field work if sufficent hours were observed.

If not correct your nav file in wordpad. Be aware that a nav file may include some of the next days data so you will have two wrong dates to correct. 

Paul in PA

@paul-in-pa

I’ve crosses those bridges. TextPad repair of obs and nav long ago. Retrieving Broadcast nav file from my favorite UFCORS was SOP years back when ZXII rolled over. Week rollover reared it’s ugly head in Z-XII long before ZSurveyor fell prey. (Which still puzzles me.)

The MISMATCH from hemisphere was wholly unexpected. (It’s fix was a no-brainer, once found.) As the hemisphere obs was correct, suspecting its nav file came only after looking for every other possible defect.

and I have new cmos batts all round, new NiMh batt for ZSurveyor, and 3 identical 701008 geodetic antennae, I think I have fine array of gps for a while yet. I think the antenna is the most critical component. Z data is as good now as any L1/L2 data. 

And the rinex fixer util that a friend wrote for me just streamlines opus submission, which I access quite often. 

@larry-scott

Larry, I recently acquired a pair of Hemisphere S320 receivers to replace my older Topcon Hiper Pro receivers.?ÿ So far so good, but I am now navigating for the first time how to submit to OPUS based on the BIN file logged onto the SD card on the S320 base.?ÿ Looks like I might need to convert the BIN to RINEX.?ÿ What software do you use for this??ÿ And, what is the "rinex fixer" utility you mention??ÿ Any help would be appreciated...

EDIT: I found Hemisphere's "Rinex - Desktop" conversion utility, version 1.9.3, under Utility Software on the page below:

https://www.hemispheregnss.com/firmware-software/

and managed to convert the BIN file to RINEX 2 observation file, and submitted to OPUS.?ÿ Barring an unanticipated failure, this looks like it'll work...Would still be interested to know about the rinex fixer and how/when you use it...

Al

@big-al
I do not have Hemi320, a friend does. The bin-> rinex did produce a valid obs file, no issues.

However, the quirk was that the NAV file was not valid. His NAV file was week-rollover afflicted, the dates 1024 weeks retarded. It drove me nuts. (I discarded it, and used a manually edited nav file. Of course you can download a broadcast eph/nav file. Or copy a correct nav file from another source.)?ÿ

my rinex fixer is for week rollover afflicted rinex 2.11 OBS files only. My Ashtechs return incorrect dates for the obs and nav files. I ƒ??fixƒ?? the obs file for opus submission, so the nav file is not used. And the Hemi rinex obs for opus was good. (Assuming you have the same version) ?ÿ?ÿ

It was the unbelievable output from the Hemisphere rinex that hit me: the obs correct, the nav incorrect. So, for fun, check the dates in hemisphere rinex nav file output and see if theyƒ??re correct. It was a funny glitch to see that the obs and nav had different dates.?ÿ