1 Gait control tables

Each articulation is characterized by the angle between the two segments it links. The shape of the worm, at a given instant $t$, is determined by the angular position vector $\overrightarrow{\varphi(t)}=(\varphi_{1},\varphi_{2},...,\varphi_{n})$. Figure [*] shows a six articulations worm-like robot and the angular position vector at a given time.

Figure: Angular position vector for a worm-like robot composed of 6 articulations: $\protect\overrightarrow{v}=(\varphi_{1},\varphi_{2},\varphi_{3},\varphi_{4},\varphi_{5,}\varphi_{6})$
\includegraphics[%
scale=0.8]{ps/vector_angular.eps}

For every instant, an angular position vector there exist, determining the shape of the worm: $\overrightarrow{\varphi(t_{0})},\overrightarrow{\varphi(t_{1})},...,\overrightarrow{\varphi(t_{m})}$. The control table is a matrix, which rows contains the angular position vectors for every instant. In order to generate the movement, the controller has to read the table, row by row, positioning the servos.

In robots like Polybot, this tables are pre-calculated and downloaded into the modules. Each table represents one gait. It is not possible to calculate or store all the possible tables for all the different gaits. Those tables are generated automatically in Cube.

Juan Gonzalez 2004-10-08