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!
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.
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.
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? https://github.com/emlid/RTKLIB/tree/emlid_2.4.3
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)