Control: Difference between revisions
| (43 intermediate revisions by the same user not shown) | |||
| Line 10: | Line 10: | ||
[[File:blockdiagram_software.png|700px]] | [[File:blockdiagram_software.png|700px]] | ||
Figure 1. Overview of software data flow. Yellow | Figure 1. Overview of software data flow. Yellow are the control blocks. | ||
Green is hardware (motor and sensors), | Green is hardware (motor and sensors), and light-green is calculations. Light blue is obtained values. | ||
Gray is input values. | Gray is input values. | ||
The sample time for all controllers and data values is 1ms. | |||
All software is written in c++, based on Arduino libraries. | All software is written in c++, based on Arduino libraries. | ||
Most controllers can be switched off (not enabled). When switched off there | Most controllers can be switched off (not enabled). When switched off, there is no connection from reference input to output. If a direct open loop is desired, enable the controller with a Kp = 0 and a feed-forward Kff = 1 (or any other relevant value). This can be valid for measuring the open-loop system in some cases. | ||
'''Note''': The turn-radius controller (top-left) is not a controller but feed-forward only. The nominal speed for each wheel for a given turn radius is calculated, but the resulting turn rate is not measured. The end angle of the turn (part of the tr command line) is measured, but the turn is stopped a bit before the end angle is reached. Subsequently, the specified angle is reached (and controlled by "Turn control") on the following straight path. | |||
* [[Design calculations]] | * [[Design calculations]] | ||
| Line 27: | Line 29: | ||
[[File:Gui_control_data_points.png | 800px]] | [[File:Gui_control_data_points.png | 800px]] | ||
Figure 2. The general PID controller design with additional optional controller parts. "'''r'''" is reference input. And after the optional "'''pre-filter'''" the reference is compared with the measured value "'''m'''", optionally through a Lead filter. The "'''m-dot'''" is an optionally derivative of the measurement, that can be used for a less noisy Lead (with tau_d as normal, but no pole). The error signal "'''e'''" is fed through a gain "'''Kp'''", an optional Lead and an optional integrator. After this the output "'''u1'''" is summed from "'''up'''" (proportional/Lead), "'''ui'''" integrator term and "uf" from an optional feed forward branch. The output "'''u1'''" can further optionally be integrated (if '''Kz'''=0, if '''Kz'''=1 then the post-integrator has a zero). The output is finally limited to signal "'''u'''". | Figure 2. The general PID controller design with additional optional controller parts. "'''r'''" is reference input. And after the optional "'''pre-filter'''" the reference is compared with the measured value "'''m'''", optionally through a Lead filter. The "'''m-dot'''" is an optionally derivative of the measurement, that can be used for a less noisy Lead (with tau_d as normal, but no pole). The error signal "'''e'''" is fed through a gain "'''Kp'''", an optional Lead and an optional integrator. After this the output "'''u1'''" is summed from "'''up'''" (proportional/Lead), "'''ui'''" integrator term and "uf" from an optional feed forward branch. The output "'''u1'''" can further optionally be integrated (if '''Kz'''=0, if '''Kz'''=1 then the post-integrator has a zero). The output is finally limited to signal "'''u'''". There is more than one '''t2''' (called tau_pole in the interface) and '''ti''' values in the diagram, but they are all individually setable. | ||
All integrators can be limited. The integrators are further disabled if the output limiter limits the output. Some of the control interfaces (all but the balance controllers) further disables integrators when there is defined an acceleration limit in the mission, and | All integrators can be limited. The integrators are further disabled if the output limiter limits the output. Some of the control interfaces (all but the balance controllers) further disables integrators when there is defined an acceleration limit in the mission, and these actually are limiting the acceleration. | ||
The "'''post-integrator'''" is (mostly) usable in the balance controller. | The "'''post-integrator'''" is (mostly) usable in the balance controller. | ||
The "'''feed forward'''" is (mostly) usable for the velocity control. | |||
The balance controller replaces the "'''Lead'''" after "'''m'''" with a "1", and uses tau_d after "'''m-dot'''", and "'''m-dot'''" is connected to tilt velocity from the gyro (see also figure 1). | The balance controller replaces the "'''Lead'''" after "'''m'''" with a "1", and uses tau_d after "'''m-dot'''", and "'''m-dot'''" is connected to tilt velocity from the gyro (see also figure 1). | ||
The yellow circles show points in the controller that can be logged (with the indicated names), see also | The yellow circles show points in the controller that can be logged (with the indicated names), see also [[User_interface#Data_logger]]. | ||
===Controller configuration=== | ===Controller configuration=== | ||
| Line 41: | Line 45: | ||
All controllers can be configured from the "control" page of the GUI. | All controllers can be configured from the "control" page of the GUI. | ||
[[File:Gui_control.png | 800px]] | <!-- [[File:Gui_control.png | 800px]] --> | ||
[[File:control_tab.png | 700px]] | |||
Figure 3. All control values are set from this page, click on the relevant controller and enter the relevant values in the dialogue window shown below. | Figure 3. All control values are set from this page, click on the relevant controller and enter the relevant values in the dialogue window shown below. | ||
| Line 47: | Line 52: | ||
[[File:Gui_control_dialog.png | 500px]] | [[File:Gui_control_dialog.png | 500px]] | ||
Figure 4. This dialogue configures the wheel velocity controller - shown as a PI-controller with output limit at (+/-) 9V and a lead in the feedback branch with a | Figure 4. This dialogue configures the wheel velocity controller - shown as a PI-Lead-controller with output limit at (+/-) 9V and a lead term in the feedback branch. A feed-forward is active with a constant gain. All other options are disabled. The blue framed boxes indicate a traditional PID controller with lead in forward (and)/or in the feedback branch. | ||
In figure 4 the control is set to feed-forward only (Kp=0 and a Kf=4), there is further a transfer function in the feedback path with a pole with tau_pole=0.005, a low pass filter with a time constant of 5ms, which for this robot is a good idea the reduce the noise in the velocity measurements. | |||
The output is here limited to +/-9V. | |||
The integrator with an integration limit can be set. | |||
Feedforward is in figure 4 set with a constant gain of 4, but a pole-zero pair could be added too. | |||
NB! As velocity measurements are rather noisy, the filter in the feedback path (Lead/Lag in feed back) could be implemented as a low-pass filter with tau_zero = 0 and tau_pole = 0.005 (recommended). | |||
== Calibration== | == Calibration== | ||
| Line 57: | Line 70: | ||
=== IMU=== | === IMU=== | ||
The IMU page shows data from the IMU, and is used for tilt | The IMU (Inertial Measurement Unit) page shows data from the IMU, and is used for tilt measurements. | ||
If the "'''IMU'''" tab is not visible, then enable it in the "'''Show'''" menu line. | If the "'''IMU'''" tab is not visible, then enable it in the "'''Show'''" menu line. | ||
[[File:Gui_IMU.png | 700px]] | <!-- [[File:Gui_IMU.png | 700px]] --> | ||
[[File:imu_board_orientation.png | 700px]] | |||
Figure 5. IMU data, gyro, accelerometer and tilt. The Gyro can be calibrated from here. The IMU board should be calibrated to show zero tilt, when in balance. | |||
* See [[Regbot calibration]] for IMU calibration. | |||
== Heading control feature == | |||
=== | === Heading control and motor voltage saturation === | ||
The | The heading controller changes the velocity reference for the two motor-velocity controllers. | ||
When any of these controllers are limited (by the velocity controller or the battery voltage), the commanded voltage out of the velocity controllers is reduced by a factor. This reduction ensures that the relative velocity difference is kept so that the heading controller is still active. | |||
An example can be seen in figure 6 when the output limit of the velocity controller is set to 6V. | |||
The mission is: | |||
thread=4 | |||
log=10.0: time=0.1 | |||
vel=1.0: dist=1.0, time=10.0, log=0 | |||
vel=0.0, acc=2.0: time=1.5 | |||
Where velocity is commanded to increase velocity from zero to 1m/s after 100ms. The velocity controller would suggest a very high motor voltage, and the output limiter is set to 6V. If one of the motor controllers exceeds the maximum motor voltage, then both motor voltages are reduced with a factor that ensures no voltage is above the limit. The effect can be seen in the first 0.4 seconds. | |||
[[File:steering_with_saturation.png | 500px]] | |||
[[File:steering-with-saturation-heading.png | 500px]] | |||
Figure 6. The left plot shows the motor voltage when the robot accelerates from 0 to 1m/s, and the motor voltage is limited to 6V. The steering control is active during acceleration. The green graph in the right plot shows that the heading is kept within +/- 0.5 degrees during acceleration. | |||
To the right, it can be seen that it takes a little more than 1 second to reach 1m, and the deceleration starts. | |||
Latest revision as of 13:03, 7 December 2023
Back to Regot main page.
The main purpose of the robot is to train control theory.
Robot overview
The figure gives the robot functionality with focus on control.
Figure 1. Overview of software data flow. Yellow are the control blocks. Green is hardware (motor and sensors), and light-green is calculations. Light blue is obtained values. Gray is input values.
The sample time for all controllers and data values is 1ms. All software is written in c++, based on Arduino libraries.
Most controllers can be switched off (not enabled). When switched off, there is no connection from reference input to output. If a direct open loop is desired, enable the controller with a Kp = 0 and a feed-forward Kff = 1 (or any other relevant value). This can be valid for measuring the open-loop system in some cases.
Note: The turn-radius controller (top-left) is not a controller but feed-forward only. The nominal speed for each wheel for a given turn radius is calculated, but the resulting turn rate is not measured. The end angle of the turn (part of the tr command line) is measured, but the turn is stopped a bit before the end angle is reached. Subsequently, the specified angle is reached (and controlled by "Turn control") on the following straight path.
Control loop configuration
All control blocks (yellow boxes in the figure 1 above) can be configured as P, PI, P-Lead and PI-Lead controllers, with the possibility for a (1st order) prefilter, a (1st order) feed forward and a post integrator. The Lead can be implemented in the forward and return branch, and can also be used more flexible with any pole and zero combination, but all with a steady state gain of 1.
Figure 2. The general PID controller design with additional optional controller parts. "r" is reference input. And after the optional "pre-filter" the reference is compared with the measured value "m", optionally through a Lead filter. The "m-dot" is an optionally derivative of the measurement, that can be used for a less noisy Lead (with tau_d as normal, but no pole). The error signal "e" is fed through a gain "Kp", an optional Lead and an optional integrator. After this the output "u1" is summed from "up" (proportional/Lead), "ui" integrator term and "uf" from an optional feed forward branch. The output "u1" can further optionally be integrated (if Kz=0, if Kz=1 then the post-integrator has a zero). The output is finally limited to signal "u". There is more than one t2 (called tau_pole in the interface) and ti values in the diagram, but they are all individually setable.
All integrators can be limited. The integrators are further disabled if the output limiter limits the output. Some of the control interfaces (all but the balance controllers) further disables integrators when there is defined an acceleration limit in the mission, and these actually are limiting the acceleration.
The "post-integrator" is (mostly) usable in the balance controller.
The "feed forward" is (mostly) usable for the velocity control.
The balance controller replaces the "Lead" after "m" with a "1", and uses tau_d after "m-dot", and "m-dot" is connected to tilt velocity from the gyro (see also figure 1).
The yellow circles show points in the controller that can be logged (with the indicated names), see also User_interface#Data_logger.
Controller configuration
All controllers can be configured from the "control" page of the GUI.
Figure 3. All control values are set from this page, click on the relevant controller and enter the relevant values in the dialogue window shown below.
Figure 4. This dialogue configures the wheel velocity controller - shown as a PI-Lead-controller with output limit at (+/-) 9V and a lead term in the feedback branch. A feed-forward is active with a constant gain. All other options are disabled. The blue framed boxes indicate a traditional PID controller with lead in forward (and)/or in the feedback branch.
In figure 4 the control is set to feed-forward only (Kp=0 and a Kf=4), there is further a transfer function in the feedback path with a pole with tau_pole=0.005, a low pass filter with a time constant of 5ms, which for this robot is a good idea the reduce the noise in the velocity measurements.
The output is here limited to +/-9V.
The integrator with an integration limit can be set.
Feedforward is in figure 4 set with a constant gain of 4, but a pole-zero pair could be added too.
NB! As velocity measurements are rather noisy, the filter in the feedback path (Lead/Lag in feed back) could be implemented as a low-pass filter with tau_zero = 0 and tau_pole = 0.005 (recommended).
Calibration
For especially the balance control the gyro offset and the balance point need to be calibrated using the REGBOT GUI application.
IMU
The IMU (Inertial Measurement Unit) page shows data from the IMU, and is used for tilt measurements.
If the "IMU" tab is not visible, then enable it in the "Show" menu line.
Figure 5. IMU data, gyro, accelerometer and tilt. The Gyro can be calibrated from here. The IMU board should be calibrated to show zero tilt, when in balance.
- See Regbot calibration for IMU calibration.
Heading control feature
Heading control and motor voltage saturation
The heading controller changes the velocity reference for the two motor-velocity controllers. When any of these controllers are limited (by the velocity controller or the battery voltage), the commanded voltage out of the velocity controllers is reduced by a factor. This reduction ensures that the relative velocity difference is kept so that the heading controller is still active.
An example can be seen in figure 6 when the output limit of the velocity controller is set to 6V. The mission is:
thread=4 log=10.0: time=0.1 vel=1.0: dist=1.0, time=10.0, log=0 vel=0.0, acc=2.0: time=1.5
Where velocity is commanded to increase velocity from zero to 1m/s after 100ms. The velocity controller would suggest a very high motor voltage, and the output limiter is set to 6V. If one of the motor controllers exceeds the maximum motor voltage, then both motor voltages are reduced with a factor that ensures no voltage is above the limit. The effect can be seen in the first 0.4 seconds.
Figure 6. The left plot shows the motor voltage when the robot accelerates from 0 to 1m/s, and the motor voltage is limited to 6V. The steering control is active during acceleration. The green graph in the right plot shows that the heading is kept within +/- 0.5 degrees during acceleration. To the right, it can be seen that it takes a little more than 1 second to reach 1m, and the deceleration starts.
