Skip to main content

time to build something new

I've been making good use of the previous project. It did fail me once (unfortunately, that moment was probably the most necessary situation for the project..), but overall, it has been serving me well.

Ever since, I've been constantly thinking about what project I should start on next (or rather if I should even start on something else), but I never really got to thinking up an idea that is useful, not too time consuming, and relatively fun. It took some outside factors to get me started on a new project.

A couple of weeks ago, I was approached by a friend in church who wanted advice for a project she has to work on. It was an industrial design project in nature but required electronic functionality. As soon as I heard the general specifications, it spoke "I could be done with an Arduino." I decided it would be a win-win situation to help out by implementing the electronic part, as it is my understanding that the main focus of her project--what's graded--is the design/implementation and not the building of what goes in it (that are not related to design).

Basically, the project is about a key container that, when activated, would lock a key inside and will only open after a breathalizer check that returns a legal BAC (blood-alcohol content) level for driving.

So far, the requirements I have understood for the electronics is:

- a breathalizer component that measures BAC
- a simple LED display that displays the BAC
- a locking device that controls lock/unlock electronically
- an on/off button

 I've searched for available instructions on building a DIY breathalizer, and this Instructables entry seems to provide me with a good start.

Currently, my idea for the implementations for these components is:

- a circuit built around the MQ-3 Alcohol Gas Sensor for the breathalizer 
- a 4-digit 7-segment display
- no idea on locking device yet
- any kind of latching switch 

I've already ordered the alcohol sensor, will have to start ordering the other parts.

Let's start a new project!

Comments

Popular posts from this blog

duty cycle testing

Now that I saw a physical response, I should try to make it similar to how a servo should be controlled. Servos are actuators that receive (expect) position input (as opposed to motors, which receive speed/intensity input). Simply put, it registers input as pulses, decoding the ratio of high (a "on" signal) to low in a given period as a position value.  A better explanation :  http://learn.adafruit.com/adafruits-raspberry-pi-lesson-8-using-a-servo-motor/servo-motors As I am waiting for my servo to be shipped, I will continue to work with the LED light.  As opposed to my previous setup of having the light turn on every time the request is given, I will have the light turn on and off in a regular pattern until a request is given, upon which the pattern will change for one "cycle" (on-and-off pair). The on-and-off logic (previously the LED control logic) will be run in a separate thread: def dCycle(*args):    global dCVal   ...

dabbling with android

I've been wanting to dabble with Android development recently, and yesterday I realized that there is a Socket.IO client API available for Java/Android. The API is pretty straightforward, so I loaded a test Android project I had made for going through Android basics and connected to the OpenSesame Node server. and it works! I mean, the interface is non-existent and it's really just bare-bones, but having the servo respond through an Android application was pretty refreshing. (the web client and the android client "communicating" with each other--messaging is pretty much for debugging purposes)

playing with servos

some servos that I had ordered were delivered. the instructions suggested another brand/model of servos, but these were a much more economical (cheap).  I tried adding them to the hand: I'll have to print the "pulley" pieces that will be attached to the servos. meanwhile, I did somewhat (hackily) got the wrist to work, for now: you keep hearing the "usb plugged out" sound in the background, and that's because the servo was being powered by the arduino. the servo's power draw appears to be causing a shutdown of the device. will need a better power source for the servos. it feels like these pieces that are supposed to be plugged into the servo will have size issues.