OPUS worked with version 27 and 27.1 and now with version 28 I get these types of errors without converting the file to RINEX 2.10 in RTK CONV and doing the same behavior as before.
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
This is something we will need to investigate. We always double-check our firmware before making a release. In particular, we’ve been testing the logs in OPUS with good results. So if something is not working right for you here, we’ll need to take a closer look.
Can you please share your logs with me? I’ll check if I can see anything amiss in them.
I don’t believe there is anything amiss with the logs, it simply doesn’t work because it’s not an OPUS specific log (it’s custom). What I’m referring to is in version 27 the way we set up our logging for our LiDAR would also work without conversion for OPUS. Now with version 28 it is back to needing conversion to work. Once converted it works fine, it was certainly nice to be able to skip that step though with version 27 and 27.1
I get you. We’ve been adjusting the logging settings for the most comfortable use with OPUS specifically. There are a few reasons for that, one is that we don’t recommend using time-adjusted logs in any other application but with OPUS. It can lead to result inconsistency due to the nature of the adjustment.
However, I see how your workflow is affected at the moment. We’ll consult with the devs about it and whether we can suggest any alternative workflow for you. Still, there won’t be fast changes as we intend the presets workflow to be present for PPP’s sake.
I sent the logs a while back but happy to export again. I have moved the sim to another RS2 which doesn’t have the issue. Unfortunately the sim lock came off the original base when removing it in the field and I couldn’t find it, any idea where I can get one?
It’ll be great to test the unit on a new firmware version before exporting them. If you can use the SIM, that is I’m pretty sure you can get one of the covers from the closest electronic shop after checking it out with the closest dealer to you. As I know, it’s rather easy to insert the cover back in the slot.
I’m pretty sure you can get one of the covers from the closest electronic shop after checking it out with the closest dealer to you. As I know, it’s rather easy to insert the cover back in the slot.