Hello,
As the title suggests, I have a Raspberry shake that is designed to operate in a remote mountain-top location, without internet, and operating on solar setup. The shake is configured to run in standalone mode, and it has a GPS antenna attached (USB purchased from Raspberry shake).
It seems that when booting up, the Data Consumer and Data Producer do not start. It seems they stay off indefinitely. However, if I issue the rsh-restart
command, the producer and consumer start up and the data starts being written to the archive.
As this is a remote instrument and may shut down over the winter periodically if the battery power drops, I am trying to sort out why the producer/consumer are not starting up.
The simple, ugly fix is simply to put an rsh-restart
command in the crontab, and run that some number of times per day, just to make sure that they start up if not running. However, I assume that restart will result in a few seconds of data loss during the restart cycle. Not a deal breaker by any means, but if it can be avoided, that would be great.
I will attach some log files to this thread tomorrow, but I wanted to post in case there was some obvious answer as to what may be stopping these from starting up. Ie, if there is no NTP time enabled, and the GPS does not have a timing lock when the device boots, will the producer and consumer wait until the GPS has a lock to start? In the brief testing I did, even if the GPS was not yet locked, issuing the rsh-restart
command resulted them both starting up, even though there was no GPS PPS signal.
Also, for full disclosure, this RS is in a custom enclosure and has two other boards in the GPIO stack, with the shake board still being on the top. We are using a Power Hat connected to the 12v solar system to power the pi via the GPIO pins. And also in the stack is a custom PCB also connected through the GPIO that monitors the battery voltage of the 12 volt power system, acting as a smart LVD/LVR. Essentially, it is an LVD/LVR that gives the PI time to shutdown gracefully. Then, when the LVR condition is reached, it issues a reboot to the PI board to start it up again. As best we can tell, none of the GPIO pins are interfering with each other. But if we cannot find any other reason why this is happening, then we will start diving further into any possible issues with the sleep/wake controller.
Thanks,
Andrew