Integration Project Systems and Control 2013 Group 1: Difference between revisions
Jump to navigation
Jump to search
| Line 97: | Line 97: | ||
== Progress == | == Progress == | ||
==== | ==== Feb 18 - Feb 24 ==== | ||
Regarding our planning for the first week we came up with the following conclusions: | Regarding our planning for the first week we came up with the following conclusions: | ||
{| | {| | ||
| Line 105: | Line 105: | ||
| -we can control the move of each axis (and so each motor) separately cause they are independent. So it is needed to construct 4 PID controller, since we can handle the problem as a 4 SISO systems problem. | | -we can control the move of each axis (and so each motor) separately cause they are independent. So it is needed to construct 4 PID controller, since we can handle the problem as a 4 SISO systems problem. | ||
|- | |- | ||
| -the design of PID controller is based on the fact that | | -the design of PID controller is based on the fact that is should follow the setpoint trajectory. | ||
|- | |- | ||
| -we will use as inputs for each motor sine wave, and to represent the disturbance we will use white noise. | | -we will use as inputs for each motor sine wave, and to represent the disturbance we will use white noise. | ||
|- | |- | ||
| -regarding the design criteria we need total time to transfer the pizzas at about 15 secs(less than that if it is possible), as high as possible velocity and acceleration (we have to take care that the pizzas should not fall down from the fork during the movement of the robot) and also the fork should not touch the holding brackets of the pizzas. | | -regarding the design criteria we need total time to transfer the pizzas at about 15 secs(less than that if it is possible), as high as possible velocity and acceleration (we have to take care that the pizzas should not fall down from the fork during the movement of the robot) and also the fork should not touch the holding brackets of the pizzas. Also, the controller should work with sampling frequency of 500 Hz, because this is the sampling frequency of the system. | ||
|} | |||
==== Feb 25 - Mar 3 ==== | |||
Regarding our planning for the second week we came up with the following conclusions: | |||
{| | |||
|- | |||
|-the system can be approached as 4 SISO systems so we do not have problems regarding coupled phenomena. | |||
|- | |||
| -we designed the stabilizing controller for our plant (PID controller) | |||
|- | |||
| -regarding the system identification procedures, we decided to perform FRF measurements.We took the FRF measurements applying both sine waves and white noise in order to avoid the non-linearities since FRF method refers to linear models-systems. | |||
|- | |||
| -about the friction model, we will check it on a later stage together with the feedforward control. | |||
|} | |} | ||
Revision as of 12:31, 7 March 2013
Group Members
| Name: | Student id: | Email: |
| Abhishek Bareja | 0825433 | a.bareja@student.tue.nl |
| Ioannis Kokkinakis | 0832282 | i.kokkinakis@student.tue.nl |
| Evangelos Stamatopoulous | 0827743 | e.stamatopoulos@student.tue.nl |
| Donatella De Cesare | 0821444 | d.de.cesare@student.tue.nl |
Planning
| Week: | |
|---|---|
| Feb 18 - Feb 24 | |
| Literature Study regarding the following aspects: | |
| - matlab files provided | |
| - inputs/output variables regarding the given model | |
| - different types of controller | |
| - design Criteria | |
| Lab activity: | |
| - meeting the robot | |
| - how the robot moves | |
| Feb 25 - Mar 3 | |
| Literature study regarding the following aspects: | |
| - non-linearities | |
| - friction model | |
| - coupled phenomena | |
| - design a PID feedback controller(preparation for the lab) | |
| - system identification procedures | |
| - FRF measurement(preparation for the lab) | |
| Lab activity: | |
| - design the stabilizing(PID) controller | |
| - get the FRF measurements | |
| Mar 4 - Mar 10 | |
| Literature study regarding the following aspects: | |
| - feedforward Controller | |
| - design criteria (bandwidth, margins, sensitivity, steady state error, time response) | |
| - work with shapeit to design optimal controllers for each axis (prepare the controllers to test them during the lab) | |
| - reference trajectory(preparation for the lab) | |
| Lab activity: | |
| - get the FRF measurements for the left robot | |
| - test the controllers that we construct on shapeit | |
| - get the reference trajectory |
Progress
Feb 18 - Feb 24
Regarding our planning for the first week we came up with the following conclusions:
| -making a literature research, we realized that PID controller is used in most industrial robots, and since it is the type of controller with which we are more familiar with, we will use PID. |
| -we can control the move of each axis (and so each motor) separately cause they are independent. So it is needed to construct 4 PID controller, since we can handle the problem as a 4 SISO systems problem. |
| -the design of PID controller is based on the fact that is should follow the setpoint trajectory. |
| -we will use as inputs for each motor sine wave, and to represent the disturbance we will use white noise. |
| -regarding the design criteria we need total time to transfer the pizzas at about 15 secs(less than that if it is possible), as high as possible velocity and acceleration (we have to take care that the pizzas should not fall down from the fork during the movement of the robot) and also the fork should not touch the holding brackets of the pizzas. Also, the controller should work with sampling frequency of 500 Hz, because this is the sampling frequency of the system. |
Feb 25 - Mar 3
Regarding our planning for the second week we came up with the following conclusions:
| -we designed the stabilizing controller for our plant (PID controller) |
| -regarding the system identification procedures, we decided to perform FRF measurements.We took the FRF measurements applying both sine waves and white noise in order to avoid the non-linearities since FRF method refers to linear models-systems. |
| -about the friction model, we will check it on a later stage together with the feedforward control. |