ReachView v0.4.7 update


We’ve just rolled out a new ReachView update, v0.4.7. This update if focused on improving Reach’s RTK performance.

The RTKLIB engine was updated to the newest version - 2.4.3 b16, which brings a lot of internal bugfixes. Apart from that, we incorporated some fixes from the excellent rtklibexplorer blog.

As usual, you can update in the settings tab(represented by a gear) of the app.

Fixed solution will now be more stable and easier to achieve, overall positioning results better. We encourage you to try it out!


thanks to the team of emlid!

if you can write down the changes from trklibexplorer it would be helpful to us!


1 Like

Most of those fixes are already applied on the latest upstream beta. We incorporated a fix the dynamics filter which makes it less computationally intensive. Also, one of the latest fixes, regarding raw receiver data parsing.

1 Like

Egor & Andreas,

Been testing v0.4.7 update. Most testing with limited skyview GPS + GLO using STATIC mode…

I observed that FIX was attained and held much easier than before the update. I do not think I have experienced as consistent FIX as with this release.

I have been experiencing false FIXes in RTKPOST processing with the REVERSE and COMBINED modes. This does not seem to affect realtime operation, but seems to be some bug in RTKLIB postprocessing. With the improved ability to maintain a FIX, it appears that the AR Ratio can be increased to lessen false fixes. For some reason the FORWARD mode seems less affected.

In summary, I think this is a significant upgrade. I look forward to more testing, feedback from others, and congratulate Emlid for pushing the state of the art in Single Carrier GPS with ReachView.

Richard Johnson


Hi Egor,
I would liek to compile your version of RTKLIB on my system for postprocessing reach data.
Is this the emlid_2.4.3 branch on your github?

Yes, go ahead!

1 Like

I compiled it on Ubuntu, but get when I run rnx2rtk, I get a buffer overflow error (while it workes with the 2.4.2 version).

Could you please provide more info on the error?

hi, sorry for the late reply,
I using the latest version from emlids github.
It’s working with both the latest dev branch from tomoji takasu (b19) and rtklibexplorers demo5.
here the logs:
rnx2rtk compile warning:

../../../src/rtkpos.c: In function ‘rtkpos’:
../../../src/rtkpos.c:1868:12: warning: assuming signed overflow does not occur when assuming that (X + c) >= X is always true [-Wstrict-overflow]
 extern int rtkpos(rtk_t *rtk, const obsd_t *obs, int n, const nav_t *nav)

error when executing:

 reading    : 2016/07/27 15:01:06*** buffer overflow detected ***: /../RTKLIB_emlid/app/rnx2rtkp/gcc/rnx2rtkp terminated
======= Backtrace: =========
======= Memory map: ========
00400000-004d3000 r-xp 00000000 08:06 4850456                            /../RTKLIB_emlid/app/rnx2rtkp/gcc/rnx2rtkp
006d2000-006d3000 r--p 000d2000 08:06 4850456                            /../RTKLIB_emlid/app/rnx2rtkp/gcc/rnx2rtkp
006d3000-006d6000 rw-p 000d3000 08:06 4850456                            /../RTKLIB_emlid/app/rnx2rtkp/gcc/rnx2rtkp
006d6000-008ba000 rw-p 00000000 00:00 0 
0108a000-011aa000 rw-p 00000000 00:00 0                                  [heap]
7fee211dd000-7fee211f3000 r-xp 00000000 08:05 530712                     /lib/x86_64-linux-gnu/
7fee211f3000-7fee213f2000 ---p 00016000 08:05 530712                     /lib/x86_64-linux-gnu/
7fee213f2000-7fee213f3000 rw-p 00015000 08:05 530712                     /lib/x86_64-linux-gnu/
7fee213f3000-7fee22ff4000 rw-p 00000000 00:00 0 
7fee22ff4000-7fee2300c000 r-xp 00000000 08:05 530820                     /lib/x86_64-linux-gnu/
7fee2300c000-7fee2320b000 ---p 00018000 08:05 530820                     /lib/x86_64-linux-gnu/
7fee2320b000-7fee2320c000 r--p 00017000 08:05 530820                     /lib/x86_64-linux-gnu/
7fee2320c000-7fee2320d000 rw-p 00018000 08:05 530820                     /lib/x86_64-linux-gnu/
7fee2320d000-7fee23211000 rw-p 00000000 00:00 0 
7fee23211000-7fee233d1000 r-xp 00000000 08:05 530674                     /lib/x86_64-linux-gnu/
7fee233d1000-7fee235d0000 ---p 001c0000 08:05 530674                     /lib/x86_64-linux-gnu/
7fee235d0000-7fee235d4000 r--p 001bf000 08:05 530674                     /lib/x86_64-linux-gnu/
7fee235d4000-7fee235d6000 rw-p 001c3000 08:05 530674                     /lib/x86_64-linux-gnu/
7fee235d6000-7fee235da000 rw-p 00000000 00:00 0 
7fee235da000-7fee235e1000 r-xp 00000000 08:05 530828                     /lib/x86_64-linux-gnu/
7fee235e1000-7fee237e0000 ---p 00007000 08:05 530828                     /lib/x86_64-linux-gnu/
7fee237e0000-7fee237e1000 r--p 00006000 08:05 530828                     /lib/x86_64-linux-gnu/
7fee237e1000-7fee237e2000 rw-p 00007000 08:05 530828                     /lib/x86_64-linux-gnu/
7fee237e2000-7fee238ea000 r-xp 00000000 08:05 530744                     /lib/x86_64-linux-gnu/
7fee238ea000-7fee23ae9000 ---p 00108000 08:05 530744                     /lib/x86_64-linux-gnu/
7fee23ae9000-7fee23aea000 r--p 00107000 08:05 530744                     /lib/x86_64-linux-gnu/
7fee23aea000-7fee23aeb000 rw-p 00108000 08:05 530744                     /lib/x86_64-linux-gnu/
7fee23aeb000-7fee23b11000 r-xp 00000000 08:05 530646                     /lib/x86_64-linux-gnu/
7fee23c9a000-7fee23c9b000 rw-p 00000000 00:00 0 
7fee23ce3000-7fee23ce7000 rw-p 00000000 00:00 0 
7fee23d0d000-7fee23d10000 rw-p 00000000 00:00 0 
7fee23d10000-7fee23d11000 r--p 00025000 08:05 530646                     /lib/x86_64-linux-gnu/
7fee23d11000-7fee23d12000 rw-p 00026000 08:05 530646                     /lib/x86_64-linux-gnu/
7fee23d12000-7fee23d13000 rw-p 00000000 00:00 0 
7fffaf4ec000-7fffaf50d000 rw-p 00000000 00:00 0                          [stack]
7fffaf5e0000-7fffaf5e2000 r--p 00000000 00:00 0                          [vvar]
7fffaf5e2000-7fffaf5e4000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]
Aborted (core dumped)

That seems really weird. What are you compiling on? Are you cross-compiling?

A post was split to a new topic: ReachView for Windows Mobile