[OpenRelief Developer] Modules - a hardware overview post

Shane Coughlan shane at openrelief.org
Fri Mar 16 17:27:45 GMT 2012


OpenRelief solutions consist of three parts; modules, transport systems and analysis and control systems. These can be combined to address challenges.
The modules provide simple ways to deal with individual challenges. They can be used alone or with transport and control systems to create a comprehensive recovery system. There are five modules that it would be nice to have ready for the launch of the project, plus one "meta-module", a container that can hold any of the module components for use either by hand, mounted on module racks or in the transport system (UAV).
== The module box ==
It might be a rather nifty and useful to take inspiration from Lego (tm) and other similar systems of clicking standard bits together :)
It would be nice to have one container with the same external dimensions and the same input/output connections for all of the modules. This module box would present us with several advantages in the field.  For example, you could easily clip one module out from a UAV or monitoring station and put another into place. If you are technical, you can pop open the box and take out parts to fix it (expand it, repair it). Taking this one step further, the module box could have  all the input/output connections on one side, so you could literally push, click and it's operational on the UAV and any other transport with a compatible loading bay.  Over time, having the same module box for everything would have advantages beyond ease of use, with one example being that it would make shipping modules easier and cheaper.
If the modules proceed as Arduino-based technology as outlined below, then it sounds like we need a power input and a serial output. Given that the UAV platforms will default to 5V for the off-the-shelf technology and we should also make it easy to create ad-hoc ground stations (e.g. from car batteries), we probably need to have two power inputs (5V and 12V) plus the serial output. Or one one power input that can deal with various voltages. Whatever makes the most sense from an easy of use and cost perspective.
== The modules ==
There are five modules it would be excellent to see. Some of these modules essentially already exist, but what we would like to do is review what's there, and try to have something to adheres to the ideas of Keep It Simple and Aim for the Best by launch.  Our framing principles are everything should be easy to build, use, maintain and customize, and that everything should solve problems with the greatest quality and reliability possible. Good tools cause minimal overhead when helping people overcome challenges.
Device: earthquake detector
Outline:
Detecting and understanding the scale of earthquakes is a critical part of disaster relief. This device would be a cheap, simple and reliable way to get seismic readings from a number of locations. 
Technology:
Arduino with Bluetooth, a MSGEQ7 graphic equalizer chip, passive electronics and a good quality microphone that separates frequencies detected into seven sound waves, and has software to detect the harmonic frequencies associated with earthquakes.  
Deployment:
This device is intended for deployment to mountain ranges and sea rocks to allow for maximum coverage.
Reference URL: http://solderpad.com/klattimer/odrseis
Device: submersion detector
Overview:
Detecting flood levels and extent is an important part of dealing with numerous types of disaster. This device is cheap enough to be used in clusters around areas with known risk to provide high fidelity reports if and when a disaster occurs.
Technology:
Arduino with a sensor that when submersed triggers a transmission to allow understanding of the scale of a flood. 
Deployment:
This device could be deployed as a stationary monitoring system.
Device: weather station
Overview:
Monitoring heat, wind strength and direction, humidity and air pressure is an important aspect of understanding the local environment and planning relief activities. This device can be deployed in relatively large quantities to deliver detailed information where required.
Technology:
Arduino with a Dallas 1Wire thermometer, wind strength sensor, wind direction sensor, humidity sensor and air pressure sensor. The use of 1Wire allows engineers to remove the weather station from the container and stack with other sensors (e.g. radiation sensor and earthquake detector) as needed.
Deployment:
This device could be deployed either as a stationary monitoring system or as an module in an outreach solution.
Device: radiation detector
Overview:
A Geiger counter to allow radiation-level monitoring on air, sea and land. 
Technology:
There are two approaches to developing the first generation of this device.  One is to use an Arduino with the Libelium open source geiger counter, optionally paired with wireless and its own power source.  The other is to re-engineer a less complex solution using an Adruino, a Dalas One Wire and a simple Geiger counter.
Deployment:
This device could be deployed either as a stationary monitoring system or as an module in an outreach solution.
Reference URL (Basic Libelium): http://www.cooking-hacks.com/index.php/documentation/tutorials/geiger-counter-arduino-radiation-sensor-board
Reference URL (Advanced Libelium): http://www.libelium.com/wireless_sensor_networks_to_control_radiation_levels_geiger_counters/
Reference URL (simple Geiger counter): http://solderpad.com/solderpad/mightyohm-geiger-counter
Device: FM radio transmitter
Overview:
When a disaster occurs it can be very difficult for normal citizens to obtain accurate information inside the affected area. This device provides one option for reaching a broad audience via FM transmissions. 
Technology:
There are quite a few open FM transmitter systems available, ranging from Kogawa Sans simple transmitter through to more advanced systems. These can be combined with an Arduino board and communications technology (GSM, wireless, wired) or pre-recorded material (SD card) to deliver a compact local radio broadcast solution.
Deployment:
This device could be deployed as a stationary communication system.
Reference URL (very simple transmitter): http://anarchy.translocal.jp/radio/micro/howtotx.html
Reference URL (more complex transmitter): http://mikeyancey.com/FM-Stereo-Broadcaster.php 
Reference URL (potential platform recommended by Andrew): http://www.openthing.org/products/niftymitter/
You will notice that we don't have a specific plan for how the modules can transmit their data if they are located outside a UAV (i.e. the module overviews are just about the single task, not how that task is communicated).  This is because it needs to be discussed whether another module - a networking module - could be beneficial. It is possible that a Raspberry PI and a wireless router could be used to provide a system that can take serial inputs, combine and reformat the data as required, and send it on via wire, wireless or even something like a USB GSM dongle. Such a module may also be useful as a quick and cheap computer for disaster zones. 
== The Future ==
There are plenty of potential modules to consider for the future. Some food for thought can be found at the following URLs:
http://solderpad.com/solderpad/phduino
http://solderpad.com/jcw/gravity-plug
http://solderpad.com/solderpad/ronja-10m-receiver/
http://solderpad.com/solderpad/ronja-10m-transmitter
http://solderpad.com/solderpad/ronja-twister-2
http://solderpad.com/solderpad/seeedstudio-gprs-shield
http://solderpad.com/solderpad/sparkfun-openlog
http://solderpad.com/solderpad/twig-3-axis-compass
http://solderpad.com/jcw/heading-board
http://solderpad.com/folknology/dual-stepper-motor-module Roving
http://solderpad.com/solderpad/arduino-mega-pro-3-3v
http://solderpad.com/solderpad/arduino-nano-3
http://solderpad.com/jcw/dc-motor-plug
http://solderpad.com/solderpad/beagleboard-xm-rev-c
But let's keep it focused on the first five modules. The idea is to formally launch the project in June with nice tools everyone can play with.  From there, we can try and take over the world... 
(bonus points to whoever got the Pinky and The Brain reference first)


More information about the Developer mailing list