Skip to main content

got the servos, got them working



The servos were delivered today, and I started working on them once I came back home from work. 

The initial set up I had with RPi.GPIO was... a failure. 

When connected, the servo would just twitch and continue to groan with uncertainty about where it should position itself. 

Wanting to see what it should actually do, I fired up my Arduino that's been inactive for quite some time, connected the servo and loaded up the Servo library. It worked like a charm. The difference between a real-time PWM and a soft PWM was very visible. 

For a while, I was thinking about maybe using the Arduino as the servo controller and have the Raspberry Pi just send a single high signal that would trigger the Arduino to move the servo. However, the extra size and power that would be required put me back to my senses.

I have to say I was pretty discouraged. It was probably because I was really expecting whatever I had implemented to work right off the bat. After eating a late dinner, I pushed myself to try more. 

I tried installing the WiringPi library, but after reading about it, it didn't seem much different from RPi.GPIO, so I didn't bother to use it. 

I then thought I should maybe install the Occidentalis OS that is developed by Adafruit, seeing how it comes with servo kernels. Felt like starting from scratch (at least in the Raspberry Pi side) should be a last resort option, so I decided to try to find something else. 

Finally, I landed on ServoBlaster. It relied on writing a duty cycle value to a location in the system, but it worked smoothly, and beautifully. It also did not need to constantly drive the servo a constant signal but activated only when the position was changed (with a timeout value in the initialization parameters). 

echo 5=70 > /dev/servoblaster 

The "70" is the amount of time the signal will be high. The cycles are counted by 10 us (microsecond), making the "70" 700 us, or .7 ms. This would put the servo near the 0 degree position. 

echo 5=230 > /dev/servoblaster

This would put the servo near the 180 degree position.

Had to use system calls through the os module, but once implemented, it finally works.
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

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

finally got around to it (nrf24l0+ and servo)

On a previous post , I used the nrf24l01+ wireless chip to communicate between the Raspberry Pi and an Arduino, but only got lights to turn on. I remember being confused as to why servos would not work, and somewhat left it there. I started messing around with it again, and I am concluding that it might have been just a power issue. Here is the servo moving properly: The Arduino is on the ground due to the short length of the wires powering them. Just as a recap, what is happening is: - a C++ program using the RF24 library is compiled in the Raspberry Pi (connected to an nrf24l01+ chip) to broadcast a message. When executed, it will broadcast the message. - the Arduino (connected to another nrf24l01+ chip) programmed to receive messages receives the message, and upon receipt sends a signal to an Arduino that is wired to the servo to move the servo. Two separate Arduinos are used, as it seems that the servo library and the RF24 library do not seem to run properly toget...
Post a Comment
Read more