It appears extending the app made some of our cache problems resurface. Currently working on a fix for this. Meanwhile, this helps.
Thanks for the kind words
Reach checks for updates automatically every boot, but only once. You should either reboot it with a wi-fi network available or go to
192.168.1.15/updater to check for updates manually.
The coordinates are being averaged. I think the approach @TB_RTK mentioned seems more than reasonable.
Many thanks to the emlid team for the continuous software improvements: you are really doing a fantastic job!
May I add to the wishlist the possibility to load basemaps or shapefiles on reachview? It would became the definitive survey tool!
Point stakeout with external data import is in the works, together with CRS support.
RTK surveying interface
Everyone who had problems with cache and a blank survey tab should update to v2.3.1. This new version will tame the cache beast.
Just a tip if you having trouble getting the update notification. Try clearing cache (or run incongnito mode) and then turn off and on again the Reach.
This is a great feature thanks for the hard work. Is there any way to download not only the average point but also all of the points collected (ie the log) without manually starting and stopping the log each time?
Or what is the suggested workflow for collecting points without live RTK communication, but post processing (PPK)?
I use time mark with an interrupter for ppk
Awesome. I love it. “Stop and go”, I like it. Thank you emlid team, you are the men.
Could you please elaborate or give tutorial of your method for PPK? How did you know you collect enough data for PPK without live RTK from base? How long you have measure rover point for PPK?
Is there any chance to have tool for collecting data for PPK without getting live RTK from Base? I tested in a construction site and I lost LoRa radio after around 400m from Base.
Thank you Emlid. This now gives the Reach the basic needs for land surveying. Any audible tones for RTK fix changes?
Here’s an example, from Lefebure NTRIP client for Android.
Audio Alert on Fix Change - When this is enabled, you will hear the notification sound when the type of solution changes. For example, if you go from RTK to Float-RTK or from DPGS to RTK.
I am considering an RTK system for a precision agriculture research project. Is it possible to use a particular button of a bluetooth keyboard to trigger point collection by a smartphone? A touchscreen is difficult to use on a field by senior researchers because they have to put glasses on to use the phone, then take them off to do the rest. Besides, hands get dirty and moist in field work.
I’m not that familiar with Reach / RS software, but if the I2C signals are available, they could be used for hardwire custom I/Os . And probably Bluetooth would be OK for remote. I defer to Emlid on this.
(I grew up on a farm. Dirty and moist & steamy …!!!)
Something that works and is simple is about to get complicated.
Please can you stop!
Create a second application for CRS conversion, point collection, shape import , etc. Reachview is simple and works. I use mapit or cybertracker on android and cybertracker on windows CE. to do all my ‘survey’ work, and they interface to my TruPulse laser. Sometimes it is good to recognise when you polishing starts to make things dull not add to the shine.
PPK requires a different approach - using RINEX logs with special events. Working on it atm.
Good point, we will try to figure something like this out.
I’ve actually been waiting for a request like this for a long time. It means a lot to see these updates might feel like “too much” to somebody. Thank you!
Regarding your post, I think the point collection is very far from “polishing”. It’s a huge feature, which actually makes Reach a capable surveying tool out of the box. We feel the need for Reach to be used independently of anything else.
We want to make it powerful, simple and integrated, but in no way plan to force it. You can still use whatever collection software you like.