Hi, the other day (April 7th) my raspberry pi appeared to have halted producing any waveform graphs and no longer outputs any data from the geophone. This appeared to have occurred at random (possibly?), and I have not been able to trace back an event to this particular time that leads to this failure.
I have attempted the following general troubleshooting attempts as per some other threads on the forums experiencing a similar issue.
- Cleaned out all components of cobwebs, dust, fluff with a soft brush.
- Changed power supplies.
- Changed the pi 3 board that the shake board attaches to.
- Checked the SDCard for corruption (there was none).
- Booted the pi 3 board without the addon board attached to the GPIO. No issues.
Attached are the logs from the device, the archive is gzipped from the tar.
RSH.RD4B6.2021-04-09T04_02_08.logs.tar.gz (290.8 KB)
Please note that the domain resolution errors are from me having the shake not attached to the network (LAN/WLAN disconnected).
This is the last image produced:
The device boots up, no problem there, SSH in and have no issue browsing about. The issues seem to arise at the raspberry shake board.
Whenever the device begins to spool up the GPIO shake board and geophone, this is the result:
2021 098 23:35:13: Setting Serial Port Name: HW Revision: a22082 / Port Name: /dev/ttyS0
2021 098 23:35:29: Unable to read Firmware version number off of Serial Port /dev/ttyS0 after trying for 15 seconds, cannot continue!
2021 098 23:35:29: Is the Pi computer connected to the Raspberry Shake Board? Please confirm and try again.
Checking /dev/, this is what I have listed for ttyS0:
root@seismo:/dev# ls -la|grep ser
lrwxrwxrwx 1 root root 7 Apr 9 03:53 serial0 -> ttyAMA0
lrwxrwxrwx 1 root root 5 Apr 9 03:53 serial1 -> ttyS0
Thank you for the logs and more, thank you for the very detailed explanation of all the processes and tests you have undertaken to try and solve this situation.
It seems a difficult case, and thus I have passed it to my colleagues in the tech team. We will take a look at all the info you have provided and I’ll get back to you as soon as I have a procedure or news.
Thank you for your patience.
Thanks for the reply. If any more information or details are needed, feel free to contact me via these forums or via email on this account.
The raspberry shake unit (case, geophone, and the blue board attachment to the pi3’s GPIO) that I have has been working flawlessly since receiving it from Kickstarter a few years ago, up until a couple of days ago.
From what I can see, it seems that the blue circuit board just flat-out stopped communicating with the pi3 board. I’ve three pi3b’s and all result in the same issue - and that is nothingness being returned despite being ‘seen’ on the /dev list. Is there a method i can use to directly query / see data returns from the GPIO’s plugged-in board?
you’re welcome, no problem at all.
It is actually the same thought that I am having because, unless there is a hidden issue somewhere that I am not noticing, it definitely seems that the blue Shake board has stopped working.
The Shake Board Tx/Rx is on GPIO pins 08/10, as shown in our manual: Technical Specifications — Instructions on Setting Up Your Raspberry Shake You would need to try to see if anything is passing through those pins, but if the Shake OS is not seeing the board at all, it could be a moot point anyway.
So to update this, am seeing “Input/Output Error” when querying the serial device directly. I can use a python monitor script to monitor pin 10 and i see some sort of data being spammed to me, not sure what though.
I am going to reinstall the OS and see if some funky config change somehow happened in the past couple of weeks.
OS reinstall completed, and something is really funky. While the shake board is once more outputting data, real-time data is also good. There is absolutely nothing being dumped to the static images.
SWARM shows the following data…
but the static files look like this:
Just as i post that, it would appear the shake has decided it was time to populate the image… it’s very squiggly! Guess that’s the result of plopping it next to my homelab equipment.
TLDR for anyone else that ever gets this issue: Something changed or (maybe?) a core file on install somehow became corrupted. An OS reinstall fixed it.
Thank you very much for showing all the steps you made to check what you were doing!
Yes, if the Shake is on a table or near some vibration source it can get very squiggly! I remember the first time I turned mine on, it was registering quite a lot.
We will add this to our protocols, so that other users with a similar problem can try the same procedure.
Thank you, and enjoy your Shake!
Just for fun, and to reinforce the importance of good siting, here’s an image between it being in a high-noise / high-vibration environment (fans, hard drives, foot steps, bass from speakers, and being up on a table) vs a properly sited location.
It makes all the difference!
Wow, thanks for sharing that example @BrettC