Editing Signal path of motor drive

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help page.

Latest revision Your text
Line 5: Line 5:
 
===Setpoint signal path===
 
===Setpoint signal path===
 
Main parts are:
 
Main parts are:
*Input multiplier. Purpose of this is to increase resolution of input setpoint to allow more fine grained velocity & acceleration control in trajectory planner. By default {{param|MUL}} value is 50.
+
*Input multiplier. Purpose of this is to increase resolution of input setpoint to allow more fine grained velocity & acceleration control in trajectory planner. By default [[MUL]] value is 50.
 
*Setpoint smoothing filter. If enabled, applies low pass filter to signal reducing jitter and roughness of signal but also introduces about some delay. By default the filter has 100% attenuation at 250Hz.
 
*Setpoint smoothing filter. If enabled, applies low pass filter to signal reducing jitter and roughness of signal but also introduces about some delay. By default the filter has 100% attenuation at 250Hz.
*[[Trajectory planner]]. This limits rate of change of setpoint signal based on {{param|CVL}} and {{param|CAL}} parameters. Output rate maximum rate of change:
+
*Trajectory planner. This limits rate of change of setpoint signal based on [[CVL]] and [[CAL]] parameters. Output rate maximum rate of change:
**Velocity changes max {{param|CAL}} nubmer of units per [[control cycle]] (control cycle is 400µs in most GD drives)
+
**Velocity changes max [[CAL]] nubmer of units per [[control cycle]] (control cycle is 400µs in most GD drives)
**Velocity maximum value is limited to {{param|CVL}}
+
**Velocity maximum value is limited to [[CVL]]
*Input divider. This divides setpoint signal by {{param|DIV}} to give desired output scale for ''internal setpoint''. Combination of multiplier and divider can be used change total scaling of setpoint signal.
+
*Input divider. This divides setpoint signal by [[DIV]] to give desired output scale for ''internal setpoint''. Combination of multiplier and divider can be used change total scaling of setpoint signal.
  
  
Line 29: Line 29:
 
* Velocity mode: frequency input, setpoint = number of edges of either channel per [[control cycle]]
 
* Velocity mode: frequency input, setpoint = number of edges of either channel per [[control cycle]]
 
|-
 
|-
| PWM || rowspan="2" |Absolute || Full input scale equals setpoint range of +/-16384. In loss of PWM signal, setpoint is 0. || rowspan="3" |
+
| PWM || rowspan=2 |Absolute || Full input scale equals setpoint range of +/-16384. In loss of PWM signal, setpoint is 0. || rowspan=3 |
 
*Direct 1:1 absolute value in position mode
 
*Direct 1:1 absolute value in position mode
*Velocity & torque mode: +/-16384 represents full torque or speed scale
+
*Velocity & torque mode: +/-16834 represents full torque or speed scale
 
|-
 
|-
 
| Analog || Full input scale equals setpoint range of +/-16384  
 
| Analog || Full input scale equals setpoint range of +/-16384  
Line 38: Line 38:
 
|}
 
|}
  
It should be noted that trajectory planner operates after multiplier meaning that {{param|CVL}} velocity limit value is not in equal scale with velocity setpoint value.
+
It should be noted that trajectory planner operates after multiplier meaning that [[CVL]] velocity limit value is not in equal scale with velocity setpoint value.
  
 
===Internal setpoint===
 
===Internal setpoint===
Line 44: Line 44:
 
*Position mode: position sensor [[Quadrature|counter]] raw value
 
*Position mode: position sensor [[Quadrature|counter]] raw value
 
*Velocity mode: internal goes through '''Velocity normalized''' that changes scales depending on setpoint source:
 
*Velocity mode: internal goes through '''Velocity normalized''' that changes scales depending on setpoint source:
**In PWM & Analog source: Internal setpoint of +/-16384 represents whole speed range covered by {{param|CVL}} parameter. I.e. 10V input to analog input runs motor at 100% speed and -5V at -50% etc.
+
**In PWM & Analog source: Internal setpoint of +/-16384 represents whole speed range covered by [[CVL]] parameter. I.e. 10V input to analog input runs motor at 100% speed and -5V at -50% etc.
 
**In all other sources: number of feedback device [[Quadrature|counts]] per one [[control cycle]]. Obtained by calculating the difference of position feedback values at every control cycle.
 
**In all other sources: number of feedback device [[Quadrature|counts]] per one [[control cycle]]. Obtained by calculating the difference of position feedback values at every control cycle.
*Torque mode: '''Torque normalizer''' scales internal setpoint so that value of +/-16384 represents full torque scale (i.e. internal setpoint value 16384 outputs configured peak current {{param|MMC}} and 8192 outputs {{param|MMC}}/2)
+
*Torque mode: '''Torque normalizer''' scales internal setpoint so that value of +/-16384 represents full torque scale (i.e. internal setpoint value 16384 outputs configured peak current [[MMC]] and 8192 outputs [[MMC]]/2)
  
 
==Controller==
 
==Controller==
Line 54: Line 54:
  
  
[[File:Driveblockdiagram controller.png|898x898px]]
+
[[File:Driveblockdiagram controller.png|800px]]
  
<nowiki>*</nowiki>) Update rates may be drive model specific. 2500 Hz and 20 kHz apply for most drives including IONI and ATOMI. However, torque control domain on ARGON is 17500 Hz.
 
==Calculation formulas and examples==
 
These examples focus on calculating values on a rotary motor and linear axis.
 
===Constants used later in calculations===
 
Assuming control cycle to be 400µs / 2500 Hz (default in GD drives):
 
  
<math>f=2500</math>
 
  
Calculation of how many counts the [[feedback devices|feedback device]] produces per one physical unit:
 
  
<math>X_{FeedbackDeviceCountsPerUnit}=4\frac{P_{FBR}}{P_{AXS}}</math>
+
==Setpoint scale examples==
 +
Assuming control cycle to be 400µs / 2500 Hz (default in GD drives).
  
AXS is a number that tells how many physical lenght units (such as millimeters a linear axis) translates per one rotary motor revolution.
+
===Example 1===
 +
;Calculating setpoint
 +
*Motor has 2500 P/R encoder (10000 CPR) and user wants to rotate it at 1000 rpm in velocity mode. Scaling is set to 1:1 (MUL/DIV ratio is 1)
 +
*Rotation speed is 1000/60 = 16.667 revs/s (RPS) Needed encoder count frequency is 16.667*10000 = 16667 counts/s.
 +
*Internal setpoint is the amount of counts per control cycle so in this case it's 16667/2500 = 66.667
  
===Example 1 - Calculating setpoint in position mode===
+
Because set point is integer value user must round setpoint to 66 or 67. To achieve exact speed, he could change input scaling (MUL/DIV) to allow unrounded value here.
Here we convert physical units (such as millimeters) to setpoint value in position control mode:
+
  
<math>setpoint=\frac{P_{MUL}}{P_{DIV}}*D_{DesiredPosition}*X_{FeedbackDeviceCountsPerUnit}</math>
+
;Calculating acceleration and velocity limits
 
+
If DIV is 50, then user must have [[CVL]] value at least 3333 (66.6667*50).
===Example 2 - Calculating value for CVL parameter===
+
Here we convert speed (such as mm/sec, or whatever lenght units AXS represents) to {{param|CVL}} value:
+
 
+
<math>P_{CVL}=\frac{V_{DesiredSpeedLimit}*X_{FeedbackDeviceCountsPerUnit}*P_{DIV}}{f}</math>
+
 
+
===Example 3 - Calculating value for CAL parameter===
+
Here we convert speed (such as mm/sec<sup>2</sup>, or whatever lenght units AXS represents) to {{param|CAL}} value:
+
 
+
<math>P_{CAL}=\frac{A_{DesiredAccelerationLimit}*X_{FeedbackDeviceCountsPerUnit}*P_{DIV}}{f^2}</math>
+
 
+
In alternative method we don't need acceleration value, but just time <math>t</math> in seconds to define how long motor should take to accelerate from zero speed to maximum speed defined by CAL:
+
 
+
<math>P_{CAL}=\frac{P_{CVL}}{tf}</math>
+
  
 +
If user wants motor to accelerate to 1000 rpm in 0.1 seconds, then [[CAL]] is value should be 3333/2500/0.1 = 13.33. Value must be again rounded to integer and rounding error could be reduced by adjusting scaling (adjust DIV).
 
{{tip|Granity calculates real world units thus it can be used to calculate and experiment with the scales. As scales are linear, interpolation of values is viable choice.}}
 
{{tip|Granity calculates real world units thus it can be used to calculate and experiment with the scales. As scales are linear, interpolation of values is viable choice.}}
 
==See also==
 
*[[Trajectory planner]]
 
 
[[Category:Development]]
 
[[Category:Glossary]]
 
[[Category:Argon_user_guide]]
 

Please note that all contributions to Granite Devices Knowledge Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Granite Devices Knowledge Wiki:Copyrights for details). Do not submit copyrighted work without permission!

Select categories:

To edit this page, please answer the question that appears below (more info):

Cancel | Editing help (opens in new window)