Quote:
Originally Posted by jerry_yang
![View Post]()
hi Casey,
The MCEDesigner V2.2 is the parameter set with the MCEWizard V2.2, and the MCEDesigner V2.3 is the parameter set with the MCEWizard V2.3,These parameters Settings in each version of the MCEWizard are the same except for some new questions in the MCEWizard V2.3.and the corresponding firmware was used.Is the firmware causing the problem?
Indeed, this low speed operation will produce a fault, which is fault Rotor lock fault. However, I managed to disable the fault.
How can this fault be eliminated?And how to achieve the target speed?
The MCEDesigner V2.2 is the parameter set with the MCEWizard V2.2, and the MCEDesigner V2.3 is the parameter set with the MCEWizard V2.3,These parameters Settings in each version of the MCEWizard are the same except for some new questions in the MCEWizard V2.3.and the corresponding firmware was used.Is the firmware causing the problem?
Indeed, this low speed operation will produce a fault, which is fault Rotor lock fault. However, I managed to disable the fault.
How can this fault be eliminated?And how to achieve the target speed?
Regarding v2.3 and v2.2, I dont believe firmware is the issue... I think there may be a problem with the speed loop tuning. When the speed is unstable the motor current will be oscillating which makes the wave form look non sinusoidal. I would check the waveform in current control mode or voltage mode with v2.3 and see what you get.
So a fault condition is not the reason for why you are not reaching target speed?
The rotor lock fault detects the condition where the motor is not generating enough current to reach the target speed within the specified time limit. This is meant to detect an unexpected load condition, such as a bearing or gear failure, that tops the shaft from turning easily. The fault detection functions are there to automatically shut down the drive in the case of abnormal operating conditions but like you have done they can be disabled in the drive bring up phase since the user is closely monitoring the drive. In the case of rotor lock the unexpected condition is a load that is greater than the torque that the motor can generate at that speed. You can set the Rotor lock time by configuring Rotorlocktime parameter (see screenshot below).
Attachment 4920
If you are not experiencing a fault condition the drive may not be reaching the target speed because of invalid motor parameters or because startup and application settings are not matched to the load. The low speed limits (Q13-14) and motoring current limit (Q52) should be set so that the motor has enough torque to match the expected application load. I recommend to start testing with an unloaded motor to confirm that the motor parameters are correct.
Attachment 4921
Attachment 4922
