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!

Labels:

Comments

Post a Comment

Popular posts from this blog

websockets and mobile networks and ssl

Gahhh. Just going to ramble on this one: Websockets is unstable going through cellular networks Searched Google and solution seems to be SSL connections Tried to implement, and it works to some extent,  but realized that I'll have to have both Apache, which was running my web front end, and Tornado both listen to 443 which cannot happen Realize finally that Tornado is a SERVER just like Apache Try to implement web client through Tornado It works but Websocket server and the web client still different instances so still can't have both listen, or that's what I'm thinking but I don't have time to think about it at present. Gotta sleep.
Post a Comment
Read more

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   ...
Post a Comment
Read more

finally got around to it (nrf24l0+ and servo)

On a previous post , I used the nrf24l01+ wireless chip to communicate between the Raspberry Pi and an Arduino, but only got lights to turn on. I remember being confused as to why servos would not work, and somewhat left it there. I started messing around with it again, and I am concluding that it might have been just a power issue. Here is the servo moving properly: The Arduino is on the ground due to the short length of the wires powering them. Just as a recap, what is happening is: - a C++ program using the RF24 library is compiled in the Raspberry Pi (connected to an nrf24l01+ chip) to broadcast a message. When executed, it will broadcast the message. - the Arduino (connected to another nrf24l01+ chip) programmed to receive messages receives the message, and upon receipt sends a signal to an Arduino that is wired to the servo to move the servo. Two separate Arduinos are used, as it seems that the servo library and the RF24 library do not seem to run properly toget...
Post a Comment
Read more