I notice a bug in your way to compress the log file (ubx in my case) at the startup of the reach m+.
If you unplug the device during the startup (when the reach is making the archive), the previous log can be corrupted. You should make the archive and then delete the log file, this can avoid to loose some precious log file.
Could you make a fix for that ?
Thanks for noticing this!
We have software features that help avoid such issues. However, they may not work out in all cases. Hence, we recommend shutting down the receiver safely via software and don’t recommend unplugging it manually. You can press the receiver’s icon and turn it off as shown in the screenshot below:
UPD: reworked the response
thanks for you answer. I agree that unplug the reach is not the ideal case, however, in our setup we do not have choice. In general, we never loose a log, this only happen when the reach is making the archive. It will be very nice if you can find a solution
Please send us a dataset via firstname.lastname@example.org: usual and corrupted logs with raw data debug option. I’ll show them to the team to check what we can do to prevent damaging the log.
I just send you the data. I hope you will be able to find a solution. Thanks
I’ve received it, thank you! We are checking the data and investigating which options we can provide you with.
I’ll keep you in the loop!