Difference between revisions of "Argon user guide/Drive parameterization"
From Granite Devices Knowledge Wiki
| [checked revision] | [checked revision] |
(→Feedback device) |
|||
| (29 intermediate revisions by one other user not shown) | |||
| Line 6: | Line 6: | ||
# Be familiar with the operation and parameters of [[Granity]]. Make sure you have read [[Granity user guide]]. | # Be familiar with the operation and parameters of [[Granity]]. Make sure you have read [[Granity user guide]]. | ||
# Granity connection working. See [[Argon_user_guide/Making_the_first_Granity_connection|Making the first Granity connection]] | # Granity connection working. See [[Argon_user_guide/Making_the_first_Granity_connection|Making the first Granity connection]] | ||
| − | ==Walk-through of parameterization== | + | ==Walk-through of initial parameterization== |
| − | In this chapter we walk-trough all Granity tabs and modify the parameter needed. This guide assumes that the drive is in factory defaults state (not configured before). Restore drive to factory state can be done by uploading a firmware file to the drive. | + | In this chapter we walk-trough all Granity tabs and modify the parameter needed. This guide assumes that the drive is in factory defaults state (not configured before). Restore drive to factory state can be done by [[Granity user guide/Uploading a firmware|uploading a firmware]] file to the drive. |
| + | {{tip|'''Experimenting with drive parameters is (mostly) safe.''' If motor is attached to machine or bench for testing and nothing is attached to shaft (so motor can't jump but it can spin freely), then playing with all drive parameters can be regarded safe. The most important parameters are proper motor {{param|MMC}} and {{param|MCC}} to avoid overheating of motor. If unsure of proper current limits, start with low values and increase gradually if motor stays cool.}} | ||
===Connect tab=== | ===Connect tab=== | ||
No other actions than connect to drive needed on this tab. Once connection successful, proceed to the next tab. | No other actions than connect to drive needed on this tab. Once connection successful, proceed to the next tab. | ||
===Goals tab=== | ===Goals tab=== | ||
| + | The factory defaults (torque control as control mode and serial only as setpoint) as well as the other defaults are the correct ones for beginning. | ||
| + | ===Machine tab=== | ||
| + | In this tab we configure the motor and its feedback device. | ||
| + | ====Axis mechanics==== | ||
| + | Parameters {{param|AXT}} and {{param|AXS}} affect only on the [[Granity unit conversion|unit conversion of Granity]] parameters (such as acceleration/velocity limit unit conversions) and has no effect on drive operation. | ||
| + | Choose your axis type and scale, or leave them as defaults. | ||
| + | ====Motor==== | ||
| + | Find motor parameters from the motor data sheet/manufacturer specifications. | ||
| + | #Choose motor type from the drown down list {{param|MT}}. If motor is linear type, see [[configuring linear servo motor]]. | ||
| + | #Set motor {{param|MPC}} (non-brush DC motors only). If unsure, see [[Determining motor pole count]]. | ||
| + | #Set {{param|MMS}} of the motor, or alternatively the maximum allowed motor speed in the target application | ||
| + | #Set motor {{param|MMC}} and {{param|MMC}} current values. If non-brush DC motor type has been selected, then these are measured as the [[peak value of sine]]. See [[Motor peak and continuous current limits]] for description. | ||
| + | #Set motor {{param|MR}} and {{param|ML}}, these values are measured [[Phase-to-phase]]. If unavailable, perform [[Tuning torque controller]] manually after initial parameters are set. | ||
| + | #Set {{param|MTC}}. Motor thermal time constant value in seconds, used for thermal modeling of motor to avoid motor overheating with {{param|MMC}}. If not available, use formula 200*motor_weight (kg) as approximate, so a 2 kg motor would get a 400 second time constant. There is no guarantee of accuracy of this method. | ||
| + | {{tip|As torque is directly proportional to motor current, it is advisable to set current limits lower at the beginning of testing. I.e. 50% of motor's rated current will produce 50% of motor's rated torque.}} | ||
| − | [[ | + | ====Feedback device==== |
| + | #Choose feedback device type from the drop down {{param|FBD}} | ||
| + | #Set feedback device resolution. If {{param|FBD}} is [[quadrature]] encoder, then manufacturers typically give resolution as pulses per revolution (PPR) or lines per revolution (LPR) which are the same thing and shall be entered directly into {{param|FBR}} field. Some manufactures also call PPR as CPR. | ||
| + | #Configure the polarity of feedback device counting direction by {{param|FBI}} parameter. Motor and feedback device must have same electrical positive rotation direction to make a stable servo system. If your system shows no stability (instant following error after a motor "jump"), try changing this setting. | ||
| + | #Leave the Hall sensors Off from the parameter {{param|FBH}} during initial setup. Enable later if necessary ([[Argon_user_guide/J1_connector_wiring#Hall sensor|see when]]). | ||
| + | # For SinCos encoders, see [[Using SinCos encoder|Using_SinCos_encoder]]. | ||
| + | |||
| + | ===Tuning=== | ||
| + | Tuning tab contains feedback gain values for velocity and position control modes as well as torque bandwidth limit setting. Configuring these parameters are documented in [[Servo motor tuning guide]]. However, before proceeding into tuning, go through all other settings listed in this article. | ||
| + | ===Fault limits=== | ||
| + | Fault limits define the conditions in which drive is willing to operate. If condition is out of the set values, drive will enter into a fault state and stop motor control until errors are cleared. | ||
| + | ====Drive fault limits==== | ||
| + | These settings specify drive electrical condition such as supply voltage and over current tolerance. | ||
| + | #Leave {{param|FOC}} value as default if no overcurrent faults occur. See [[Tuning torque controller]] if overcurrent faults occur. | ||
| + | #Set {{param|FUV}} and {{param|FOV}} by following the page [[Configuring drive voltage limits FUV and FOV]]. | ||
| + | #It is important to goal deviation faults (i.e. {{param|FFT}}, {{param|FPT}}, {{param|FVT}}, {{param|FEV}}) as low as possible. Set them so that faults don't occur during normal operation but any anomaly or unexpected behavior will trigger them. | ||
| + | {{warning|If goal deviation faults are unnecessary high, drive may pose a danger in case of unexpected behavior. For example if motor starts running away full speed without command, then proper velocity fault threshold values may save from damage.}} | ||
| + | |||
| + | ====Goal deviation faults==== | ||
| + | These faults adjust motor monitoring during operation. Drive will enter into fault state if motor condition deviates more than allowed from the desired condition. See [[Granity unit conversion]] before adjusting. | ||
| + | #{{param|FFT}} sets the time how fast {{param|FPT}}, {{param|FVT}}, {{param|FEV}} and {{param|FMO}} faults react. Setting higher time value allows drive to continue operation over short deviations thus avoid false triggering. Set this from 0.0 to 0.2 seconds in the beginning. | ||
| + | #Set Position tracking error threshold {{param|FPT}} according how much mechanical axis is allowed to deviate from the setpoint position in position control mode. | ||
| + | #Set Velocity tracking error threshold {{param|FVT}} according how much motor or axis speed may may deviate from the velocity setpoint. This affects also in position mode as velocity controller is the intermediate step between torque and position controllers. | ||
| + | #Set {{param|FEV}} according to the maximum speed allowed for the motor or axis. Helps to stop motor if system goes totally out of control and speeds up spuriously. | ||
| + | #Leave {{param|FMO}} as 0 (0 = disabled) for the beginning. Using nonzero value enables motion fault. | ||
| + | #Choose {{param|LFS}} according to your preference. If other than ''Do nothing'' option requires that limit switches are installed and connected to J5 port. Note: at the moment ''Servo stop'' option is active in the drive [[firmware]] and will do nothing until FW upgrade enables it. | ||
| + | ===Testing tab=== | ||
| + | These settings does not affect drive operation, so nothing to be changed here at this point. These controls will be used for servo tuning purposes and fault analysis. | ||
| + | |||
| + | ==Servo motor tuning== | ||
| + | Tuning a servo motor is a compulsory task to make motor behave as desired and perform well during operation. Follow the [[Servo motor tuning guide]]. | ||
| + | ==Finishing touches== | ||
| + | The last step of parameterization is to adapt settings to match the motion [[controller]]. Steps: | ||
| + | |||
| + | # Choose [[setpoint]] input {{param|CRI}} to match your motion [[controller]]. | ||
| + | # If external motion [[controller]] with acceleration limit (such as CNC controller) is being used, then it is advised to set {{param|CAL}} value to maximum of 32767 (unlimited acceleration) after [[Servo motor tuning guide|motor tuning]] to enable motion tracking without delay. Use a limited acceleration value if drive is being used with [[Pulse burst positioning|pulse burst positioning]] or [[SimpleMotion V2]] controller. | ||
| + | # If [[setpoint]] is too sensitive or not sensitive enough (such as limiting speed), then adjust setpoint scaling factory by adjusting {{param|MUL}} and {{param|DIV}}. | ||
| + | #If [[setpoint]] signal is noisy or jittering, try enabling {{param|CIS}} to smoothen it inside drive. However, leave {{param|CIS}} disabled if setpoint tracking without any delay is desired. | ||
| + | #Set-up [[homing]] if required by application | ||
| + | |||
| + | [[Category:Argon_user_guide]] | ||
| + | [[Category:Pages_needing_update_after_FW_upgrades]] | ||
Latest revision as of 16:23, 31 October 2019
This article will describe how to set-up Argon parameters with Granity to make motor operational and ready for servo tuning.
Preparations and connection[edit | edit source]
As the goal is to parameterize and make motor operational, we should have:
- The drive and motor fully wired. However it's not required to have controller (to J5 port) or braking resistor connected at this point.
- Be familiar with the operation and parameters of Granity. Make sure you have read Granity user guide.
- Granity connection working. See Making the first Granity connection
Walk-through of initial parameterization[edit | edit source]
In this chapter we walk-trough all Granity tabs and modify the parameter needed. This guide assumes that the drive is in factory defaults state (not configured before). Restore drive to factory state can be done by uploading a firmware file to the drive.
 | Experimenting with drive parameters is (mostly) safe. If motor is attached to machine or bench for testing and nothing is attached to shaft (so motor can't jump but it can spin freely), then playing with all drive parameters can be regarded safe. The most important parameters are proper motor Peak current limitMMC and Continuous current limitMCC to avoid overheating of motor. If unsure of proper current limits, start with low values and increase gradually if motor stays cool. |
Connect tab[edit | edit source]
No other actions than connect to drive needed on this tab. Once connection successful, proceed to the next tab.
Goals tab[edit | edit source]
The factory defaults (torque control as control mode and serial only as setpoint) as well as the other defaults are the correct ones for beginning.
Machine tab[edit | edit source]
In this tab we configure the motor and its feedback device.
Axis mechanics[edit | edit source]
Parameters Axis type & unitsAXT and Axis scaleAXS affect only on the unit conversion of Granity parameters (such as acceleration/velocity limit unit conversions) and has no effect on drive operation.
Choose your axis type and scale, or leave them as defaults.
Motor[edit | edit source]
Find motor parameters from the motor data sheet/manufacturer specifications.
- Choose motor type from the drown down list Motor typeMT. If motor is linear type, see configuring linear servo motor.
- Set motor Pole countMPC (non-brush DC motors only). If unsure, see Determining motor pole count.
- Set Maximum speedMMS of the motor, or alternatively the maximum allowed motor speed in the target application
- Set motor Peak current limitMMC and Peak current limitMMC current values. If non-brush DC motor type has been selected, then these are measured as the peak value of sine. See Motor peak and continuous current limits for description.
- Set motor Coil resistanceMR and Coil inductanceML, these values are measured Phase-to-phase. If unavailable, perform Tuning torque controller manually after initial parameters are set.
- Set Thermal time constantMTC. Motor thermal time constant value in seconds, used for thermal modeling of motor to avoid motor overheating with Peak current limitMMC. If not available, use formula 200*motor_weight (kg) as approximate, so a 2 kg motor would get a 400 second time constant. There is no guarantee of accuracy of this method.
| As torque is directly proportional to motor current, it is advisable to set current limits lower at the beginning of testing. I.e. 50% of motor's rated current will produce 50% of motor's rated torque. |
Feedback device[edit | edit source]
- Choose feedback device type from the drop down Feedback deviceFBD
- Set feedback device resolution. If Feedback deviceFBD is quadrature encoder, then manufacturers typically give resolution as pulses per revolution (PPR) or lines per revolution (LPR) which are the same thing and shall be entered directly into Feedback device resolutionFBR field. Some manufactures also call PPR as CPR.
- Configure the polarity of feedback device counting direction by Invert feedback directionFBI parameter. Motor and feedback device must have same electrical positive rotation direction to make a stable servo system. If your system shows no stability (instant following error after a motor "jump"), try changing this setting.
- Leave the Hall sensors Off from the parameter Hall sensorsFBH during initial setup. Enable later if necessary (see when).
- For SinCos encoders, see Using_SinCos_encoder.
Tuning[edit | edit source]
Tuning tab contains feedback gain values for velocity and position control modes as well as torque bandwidth limit setting. Configuring these parameters are documented in Servo motor tuning guide. However, before proceeding into tuning, go through all other settings listed in this article.
Fault limits[edit | edit source]
Fault limits define the conditions in which drive is willing to operate. If condition is out of the set values, drive will enter into a fault state and stop motor control until errors are cleared.
Drive fault limits[edit | edit source]
These settings specify drive electrical condition such as supply voltage and over current tolerance.
- Leave Over current toleranceFOC value as default if no overcurrent faults occur. See Tuning torque controller if overcurrent faults occur.
- Set Under voltage fault thresholdFUV and Over voltage fault thresholdFOV by following the page Configuring drive voltage limits FUV and FOV.
- It is important to goal deviation faults (i.e. Goal faults filter timeFFT, Position tracking error thresholdFPT, Velocity tracking error thresholdFVT, Over speed faultFEV) as low as possible. Set them so that faults don't occur during normal operation but any anomaly or unexpected behavior will trigger them.
 | If goal deviation faults are unnecessary high, drive may pose a danger in case of unexpected behavior. For example if motor starts running away full speed without command, then proper velocity fault threshold values may save from damage. |
Goal deviation faults[edit | edit source]
These faults adjust motor monitoring during operation. Drive will enter into fault state if motor condition deviates more than allowed from the desired condition. See Granity unit conversion before adjusting.
- Goal faults filter timeFFT sets the time how fast Position tracking error thresholdFPT, Velocity tracking error thresholdFVT, Over speed faultFEV and Motion fault thresholdFMO faults react. Setting higher time value allows drive to continue operation over short deviations thus avoid false triggering. Set this from 0.0 to 0.2 seconds in the beginning.
- Set Position tracking error threshold Position tracking error thresholdFPT according how much mechanical axis is allowed to deviate from the setpoint position in position control mode.
- Set Velocity tracking error threshold Velocity tracking error thresholdFVT according how much motor or axis speed may may deviate from the velocity setpoint. This affects also in position mode as velocity controller is the intermediate step between torque and position controllers.
- Set Over speed faultFEV according to the maximum speed allowed for the motor or axis. Helps to stop motor if system goes totally out of control and speeds up spuriously.
- Leave Motion fault thresholdFMO as 0 (0 = disabled) for the beginning. Using nonzero value enables motion fault.
- Choose Limit switch functionLFS according to your preference. If other than Do nothing option requires that limit switches are installed and connected to J5 port. Note: at the moment Servo stop option is active in the drive firmware and will do nothing until FW upgrade enables it.
Testing tab[edit | edit source]
These settings does not affect drive operation, so nothing to be changed here at this point. These controls will be used for servo tuning purposes and fault analysis.
Servo motor tuning[edit | edit source]
Tuning a servo motor is a compulsory task to make motor behave as desired and perform well during operation. Follow the Servo motor tuning guide.
Finishing touches[edit | edit source]
The last step of parameterization is to adapt settings to match the motion controller. Steps:
- Choose setpoint input Setpoint inputCRI to match your motion controller.
- If external motion controller with acceleration limit (such as CNC controller) is being used, then it is advised to set Acceleration limitCAL value to maximum of 32767 (unlimited acceleration) after motor tuning to enable motion tracking without delay. Use a limited acceleration value if drive is being used with pulse burst positioning or SimpleMotion V2 controller.
- If setpoint is too sensitive or not sensitive enough (such as limiting speed), then adjust setpoint scaling factory by adjusting Setpoint multiplierMUL and Setpoint dividerDIV.
- If setpoint signal is noisy or jittering, try enabling Setpoint smoothingCIS to smoothen it inside drive. However, leave Setpoint smoothingCIS disabled if setpoint tracking without any delay is desired.
- Set-up homing if required by application
