The ROCK R1A Survey package includes the Emlid Reach RS2 GNSS receiver as its base station. From time to time you may need to get an OPUS solution using the logged RINEX data on the device. OPUS can sometimes have trouble with the Emlid Reach RS2 data. Below is a solution that has worked for me:
Select the RINEX file you downloaded from your EMLID Reach RS2
Select to output as RINEX with an interval of 1s
Select the output directory and name the new obs
Upload this data to OPUS and be sure to select the EML_REACH_RS2 antenna.
Other problems encountered:
From time to time I get an error:
9011 OPUS could not process the data file that was submitted. The data was
9011 either very noisy or it was collected in kinematic mode.Or OPUS software
9011 has issue during this time, please reupload later.
9011
Blockquote
To fix this, cut some observations off of the beginning and end of the file:
Has there been a solution to this? Seems daft we canāt get a proper setup on the Reach to process though OPUS. Iāve been working on different combinations and canāt seem to get one through. The odd thing is the errors Iām getting are as if there isnāt enough elapsed time from capture to processing, but itās been past midnight. I know it used to be 24 hours before processing through OPUS, but I thought they had switched it to once itās past midnight you can submit. Is the 24 hour rule still the way?
Wait a day before submitting your file: OPUS will use the best CORS and orbits available at the time you upload your data. While most CORS are archived within 30-minutes past the hour, some arenāt available until the next day. If you process your data in less than 24 hours after collection, OPUS will use Ultra-Rapid orbits. Rapid orbits, available at 17:00 UTC the next day, will offer a slight improvement in your accuracy. Final orbits, available weeks later, offer only slight benefit to solutions in areas with usable CORS nearby.
@Alex Still getting the same return. Data collection was completed around 10:50PM Wednesday night. OPUS is still aborting as of this morning when I try. Weird thing, I ran one last night for a couple of hours (No changes in base station settings) and OPUS now says it has a 20 second collection rate. Very weird, as itās still set to 1 second.
@alex I shouldnāt have to according to the settings that Emlid has provided on their site. The first file I have collected is āworkingā according to the errors Iām receiving from OPUS, itās just too soon for data for some reason. For the second file to have a 20 second collection rate is very weird. Iāve had issues in the past with large files which Iāve decimated in TEQC, but nothing like this.
Iāve ran the most recent 2 hour session through RTKCONV but no file is generated. It appears to be working, but no file is kicked out.
Ah Yes @AreDub we 100% agree, we should not have too. But after seeing users of EMLID struggle through countless OPUS posts on EMLIDs own forum, we dove down and found a reliable way to make the RS2 work for OPUS. We hope emlid can see this and make changes to the firmware to assure this works out of the box, but this has not been our experience.
The above workflow works and is usable. Thanks @Alex
I would move by 20 minutes from the beginning and end to begin with.
Otherwise we had good luck with gps-solutions.com as well. There are other precise positioning services that Iām taking a look at as well. OPUS can be tricky sometimes.
1020 OPUS aborted on the submitted data file for one or more of the following
1020 reasons. OPUS cannot process the data file.
1020 1. Collection interval of the data file was not one of the allowed rates.
1020 The intervals that are accepted are 1,2,3,5,10,15,30 seconds.
1020 2. The time of each epoch is offset from one of the above intervals. The
1020 seconds epoch field must coincide with one of the above rates.
1020 3. The data file may have been collected in kinematic mode. OPUS does not
1020 process kinematic data files.
1020 4. Note: OPUS processes data every 30 seconds, and 2+ hour files
1020 collected at the 1 second rate should be changed to 30 seconds.
1020 5. If your data were collected today or yesterday, we may not have
1020 sufficient CORS data - try resubmitting your file tomorrow.
1020
