I am looking to use the offline mode feature for demonstrations in places where I do not expect to have internet access other than through a cell phone and need a little advice to determine the best workflow for accomplishing this. I am able to to put the Raspberry shake in ‘offline mode’ and am then able to view the data with Swarm, but it will not show real time wave data…which is what I really want to have for demonstrations. Does the real time waveform feature not work because the time hasn’t been set or is there something else I need to do? I would prefer to use Swarm for demonstrations, but I am open to using other programs if that is the only way to view wave data in real time.
You can set the data and time manually. Ssh into the device and use the command:
sudo date -s 'YYYY-MM-DD HH:MM:SS’
eg: date -s ‘2022-02-22 15:05:30’
That should be close enough for demo purposes. Don’t know if that will resolve your Swarm problem…
1 Like
Thanks for attempting to help. Prior to posting I saw that ssh is potentially an alternative, but that route is not without more learning and more work on my part. I have not found the guides for how to use ssh very helpful. There’s too many gaps in the instructions for it to be worth the hassle. I have a decent understanding of Linux, but I am trying to use Swarm because it is easy to use and works with Windows. Windows is the operating system installed on the laptop I have available for demo purposes. I am really trying to avoid having to repartition my hard drive for the sole purpose of installing Linux in order to communicate with my Raspberry Shake. My senses indicate to me that there should be an easy way to quickly setup a Raspberry Shake for demo purposes. If there is a way to do demos with realtime waves with Swarm, I’d really like to know how its done.
1 Like
Hello tadamswa, welcome back to the community!
As Philip said, it is possible that the time offset between the Shake in Stand-Alone mode and the SWARM clock on the computer is too big for SWARM to be able to display real-time waveforms.
We have a guide on how to set up a stand-alone application here: Offline and stand-alone applications (like classroom demos) — Instructions on Setting Up Your Raspberry Shake
You have already done the first part, and the second, starting from If you need the time to be close to current time, take the follow steps: onwards is what you need to set the time up, as Philip suggested.
You don’t need to partition your drive and install Linux for this, you can easily SSH into the Shake from a Windows terminal by opening your Command Prompt and entering ssh myshake@shake_ip_local_address. Once the password (which is the standard shakeme unless you have changed it) has been entered and you have logged in, you can then input the time setting command that Philip has shown.
Once done, log out, reopen SWARM, and you should be able to see the waveform in real-time.
Hello and thanks.
I did not realize from the guide that ssh was possible with Windows, so that is good to know. That does make it so the time is as close to accurate as possible from the main 24 hour helicorder viewing window. The ‘Open Realtime Wave’ feature unfortunately does not work, so perhaps that is simply a limitation of Swarm in offline mode. That was the feature I was really looking to use because I think real time waveforms will be more interesting for an audience of people to look. With the main 24 hour helicorder viewing window, the data refreshes every 15 seconds by default and I guess that will have to do for an offline demo. Thanks for the help.
1 Like
Hello tadamswa,
Yes, we recommend to use PuTTY with Windows systems because it seemed to be the best option for users not accustomed to command-line execution.
I’m sorry to hear that the realtime waveform is still not working. You could ask the USGS (who has developed and maintained the software in the past) if they have any suggestions for you. Also, you can try to download and install different past versions of the software (available here: USGS: Volcano Hazards Program) to see if the issue is caused by some more recent implementations.
No problem at all, you’re welcome!
1 Like