OPUS-RS aborting
 
Notifications
Clear all

OPUS-RS aborting

3 Posts
3 Users
0 Reactions
5 Views
(@new-mexico)
Posts: 57
Registered
Topic starter
 

I saw the previous posts about OPUS-RS, so I submitted a file I had tried in February. At that time the message; not enough stations for a solution.

Now the message is:

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

So I just collect 2+ hours of data if we are way back in the boonies.

 
Posted : March 27, 2014 11:01 am
(@kevinfoshee)
Posts: 147
Registered
 

Can you view your raw data? I had that problem once. Somehow my receiver had collected data at a 14 second interval to start the file. all the other ephochs were 30 seconds apart. I opened the file and deleted the first epoch; and opus processed the file.

 
Posted : March 27, 2014 1:20 pm
(@paul-in-pa)
Posts: 6044
Registered
 

I had one last week at 70 seconds. Default interval is 10 seconds, but it stored data to start then skipped the next 6 epochs because the # of sats was below minimum.

Took the first one out and no problem.

Paul in PA

 
Posted : March 27, 2014 2:50 pm