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

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