I agree I have 2 days with it so far and it’s a pain especially in challenging environments like using it to find some corners under trees it’s impossible to use the way it is. and in those times, I’m not expecting it to be perfect just close enough to find my corners. this is not the only tool on the truck and for what we use it for this update makes it useless.
1 Like
Well that’s not really a “recommendation” then is it.
This policy should be dropped.
4 Likes
As this firmware is making receivers unusable can you please provide a solution, even if it means rolling the firmware back to previous stable. I’m concerned that I will be unable to, or it will be impractical to complete work in the field with the receiver behaving as it is
This is the same problematic behaviour that I had trouble with when trialling Firmware 32 Beta 3 so perhaps there should have been a Beta 4 of the IMU initialisation fix before this firmware version was released as stable.
2 Likes
Hello everyone! I don’t like this situation either. In the previous version, the IMU worked much better. In the previous version, if after losing Fix, the fixed solution was restored within a short time, then the IMU did not require calibration and worked perfectly, but now, if you lose Fix even for 1 second, you need to restore and calibrate the IMU. This behavior only interferes with work, after installing a new firmware, I almost always turn off the IMU, because it interferes with work, although it should help.
2 Likes
Have you tried to find the old firmware and install it via Reach Firmware Flash Tool installation? If the situation does not improve soon, I will try to roll back this way.
1 Like
With the new firmware, if the receiver is still for more than 30s or if you lose fix for even a second the IMU needs recalibrating . This is highly irritating and not user friendly, because you end up spending more time waving the pole around than actually doing work. The IMU worked much better before
4 Likes
After a couple more days in the field with the new firmware I am finding the same, the need to stop recording mid-feature and wave the pole around is disruptive and time wasting. Having the IMU and tilt correction was supposed to make recording faster without the need to average positions, this latest firmware is counter to that with continual interruptions to recording until the IMU is made happy again.
2 Likes
I have not tried this, but I believe that the firmware flash tool automatically offers the latest firmware. I don’t know that other firmware versions are available using this method, or if they can be downloaded for use with the tool.
2 Likes
Yes, you can, if you have saved the installation file of the old firmware.
1 Like
I previously updated the receiver firmware directly via Flow 360 software or web UI so have never downloaded any firmware packages. 
Hi guys,
Thank you for all your feedback about the new firmware. I’ve passed them on to the team, and we’ll look into the situation to figure it out. Once we have news, I will post it here.
Give me your email, I’ll send it to you.
1 Like
amaland[at]duck.com
Thanks.
Check your mail
1 Like
Hi guys,
I’ve discussed this topic with our developers. We understand the situation about the usage of tilt compensation, and we’ll look into it in more detail. If there are any updates, we’ll share them with you.
1 Like
Good day.
Has there been any updates a week later?
Or should we just live with turning the tilt off and only turning it on when we need it.
1 Like
Hey guys, I wanted to provide an update on the investigation into the performance of tilt compensation. While we have been a bit quiet here, the team has been hard at work in the background analyzing logs and trying to figure out what went wrong, as all of our tests have shown superior performance in this release.
We delivered a significant update to the IMU tilt compensation in Firmware 32, based on feedback and edge cases found during the time Reach RS3 has been used in the field. Our main goal was to make the feature as reliable and robust as possible. We now understand, based on your feedback, that we skipped a crucial scenario in our testing and development that we should have paid more attention to. It is the one with the short term loss of fix, which happens really often when the receiver is carried around. In this case, the receiver de-initializes the IMU unnecessarily aggressively. This is already being addressed by the development team and we will release a hotfix after it has gone through all the testing steps.
The scenario where the receiver is somewhat stationary, but not completely static, is the most complicated for the IMU, as it doesn’t allow for drift correction by motion, as the magnitude is not high enough, but also not by steady state, as the IMU is still experiencing some motion. If the receiver spends several minutes or more in this type of motion, we have found that it is more reliable to require a proper initialization before moving on to the next point. For this reason, we do not recommend taking long measurements. While this is typically good surveying practice, tilt compensated measurements require a different approach. The accuracy of the IMU actually degrades during longer averaging sessions, resulting in less accurate results than if the point was just measured instantly or with a few seconds of averaging.
We will push a hot-fix soon and amend our testing procedures with this scenario. I sincerely apologize for putting you in this situation, it is our main goal to deliver a very stable and reliable product and to make your work easier and not harder.
13 Likes
Thank you for the update and listening to your users feedback
5 Likes
It was for this approach to business and to its users that I liked Emlid at the time. Emlid can listen to its users, not be shy and openly admit their mistakes and try to correct all the mistakes as quickly as possible. I hope this attitude towards its users will always be.
7 Likes
Thanks for the detailed response and acknowledgement of the issue. The reputation that Emlid had this level of commitment to supporting their users was one of the reasons I moved to them.
4 Likes