Hello,
One of my shake ( AM.RE0E2) does not produce continuous data since few weeks. Let say around 15% of the total amount expected. This is not due to transmission issue (because the archive on the shake is also lacking a lot of data).
Is there any specific test to be done to make a diagnostic ?
Or do you have any idea of the source of that issue ?
Thanks
2 Likes
Hello Mickael, and welcome back to the community!
From your description, it seems that the issue could be something related to a lack of power supply or other possible sources. However, we need more information to be sure of this.
Could you reboot the Shake and see if its LEDs are behaving as expected here: Technical Specifications?
Could you also download and send the logs from the Shake in question?
And, to have more data available, can you upload one of the helicorders on the Shake that you deem most representative of the lack of data issue?
Thank you!
Thanks for your answer.
The shake is on the field, so I canât actually hard reboot it (I have tried the soft reboot), but I canât watch the ledsâŚ
I have attached the log files.
About the helicorder, they look like thatâŚ
Except today, that seems a little bit better but not totaly complete.
Thanks.
RSH.RE0E2.2025-02-14T16_30_00.logs.tar (4.9 MB)
Hello Mickael,
Thank you for both the screenshots and the logs from the Shake! In more detail:
2025 045 16:29:47>> 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 045 16:29:47>> Data has been successfully received, fatal condition resolved.
2025 045 16:29:47>> internal error: buffer overflow! cannot process read data...
2025 045 16:29:47>> buf: {ĂżOkË
2025 045 16:29:47>> M¤eW27S ÂĂâAĂE
2025 045 16:29:47>> 'AQ0ZE
As you can see, the logs youâve provided contain some âgibberishâ mixed with âno data receivedâ errors.
I would recommend checking (and this is the very likely cause of the issues youâre seeing) if the current power supply that is being used is continuing to deliver a stable voltage between 5.0 and 5.2V and a current of at least 2.5A at all times, as a decrease in power could lead to data services interruption. If you have another Pi power supply that you know is in working condition, please try to exchange the current one with that, and see if the Shake now properly works for longer.
A second check that 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 from dirt or any other element that could compromise transmission. If you decide to disassemble the Shake when doing this, please make sure you are using proper ESD (ElectroStatic Discharge) protection (such as gloves, etc.), as electronics do not like static electricity too much.
As a last resort, and if all these checks come out as positive, then I would recommend re-burning the microSD card again (or using a different microSD) after formatting and erasing all its data/partitions first (you can use DISKPART for this as it is very efficient), and see how the Shake behaves with the newly installed system, removing potential issues derived from corrupted files. I will leave the burning instructions link here for your convenience: microSD card topics
I understand that, with the Shake being in the field, the advice above will be challenging to implement in a timely manner, or with relative ease. However, the cause of what you see is one of the described three, so I think a visit to the Shake has become necessary.
I would prepare a new microSD card beforehand, a new Pi board and, depending on how the field installation is set up, a new power supply. In this way, you can do all checks with a single trip.
Thx for your answer. At a first stage, I have gave a new power supply to the person that hosts the shakeâŚI will see if its change anything.
2 Likes
Itâs no trouble at all.
Good idea! Letâs start with the power supply and see if that brings any improvements to the current situation.