RS1D with Gaps sometimes others no

[korrozivelab]

Hi there Raspberry Shake team

I’m happy to be here again with you. After my RS1D arrived, unfortunately I haven’t have much time to set up my stations. So, meanwhile I’m tinkering with soldering and other stuff to create a battery backup station.

At this moment I’m testing one of my units and I have noticed that data gaps sometimes appears, despite it is connected through a LAN cable to my router. I thought it could be caused by voltage variation of my power source, so I change to another dc adapter, but got same results.

Guys, I was wondering if you could help identifying what is the cause of these data gaps on my RS1D?. Is it possible to damage raspberry shake DAQ board during cycling undervoltage operating?

Thanks in advance,

RSH.RD17E.2021-08-06T02 36 55.logs.tar (1.3 MB)

[Stormchaser]

Hello korrozivelab, happy to hear back from you!

Thank you for posting the current Shake logs and for providing all the details! From them, it appears that the gaps are caused by corrupted (like this)

2021 217 16:27:58>>	buf: {'MA': 'RS1D-8-4.11','DF': '1.0','CN': 'SH3','TS': 0,'TSM':P¡T€S
2021 217 16:27:58>>	AAºEBaƒaÐIªÔEE
2021 217 16:27:58>>	Á…‹WDIàÅW eœEDªQ+$SdE…E
2021 217 16:27:58>>	I‹QÁDIàEQ e
2021 217 16:27:58>>	5¨*]àU SLEmE
2021 217 16:27:58>>	T UBQÒIIðħÔE]…ªS«%‘gDUEØEEU	E
2021 217 16:27:58>>	ŠÖ‚BS›
2021 217 16:27:58>>		16290	441

or missing data packets (like this)

|2021 217 16:27:51>>|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!|
|2021 217 16:27:51>>|Data has been successfully received, fatal condition resolved.|

I would then advise you to check that all the connections between the sensor and the blue Shake board, and between this board and the Pi computer, are solid. They are usually the main reason for these errors that I can see in your logs. We also recommend checking the power supply, but, from your message, you have already done that.

I can also see this:

2021 218 02:33:01>>	Time adjustment M0: HARD RESET.  This will result in a one-time time-tear.
2021 218 02:33:01>>	5.0: NTP Time (Init): NTP:	1628217181.666224480
2021 218 02:33:01>>	5.2: NTP Sync (HARD): VEL Before: 1628217167.151000023	After: 1628217181.405999899	Diff: 14.254999876
2021 218 02:35:07>>	Time adjustment M0: HARD RESET.  This will result in a one-time time-tear.

which means that on some occasions the gaps are also caused by missing connections to the NTP time synchronisation servers. I don’t know, however, if these happened during tests that you were doing with the Shake disconnected from the internet, so I will leave it to you to crosscheck this.

The best thing to do would be to disassemble everything, reassemble it taking care of the connections, re-burn the microSD card to start fresh, and see if the same gaps start to appear again or not.

T hese are the instructions to prepare the new OS image:

• Please take the microSD card you have and format it before burning the new Shake OS image
• Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB like yours, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
• Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)
• Download the new Shake OS image from here: https://gitlab.com/raspberryShake-public/raspShake-SD-img/raw/master/raspishake-release.zip
• And follow the microSD burning instructions from here: raspishake-microSD-card-software-Instructions.txt · master · raspberryShake-public / raspShake-SD-img · GitLab

I followed the numbered list points to burn the files on my SD cards, and I have not used Etcher or similar software.