Troubleshooting
11-15
FM 353 Stepper Drive Positioning Module
6ES7 353-1AH01-8BG0
Table 11-6 Operator errors, continued
Cl.
Mes-
sage/
Display
Error message,
error analysis and remedy
No.
Operator errors Error response: “Feed STOP” see Table 11-2
2 (02) 22 (16) On-the-fly MDI block inoperative CBS
Cause MDI block inactive or already executed
Effect On-the-fly MDI block is not being processed
Elimination Delete error message and initiate execution as MDI block.
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
Table 11-7 Travel errors
Cl.
No.
Error message,
error analysis and remedy
Mes-
sage/
Display
Travel errors Error response: “Feed STOP” see Table 11-2
3 (03) 1 (01) Software limit switch, beginning CBS
Cause Limit switch approached: in “Jogging” mode, in “Automatic”
operating mode if G88/89, without switching signal from the
corresponding digital input.
The axis is located to the left of the software limit switch be-
cause of actual value set.
Effect S Axis movement is stopped at the limit switch position.
S Set actual value is not executed.
Elimination S Following acknowledgment of the error, it is possible to
traverse to the working range.
S Alter value of software limit switch (MD21)
S Switch off monitoring limit switch occasionally!
(With the limit switches (MD21/22) disabled, the
travel range limits are established by the
maximum allowable values for the limit switches).
!
Cl. = Detail event class, No. = Detail event number, CBS = checkback signals, DB = data block
Note: Value (xx) = Hexadecimal notation of the error number
To Next Page
Loading...
