Emlid

ReachView v2.14


(Egor Fedorov) #1

Hello everyone,

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.

Features

  • 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.

The new survey project view:

The new Wi-Fi tab:

Fixes

  • 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.

Best regards,
Emlid team


ReachView v2.15.2 dev update - Point stakeout
Trying to subscribe for dev version
Feature Request: Web Map Background
(Timd1971) #2

AWESOME!!!

You guys are genuinely AWESOME! Thank you! Such a great company, products and people (and community!)!


(Dmitriy Ershov) #3

Mapit GIS doesn't show correct status anymore
(Erro Alfaro88) #4

Hi.

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 ?.

Regards


#5

15 posts were split to a new topic: Reported baseline distance vs. measured


#6

A post was merged into an existing topic: Reported baseline distance vs. measured


(Erro Alfaro88) #7

The continuous mode must be in the two antennas (base and rover)? Or only in one of them (Base=fix and hold, Rover=Continuous)?.

I would appreciate your help

Regards


Reported baseline distance vs. measured
#8

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.


(Igor Vereninov) #9

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.


(Christian Grüner) #10

@igor.vereninov, are there plans to make AR available for the Galileo system? Seems to be the only missing major system, at least in RTKlib.


(Igor Vereninov) #11

@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).


(Christian Grüner) #12

Ah, didn’t know that!
GPS having the 2 different modes, Continuous & Fix-and-hold, how are Glonass and Galileo doing their AR?


(Igor Vereninov) #13

According to the GPS setting.


(Christian Grüner) #14

Very good to know, thanks!


(Erro Alfaro88) #15

Thanks Bide


(Erro Alfaro88) #16

Great. Thanks Igor


#17

I tried Glonass AR with SAPOS data in Germany. Worked without problems.
Great improvement!


(Dmitriy Ershov) #18

Hi everyone,

Note that we’ve also 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.

I’ve edited the original post.


(Tatiana Andreeva) #19

16 posts were split to a new topic: Unstable Bluetooth connection


(Tatiana Andreeva) #21

4 posts were split to a new topic: Missing “collection start” and “collection end” values in the csv export