We are rolling out yet another update, and it is kind of huge. This is one of the biggest updates we’ve made to our navigation engine, RTKLIB, in terms of general performance improvements. This update focuses on two things. First is making solution more stable in an environment where the link is not entirely reliable(meaning LoRa and other radios). Second is restoring fixed solution after losing it in a bad, multipath-prone environment. This provided some amazing results in our tests, and should get your fix the “stuck in float” state several Reach users reported. Apart from that, we’ve fixed some small-time bugs, more details below:
- Phase-bias is reset on large residuals, making going back to fixed mode much easier, eliminating solution drifting off
- We can now use observations from different epochs, increasing solution reliability in case of correction link data loss
- RCH-806 - Sometimes downloading logs failed until you perform a refresh
- RCH-799 - Point view inside survey projects would not show big heights
- RCH-671 - Reconnecting USB on Reach RS stops the data until new settings are applied
You can now enable more constellations while using the LoRa radios, with time to first fix significantly shortened. Different update rate on different messages doesn’t lead to erroneous behavior anymore.
We have found the following base message combination to work really well in our tests:
- 1 Hz 1002(GPS), 0.5 Hz 1010(GLONASS), 0.5 Hz 1097(Galileo), 0.1 Hz 1006(base position)
We are looking forward to your test results and feedback!
We’ve released a new minor update, v2.9.2. This one includes several bugfixes and LoRa frequency band constraints for Australia.
- RCH-747 Fixed NTRIP correction input screen crashing with several casters with unhealthy mountpoint info.
- RCH-833 QZSS RTCM3 message rate will now mirror that of 1002 to avoid problems @BenLewis and @Simon_Allen have talked about in the comments to this post.
- RCH-840 LoRa will now automatically adjust to local radio regulations. After getting its location, Reach will enforce a frequency band and adjust settings if needed. You can view the available frequencies in the configuration menu. We are starting off with Australia with more countries to come.
One more thing!
We’ve finally managed to publish our native app to the iOS App store
Just search the store for “ReachView” or click this link. Please enjoy!
ReachView v2.9.3 has been released. It fixes the bluetooth output getting overfilled with data in some configurations and app interface freezes when data from serial output was not being read.