The EEROS Education Robotics Platform

User Tools

Site Tools

You are here: EEDURO Delta Robot » Control System
control_system

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
control_system [2019/12/01 07:47] – [Inputs] grafcontrol_system [2023/05/11 17:13] (current) – [Motor Model] ursgraf
Line 1: Line 1:
 ====== Control System ====== ====== Control System ======
 +
 +The coordinate system is as follows
 +[{{ :delta:software:orientation.png?200 |//Orientation of the axis// }}]
 +In z direction, positive values move the TCP upwards.
 +\\
 +
 The figure below shows the complete control system for our delta roboter.  The figure below shows the complete control system for our delta roboter. 
-{{:delta:software:controlsystem.png|Control System of the Delta Roboter}}+{{:delta:software:controlsystem.png|//Control System of the Delta Roboter//}}
  
  
Line 8: Line 14:
 Lets start with the blue box at the bottom center of the diagram. This box represent the motors including the gears and the encoders. The encoders are defined as ''Peripheral Input''. This ''Peripheral Inputs'' are described in the HAL configuration file, see [[hal|]]. To initialize the encoder inputs, you have to call the constructor of the ''Peripheral Input'' and add the respective ''signalId'' from the HAL configuration file as parameter, e.g. Lets start with the blue box at the bottom center of the diagram. This box represent the motors including the gears and the encoders. The encoders are defined as ''Peripheral Input''. This ''Peripheral Inputs'' are described in the HAL configuration file, see [[hal|]]. To initialize the encoder inputs, you have to call the constructor of the ''Peripheral Input'' and add the respective ''signalId'' from the HAL configuration file as parameter, e.g.
 <code c> <code c>
-eeros::control::PeripheralInput<double> encoder1("enc1");+eeros::control::PeripheralInput<double> enc1("enc1");
 </code> </code>
 If the HAL is configured correctly, we get the current position in radian of each encoder. Next, the ''Mux'' collects the three encoder values and puts them into an ''AxisVector''. ''AxisVector'' is defined as  If the HAL is configured correctly, we get the current position in radian of each encoder. Next, the ''Mux'' collects the three encoder values and puts them into an ''AxisVector''. ''AxisVector'' is defined as 
Line 14: Line 20:
 using AxisVector = eeros::math::Matrix<3, 1>; using AxisVector = eeros::math::Matrix<3, 1>;
 </code> </code>
 +The mouse delivers a signal with four dimensions. As we do not use the fourth dimension (additional wheel would be necessary) we have to reduce the mouse signal to three dimensions with a special block. At the same time this block swaps x and y axis in order to adapt to the axis setup of the robot. 
  
  
Line 26: Line 33:
   * The ''Mouse Input'' gets the movement of the mouse. We use this block to manually control the Delta robot. The output of the ''Mouse Input'' is an vector with 4 entries. We must reduce it to 3 containing x, y, z.   * The ''Mouse Input'' gets the movement of the mouse. We use this block to manually control the Delta robot. The output of the ''Mouse Input'' is an vector with 4 entries. We must reduce it to 3 containing x, y, z.
  
-==== Headline ====+You have to make sure, that the path planner delivers a path with a acceleration and velocity which can in fact be achieved by the robot. If not, the arm might move in unpredictable ways. That is, moving from e.g. 0/5 to 5/5 must be made in a straight line. 
  
-The "Motor Model" gets the actual speed and the calculated torque as input, and outputs the desired voltage for each motor.\\  +==== Controller ==== 
-The "voltageSetPoint" serves for the initializing of the encoder. This block is no longer used after reaching Safety Level "systemReady".+ 
 +The position of the TCP is controlled by taking in the setpoint (see above) and adding planned velocities and accelerations. The resulting total acceleration is then fed into the block 'Inertia' which - through Newton's law - calculates the resulting force. This force is still in cartesian coordinates and has to be translated into torques applied to each of the three motors.  
 + 
 +==== Motor Model==== 
 +As our board cannot only control voltages fed to each motor, we must use a motor model to calculate these voltages. The block 'Motor Model' gets the actual speed and the calculated torque as input, and outputs the desired voltage for each motor. We must also take the gear into account. The speed is reduced by the gear ratio while the torque must be multiplied with the same ratio. The following equation holds 
 +<code> 
 +U = kM * w + I * RA + dI/dt * L  
 +</code> 
 +with I = M / kM and dI/dt * L beeing very small with our motors and accounting for the gear i we get 
 +<code> 
 +U = kM * w * i + M * RA / (kM * i) 
 +</code>
 ==== Outputs ==== ==== Outputs ====
 The drive signals to the motor are of type ''PeripheralOutput''. They are described in the HAL as well. The drive signals to the motor are of type ''PeripheralOutput''. They are described in the HAL as well.
 +<code c>
 +eeros::control::PeripheralInput<double> mot1("motor1");
 +</code>
 +
 +The block 'voltageSetPoint serves for the initializing of the encoder when homing. It drives the motors with slow speed into a mechanical stop. This block is no longer used after reaching Safety Level ''systemReady''.
control_system.1575182835.txt.gz · Last modified: 2019/12/01 07:47 by graf