Skip to main content

fun with the nrf24l01+

What I am trying to do nowadays is to get the "open sesame" system to work wireless.

The servo that opens the door is currently connected directly to the Raspberry Pi, which limits the use of the Raspberry Pi for just this purpose, and I was starting to want to have it around for more things.

The NRF24l01+ is a neat, cheap little device I found in the internet that gives devices a means to communicate with each other wireless through a 2.4 GHz network.

I've been looking at this site for a good sample to follow and build upon.

Currently, I have not been able to build the Raspberry Pi source given from that site on my own, but someone in the comments managed to upload a working, built binary for it, which I have been using so far for testing. I'll eventually have to be able to build it on my own, as I'll probably have to change the code for my purposes.

I've been playing around with it, and I've been able to make lights blink. However, everything seems to malfunction when I try to wire the servo. I haven't actually wired the servo used for the testing on its own, so I have to first rule out that it's a servo/power issue that's causing it.

For now, blinking lights:


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.