About PDOP value, Reachview 2 shows it, while Reachview 3 doesn’t (or I couldn’t find it).
I run the same test again. This time Fix was faster. The RS2 was static on the same point for about 1:40 hour, and now variation in Z was less than the first test. There is a “jump” at the beginning and from 14:07 the maximum variation is about 15cm.
It´s not perfect, but for 53km baseline maybe is reasonable. Variaton in E/N is about 4-6 cm.
Z value for “Position” from the “Solution LLH” file. 15cm difference over time.
this one seems to process much easier. However, Looking at GPS alone, you still have issues with your PDOP.
However, I still think it somehow the ntrip playing up. Can you get between 2 CORS and process against both in PP?
I don’t know… 53km for a base is kinda pushing it to the limits. We use Javad receivers and even in a 20 point network we just completed, most of the baselines were about 10-15 km apart. This was a two county project for aerial mapping for the state. Overall accuracy per point was less than 0.01cm vertical/horizontal, static observations in clear sky environments, 1-hour observation per point. I even used my 2 M2’s on two points as a check, great results with them using the HARXON-HXCGPS500&NONE antenna.
As a side note, we even included three CORS in the network, all of them were less than 10km from the main points. Most of the CORS in our area are spaced about 30km maximum distance.
You need to look at Reach’s data sheet for their machines.
Yes I know 53 is not the best distance, but is the nearest CORS I have, so I can not run the test at a shorter distance.
What I was trying to figure out is why the RTK solution was “Fixed” and the Z value changed through time, 1m in 1 hour. I would prefer it to be “Float” or that Reachview gives some warning that the “Fixed” coordinate may not be good.
I would like to have 2RS2 to run the same test at a logical distance (2-3km) but I don’t have them.
I do have a M+, so maybe I’ll try with the Emlid Caster Beta and RTK to see what results I can get at shorter distances.
Why not establish your own CORS for the point you have… You sure enough have the data to determine precise positioning. I would simply PP the data you have with surrounding CORS to determine the position. You’re not getting anywhere with a 53km RTK baseline… atmospheric issues and other factors will limit any RTK value that you’re getting now.
I’ve got two M2’s (dual freq) that I use as static receivers. You really aren’t getting the benefit of having an RTK or RTN system if M+(single freq) is base and the RS2(dual freq). It may not even work from reading on the forum. Best to use dual freq. for both receivers, greater range, stability. You have the option of LoRa, which I haven’t tried yet as I have mostly Javad gear here. There are some simple settings for the radio’s listed on Emlid’s site here. I’d advise you to read thoroughly thru the recommendations.
I’m planning on buying the LoRa soon as something to experiment with and possibly to set up a base via internet, doesn’t look that hard; just haven’t had the time.
The behavior you experienced is not natural for Reach receivers and rather unexpected. I’ve checked the logs, but it seems we need more data to investigate it further.
Bryan and Christian are right: with such a baseline, the number of common sats you have may not be enough, and you may experience difficulties with calculating fix solution. Still, such conditions should not lead to the situation you encountered.