Robot
Published on December 12 2012

Cyberdude's Wall-e

StorySkip to comments

Well, I've been at a standstill on this guy for months due to parts issues and time constraints.

Got the parts, got the time. So, with no further adieu...

Image #1 shows the aftermath of converting the head to being able to nod. I thought long and hard about how I could keep the original eye movement mechanism, but after long debate (and lack of a good solution), I went ahead and removed most of the stock material and, using a micro 9 oz. metal gear servo, put a tube across the eyes and attached it to the top of the neck (modified to basically be a saddle for the tube). The servo is mounted in the left eye socket, and fits quite well.
User-inserted image
Image #2 show how I threaded the servo wire down the neck and hid it in the structure...
User-inserted image
Image #3 shows where the servo wire comes out of the neck and goes through the rotation plate at the base.
User-inserted image
Images #4 shows that this wire now wraps next to the neck rotation servo mounted to a custom plate and uses the existing mounting holes.
You can also see that I have used those same micro servos for the arms. The good news is that with little grinding of material from the chassis, these servos fit quite well. The downside however is that unless these servos are under load, the weight of the arms (and head) tend to make them fall. I don't know how much of an issue this (yet...)
User-inserted image
Image #5 shows how I was able to position the neck rotation servo perfectly under the neck plate. This is cool because it makes the presence of the servo invisible.(My Primary goal with all of the servos).
User-inserted image
Image #7 shows the head and neck in place on the top plate with wires.
User-inserted image
Image #8 shows the placement of the "ping" sensor. As you can see, I chose an interior mount rather than an exterior mount. This works OK, but not great. I looks good, but the distance to impact and rotation from obsticle will need to be modified due to the fact that the window in object recognition is smaller than the width of the robot, therefore, if he doesn't stop and turn enough, early enough, his treds hit the object.
User-inserted image
Image #9 is the camera mounted in the right socket. I would image this is the prototypical installation, so nothing to "see" here but to mention that I hard wired the camera.
User-inserted image
Image #10 is, finally, the other side of the camera mount. I found it EXTREMELY challenging to finesse the camera circuitry into the head unit. In fact, having had to remove all of the mounting holes in the plastic, I'm not quite sure how to reassemble it : (
User-inserted image

OK, that's it for this post. Next up is audio, and programming.
February 23 2013
Wow, that wall-e actually looks smaller than the U-command, i noticed you say its based off of it.
Can you tell me which Wall-e toy that was? Or if it is the U-command?
February 24 2013
This is the U-Command model.
February 24 2013
OK, as promised, here are some updates to the project...

User-inserted image

Okely Dokely, here's what we have...

1. This is the AU5032 from MDFly.

2. This is a 5v step down circuit that I picked up from eBay. (I have a few more if ya need one.) " AMS1117-3.3 DC/DC Step-Down Voltage Regulator Adapter Convertor W 3.3V Out"

3. This is also from MDFly: Logic Level Converter - 2.5v/3.3v/5v. I could have used two of these instead of the AMS1117 above, but this was $2.95 PLUS shipping from MDFly whereas the AMS1117 was $2.17 for FIVE INCLUDING SHIPPING!

4. Amplifier (the sound card is not amplified)

5. Speaker.

So the deal is that this particular sound card requires TWO 3.3v voltage inputs to function; one drives the comms signal, the other drives the circuit. I'm no EEE, so I have no idea why, I just know that I needed both.

All in all, it set me back something like $24 bucks not including the speaker and micro card (I had both laying around.)

Also, I should mention that one set of leads goes to a free port on the controller. the voltage-only leads go to the 5v out pins on the controller. I wasn't using them for anything else, so there ya go.
It uses typical serial comms.
February 24 2013
Very well explained, these contributions are appreciated, and a whole costs something like half the price of the trigger mp3 spankfun.
Does that mean that the communication via ez-b from any port makes digital?
February 24 2013
If I understand your question correctly, the answer is, the signal and signal voltage comes from and digital port. The second voltage can come from any port supplying 5v, but since there's a 5v for external power head, I used that for the second power feed.