Since the new firmware update, my base does not automatically start sending out corrections via LoRa once it’s position is established. I have to configure the radio, which is already set to broadcast corrections via LoRa, to broadcast the corrections via LoRa. In other words, even though it already says that output is set to LoRa, I have to open the output settings, select the radio settings, and save it as is to get the radio to actually broadcast. Is anyone else having the same tedious problem? With previous firmware, I did not have to bother addressing the output every time because its already set to broadcast via LoRa and it does.
Have you been able to resolve this? If so, please advise.
What is the firmware version you are talking about ? Which one do you use now, and which one used to work fine ?
I’m on 30beta1. The previous firmware worked fine.
Thanks for letting us know about this!
If you’d like to get back to the stable firmware version, you can go to Beta updates in ReachView 3 and tap the Roll back to stable version button.
I sent the full system report. I’m hesitant to revert because I do enjoy the faster startup and don’t want to have to go over all the settings again. I’ll just wait for the next update.
I’ve received it, thanks! I’ll check the report with the devs and let you know what we’ve found then.
We’ve found the issue causing such behavior. The devs are working on the fix and should release them in future updates.
Thanks for helping in catching this bug! Once the fix is released, I’ll post an update here.
The fix for this bug is out in 30 Beta 2! Don’t hesitate to let me know how it works for you.
It seems that this problem is back. I’m running 30.3 beta.
Oh, that’s quite unexpected. Can you please share the Full system report from your receiver with me, then? I’ll check this with the devs.
Here it is!
Thanks! I’ve downloaded the report. I’ve removed it from your post as the report contains some sensitive info so it’s better not to share it publicly. I’ll get back to you with the news soon!
I’m back to let you know that we’ve just released Reach Firmware 30 stable release that should resolve this issue. Please, update your device to this firmware version to check how this works for you. In case of any issues, don’t hesitate to let me know about them!
Is the change also applied to the new beta?
This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.