Notepad++ can select a column of data off the side of of the group of unsorted ascii. Its awesome just for that function, saves me much time.
There is a bug in the new firmware 26 Beta 2 with regards to the new logging settings. I found it happens on both of my RS2 units primarily when the RTK Settings Update rate is set at 3Hz.
Tested Logging settings:
Constellation: happens with GPS only, with GPS + GLO, and GPS, GLO, GAL, BEI
File format: Tested both Rinex 3.01 and 3.03
At this point, it does not seem to happen when the RTK Settings Update Rate is set at 1 Hz or 5 Hz.
Left: Rinex file downloaded direct from RS2
Right: UBX file from RS2 converted to Rinex with rtkconv/rtklib 34a (from rtkexplorer)
Buenas a todos los colegas . esperando se encuentre bien queria consultar a los mas experimentados de estos receptores. Es conveniente pasar de la versión firmware 2.24.2 a la version beta 26.1.
desde ya muchas gracias
We’ve got some updates about the legacy messages issue. To ensure the messages are correctly read on your rover, please, set the Update rate in GNSS setting the same as the frequency of the GNSS RTCM3 messages in the Base mode tab.
So you need to set the update rate to 1 Hz on in GNSS Settings:
Then, the GNSS RTCM3 messages frequency should be also set to 1 Hz:
Please check if this works for you. We’ll be glad to hear your feedback.
Edited: fixed the screenshot and the information about frequency.
Exactly, this setting is just adding information about the antenna and antenna height to the RINEX header. This should make processing in various open software easier.
Thanks for the report!
We’ll take a closer look at it and we’ll be in touch with the news.
Beta releases usually contain the new features that are not yet implemented on the stable versions. However, they are not as throughly tested as the stable releases. That’s why we don’t recommend using Beta versions for the important fieldwork.
Also, please use English on this part of the forum. This will help everyone to understand your questions and help you with your requests faster.
Can I get a link to download?
You can update to the latest Beta version only via the ReachView app. Your unit needs to be connected to the Internet to be able to check for updates. To receive information about Beta releases, you will need to subscribe to the dev updates in the Firmware Updates tab. The detailed information about the updating process can be found in our Updater docs.
Currently, all of the fixes and improvements from the latest 26 Beta 2 firmware version are added to the latest stable 26 Firmware. You can check the full changelog in this community forum thread.
I have updated my M2 and now my iPhone sees the devise but when I try to connect to the M2 through RV3 app the screen goes blank and eventually I get an error message. Can I revert back to the previous firmware?
I find with the iphone you have to fully close the app and restart it on the phone to grab the RS2/M2 again.
The emlid also seems very determined to make its own hotspot, vs joining your phones.
Now can multiple points be exported all at once?
Welcome to the forum!
Please make sure the antenna is connected to Reach M2 and the unit is provided with sky visibility. All LEDs should be lit up to ensure you can connect to the unit.
To get back from the Beta firmware version to the stable one, you need to perform a reflashing procedure. You can follow the steps that are described in our Firmware Reflashing guide. Please note that reflashing deletes all the data and resets all settings.
You can use ReachView 3 app to collect multiple points with the Reach receivers. All points will be collected in one project. After the survey, it’ll be possible to export the project with all the points in CSV format.
7 posts were split to a new topic: No Fix Since 26 Firmware Update
A post was split to a new topic: RV3 functionality
A post was split to a new topic: Logs loss on new FW
A post was merged into an existing topic: Gaps in the raw data logs
Just wanted to tell you that we’re currently working on fixing this in the upcoming Beta release. Currently, the workaround would be to avoid using the 3 Hz update rate. Thank you!
2 posts were split to a new topic: RS2 antenna calibration details