Opus rapid static n...
 
Notifications
Clear all

Opus rapid static not working

7 Posts
6 Users
0 Reactions
3 Views
(@fct487)
Posts: 44
Registered
Topic starter
 

Is anyone else having trouble getting a solution from rapid static. I know it was down a couple weeks ago when I was getting the same error message.

005 NOTE: The IGS precise and IGS rapid orbits were not available
2005 at processing time. The IGS ultra-rapid orbit was/will be used to
2005 process the data.
2005
6029 After the single baseline analysis, fewer than 3 useable
6029 reference stations remain. Aborting.
6029

But if I collect And send static is it working

 
Posted : 12/06/2014 10:37 am
(@john-harmon)
Posts: 352
Registered
 

Yes, I had trouble last week. Finally after three days a solution came. This week there was a two day delay. Same goofy message you received.

 
Posted : 12/06/2014 2:07 pm
(@j-t-strickland)
Posts: 494
Registered
 

I got the same thing a couple of times last week. Waited a day and everything was fine.
I normally send the native topcon file, but if I'm having trouble I'll convert it to a rinex file and leave the glonass out of it. Sometimes that helps, but I imagine it just needs another day or so.

 
Posted : 12/06/2014 2:53 pm
(@fct487)
Posts: 44
Registered
Topic starter
 

So there is no reason to go collect again it will send a solution eventually

 
Posted : 12/06/2014 3:22 pm
(@paul-in-pa)
Posts: 6044
Registered
 

No Guarantee On Solutions

OPUS-RS is finicky about clean data. It is possible to get all kinds of OPUS solutions but if theC1/P1 and C@/P2 data is not clean you will never get an OPUS-RS Solution. If you cannot afford a return trip make sure you get long enough data for a good OPUS solution.

Your problem is most likely that the data is not there yet for enough close CORS, OPUS-RS wants closer CORS than OPUS works with.

The problem may be the nearby CORS data is not clean but may get cleaned up by NGS utilities after arrival, though not always the same day.

Lastly the problem may be new receiver or changing the settings on existing receivers to get the newer observables. The RINEX details sometimes need adjustment before a CORS works on a regular basis.

You need to learn to recognize if you have good enough RINEX yourself before submitting to OPUS-RS. The you need to check the local CORS data for your time periods to see if it to is good enough for OPUS-RS.

Paul in PA

 
Posted : 12/06/2014 6:52 pm
(@samizdat)
Posts: 24
Registered
 

We ran static on 3 points in the north Georgia mountains, and got the 6029 message without any other messages. Has anyone ever seen that??ÿ

Do I have to continue submitting the files on OPUS until I get a solution, or does OPUS send it when its ready?

 
Posted : 12/07/2018 5:48 am
(@mark-silver)
Posts: 713
Registered
 

Check out page 4 of my [ Best OPUS Practices document ]. It has a 'worked example' of the issue that you are seeing. Actually the entire document is worth reading and if anyone has more case studies to contribute, I will add them. I am actually working on adding some more customer foopaah examples at this moment.

I am in a unique position to maintain this FAQ because I have become the sounding board for failed OPUS-RS jobs due to static receiver sales. No one ever calls here to talk about a job that goes well. It is just a string of (mostly operator) induced failures. OPUS-RS causes us huge problems. Over and over and over and over. The same stories. Just different victims.

Sheep Ranching and OPUS-RS are very similar: Sheep are just looking for a reason to die. OPUS-RS jobs are just looking for a reason to fail. Any reason will do.

And be sure to read my joke at the beginning of the FAQ.?ÿ

?ÿ

 
Posted : 12/07/2018 6:25 am