Skip to main content

alcohol sensor (it's working!)

Built a voltage-regulation circuit that was shown here (seems like this layout is uncommon, as other resources seem to agree on using a circuit with a 10uF and a 1uF capacitor. I already ordered a 1000uF shown here, so I'll go with this). Seems to work like a charm. I connected it to the alcohol sensor circuit using a 9V battery as input, but it still did not seem to work:

Output voltage was constant @ ~5V. Expected behavior is 5V = maximum alcohol level. 


After some thought, I just decided to try wiring the alcohol sensor circuit again. I was almost sure I had the wiring right before, but once I connected it after the re-wiring, output voltage started dropping:

Voltage dropping. As stated in the previous post, the sensor requires a 24-48 hour calibration time (to reach 0V state)

Two key functionalities are now usable. Time to start putting them together.

Comments

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.

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.

dabbling with cylon

I'm playing around with Cylon JS whenever I have the time. in order to use the leap motion for control, the hand control will need to communicate with the pc that is connected to the leap motion device (leap motion does not provide an arm/linux driver). it seems that Cylon devices can communicate with each other through socket.io or http, and I am currently playing around with that.