Error returned from OPUS... twice!

Reach RS2 / RS2+ RTK / PPK configuration
1

I’ve tried twice at different locations to get a static solution from OPUS and have gotten the same error. Can anyone suggest what I’m doing wrong?

FILE: NFDS_Base_raw_20240809122506.24O OP1723212683368

2005 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

I set the base up using the OPUS logging settings with RTCM3 backup and logged for one hour both times. I am receiving corrections from the FL NTRIP service - could that be the problem?

Thanks in advance!

3

This could be due to several issues

  1. Is the receiver a dual frequency unit ? OPUS will not process single frequency data.

  2. Is this a file with only a single point data ? Files with kinematic data will not process. Make sure the file you submitted has data only for a single point.

  3. Have you tried other CORS surrounding your point ? As stated in one of the error messages “6029 After the single baseline analysis, fewer than 3 useable reference stations remain. Aborting”. Apparently some of the CORS selected by OPUS either have erroneous data or are offline.

You can select other CORS here from the map

https://geodesy.noaa.gov/CORS

If the data submitted has a lot of multipath, OPUS will not process or it will give a low accuracy solution.

Make sure you follow the guidelines here

https://geodesy.noaa.gov/OPUS/about.jsp

2 Likes
4

Thanks Bryan! I resubmitted this morning, a few days later, and got a successful response.

So, is waiting a day or two crucial?

1 Like
5

Usually the next day, sometimes the day of observation.
It’s usually a hit or miss.

All CORS data is usually available within an hour of each hour. Using Javad’s DPOS service (it’s just like NGS OPUS), I can usually submit within an hour of observation time and have a result. Javad’s DPOS is only for Javad receivers.

If using OPUS, I’d wait a minimum of 2 hours before submitting. In your case the next day. I think the CORS data is possibly checked before being made available.

2 Likes
6

In general, waiting until after 5 PM the next day is a decent tactic because the OPUS system replaces the ultra rapid ephemeride data with rapid ephemeride data AND it is better aware of which of its CORS have data that pass some quality tests.

2 Likes
7

Hi @kevin3,

As is common here, you seem to solve the problem just by bringing it up. Let me add a quick note:

OPUS relies on precise satellite orbit (ephemeris) and clock data to deliver high-accuracy positioning results. These precise data sets, called “final” or “ultra-rapid” ephemerides, are provided by agencies like the International GNSS Service (IGS). However, they aren’t available immediately and are typically released about 24 hours after the data is collected.

That’s why you need to wait at least a day before submitting the logs.

8

Thank you to everyone for the great info and your willingness to impart wisdom to the masses!

Kevin

3 Likes
10

Just an FYI: the NGS recently updated its OPUS BETA product, which computes solutions using data from multiple satellite constellations.
https://beta.ngs.noaa.gov/OPUS/

I’ve been using it for the last few months. So far, so good.

1 Like
11

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.