Editing Template:DriveFaultbits
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 33: | Line 33: | ||
|SimpleMotion||[[SimpleMotion V2]] Communication error detected, possibly connection lost, invalid parameter value is sent or transfer error caused by [[EMI]] or bad wiring || ||None | |SimpleMotion||[[SimpleMotion V2]] Communication error detected, possibly connection lost, invalid parameter value is sent or transfer error caused by [[EMI]] or bad wiring || ||None | ||
|- | |- | ||
− | |Configuration||Fault caused by invalid or unstable configuration parameters|| Refer to Fault location number for pin-pointing the fault source|| | + | |Configuration||Fault caused by invalid or unstable configuration parameters|| Refer to Fault location number for pin-pointing the fault source|| |
|- | |- | ||
|Fault location ID||See [[Fault location]]|| || | |Fault location ID||See [[Fault location]]|| || | ||
|} | |} | ||
1) The time duration that drive will allow fault condition be ''true'' before fault status is latched. Some faults have user adjustable time delay to reduce error sensitivity in dynamic conditions, such as rapid acceleration. | 1) The time duration that drive will allow fault condition be ''true'' before fault status is latched. Some faults have user adjustable time delay to reduce error sensitivity in dynamic conditions, such as rapid acceleration. |