Skip to main content

how everything is connected (for now)

There are currently three different parts:

  • A "requester" client that will request for a door opening.
  • A single "target" client (the Raspberry Pi) that will receive requests
  • A central server that will relay the messages between the "requester" clients and "target" client

The messaging is done using WebSocket--really great stuff.

"Requester" Client
Currently just a simple PHP/JavaScript page that can send a textual message to the central server.

"Target" Client
A Python script that keeps an active WebSocket connection to the central server. As said above, this is executed in the Raspberry Pi.

Central Server
A Python script that listens for WebSocket messages. This uses the Tornado library for Python for creating the WebSocket server. This is executed in the Ubuntu web server.

I'll try to put more details as I go, but for now, I think this 10000-feet view is the better for catching up with the status logging.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

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