Skip to main content

it's been a while (but not without updates!)

I did not have much free time to work on this over the last couple of months,

but every once in a while when I did remember (hard not to, I keep the robot hand right in front of the computer), I tried to do something, mostly in the hardware procurement side of things.

some of the things I ended up acquiring:

- Raspberry Pi Zero (also the Raspberry Pi Zero W, which has wifi+bluetooth internally, but I just received it today thanks to Mr. Arjun Rao), for more versatile control (also to make possible to connect to the Leap Motion)
- AA battery power holders, to use AA batteries to power the servos
- A PCA9685 chip, for multiple servo control
- various electronic circuitry (probably won't be necessary for this project anymore)

in addition, I was made aware of a nice project called Cylon.js and its sister project Gobot, which allows users to program microcontrollers using JavaScript and Golang, respectively.

I really wanted to try Gobot and take a dive into the Golang world, but it currently does not have support for the PCA9685, which Cylon.js seems to provide. 

with that said, and with a few lines of code, here is the result:


the control of the servos are done through the PCA9685 connected to a Raspberry Pi Zero (no more Arduino), and the servos are powered through the 4-AA batteries. 

the next step is to read values from the Leap Motion, which Cylon.js claims to provide. 

when that works, we are starting to reach a good place. 


Labels:

Comments

Post a Comment

Popular posts from this blog

finally getting back to it

Things went by pretty quickly this month, and I was not able to play around with this project much.  I did tinker with it every now and then, but I was never able to get myself past the residing issue of compiling the RF library in the Raspberry Pi. It seemed people are generally interested in the project linked in the previous post, as people were actively posting comments on it.  Couple of days ago a user posted a solution to the compile issues (changes to method names and usage of pre-defined values for parameters), and I thought I should try following it to see if it works.  The code indeed compiled, and I was able to change it a little more to be more fitting to my project.  On the Arduino side, it might be a premature assumption, but it seemed like the Arduino was unable to handle messaging through the RF and controlling the servo at the same time. My assumption is that the inability to control them in separate threads is causing some timing issues, but I mig
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

GPIO testing

Since the environment of the client-server-target is currently quite functional in the messaging standpoint, I decided to try connecting a simple LED light to the Raspberry Pi to see if it could "open" a door when the command is received. Installed the RPi.GPIO module (a Python module that gives the user command of the GPIO--General-Purpose Input/Output--ports in the Raspberry Pi) and connected the LED light to a GPIO pin. When the target received a request message, it would signal the GPIO pin to drive a current to the LED to light it up for 2 seconds. in main: if __name__ == "__main__":   GPIO.setmode(GPIO.BCM)   GPIO.setup(17, GPIO.OUT) in the on_message's request-received logic:      GPIO.output(17, True)      time.sleep(2)      GPIO.output(17, False) The video is a weak visual result. You can a click when the LED lights up; that was the sound of the key being pressed that sent the request message. Now, time to get (think up of ) some a
Post a Comment
Read more