Robobot architecture
From Rsewiki
(Difference between revisions)
(→RSE level 1) |
|||
Line 10: | Line 10: | ||
[[File:robobot_level_1.png | 800px]] | [[File:robobot_level_1.png | 800px]] | ||
+ | |||
+ | Figure 2. The lowest level in the control software. The encoder ticks are received form the hardware (from the Teensy microprocessor) in the sensor interface. The encoder values are then modeled into an odometry pose. The pose is used to control the wheel velocity using a PID controller. | ||
+ | The desired wheel velocity for each wheel is generated in the mixer from a desired linear and rotational velocity. | ||
+ | |||
+ | == RSE level 2 == | ||
[[File:robobot_level_2.png | 800px]] | [[File:robobot_level_2.png | 800px]] | ||
+ | |||
+ | Figure 3. At level 2 further sensor data is received, modelled and used as optional control sources. |
Revision as of 12:08, 20 June 2023
Back to Robobot B
NASREM
The software architecture is based on the old NASREM architecture, and this is the structure for the description on this page.
RSE level 1
Figure 2. The lowest level in the control software. The encoder ticks are received form the hardware (from the Teensy microprocessor) in the sensor interface. The encoder values are then modeled into an odometry pose. The pose is used to control the wheel velocity using a PID controller. The desired wheel velocity for each wheel is generated in the mixer from a desired linear and rotational velocity.
RSE level 2
Figure 3. At level 2 further sensor data is received, modelled and used as optional control sources.