Read Time: ~ 15 minutes
Build Time: ~ 60 - 90 minutes
How much impact can the human body handle? Whether it's football, rock climbing, or a bicycle accident, knowing when to seek immediate medical attention after a collision is incredibly important, especially if there are no obvious signs of trauma. This tutorial will teach you how to build your very own impact force monitor!
This open-source project uses a Raspberry Pi Zero W and an LIS331 accelerometer to monitor and alert the user of potentially dangerous G-forces. Of course, feel free to modify and adapt the system to suit your various citizen science needs.
To keep this tutorial short n' sweet (er, well, as much as possible), I'm assuming you're starting with a functional Pi Zero W. Need some help? No problem! Here's a full setup tutorial.
We'll also be connecting to the Pi remotely (aka wirelessly). For a more thorough overview on this process check out this tutorial on making a "headless" Raspberry Pi:
Also, check out the datasheet for the LIS331.
To follow along with this tutorial, you will need the following materials. You may not need everything though depending on what you have. Add it to your cart, read through the guide, and adjust the cart as necessary.
The items in the wishlist include:
You will also need the following tools.
Fortunately, the term "impact force" is pretty straightforward: the amount of force in an impact. Like most things though, measuring it requires a more precise definition. The equation for impact force is:
where F is the impact force, KE is the kinetic energy (energy of motion), and d is the impact distance, or how much the object crunches.
There are two key takeaways from this equation:
Force is typically measured in Newtons (N), but impact force may be discussed in terms of a "G-Force", a number expressed as a multiple of g, or earth's gravitational acceleration (9.8 m/s^2). When we use units of G-force, we are measuring an objects acceleration relative to free fall towards the earth. Technically speaking, g is an acceleration, not a force. However, it is useful when talking about collisions because acceleration (the change in speed and/or direction) is what damages the human body.
For this project, we'll use G-force units to determine if an impact is potentially dangerous and deserving of medical attention. Research has found that g-forces above 9G can be fatal to most humans (without special training), and 4-6G can be dangerous if sustained for more than a few seconds.
Knowing this, we can program our impact force monitor to alert us if our accelerometer measures a G-force above either of these thresholds. Hooray, science!
For more information, read about impact force and G-force on Wikipedia!
Gather your Raspberry Pi Zero and peripherals to configure the Pi to be headless!
Connect the Pi to a monitor and associated peripherals (keyboard, mouse), plug in the power supply, and log in.
Update software to keep your Pi speedy & secure. Open the terminal window and type these commands:
Type and enter: sudo apt-get update
Type and enter: sudo apt-get upgrade
Reset: sudo shutdown -r now
Click the WiFi icon on the upper right corner of the desktop and connect to your WiFi network.
In the terminal type this command to bring up the Pi's Software Configuration Tool: sudo raspi-config
Select "Interfacing Options", then "SSH", and choose "Yes" at the bottom to enable.
Go back to "Interfacing Options", then "I2C", and select "Yes" to enable.
In the terminal, install remote desktop connection software: sudo apt-get install xrdp
Type 'Y' (yes) on your keyboard to both prompts.
Find the Pi's IP address by hovering over the WiFi connection (you might also want to write it down).
passwd command.We can now ditch the HDMI and peripherals, woohoo!
Setup a remote desktop connection.
On a PC, open Remote Desktop Connection (or PuTTY if you're comfy with that).
For Mac/Linux, you can install this program or use a VNC program.
Enter the IP for the Pi and click "Connect" (Ignore warnings about unknown device).
Here's the electrical schematic for this project:
Here's the pinout for the Pi Zero W for reference:
Solder and carefully remove any flux residue on the accelerometer and Pi GPIO's header pins.
 |
 |
Then connect jumper wires between the LIS331 breakout board and Pi between the following pins:
| LIS331 Breakout Board | Raspberry Pi GPIO Pin |
|---|---|
| GND | GPIO 9 (GND) |
| VCC | GPIO 1 (3.3V) |
| SDA | GPIO 3 (SDA) |
| SCL | GPIO 5 (SCL) |
To make it easier to connect the sensor to the Pi Zero, a custom adapter was made by using a female header and jumper wires. Heat shrink was added after testing the connections.
Solder a current limiting resistor to the negative LED leg (shorter leg) and add shrink wrap (or electrical tape) for insulation.
 |
 |
Use two jumper cables or header pins to connect the positive LED leg to GPIO26 and the resistor to GND (header positions 37 and 39, respectively).
Connect the battery pack to the Pi's input power to complete the setup!
The Python code for this project is open-source! Here's a link to the GitHub repository.
User Parameters" section at the top.The maximum acceleration scale used in this project is 24G, because impact force gets big real quick!
It is recommended to comment out the acceleration print statements in the main function when you are ready for full deployment.
Before you run the program, double check that the accelerometer address is 0x19. Open the terminal window and install some helpful tools with this command:
sudo apt-get install -y i2c-tools
Then run the i2cdetect program:
i2cdetect -y 1
You'll see a table of I2C addresses displayed as shown in the image below. Assuming this is the only I2C device connected, the number you see (in this case: 19) is the accelerometer address! If you see a different number, take note and change in the program (variable addr).
The program reads the x, y, and z acceleration, calculates a g-force, and then saves the data in two files (in the same folder as the program code) as appropriate:
G-forces above our safety thresholds will also turn on our alert LED and keep it on until we restart the program. Stop the program by typing "CTRL+c" (keyboard interrupt) in the command terminal.
Here's a photo of both data files created during testing:
Open the terminal window, navigate to the folder where you saved the program code using the cd command.
cd path/to/folder
Run the program using root privileges:
sudo python NameOfFile.py
Check that the acceleration values in the x, y, and z-direction are printing to the terminal window, are reasonable, and turn on the LED light if the g-force is above our thresholds.
To test, rotate the accelerometer so that the each axes point towards the earth and check that the measured values are either 1 or -1 (corresponds to acceleration due to gravity).
Shake the accelerometer to make sure the readings increase (sign indicates direction of axis, we're most interested in the magnitude of the reading).
Once everything is working correctly, let's make sure the impact force monitor can actually withstand impact!
Use heat shrink tube and/or coat the electrical connections for the accelerometer and LED in epoxy.
For super durable, permanent installations, consider coating the whole shebang in epoxy: the Pi Zero, the LED, and the accelerometer (but NOT the Pi cable connectors or the SD card).
Secure to a helmet, your person, or a mode of transportation like your skateboard, bicycle, or cat*!
Fully test that the Pi is securely fastened or the GPIO pins may become loose causing the program to crash.
Theres a few methods of embedding the circuit into a helmet. Here's my approach to a helmet installation:
If you have not already, connect battery to Pi (with battery off). Secure the accelerometer to the back of the Pi with nonconductive insulation in between (like bubble wrap or thin packing foam).
Measure the dimensions of the Pi Zero, accelerometer, LED, and battery connector combination. Add 10% on either side.
Draw a cutout for the project on one side of the helmet, with the battery connector facing towards the top of the helmet. Cut out the padding in the helmet leaving a few millimeters (~ 1/8 in.).
Place the sensor, Pi, and LED in the cutout. Cut pieces of the excess helmet padding or use packaging foam to insulate, protect, and hold the electronics in place.
Measure the battery's dimensions, add 10%, and follow the same cutout for the battery. Insert the battery into the pocket.
Repeat the insulation technique for the battery on the other side of the helmet.
Hold the helmet padding in place with tape (your head will keep 'em in place when you are wearing it).
Power up the battery pack!
Now you can remotely log into the Pi through SSH or remote desktop and run the program via the terminal. Once the program is running, it starts recording data.
When you disconnect from your home WiFi, the SSH connection will break, but the program should still log data. Consider connecting the Pi to your smartphone hotspot WiFi, or just log back in and grab the data when you get home.
To access the data, remotely log into the Pi and read the text files. The current program will always append data to the existing files -- if you want to delete data (like from testing), delete the text file (via the desktop or use the rm command in the terminal) or create a new file name in the program code (in User Parameters).
If the LED is on, restarting the program will turn it off.
Now go forth, have fun in life, and check on the data every so often if you happen to bump into something. Hopefully, it's a small bump but at least you'll know!
Looking for improvements to the impact force monitor? It is outside the scope of the tutorial but try looking at the list below for ideas!
That's a wrap, folks! Please let me know if you have any questions or comments by sharing your thoughts in, well, the comments! Thanks for reading & happy building!
For more information used in t, check out the resources below:
Need some inspiration for your next project? Check out some of these other cool Pi tutorials for more inspiration!
learn.sparkfun.com | CC BY-SA 3.0 | SparkFun Electronics | Niwot, Colorado