Danfoss MCO 305 Design Manual page 236

MCO 305 Design Guide
33-82 Drive Status Monitoring
STATUSMONITORING
Option
Off
On
Function
Enable/disable monitoring of FC 300 status while
position control from MCO 305 is active.
Select Off [0] if monitoring must be disabled i.e.
MCO 305 will try to control the motor independent
of FC 300 status. Will normally lead to a position
error (error 108) when trying to start a movement
while FC 300 is not enabled.
Select On [1] if monitoring must be enabled. Error
113 will be activated if FC 300 is not enabled (e.g.
trip) while MCO 305 is in the MOTOR ON state
(position control).
33-83 Behavior after Error
ERRCOND
Option
Coast
Coast and brake
Controlled stop
Controlled stop and brake
Jumps to error routine without
automatic MOTOR OFF
Function
The behavior in case of limit switches is changed
starting with MCO 5.00:
In case of hard and software limit switches it is
possible to clear a software limit error and then
drive in the opposite direction. If you try again to
move in the wrong direction, then a new error is
generated.
Handling of hardware limit switches is the same as
software limit switches. That means that you can
clear the error and drive in the opposite direction.
But if you try to move in the wrong direction, then
the error 198 occurs.
0 = Standard, i.e. drive moves in COASTING,
control loop is interrupted.
1 = Like [0], but brake output (if defined) is
activated.
2 = Motor stop with maximum deceleration (stop
ramp), subsequently standstill control.
default setting
236
__ Parameter Reference __
[0]
[1]
[0]
[1]
[2]
[3]
[5]
[ ] value for use in communication via serial communication port
®
MG.33.L5.02 – VLT is a registered Danfoss trademark
3 = Like [2], brake output (if defined) is activated
in addition, but only after MOTOR STOP.
All other activities such as MOTOR OFF etc.
must be set in the ON_ERROR routine.
5 = Jumps to the error routine, but the control will
not switch off automatically. This can or must
be initiated in the application program with a
MOTOR OFF in the error routine.
That way avoid in case of data transfer with
CAN terminals that just a disturbed CAN com-
munication stops the control. (E.g. when
simple information data are transferred to a
terminal and the correct display is not security
relevant or the data will be updated cyclic
anyway.)
Then you can check in the error routine at
first, whether it is a CAN error (189) which can
be deleted at once. In all other cases the
control can be switched off in the error routine
and the running process can be stopped
corresponding the application requirements.
NB!:
A brake output has to be defined in
parameter 33-63 through 33-70,
O_FUNCTION_n Option 5 and 6.