Firmware 0.16


My Raspberryshake 4D has recently upgraded to firmware v0.16, and if I go to actions -> turn stand alon On, it asks my password but If I cancel without giving the password, it Turns ON !!!. It also turns off, cancelling without writing the password… Perhaps is there a bug??

Best regards

Hi Mario, thanks for bringing this to our attention. Indeed I can reproduce this behavior. I will file a bug report in our system and fix it for the next release.

Ok, thanks!

Indeed, could you please explain in more detail in the manual what’s happening when this option is on?

Is RS still sending data? Is It not waiting for npt to syncronize the time, then avoiding data gaps when Network and time are lost?



Hi Mario, I assume you have seen the manual page about stand alone mode: If you have, I will give a separate brief explanation for you.

During normal operation, the Shake will wait a significant length of time for an internet connection to become available (in order to start NTP services) prior to starting up its own software. This is because we try our best to adhere to seismological standards by not recording data with incorrect timestamps, prior to the system time being synced to UTC. Once the system time is synced, then services start as normal. If internet does not become available after a period of time (I don’t know the period off the top of my head but I think it’s somewhere between 5 and 20 minutes) then NTP will fail and the system will behave according to this case.

During stand-alone operation, the Shake does not wait for NTP to become available prior to starting its services. When a GPS is attached, this is not a problem; the link with the GPS is available immediately at startup, and the NTP daemon will recognize that and change the system time via GPS timing messages accordingly. If no GPS is attached, the Shake will start with the system time set to the last known system time, which—because the Pi has no onboard independently powered timing chip—has to be read from disk. This means that unless the time is set by the NTP daemon, the system will boot thinking that no time has elapsed since the last time a date and time was saved to disk.

We recommend that most users with an internet connection do not use stand-alone mode. We do recommend stand-alone mode if there will never be an internet connection available. Using a Shake in the field (with or without a GPS) falls under this category.

Hi Ian, Thank you very much for your time and help.

My internet connection at home is not so good,

and wifi often fails. All my raspberrys (4 at the moment) usually loose wifi connection. Some time in less than a week, so NPT has no time to “learn” how RS drifts. Could this explain data gaps in my data? (See precedent posts). I’m waiting for an stable firmware release to reburn my microsd, but this paragraphs make sense to me:

“When an Internet connection is restored, and NTP makes a large adjustment to the local Raspberry Pi clock (large defined as >= one sample interval of time), the data processing program will do a hard reset of the data packet timestamp, thus forcing a timestamp re-sync with the local clock.”

“If at some later time an internet connection is detected, the unit will reboot. After reboot, NTP timing will behave as described above in Case 0. Note: internet detection and system reboot is automatic”

Could stand alone help in this case? Can stand alone and npt work together avoiding reboots when Network fails? Or is It incompatible with internet ?

Best Regards,


Probably not. If the Shake boots with an internet connection and NTP only has to make minor adjustments it will typically only make one tear in the data to correct the clock and account for drift.

If it starts without a reliable internet connection, and NTP connects later and discovers a large difference between the system time and UTC, then it will reboot since large system time adjustments cause bad things to happen at the OS level. If there is no reliable internet connection at startup again, this process could repeat. This is one of the reasons I try to caution against using WiFi.

Yes, technically it could. However, it would almost guarantee the time to be less accurate. The most reliable solutions for you are either:

  1. an ethernet connection
  2. keeping your WiFi connection but introducing GPS timing

Thank you Ian, I’ll try to move it closer to the Ethernet connection once I reflash de microSD.
Best Regards