Data not saved on the local disk when internet disconnects

Hello,

I hope you are doing well.

I have been facing some problems recently with my RS3D. It all started after changing my internet connection from 4G (using a USB dongle) to an ethernet connection. The instrument disconnected from the internet for a while (did not appear online). I went to the instrument and rebooted it, and then it went back online again.

The actual problem is that, while the RS3D was offline, the streams were not saved at all on the SD card. My understanding is that it should save the data locally even if it is not connected to the internet. That is, I did not find the MSEED files corresponding to the days when the instrument was disconnected from the internet.

My questions are:

  1. Is this behavior of MSEED files not getting saved normal?
  2. If not, can the log files (attached) reveal the reasons?
  3. Can formatting the SD card (burning the Raspberry Shake OS image again) solve the issue?

Thank you in advance.

Regards,
Houssam AL JAMAL

log_files_RS3D_190126.zip (354.4 KB)

Hello Houssam Al Jamal, and welcome back to the community.

Regarding your questions:

  1. Your understanding is correct. Even if the Shake is not connected to the internet, the mSEED files will still be recorded and saved locally.
  2. Yes, the logs revealed the issue. Thank you for attaching them.
  3. Potentially, but let’s try something else first.

Booting appears to be ok, there are no issues while the instrument is starting. The problems begin a little later, with this series of errors:

2025 308 18:21:49>>	No Data has been received from the MCU in 12 read attempts.It appears the MCU is not transmitting data.  This is a fatal condition and should be investigated if this condition persists!
2025 308 18:21:49>>	Data has been successfully received, fatal condition resolved.
2025 308 18:21:49>>	internal error: buffer overflow!  cannot process read data...
2025 308 18:21:49>>	buf: {'MA': 'RS3D-8-4.13','DF': '1.0','CN': 'EH1','TS': 0,'TSM': 0,'TQ': 45,'SI':  5000,'DS': ['3F7C','3F2D','3F5B','3F2F','3EA0','3EC9','3F5F','4006','3F7E','3ECA','3F5F','4023','3F9A','3F13','3F9E','4091','4012','3EF2','3F68','4083','3FF8','3F01','3F70','4060','3FC9','3F0±uAe]‘EEÄ«Q‹%Ac\E1E
2025 308 18:21:49>>	UˆEQ Ae]E!…‹׉³ÔU!˜ªWdFYÐY AeM‘E1	U
2025 308 18:21:49>>	!ÆU

The gibberish above, paired with buffer overflow and MCU errors, is usually a symptom of insufficient power supply, where the Shake cannot get enough power to either start or work properly. And this is likely why data was not saved.

I would recommend checking whether the current power supply continues to deliver a stable voltage between 5.0 and 5.2V and a current of at least 2.5A at all times (3.0A if the Raspberry Pi board being used is an RPi4), as a decrease in power could lead to data service interruption. If you have another Pi power supply that you know is in working condition, please try exchanging the current one with that and see if the Shake now appears more stable. Also, try different wall sockets, and if you are using it, do not use a multi-socket extension.

A second check you can do is to see if all the connections between the sensor, the blue Shake board, and the Pi board are still solid and free of dirt or other elements that could compromise transmission. If you decide to disassemble the Shake during this process, please refer to our recommended ESD (ElectroStatic Discharge) guidelines and assembly/disassembly video guides here.

Lastly, I would recommend re-burning a completely new microSD after formatting and erasing all its data/partitions (you can use DISKPART for this, as it is very efficient), and then see how the Shake behaves with the newly installed system, possibly resolving the issues we are seeing. I will leave the burning instructions link here for your convenience: microSD card topics .

In our experience, the problem is usually related to insufficient power supply, so the first test should help.

Let me know how the checks go.

1 Like

Hello,

Thank you very much for the detailed answer. I will try the potential solutions you mentioned and keep you posted as soon as possible.

Regards,
Houssam

1 Like