Good Day,
Our company has a few RS2+'s and RS3’s. We just ordered and received a new RS3 and used it to log for ~3.5 hours last Friday while shooting RTK points throughout the day. Today, we went to pull the log and the zip file only had the LLH despite it being set up correctly to log. The unit is on the base firmware 32 from the factory, and we’re about to update to 32.2.
Is this a known issue with this firmware version, or in general?
Hi @chasee,
I would like to ask for the logs files from your receiver and the Full System Report. Note that the Full System Report contains some personal information, so please send it to our email address support@emlid.com.
@victor.ferreira Would this still be useful if we have updated the firmware since then?
In this case, updating the firmware will help in the future projects, for the missing logs, I’d like to take a closer look on the log files and the Full System Report. That way, I can check if there’s anything that might have caused the issue.
Thanks Victor, I submitted those earlier today.
Hi there. I have just experienced an identical issue (Rover zip file only contains .LLH file, no Rinex files).
I am using a brand new pair of RS3 units, and I’m doing shakedown testing before a big field deployment. The first thing I did while setting up my new units was update the firmware, so I am running version 32.2
I have done a couple test surveys with my base and rover pair. The first one went fine, and I have complete sets of Rinex files. On the second test, the Rover only has an .LLH file in the .zip log.
Is there an operational process that causes this to happen?? I noticed in an older post (already closed for comments) that this might happen for the first logfile after a reboot? But this was supposed to be fixed with fm 32.2
Suggestions welcome.
Thanks
I can say that I have not yet experienced the issue again, but only have used it a handful of times since the issue and the consequent firmware update. After speaking with Emlid, we were unable to identify exactly where the problem lay.
Hi Daniels,
Welcome to the forum!
We have introduced a fix for this issue in 33 beta 2, but we received a report that it still can happen in particular cases. We’re sorry for all the inconvenience. We’re actively working on it to make sure it doesn’t persist in the stable release. I’ll share any updates as soon as I have them.
For now, if you’re open to it, updating to 33 Beta 2 might help. I know that isn’t ideal, especially with a big deployment coming up. But in this version, we’ve identified that the issue occurs when using the Apply and Start button.
Hi Chase,
Thanks for your input! We’re still working on fully resolving this for the stable release. I’ll let you know once we have a solution.
Hi Inkar, thanks for the response.
I am open to trying 33 Beta 2.
First though, can I ask for further clarification on your suggested work-around re: the Apply and Start button?
In my instance of this problem (running fw 32.2), I didn’t use that button, as my unit had been configured to Autostart logging by default. And I didn’t change that or use the Apply and Start button.
Are you suggesting that, instead of utilizing the Autostart option, we should go to the Logging tab, and manually start (or restart) the logging before engaging in a survey?
If that’s the work-around, I can do that.
I also wonder if the way the logging session is ended may be a factor?
Options being: turning off power using the Emlid Flow app, vs turning off the power with the front panel button, vs manually stopping logging in the Logging tab before turning the unit power off.
I might test this today, if I have time.
Thanks,
Apply and Start workaround will work only in the 33 beta 2 version. If you’re working with the stable firmware version, I can only suggest to record log for about 5-10 seconds after starting the RS3 and check if the log is saved properly. The issue should happen only the first log right after rebooting the device.
It shouldn’t be a factor on the latest stable version. Since RS3 has an internal battery, the compression shouldn’t be disturbed even if you reboot the device.
