Skip to main content

a step closer to robots

well, I'm back.

"back with a 3d printer" kind of back.

took a week off earlier this month for a stay-cation, and during this time of peace, I decided it was the right time to get my hands on one.



behold, the Monoprice Select Mini.
thoughts so far:
- very inexpensive for today's standards (got it for $200)
- produces great prints
- very non-proprietary

this review convinced me in the end that this printer is the one.

by the way, the above picture shows the 3d printer with the "sample filament," which I soon realized was way, way too little to do anything.

I honestly didn't know what I should do with it at first, trying to find 3D models to print in the internet, until I stumbled into this.

an open-source, 3D-printable robot.

it's always been a dream of sorts for me to build a controllable hand.
it was my intention to build something like that during one of my college projects, but it ended up being something else (software) that is controlled (the glove controller remained).

now, this printable robot offered a printable hand (and forearm, and bicep, and shoulder, and head...).

at this point, I've actually already printed a lot of parts and am pretty well-into the process of building this.



I will elaborate my progress so far in the next post.


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