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

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

alcohol sensor (and some patience)

Soldered the alcohol sensor into something that is connectable: I tried to connect this to the Arduino, as I had the appropriate circuitry, but I did not get any legitimate output from it. 5V going in, 5V coming out with no variations. Nothing seems to be awry in wiring, as the circuit seems to be grounded properly (and the 5V current is flowing).  There are a couple of potential factors as to why I'm not seeing any results: - I'm using a 10k ohm resistor, while some guides (and the datasheet for the sensor) asks for 100-200k. However, there seems to be a good amount of people using 10k and getting at least some kind of result. A batch of 100k ohm resistors I ordered is on its way, so I guess I can try with them when they come. - This site  claims that these sensors take 24-48 hours for its signals to be stable. It also tells me that I should not be powering the sensor directly from the Arduino, which I have been doing, out of concern that the power draw of t

adding a servo

Since I don't have any lock that works based on a digital signal, it seemed appropriate to at least have something in place that would emulate the behavior of such a lock, and I thought that a servo would be a good substitute. (note: a servo is a device with which one can control a specific rotational position) Connecting a servo to the current circuit isn't too much of a challenge, as it just requires a single output connection along with the ground/power. Making the servo also just requires an addition of a few lines of code, using the Servo library . A simple video of the servo in action: Now, at least with a locking behavior in place, the one visible functionality that needs to be addressed is the device's ability to distinguish between a "standby" state (no alcohol/no breathing in: should be in "lock" mode) and a "open" state (no alcohol/breathing in: should be in "open" mode).