NTRIP corrections issues

I have a known point that my base is over but I wanted to see how close my NTRIP Keynet service would be with the EMLID RS2+ however I’m not getting the results I would expect and I may be doing something wrong or understanding how EMLID is processing the live corrected data. I have a RS2+ and I have the input as my NTRIP service. The NTRIP service has quite a few stations near me and has always given really accurate corrections with a R10. I see the corrections live in the app but the elevation data I"m seeing live isn’t even close its several feet off.

Where did the known point come from? Network or ground level-loop? Are you using the same CRS?

3 Likes

The known point came from recording a 2 hour manual observation and correcting it through Opus. We did this with both our RS2 and our R10 that had very close results within 0.05 of each other.

1 Like

I think this is part of the answer to your issue. OPUS is a short term 2-hour observation that may use up to 5 base stations to solve your position. It starts with 3 which may not be the same 3 that your network service is using. Is your network using VRS or single-base?

Another issue with OPUS is that it does not use GLONASS. You might try NRCAN and see what results you get. What confuses me is how you can get essentially the same position from OPUS with both the R10 and the RS2+ (which you should), but you are getting two different results from the CORS network, by feet no less. Were the observations on the same day and time of day?

The only other thing I can think of off the top of my head is the number of integers each receiver is using and how they are rounding. A degree in lat or lon is around 60 miles so 1/10000th of a degree is around 3ft. I have always used NRCAN so I can’t speak to OPUS variables other than that but I am sure someone can add more detail.

Hi Dave,

Thanks for the details about your setup! Let’s investigate this elevation mismatch.

Have you specified the antenna height in the logging settings and when submitting to OPUS? Also, in which datum does your NTRIP service send the corrections? It’s important to ensure the same geoid model is specified when creating a project.

Would you mind sharing the logs and the CSV file with me? I’ll take a closer look at them. You can send them in a PM or to support@emlid.com

1 Like

BETA OPUS-S 5.0.1 does exist, but the CORS sites may not support all constellations. So, the NGS Map is used to find what each station has by clicking on a station. On the Beta OPUS site, one might include the desired stations wanted…like this
KSWK
KSU1
NERC
Long story short, I find too many results like this
OPUS aborting
1025 One of the CORS sites that was selected from the pull-down menu
1025 is not available for the day in question or it did not meet the
1025 quality control requirements. Please select another CORS site
1025 to be included in the processing and re-submit the data.

1 Like

Definitely worth a try. I tried it specifically for this reason, but haven’t had any luck with it.

Each CORS site must be evaluated (pic below), and only record on Emlid receiver what CORS sites are selected to use at Beta OPUS. If Beta OPUS decides what sites will be used, they can be far way from your location…off the charts:-)
Screenshot 2024-10-04 114804

1 Like

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