Skip to main content

packaging

I've spent some time trying to figure out how to solve the 3-state problem mentioned in the end of the last post about this project,

but I haven't been able to find a solution I can use right away.

I do think the practical solution would be a "wind sensor," a primitive anemometer that would simply just distinguish between no blowing and blowing ("wind").

I would suppose a fan-like sensor would pick up the wind (in a way, a very miniature version of this).


Anyways, I'm thinking that this project should be packaged in some way for presentation sake,

and I'm guessing it could be something like this:



Of course, the contents would be inside the box, and cut-outs made to make the visible parts visible.

Note that the servo can actually work as a lock with this layout.


In order to do this, though, it will be great to have a ruler/cutting knife and someone who can use them well.


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

pwm..

I just realized that the RPi.GPIO library (for programming the Raspberry Pi's input/output) already has PWM control, giving me a much more efficient control of duty cycles... At least the previous exercise ("duty cycle testing") refreshed me on it. PWM control on RPi.GPIO: http://code.google.com/p/raspberry-gpio-python/wiki/PWM
Post a Comment
Read more

nodejs migration

Having been playing around with NodeJS recently,  I (naturally?) started re-writing some of the OpenSesame code using Node last night. I think I've only worked on it around 2 hours so far, but I've already set up a basic client interface (a socket.io chat tutorial rip) with a server that the Raspberry Pi can connect to and receive requests to open the door.  This is probably due to socket.io's socket management (socket.io is the WebSocket module for Node); for my first implementation, I had to manually write up a structure that managed sockets, but that is pretty much handled by socket.io. Also, the servo control logic is pretty much recycled (and the Raspberry Pi code is still Python), and I do remember spending some good time figuring that out.  Cool neverthelss. I'll probably keep both versions around.
Post a Comment
Read more