RBoom not online, install adivice

I have had an RBoom since the kickstarter. It went off line and I just redid the SD card now. The webpage comes up, but it says the server is off-line. The log says it cannot find the type of sensor. Anyone have any thoughts? Logs included and there is no issue with power reliability
rsh-fe.server.log (339 Bytes)
rsh-fe.output.log (898.1 KB)
rsh-fe-hst.log (1.1 KB) seedlink.log (642 Bytes) SLPurge.log (96 Bytes) postboot.log (608 Bytes)
gpsd-mgr.log (236 Bytes)

Hello hans.cunningham, welcome to the community!

Thank you for those logs and for explaining the problem, but could you post the whole zipped set? They are downloadable from the Raspberry Shake’s web configuration page, accessible via the rs.local address, then clicking on the “Download Logs” button.

There are other files that can give us a broader view on the issue.

From the postboot.log it appears also that there is no data read from the geophone. Can you confirm the connection between the geophone, the Shake board and the Raspberry Pi?

Can you send some pictures of the unit so we can take a look there too? Thank you.

RSH…2020-08-22T22_59_46.logs.tar (737.5 KB)
Thanks for the rapid response. The build is the same one that I have been running for the past two years. It is the geophone board sitting on the Rpi in the enclosure provided. No change whatsoever. I use a RPi 3B v2. It has been running for the past two years. It was a vanilla install and build. Autoupdates. Of note, the home page doesn’t display the model of the RPi either.


everything in the log files point only to the fact that no data is being received on the serial port of the on-board Pi. this could be either cables not connected, or possibly corroded over time, but without a visual examination, it’s hard to tell.

if you can log in to the unit using ssh, please run the following command directly to confirm data is streaming to the Pi:

> cat /dev/ttyS0

and report back what output this returns.


Thanks, much appreciated. The pins look fine, but I will switch out the RPi for another and see if that solves the problem. The Boom itself is indoors so corrosion shouldn’t be a problem. It sits near a server bank of RPi‘s with reliable power. Hopefully the RPi is the problem, and not the Boom. That would frustrate.


1 Like

Finally got off work. Tried cat /dev/ttyS0 and there was a streaming output of nonsensical data, an example of which is included below:
RS?EY?ն?EڞTBS?DI E.pdf (52.4 KB)

well that’s very interesting…

to confirm this is not due to the serial port being wrongly configured, please try again executing the following two lines and re-send the output:

> sudo stty -F /dev/ttyS0 230400 min 0 time 5 -isig -icanon -iexten -echo -echoe -echok -echoctl -echoke -opost -onlcr
> cat /dev/ttyS0

thanks in advance,


Thanks for all your help. It ends up being a defective pi. I switched out the Pi and put in an RPi B+ and everything is working just fine. I guess I’ll try and troubleshoot the RPi. Again thanks for the help. I am back online with AM.RC27C.00.HDF on the beautiful straights of Juan de Fuca. Best wishes and thank you again

1 Like