We are glad to release an updated stable ReachView v2.24! This is the first stable release that supports ReachView 3 Beta. We’ve made some key stability improvements that provide more robust behavior when saving collected points as well as reducing the time to fix on RS+ compared to the older firmware versions.
Here is the whole list of improvements and fixes you can find in this release.
Allow using special characters like “/” in the NTRIP credentials
Add the recovery for surveying projects
Deprecate Bluetooth scanning initiated on the device
Support shutdown on the bottom connector on RS+
Add the ability to access from public IP
Drop RTCM2 support in Correction Input and Position Output tabs
Add shutdown indication when in night mode
RTK performance improvements
Restart RTK engine if the correction input was updated (available on all L1 devices)
Fix the issue when the position might get lost when the mobile data is lost
Allow setting up the output rate to 0.1 Hz only for 1006 RTCM3 message
Eliminate some rare hotspot drops when a SIM card is inserted
Get sound notifications on volume change back
Fix ‘Send NMEA’ checkbox glitch
Fix some Bluetooth related issues on device loading
Fix hiding manual mode when the base coordinates are received
Fix selected logs removal when leaving the Logging tab
Fix incorrectly processed antenna height from some NTRIP providers
Fix status tab units formatting
Fix LoRa constraints for Thailand and Indonesia
Fix misbehavior with the toggle on the Bluetooth tab
Fix caching survey projects and logs with the same name
Fix the “unsaved” label on the RTK Settings tab
This release is available for all devices.
Some NTRIP casters send legacy RTCM messages that are now correctly handled on Reach RS2
Some of our users reported the issues with having their Reach advertise itself as linux.local rather <reach>.local. This issue is now gone.
Handy, but dangerous, I hope the remote access can be disabled. IMHO: this is a dangerous feature, anyone can access the device, probably find some saved credentials, break your station, or consume huge amount of mobile data traffic, shutdown, reboot, …
Just my 2 cents.
I updated my two rs+ units last night and went to work this morning. In survey mode the R ratio seems to be drastically higher than I remember…999 if I had line of sight from about 100m away.
What does the reachview 3 support mean? I’ve always used the web interface. Does this mean I’ll be able to save locally on a device rather than via the web then download? (p.s. If anyone knows of a postgres friendly app that allows me to save straight to the databaseB I’d appreciate it…raw data is getting lost on personal devices)
Can you quantify what is meant by “RTK performance improvements”? Does that mean an increase in position measurement accuracy and/or precision, or instead does it refer to a decrease in time required to calculate a solution?
I hope it’s not TOO different, I literally just started feeling like a big boy user with the version I’ve got!
We haven’t faced any issues with the NMEA stream before. However, Reach should have at least Single solution status to output something. Could you elaborate on your setup? Do you try to output the position from Reach to PC?