Editing Drive fault handling
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 7: | Line 7: | ||
**Short circuit (fixed limit defined by hardware, typically several times higher than drive's maximum current rating) | **Short circuit (fixed limit defined by hardware, typically several times higher than drive's maximum current rating) | ||
*Goal faults, such as [[tracking error]], over speed or travel beyond allowed boundaries (limit switch hit) | *Goal faults, such as [[tracking error]], over speed or travel beyond allowed boundaries (limit switch hit) | ||
− | |||
Faults are indicated by device LED blinking sequence as well as configuration tool status dialog. In [[Granity]], it's recommended to look at Testing tab status bits and [[Fault location]] to identify the source of error. | Faults are indicated by device LED blinking sequence as well as configuration tool status dialog. In [[Granity]], it's recommended to look at Testing tab status bits and [[Fault location]] to identify the source of error. | ||
− | |||
==Reaction to fault== | ==Reaction to fault== | ||
In most fault cases drive will enter in fault state which will: | In most fault cases drive will enter in fault state which will: | ||
Line 40: | Line 38: | ||
==Troubleshooting== | ==Troubleshooting== | ||
#If drive will stay infinitely or too long in error recovery mode (can be identified by LEDs and configuration tool status info), it is typically caused by constantly changing setpoint value. In such case drive is chasing the varying setpoint but never reaches it (typical especially with analog or PWM setpoint mode where noise can alter the setpoint, or when [[controller]] do not cease sending new setpoint values until drive is recovered). As countermeasure try increasing {{param|CRV}} value or stabilize the setpoint. | #If drive will stay infinitely or too long in error recovery mode (can be identified by LEDs and configuration tool status info), it is typically caused by constantly changing setpoint value. In such case drive is chasing the varying setpoint but never reaches it (typical especially with analog or PWM setpoint mode where noise can alter the setpoint, or when [[controller]] do not cease sending new setpoint values until drive is recovered). As countermeasure try increasing {{param|CRV}} value or stabilize the setpoint. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |