Skip to main content

more for self notes than anything

I moved into a new apartment on August, and so far, it's been great.

One of the things that I noticed when I got the keys to the apartment was that the front-door key was labeled "do not duplicate."


I normally copied a set of keys just in case I lose them, so I checked the internet to see if the "do not duplicate" denoted a physical difficulty or a moral request. The results pointed towards the former. Search results pointed out that these keys required a special "owner card," and locksmiths needed a special copying device for these specific locks. Inconvenient.

Meanwhile, I was humoring the thought of getting my hands on a Raspberry Pi, but I couldn't really think of a reason to justify the purchase.

Well, the two thoughts crossed ways, and the conclusion of "I should program something to open my front door" was made.

How?

There's an intercom system in the apartment, and I supposed that having something press the door open button would be something.

And the click on the check out button was made.

That was about 2 weeks ago.The Raspberry Pi is now here, and I have already started messing around with it. 

After working on it a bit, doing research on implementation and "learning" Python whenever it is needed, I thought that recording my progress would be a good and organized way to look back on it.

This is that record, and I'll try to write as much information as I can.

Couple of posts would be a recap of my progress to date, and future posts will be more of an update.

Comments

Popular posts from this blog

got the servos, got them working

The servos were delivered today, and I started working on them once I came back home from work.  The initial set up I had with RPi.GPIO was... a failure.  When connected, the servo would just twitch and continue to groan with uncertainty about where it should position itself.  Wanting to see what it should actually do, I fired up my Arduino that's been inactive for quite some time, connected the servo and loaded up the Servo library. It worked like a charm. The difference between a real-time PWM and a soft PWM was very visible.  For a while, I was thinking about maybe using the Arduino as the servo controller and have the Raspberry Pi just send a single high signal that would trigger the Arduino to move the servo. However, the extra size and power that would be required put me back to my senses. I have to say I was pretty discouraged. It was probably because I was really expecting whatever I had implemented to work right off the bat. After eati...

got it done

Got the ports all figured out, and after thinking about how to mount the servo + devices to the intercom, I decided that it would be best to attach only the servo and make wires long enough to keep the Raspberry Pi on the ground. I really wanted a nuts-and-bolts kind of configuration to mount the servo, but mounting squares (sponge-y tapes) were inevitably the simplest and most readily available solution. Currently, the servo would stall and stop pushing after around 3 seconds of pressing, but that should be fixed with some calibration of servo positions. Will continue to clean the project up until I get an idea for the next project, but for now, Success!

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 ...