Skip to main content

hand building: progress so far

I guess pictures are worth a thousand words for this.

I am looking at this page in the Inmoov website to download and assemble the parts.

initial printing of parts:



shown above are some of the forearm parts and some palm parts.



the rest of the palm with some of the fingers, along with the forearm part glued together.

thankfully, these parts are designed to be printed in smaller parts and put together, which makes it possible to this to be printed with a small 3D printer like mine, which only allows for only 12cm x 12cm x 12cm (~5 inch x 5 inch x 5 inch) in print size. some parts had to be realigned in the model-slicing software in order to have it fit in the print boundary.



all the printing done so far.

you can see the inside of the forearm now has a servo bed, with more things needed to be printed and attached to the inside. I will need to get screws to attach them.

currently, the only big part missing the the last wrist part, which I am considering printing with another color (just got my order for blue filament today), since the instructions call for grease to be applied to that part.

really looking like a hand at this point!


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

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, tim...
Post a Comment
Read more

pwm..

I just realized that the RPi.GPIO library (for programming the Raspberry Pi's input/output) already has PWM control, giving me a much more efficient control of duty cycles... At least the previous exercise ("duty cycle testing") refreshed me on it. PWM control on RPi.GPIO: http://code.google.com/p/raspberry-gpio-python/wiki/PWM
Post a Comment
Read more