I see others may have experienced this error in the past but am hoping someone can clarify a little better for me. On Sunday I used a Trimble 5800 and an R8 (Model 1) to collect 7 static points to process with OPUS. The R8 reciever files converted to Rinex go through to solutions no problem, The 5800 files are all returned with the same error code;
FILE: 15662082.97o OP1489437652335
9009 ERROR! OPUS terminated abnormally in one of the processing modules.
9009 PPS - zero coordinates for initial point.
9009 OPUS cannot process this dataset.
9009 Aborting...
9009
6029 After the single baseline analysis, fewer than 3 useable
6029 reference stations remain. Aborting.
6029
I believe the only difference between the 5800 and R8 is date of purchase and the R8 has a transmitter radio. I saw something in another thread about possible date conflicts in the Rinex Files. The last time I used the 5800 for an OPUS solution was January 2015 and it worked fine then, could something have been modified since then that would only effect a 5800 series receiver?
Hoping someone might have a direction I might take before going back and taking new observations with a different receiver.
Thank you.
If you only collected the data yesterday I'd wait another day or two and try submitting again. Sometimes there's a lag of a couple/few days before they will process. Unless the firmware on those receivers is seriously out of date I really doubt the problem is with the receivers themselves.
If I had a dollar for everytime I got that message....just saying...as Williwaw said, wait and submit again....
Yes, I have had that happen before. However, I looked at the rinex files in viewer and see the Trimble 5800 shows an observation date of July 27, 1997 instead of the actual date of March 12, 2017. The Trimble R8 shows observation date of March 13, 2017 and is correct.
I was able to edit the Rinex files and correct the date. The files process through OPUS now but I still feel uneasy and will be QA/QC'ing the values. I have no idea why the Trimble 5800 started using bad dates, this is brand new and will try to recreate the error.
Thank you, I have this solved for now.
This sounds like the 1024 week limitation of some firmware. Other threads have mentioned updates for the receivers in that series. Check your firmware version.
This almost sounds like you started collecting data before the receiver knew where it was. Next time let it run for 15 minutes then start collecting data. All is not lost, though you can insert a position in your RINEX file.
At about the 8th line of the header there is a line that ends with "APPROX POSITION XYZ". Most likely your files has three sets of zeroes before that indicating the former data was cleared. Once a receiver runs for a few minutes with sufficient satellites, it figures a rough position in XYZ. Older receivers are much slower to begin collecting satellites and then calculating a position. There is nothing you can do about it but be patient.
OPUS needs this rough position to pick the nearest CORS to give you a good solution. Without it, it will not waste it's own time, figuring out where you where. If you have been anywhere near and I mean within quite a few miles, you will be close enough to get a solution from OPUS. If you are way off you my want to then replace your approximate with the OPUS solution XYZ position and resubmit the file as you may get different CORS and a better solution.
Open your RINEX file in a text editor and take a look at the header information. BTW older receivers usually need to download a recent ephemeris before they really think about working diligently, which is a another reason to be patient.
If you do not use your receivers on a weekly basis, set them up, empty the files and turn them on for a half hour the day before you go out. Do not flush out all your memory the next day as you want it to start with the recent ephemeris.
Paul in PA
