So, you want to build an H-bot?
The H-bot is conceptually simple, but the design of the controls makes it amazing.
Kevin C Craig, PhD -- EDN, May 26, 2011
Designers of modern robotics based their systems on
modularity. Instead of using one six-axis robot for all
applications, mechatronics engineers design a robot
for each application. This approach places more emphasis on
model-based design and system integration.The H-bot, so-named because it resembles the letter H, is an example of such a robot. This 2-D robot, a planar mechanism for positioning an object in XY space, such as a plane, finds use in many industrial applications, such as pick-and-place, sorting, gluing, and inspection systems. It is easy to manufacture because it comprises two motors, a timing belt, and two perpendicularly mounted rails (Figure 1). Despite its dynamic simplicity, friction, backlash, and compliance throughout the mechanism are impediments to accurate positioning and represent system-design challenges.
As in any coordinated-motion system,
the computation
of the position
command to each
motor of the H-bot
is just as important
as the control
scheme you employ
to control the robot.
The successful combination
of these
two aspects will lead
to accurate positioning,
but that concept
means different
things depending
on the application.
In point-to-point-system
applications, such as a pick-and-place system,
accurately moving to the target position
is the main concern, whereas
tracking applications, such as a gluing
system, require a low number of
position-following errors.Motion applications typically use a cascade-control system that comprises position, velocity, and current loops, all typically proportional integral. Additional features, such as velocity feedforward to reduce position-following error and acceleration feedforward to reduce velocity-following error, are also usually part of the control architecture.
Many mechatronics engineers lack a thorough understanding of the position-command computation. Its complexity depends on the shape of the path the robot must follow. Paths with sharp corners, such as a square, are challenging to accurately reproduce with a machine. The challenge resides in accurately following sharp corners. Poor implementation of the calculation of the position command causes an overshoot on the corner, yielding imperfections in the product.
One approach to mitigating this effect produces perfect corners for a square shape with an H-bot. In this approach, each side of the square becomes a segment on the motion profile, which is defined by the geometry of a square projected on X and Y axes. Thus, you obtain the profile X and Y axes in the Cartesian space. You then employ the inverse kinematics of the robot to obtain the position profile at the motor shafts. Use a master axis to obtain synchronization between axes. The motion profile of this master axis plays a key role in creating perfect corners. Four segments that start and end at each corner of the square shape define this profile. To reduce machine vibration, wear, and noise, use a smooth profile, such as a fifth-order polynomial profile, to define the motion of the master axis from corner to corner.
You can find details on the design and construction of an H-bot, including modeling, analysis, control design, and experimental validation, at www.multimechatronics.com.
Talkback
-
I disagree about not being able to move fast. Servos and controls are key. In the case of a high speed move, you'd actually encourage some "rounding of the corners" or interpolated moves. In the video I filmed for our 400 watt servo high speed H-Bot on our YouTube channel, we ran a classic square corner (point to point)move. You can't see it, but we literally had two men holding the T-Bot (H-Bot) robot to the base table frame using a, 40mm x 120mm beam of aluminum. At the highest speeds, they were leaning with all their weight just to keep the robot on the table. Macron Dynamics dot com has links or just Google: T Robot 2 Axis X-Z
Steven Evers - 2012-11-5 13:19:43 PDT -
Square corners are not a problem until you want to move at any reasonable speed. This is particularly true with robots, where stepping through a profile at the safe programming speeds would yield an excellent profile, but then running at production speeds will result in quite severely rounded corners. Of course, there are ways around this problem, but they all either slow the motion or add a large amount of complexity, or do both. The "H-bot" is an interesting case, but note that programming each "side" as a separate motion profile will do exactly as I predicted, which is slow the process.
William Ketel. - 2011-31-5 15:23:24 PDT


















Kevin C Craig, PhD,
is the Robert C Greenheck
chair in engineering
design and a professor of
mechanical engineering,
College of Engineering,
Marquette University.
For more mechatronic
news, visit 



