GPIO Python 2 script for the TechResort Info-Fi project.
Script written by Ethan Brierley
Extra contributions by David Bi (hardware) and Sean Firth (documentation edits)
What it does
This Python 2 script checks to see if services are running and shows a status on a single LED to the end user, to check if there is a problem. It also features the option to power off the Raspberry Pi if a button, connected to the GPIO pins on the Pi, is pressed.
This script is designed to be as easy as possible for a fault to be diagnosed (eg, the required services are not running) and then safely shuts down or reboots the Pi if necessary.
How it works
The script runs the bash command
pstree that outputs all of the sevices that are running on the Pi. The script then checks for the services
status 1 = Everything is working = Light stays on while button is pressed.
status 2 = Crashed services = The Pi is running but one or more of the services have crashed, the light flashes on and off.
status 3 = Nothing set = Flashes in a morse code rhythm of dot dash dot dash dot dash.
status 4 = Nothing set = Flashes for a short amount of time then stays off.
The inclusion of status codes 3 and 4 allow for simple expansion should we need to in the future.
Required Python libraries:
All of these are imported at the top of the status.py file, and come as standard on the latest Raspbian Download.
Python 2.x.x is used for this project.
The GPIO naming scheme used is the Broadcom (BCM) pin numbering layout. A chart converting board (physcial) pin numbers to their BCM names can be found here.
Logs are stored in /home/pi/logs/ in the file
cronlog. Older logs are stored in
To start the script upon restart run.
sudo crontab -e
Add this line to the file that will be opened by the crontab command.
@reboot sh /home/pi/launcher.sh >/home/pi/logs/cronlog 2>&1
The file sould look something like this.
# Edit this file to introduce tasks to be run by cron. # # Each task to run has to be defined through a single line # indicating with different fields when the task will be run # and what command to run for the task # # To define the time you can provide concrete values for # minute (m), hour (h), day of month (dom), month (mon), # and day of week (dow) or use '*' in these fields (for 'any').# # Notice that tasks will be started based on the cron's system # daemon's notion of time and timezones. # # Output of the crontab jobs (including errors) is sent through # email to the user the crontab file belongs to (unless redirected). # # For example, you can run a backup of all your user accounts # at 5 a.m every week with: # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ # # For more information see the manual pages of crontab(5) and cron(8) # # m h dom mon dow command @reboot sh /home/pi/launcher.sh >/home/pi/logs/cronlog 2>&1
Save with Ctrl-x.