We’re using a regular Reach as a base and a Reach RS as a rover in an open field within an urban environment, and can’t seem to get a consistent AR validation ratio above 3.
Playing with all of the RTK parameters seems like it would jump into FIX more often than it has before, but it still usually hangs around 1.5.
Satellite signal doesn’t seem to be an issue, as we’re consistently getting above 5 green bars on both the base and the rover. This is with the base on a tripod with a ground plane; our goal is to have this work in a rural environment in Turkey. Here are pictures of the setup.
We don’t have the resources to do post-processing while in the field, and need to ensure we can get fixed solutions before we leave this summer.
Just looking quickly through your logs and photo i have couple things.
by looking at the logs i can see alot of noise and rover is missing radiolink with base most of the time.
The first part is to noisy to be used, which leaves us with the last 10-12min where you could get fix.
I see powerlines above your rover, that means trouble and obstructions around at low angle. By adjusting mask angle to around 25 degree and using gps/glonass/galileo you should get fix. But use continuous and survey several times with some time apart to rule out bad fix.
3.Watch your logs after a job if you had trouble, it tells you alot you can learn from and use next time around.
Something wrong with the correction link. Seems like it barely appeared during the log. Please provide two system reports and describe the way they are connected.
We use a mobile hotspot on a phone and connect both the rover and the base to the hotspot. For the base we output corrections using TCP on port 9000, and then for the rover we listen on the same port with the base’s local IP address.
We’ve also used the same setup on different wifi networks from different devices with the same results, usually the AR validation ratio hangs at ~1.5.
From the settings I can only see that the elevation mask is a little too high. In general, more information is better, even if it’s “low quality”. I would suggest trying in a better environment first. First times setting RTK up are often hit and miss. Once you find your workflow, you can start experimenting with worse conditions.