To build Upkie from scratch, expect to spend around $3,000 in components, 60+ hours in 3D printing, and more hours of your work assembling and testing the beast. Community support is available on GitHub for both hardware and software of the robot.
A wheeled biped that can balance, go around and more. It is fully open source, both hardware and software.
To make the experience fit your profile, pick a username and tell us what interests you.
We found and based on your interests.
To build Upkie from scratch, expect to spend around $3,000 in components, 60+ hours in 3D printing, and more hours of your work assembling and testing the beast. Community support is available on GitHub for both hardware and software of the robot.
upkie-blender.zipBlender project of the fully assembled robotZip Archive - 41.07 MB - 09/27/2023 at 19:13 |
|
|
upkie-stl.zipSTL model of the fully assembled robotZip Archive - 39.51 MB - 09/27/2023 at 19:13 |
|
This project log follows up to Hollow leg, part 1, where we redesigned Upkie's femur to route cables through. We now do the same for the tibia.
Our goals are the same:
Again, we switch to 3D printing for the tibia part, with a cable guiding hole going through it. The part is identical to the femur, but the heat-set insert holes are both on the same side this time:
The ankle socket is redesigned as well with an hexagonal shape to better transmit torques:
We also switched to cable sleeves rather than corrugated plastic tubing, as they slide more smoothly and bend less awkwardly:
Assembled, the completed hollow leg looks like this:
Let's see how this new leg fares on real robots! Details to build and assemble it are further documented in Upkie's build instructions.
While building new copies of Upkie, we wrote full Build instructions for future travelers. These instructions cover all the steps from ordering to running a first balancing experiment:
They go through intermediate stages like electronics assembly:
With figures, so that new comers know (and old timers remember 😉) the orientation of each part:
In the hope these instructions help spawn and maintain many Upkie's!
Build instructions on Hackaday.io work well for the outline, but as more copies of Upkie get built we wanted something that could scale nicely to include sub-steps, distribute related project files (3D printed parts, setup scripts, ...), and allow for discussions related to any given step.
Introducing the upkie repository!
The wiki will be completed as we assemble another copy of the beast:
Stay tuned!
Upkie communicates with a regular PS4 controller. While this is not a key robotic feature, it is both cool (especially with kids 😃) and convenient to control the robot via Bluetooth. Before trying it out I was concerned about potential lags, or the Raspberry Pi loosing its connection to the controller, but the field summary after using it for months is: it just works. Here are my configuration notes, turned project log 😉
The setup instructions are not specific to Upkie: we can connect a PS4 controller to any Raspberry Pi. Start with the Bluetooh command line:
sudo bluetoothctl
Enable the agent with the following four instructions:
agent on discoverable on pairable on default-agent
Then start scanning for devices. The terminal should start listing scan results with all the Bluetooth devices around you:
scan on
While the command tool is scanning, press and hold both the Share and PS buttons on your controller to switch it to pairing mode. Keep holding the buttons at the same time until it starts flashing white light. When it does, check the terminal output for a new line like this one:
[NEW] Device AC:FD:93:14:25:D3 Wireless Controller
Note down the controller MAC address (here AC:FD:93:14:25:D3
). Check that the controller is still flashing and do:
connect CONTROLLER_MAC_ADDRESS
That should be it! If everything went well, you should see a "successful connection" message appear in the terminal, like so:
[bluetooth]# connect AC:FD:93:FD:68:0F Attempting to connect to AC:FD:93:FD:68:0F [CHG] Device AC:FD:93:FD:68:0F Connected: yes [CHG] Device AC:FD:93:FD:68:0F UUIDs: 00001124-0000-1000-8000-00805f9b34fb [CHG] Device AC:FD:93:FD:68:0F UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device AC:FD:93:FD:68:0F ServicesResolved: yes [CHG] Device AC:FD:93:FD:68:0F Paired: yes Connection successful
Finally, trust the controller so that it can connect after a reboot:
[bluetooth]# trust AC:FD:93:FD:68:0F
That's it! The controller should now appear as a regular Linux joystick device in /dev/input/js*
. That's where the Joystick source in Vulp (Upkie's motion control software) will look for it. If it doesn't, perhaps you are running into the same reconnection issue I faced. Some follow-up troubleshooting notes in this discussion thread.
Sawing broomsticks to get Upkie up and running quickly was great at the beginning of the project, but it came with a drawback that came to light while manipulating the robot: a cable can get on the wrong side of a leg and get snapped away if the human manipulating it is not paying attention. Here is a bad instance on a shin:
Pulling a cable hasn't happened yet while balancing, as the corrugated pipes that hold power and communication cables are quite stiff by themselves and tend to stay away from the legs, but it has happened for sure while sitting and raising the beast. So, today's update is about routing cables inside the legs. (This is part 1, we'll see about the lower leg in part 2.)
Our goals are:
The idea is to 3D print a cable guide inside the hip, femur and knee parts. The femur thus becomes 3D printed (bye wood 😢).
Here is a short video summary of the update:
More details on the successive iterations:
At this stage, the leg assembly looks like this:
One further nice thing to add are small rivulets inside the hollow cable guides to hold the corrugated pipe in place during motion:
There are still several questions on the table that this design does not answer. How about turning the knee servo 180° to avoid the cable outlet in the middle of the femur? Also, can we get corrugated pipe that bends more smoothly?
Note that we are keeping some length of cable above the hips to maintain the range of motion of the hip joint, in particular so that the robot can sit down and up properly. Eventually we can redesign the side chassis plates (blue in the picture above) to hold the cable better with a hole of the matching size (as opposed to a wide rectangular hole right now).
Those points are left to future work 👷
When running the Pink balancer agent on Upkie, the four CPU cores of the Raspberry Pi are used as follows:
CPUID | Processes | Threads | Usage (%) |
---|---|---|---|
0 | Spine (+ other system processes) | Logger (+ other system threads) | 10 ± 5 |
1 | Spine | Spine loop | 10 ± 5 |
2 | Spine | CAN communications | 50 ± 20 |
3 | Agent | Python threads | 100 |
On average over all cores, the ARM processor is only used at about 50% of its capacity, but that (or the fact that one core is used at 100% all the time) is enough to drive the CPU temperature up to a problematic level:
(If you were wondering why Vulp has a CPU temperature observer, now you now 😉) The issue is that to protect itself the Raspberry Pi throttles all computations if its CPU temperature hits 80 °C, which for Upkie results mostly in skipped control frames (wheels apply their commanded velocities for too long ⇒ balancing degrades) and in the worst case triggers Vulp's safety of stopping actuators when no action is sent for more than 100 ms.
Luckily it's not hard to cool down a Pi. Having a standing fan blow air at Upkie from the sides, where its wide "seal ears" are, does the job just fine. But the robot is not designed to stay near a fan, so let's give him an "earpiece" so that it carries its own fan:
There is already a second male XT-30 connector on the pi3hat in Upkie's head, so we can order a 24 V DC fan from online retail, solder a female XT-30 connector to it, and just plug it to the power bus. In this update, the fan has the following properties:
The mount is a temporary adapter to connect to the existing right plate. Once we have settled on fan dimensions, we can redesign the plate so that it plugs into it directly:
The fan is effective immediately. It brings down the CPU temperature to an equilibrium around 43 °C while the balancer is running full steam:
Now the issue has become noise 😅 The fan's continuous 32 dBA relentlessly drill into the ears of neighboring humans, whose thoughts are inevitably driven to the next revision: smaller fan, less dBA!
🔊 → 🔉
Here comes a shot of the robot in its natural habitat: the living room!
The main improvement in this update lies in the locomotion software, which performs smoother motions and allows the robot to crouch down further.
There is also a hack, documented in the code as the non-minimum phase trick, to improve transitions from standing to driving with the simple PID balancer. Some pointers to dig further: this hack helps handle the non-minimum phase nature of balancing systems (the fact that to go one way one first needs to go "a little" the other way, like counter-steering in bikes) without going for full model predictive control.
The small wheels (OD: 100 mm) on Upkie are nice because they are sleek, which fits well the assumption made by the PID balancer that controls the velocity of the contact points with the ground, unfortunately they are also a bit small which doesn't fit the ankle design so well. That, rather than knee torques, is actually what limits how much the robot can crouch before it starts scratching the hell out of the floor (^_^)
Let's start this log with a short tour of Upkie's very first "let's put things together" version:
Cables are on their own, not attached to the skeleton (surely "skeleton" sounds better than "broomsticks" ;p) of the robot, and just float around thanks to the rigidity of the corrugated pipes that bundle them. This causes no problem for these first tests, but in future revisions we'll probably want to specify where they are and be sure Upkie can go through its full range of motion without pulling a cable out.
Build instructions are in Upkie's wiki.
Create an account to leave a comment. Already have an account? Log In.
That would be cool 😀 Especially to put the wheels on non-coplanar surfaces (like stairs, or just the two wheels on different slopes). We'd have to implement some form of lateral balancing, and check that the wheel BLDC motors have enough torque to lock the wheels in place as Upkie steps.
Please add a head for vision and two arms so this wonderful robot you've created can be truly useful!
I've been experimenting a bit with Raspberry Pi camera modules, you can see one for instance at the end of https://www.youtube.com/shorts/ccFbJTHtiAQ. They are a viable option for vision, and the locomotion code leaves one CPU code mostly free for extra tasks, so that's one way to try visual processing with Upkie.
I haven't tried arms, but the pi3hat on Upkie has two unused CAN-FD ports (JC3 and JC4) that can be used to control up to one 3-DoF arm each. I'd be curious to see folks add arms to Upkie! I'd gladly help best I can with advice or SW support for that 😃
For hollow legs, how about ABS plastic pipe used for sprinkler systems? It comes in 1/2", 3/4" and 1" diameter.
Could work! How would you rigidly attach the plastic pipe to the actuator's output shaft? (This is likely a basic question, I'm a mechanical newbie.)
When Upkie's legs were sawed broomsticks, I attached them to the output "horn" on the actuator shaft using pressure screws. They work fine at first, but as the robot moves and various efforts are exerted on the screws the connection deteriorates over date (the screw digs a hole in the wood that widens with effort).
This is a phenomenal project, very excited to see it develop.
Thanks! In November-December it will be mostly software updates (pink and upkie_locomotion packages) on GitHub: https://github.com/tasts-robots/ Then back to hardware with the hollow shins!
Following up: on the software side, upkie_locomotion is now on PyPI (pip install upkie_locomotion) and its API has leveled up so that we can run motion controllers in a few lines of Python. On the hardware side, the next project log will be on the hollow shins 😉
Become a member to follow this project and never miss any updates
hello,Can it achieve biped walking in the future?