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.

Comments

playing with servos

some servos that I had ordered were delivered. the instructions suggested another brand/model of servos, but these were a much more economical (cheap). I tried adding them to the hand: I'll have to print the "pulley" pieces that will be attached to the servos. meanwhile, I did somewhat (hackily) got the wrist to work, for now: you keep hearing the "usb plugged out" sound in the background, and that's because the servo was being powered by the arduino. the servo's power draw appears to be causing a shutdown of the device. will need a better power source for the servos. it feels like these pieces that are supposed to be plugged into the servo will have size issues.

dabbling with android

I've been wanting to dabble with Android development recently, and yesterday I realized that there is a Socket.IO client API available for Java/Android. The API is pretty straightforward, so I loaded a test Android project I had made for going through Android basics and connected to the OpenSesame Node server. and it works! I mean, the interface is non-existent and it's really just bare-bones, but having the servo respond through an Android application was pretty refreshing. (the web client and the android client "communicating" with each other--messaging is pretty much for debugging purposes)

chunk update: most parts printed and assembled

currently: stuff that happened are: wired the fingers added screws to necessary assemblies witnessed first failed print during this: servos haven't come yet, but once they do, we can start installing them into the hand/forearm. as always, credit to the Inmoov project.

the quest for robots

Search This Blog