AKD PDMM User Guide | 15.1 Fault and Warning Messages
Fault
Message/Warning
Cause
Remedy
n159 Failed to set motion task param-
eters
Invalid motion task parameters
assignment. This warning can
appear upon an MT.SET com-
mand.
Activation of any new motion or
using of DRV.CLRFAULTS will
clear the warning. Check motion
task settings and parameters.
n160 Motion task activation failed.
Activation of the motion task
failed due to incompatible
parameters, or motion task
does not exist. This warning
can appear upon an MT.MOVE
command.
Activation of any new motion or
using of DRV.CLRFAULTS will
clear the warning. Check motion
task settings and parameters to
make sure that the values
entered will produce a valid
motion task.
n161 Homing procedure failed.
Homing error observed during
the operation of homing pro-
cedure.
Activation of any new motion or
using of DRV.CLRFAULTS will
clear the warning.
n163 MT.NUM exceeds limit.
This warning appears with
n160. This warning is triggered
when you try to trigger a
motion task > 128 (such as
MT.MOVE 130).
Trigger only motion tasks
between 0 and 128. Activation
of any new motion or using of
DRV.CLRFAULTS will clear the
warning.
n164 Motion task is not initialized.
This warning appears with
n160. This warning is triggered
when you try to trigger a non-
initialized motion task.
Initialize the motion task first
before starting the task. Acti-
vation of any new motion or
using of DRV.CLRFAULTS will
clear the warning.
n165 Motion task target position is
out.
This warning appears with
n160. This warning is triggered
when you try to trigger a
motion task with an absolute
target position outside of the
selected modulo range (see
also MT.CNTL).
Move the absolute target posi-
tion of the motion task within the
modulo range.Activation of any
new motion or using of
DRV.CLRFAULTS will clear the
warning.
n168 Invalid bit combination in the
motion task control word.
This warning appears with
n160. This warning is triggered
when you try to trigger a
motion task with an invalid bit
combination in the motion task
control word (see also
MT.CNTL).
Correct the MT.CNTL setting for
the specific motion task. Acti-
vation of any new motion or
using of DRV.CLRFAULTS will
clear the warning.
n169 1:1 profile cannot be triggered
on the fly.
This warning appears with
n160. This warning is triggered
when you try to trigger a 1:1
profile table motion task while
another motion task is cur-
rently running.
1:1 profile table motion tasks
should be started from velocity
0. Activation of any new motion
or using of DRV.CLRFAULTS
will clear the warning.
139
Kollmorgen™ | December 2012
Summary of Contents for AKD PDMM series
Page 25: ...This page intentionally left blank 25 Kollmorgen December 2012...
Page 32: ...This page intentionally left blank 32 Kollmorgen December 2012...
Page 52: ...This page intentionally left blank 52 Kollmorgen December 2012...
Page 101: ...AKD PDMM User Guide 12 3 6 2 Biquad Calculations 101 Kollmorgen December 2012...
Page 133: ...This page intentionally left blank 133 Kollmorgen December 2012...
Page 158: ...AKD PDMM User Guide 17 Connection Diagrams Kollmorgen December 2012 158...
Page 470: ...AKD PDMM User Guide 48 27 VL THRESH 1 Velocity Loop 470 Kollmorgen December 2012...
Page 511: ...This page intentionally left blank 511 Kollmorgen December 2012...
Page 513: ...This page intentionally left blank 513 Kollmorgen December 2012...