Editing Signal path of motor drive
Your changes will be displayed to readers once an authorized user accepts them. (help) |
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.
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 | + | *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 [[CVL]] and [[CAL]] parameters. Output rate maximum rate of change: |
− | **Velocity changes max | + | **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 | + | **Velocity maximum value is limited to [[CVL]] |
− | *Input divider. This divides setpoint signal by | + | *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= | + | | 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: +/- | + | *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 | + | 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 | + | **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 | + | *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| | + | [[File:Driveblockdiagram controller.png|800px]] |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | ==Setpoint scale examples== | |
+ | Assuming control cycle to be 400µs / 2500 Hz (default in GD drives). | ||
− | + | ===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 | ||
− | + | 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. | |
− | + | ||
− | + | ;Calculating acceleration and velocity limits | |
− | + | If DIV is 50, then user must have [[CVL]] value at least 3333 (66.6667*50). | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
+ | 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.}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |