mls94-complete[1]
.pdf
xd |
h(θd, xd) = 0 |
θd |
Finger |
θ |
h(θ, x) = 0 |
x |
||
|
1 |
|
||||||
|
|
|
|
|||||
|
|
|
|
|
τ |
|
|
|
|
|
τd |
|
|
|
|
|
|
|
|
M1, C1, N1 |
|
|
||||
|
|
θd |
Finger |
θ |
|
|
||
|
|
|
2 |
|
|
|
||
|
|
|
|
|
τ |
|
|
|
Fd |
τd = J T G+Fd |
τd |
|
|
|
F = GJ −T τ |
F |
|
|
|
M2 |
, C2 |
, N2 |
|
|
||
|
|
|
Payload |
|
|
|
||
|
|
|
Mp, Cp |
, Np |
˜ ˜ ˜ |
|
||
|
|
|
|
|
|
|
M , C, N |
|
Figure 6.11: Data flow between two robots which have been attached to a payload.
xd |
control |
xc |
robot |
|
x |
|
|
||||
Fd |
law |
Fc |
object |
|
F |
|
|
|
|||
|
|
|
|
||
|
|
|
M, C, N |
|
|
|
|
|
˜ |
˜ |
˜ |
|
|
|
M , C, N |
||
Figure 6.12: Data flow in a typical controlled robot.
no longer a dynamic object, but rather that controllers at higher levels can ignore the dynamic properties of the robot, since they are being compensated for at a lower level. At the other end of the spectrum, a controller may make no attempt to compensate for the inertia of a robot, in which case it should pass the dynamic attributes on to the next higher level. Controllers which lie in the middle of this range may partially decouple the dynamics of the manipulator without actually completely compensating for them.
Building hierarchical controllers
The operation described above allow us to build complex hierarchical control laws for robot systems. Since a controller accepts a robot object and
306
