Reach RS3 log issue - No RINEX, only LLH when zipped

Reach RS3 Getting started
1

Hi Emlid,

I’ve had my RS3 unit loose its log file at the compression stage twice in the last several days, with a number of other logging sessions working without issue in between. Is there any way of recovering the original uncompressed log files from within the RS3 unit? (or recompressing them?)

In both cases where the loss occured the zipped log files only contain the LLH file despite the RS3 being set to record RINEX 3.03 and the other backup files.

raw data. rinex 3.03
position track llh
base correction rtcm3
backup (ra data) ubx
backup (base corrections) rtcm3

The Firmware version is 32 Beta 3 (I haven’t updated to the latest version because of the issues with the tilt readings requiring movement of the unit. And, until the last few days I’ve had no issues with the RS3.)
Emlid Flow Version is iOS 11.2.
Connecting via a GL.iNet GLe750V2 portable Wifi Router.

In both cases the following procedure was performed:

RS3 Base unit started up and allowed to obtain its position via averaging for 10 minutes.
Log files auto start when the unit starts up.
When I connect to the RS3 via Emlid Flow iOS app, I check that the logging has started, and that the log file size is growing.

After running the various jobs (either gathering GCP locations via LoRa, or providing local NTRIP to an RTK drone), the logging was stopped manually via the App.

In the first case,(around 30-40 minutes of logging) I didn’t make a note of the size of the saved log zip, but waited until the RS3 had finished compressing the file before using the iOS Flow App to shutdown the unit, I only discovered the file was miniscule when I downloaded it at the office.

In the second case today, after 4+hrs of logging, I manually stopped the logging via the app, waited for it to finish the compression, then noticed it was a very small size zip… Oh no! :face_with_peeking_eye:
Then I shut down the RS3 from within the iOS app and gloomily made my way home for a strong coffee!

Help!

I’ve exported a full system log, so I can send that to you if you want. But once again… is there any way of accessing the original uncompressed log files on the RS3 unit itself to recover them? (ie do you have a hidden 'deleted files" bin that you can ‘undelete’ them from with some secret Emlid wizardy?

Yours forlornly… in hope…

3 Likes
2

I am having a similar issue today. Using RS3 with the latest 32 firmware update. At two sites, the app showed the base was logging and when I was done, i stopped the logging process on the App. The problem is that neither logs show at all now on the RS3. This is very concerning. Is there anyway to recover these base station logs?

1 Like
4

Hi @ElectroNick,

Thanks for your email! I’ve received your data, and we’re looking into it. I’ll follow up with you via email.

@eric.gilson, could you also generate a Full System report and share it with me? What was the date and time of this log? Since it’s sensitive data, you can send it directly to support@emlid.com. Thank you!

1 Like
5

Hi @inkar.madikyzy,

The two dates/times for the missing logs are:

19 Sept 2024. from 10:31 GMT for 4Hrs 44min. - shows as 1.14Mb
and
16 Sept 2024. from 12:45GMT for 1Hrs 06min. - shows as 0.26Mb

Both were auto started, and stopped manually through Emlid Flow and the system not shut down until the compression had finished.

The system was used on the 17 Sept 2024 at three separate locations without any issues.

Thanks

1 Like
6

Hi there,

Thank you for sharing all the data! I’ve checked it with our developers. We have found possible reason for such behavior and actively investigating it and working on the solution. We understand the importance of your project and are working on resolving it quickly. Once I have any news, I’ll let you know.

From what we’ve gathered, the issue appears only with the first log right after rebooting the device. As a temporary workaround, you can start logging for a few seconds after rebooting to see if it saves.

Thank you for your patience as we work on this.

2 Likes
8

Hi guys,

I’m glad to share that we’ve just released firmware version 32.2, which includes a fix for instances when only the LLH log is recorded. Could you please update your receiver’s firmware and see if it resolves the issue?

Thank you!

2 Likes
9

Thanks Inkar, I’ve already updated the firmware and will let you know if there are any further problems.

1 Like
10

Hello, I have had the chance to use the RS3 in both base and rover configurations. No further occurrences of only the LLH being recorded. Hopefully, this issue has been solved for good!

4 Likes
12

Hi Inkar,

So far so good… I’ve had a couple of logging sessions with two RS3 acting as Base & Rover and the logs have worked as expected.

Thanks to everyone for sorting the issue quickly.

Nick

7 Likes