We’ve just pushed a new update to our stable channel - v2.14.0. As promised, this version has been released for all Reach devices. New features, previously teased with dev updates, are now available for Reach M+ and Reach RS+ too.
This post will quickly glance over everything that has been added to our receivers over the past two months. You can view my post about dev updates for more detailed descriptions.
Reach will now correct GLONASS inter frequency biases, allowing for GLONASS AR with non-Reach bases, such as NTRIP casters. The general recommendation starting with this version is to always have GLONASS AR set to on.
Beidou processing significantly improved as well.
Beautiful new survey project view. The project view has been reworked from the ground up and is based around the map with all of your collected data.
Fast and pretty Wi-Fi settings tab from Reach M+ and RS+ is now available on all Reach receivers.
Reach will now restart the processing if base position changes during processing
NMEA feedback to NTRIP casters will contain a real solution status, not just single
You are not required to punch in any info when creating a new project, you can just click next
Disconnect dialog has been reworked to be more friendly
Reach will now not reconnect to a different device and will ask you to refresh the page
ERB fixed to include DOPs and number of satellites while the solution is single per @rrr6399 request
Fixed a bug with the battery indicator that would sometimes not show the fully charged battery state
iOS Native app
Our native app for iOS has been updated with great improvements in UI responsiveness. If, for some reason, you have automatic app store updates turned off, I strongly recommend going for this one.
New images in docs
We’ve updated ReachView image in our reflashing guide to the latest version for all devices. If you need to reflash your Reach, you can flash it to v2.14 directly.
To sum up, this update is jam-packed with improvements in all areas - positioning, UI, performance.
A huge thanks to team for working so hard on all of this. And, of course, to you, helping us with testing and guiding us with your feedback.
So continuing with the features of the previous dev version.
In this new stable version should Glonass Ar always be on?.
The mask down to 5, should be gradually once you get “fix” or lower it from the beginning ?.
The choice between RTK settings, like that of fix-and-hold and continuous is one that is made during processing. When you are actually doing RTK, that choice is made at the rover end. When doing PPK processing (after data collection), then that choice is made afterward in the processing software.
A simple rule is that for your base station, the only settings under the ‘RTK’ tab that you should be concerned with are these two:
GNSS systems (GPS, GLO, GAL, etc., etc)
sample rate (1Hz, 5Hz, 10Hz, 14Hz)
They matter for both RTK and PPK.
*Now, the exception is if you are calculating your base’s coordinate by using an NTRIP connection, then your base is also acting as a rover. In that case my rule does not apply.
We recommend to set Glonass AR to on always starting from v2.14.0. We plan to remove this setting at all starting from next stable update if there are no reports of issues. Mask down to 5 can be from the very beginning.
@wizprod it is already in there and working by default. Glonass was just more tricky and it took us some time to crack it.
We recommend to always use 3 main systems for RTK. GPS+Glonass+Galileo or GPS+Beidou+Galileo. All of these systems are supported for AR now and even with mixed receivers (for example when getting corrections from NTRIP station).