I got exactly the same problem with the firmware 26 (on 10 reach m+ unit and a RS+ unit), see my ticket number ( #43855). We need a fix urgently ! the logging system is completely broke !
The things it’s that the reach start logging with a wrong filename (one that already exist). As well, I notice that it happens only when the reach is not connected to internet (in hotspot mod).
For example, on the output of the terminal below, you can see that the reach is currently logging on Reach-raw_202105271537.UBX, but the file already exist as zip file. As well, you can see that the acces time of this UBX is 16:03. On the screenshot below, you can see that the reach is up since 4min, whereas the logging tab said is logging since 24:04 …
UglyDaisy:~/logs$ ls -al
total 7432
drwxr-xr-x 2 root root 8192 May 27 15:37 .
drwxr-xr-x 9 root root 1024 Jan 1 1970 …
-rw-r–r-- 1 root root 17543 May 18 19:24 Reach-raw_202104281550_UBX.zip
-rw-r–r-- 1 root root 2740148 May 27 15:16 Reach-raw_202105261624_UBX.zip -rw-r–r-- 1 root root 651708 May 27 16:03 Reach-raw_202105271537.UBX
-rw-r–r-- 1 root root 569544 May 27 15:37 Reach-raw_202105271537_UBX.zip
-rw-r–r-- 1 root root 163687 Apr 26 15:58 UglyDaisy-raw_202104211047_UBX.zip
-rw-r–r-- 1 root root 145073 Apr 26 16:00 UglyDaisy-raw_202104261558_UBX.zip
-rw-r–r-- 1 root root 0 Apr 28 14:39 UglyDaisy-raw_202104281436_UBX.zip
-rw-r–r-- 1 root root 192 Apr 28 14:46 UglyDaisy-raw_202104281447_UBX.zip
-rw-r–r-- 1 root root 20040 Apr 28 15:48 UglyDaisy-raw_202104281448_UBX.zip
-rw-r–r-- 1 root root 42263 Apr 28 15:50 UglyDaisy-raw_202104281548_UBX.zip
-rw-r–r-- 1 root root 899771 Apr 28 15:50 UglyDaisy-raw_202105181907_UBX.zip
-rw-r–r-- 1 root root 31662 Apr 28 15:50 UglyDaisy-raw_202105181924_UBX.zip
Fyi, actually my reach m+ is currently saving log in a file from yesterday at a random time…
Below, the screenshot before start a log, during logging, and after clicking stop
My M+ and M2 units are with the log dates issue on filenames, and also broken sometimes. This Fw26 and Fw 26.1 it’s a real lottery to know when did do the work correctly.
Intermediate solution that we have achieved so far for M2 and M + without fail for file naming and correct saving without losing integrity with “Firmware 26.1”.
Enable Record recording with Rinex 3.03 enabled (Full rate RTK Settings).
Check that the log start time corresponds with the equipment’s startup time. If the file has more logging time than the actual operation time created, stop logging and restart the log file again.
After finishing the collection, do not turn off the equipment or interrupt the power supply.
Access via APP and manually stop the log record.
Important: Download immediately. If the download is carried out later, there may be a failure in the integrity of the file.
And finally, turn off the EMLID only through the APP.
With this setup, only 3 files failed in more than 200 processed files.
Do you have any update ? We are actually stuck with 10 reach m+ units completely unusable. We are actually loosing lot of day of field with PPK data! @liudmila.slepova, can you provide some schedule ?
Thanks @m.rocha for the workaround, however we cannot deploy a such solution in production on 10 units.
Do you have some news from your dev team ? Do you plan to deploy a hotfix soon ? Or at least a way to rolling back to a stable release. We need an outlook to plan our commercial flight.
Our devs team is still checking your case. It might take some more time to understand which of the factors causing such incorrect behavior and release a fix for it. I’m keeping track of your case and will let you know as soon as there’s something I can share with you.
Now, I’m checking whether there’s some workaround we can suggest to you to bypass the issue temporally.
We’ve just released Reach Firmware 26.2 update that should fix the issue with incorrect logs saving. Please update your receivers to the latest stable and check whether it works fine for you.
Thanks a lot, unfortunately, the update is not available on the reachview app (in the settings). To update, I need to go on the ip adress 192.168.xx.xx:5000 to get the update (and its not possible on the RS+)
I’ll try today the update and keep you posted.
Exactly, with the firmware 26, I can go on the port 5000 to update the firmware. However, with the firmware 26.1, it doesn’t seems to work anymore. Did you change the port of the updater in fw26.1 ?
Thanks
The update should be available in the ReachView 3 app if your unit is connected to the Internet. In case the notification doesn’t pop up, please, check your connection to the Internet.
To reach the updater page, you need to type the following to the address bar of your browser:
Thanks for your reply. I was able to update the fw26 to fw26.2. However on one with fw26.1, it doesn’t find the update. Of course, the internet connection is up, i’m writing you from this connection
There was indeed an issue with the updating process from 26.1 firmware version on the server. But we have fixed it now. So please try one more time to update via the ReachView 3 app. Now it should be possible.
