Table of Contents
Advertisement
NOTE: After an error event occurs and the drive updates the error log, bits may still be recorded in
for another 120 milliseconds. To find all possible causes of an error event, examine
TASX
addition to viewing the error log.
Bit #
Function
1*
Stall Detected: Functions when stall detection is enabled with ESTALL (encoder stall
detection) or DSTALL (drive stall detection), and Kill on Stall is enabled (ESK1).
2
Hard Limit Hit: When an input is defined as an end-of-travel input (LIMFNCi-R or
INFNCi-R; LIMFNCi-S or INFNCi-S), and that input becomes active.
Hard limits must be enabled (LH3).
3
Soft Limit Hit: Functions when soft limits are enabled (LS3).
4
Drive Fault: Detected only if the drive is enabled (DRIVE1).
5
RESERVED
6
RESERVED
7
User Fault Input: When an input is defined as a user fault input (INFNCi-F), and that
input becomes active.
8
RESERVED
9
RESERVED
10
Pre-emptive (on-the-fly) GO or registration move profile not possible at the time of
attempted execution.
11 **
Target Zone Settling Timeout Period (set with the STRGTT command) is exceeded.
12 **
Maximum Position Error (set with the SMPER command) is exceeded.
13
RESERVED
14
GOWHEN condition already true when a subsequent GO, FSHFC, or FSHFD command is
executed.
15-32 RESERVED
* Stepper axes only; ** Servo axes only
NOTE: ERRORL bits 5, 6, 8, 9, 13, 15 – 32 are reserved.
ERRORP
Error Program Assignment
Type
Error Handling
Syntax
<a_><!><%>ERRORP<t>
Units
t = text (name of error program)
Range
Text name of 6 characters or less
Default
n/a
Response
ERRORP:
*ERRORPerr1
See Also
[ ER ], ERRLVL, ERROR, TER
Using the
command, you can assign any previously defined program as the error program. For
ERRORP
example, to assign a previously defined program named
command. If you later decide not to have an error program, issue the
command, no error program will be called until you assign a new one.
ERRORP CLR
The purpose of the error program is to provide a programmed response to certain error conditions (see table
below) that may occur during the operation of your system. Programmed responses typically include
actions such as shutting down the drive, activating or de-activating outputs, etc. To detect and respond to
the error conditions, the corresponding error-checking bit(s) must be enabled with the
(refer to the ERROR Bit # column in the table below). It is the programmer's responsibility to determine the
cause of the error, and take action based on the error. The error condition can be determined using the
evaluation in an
statement (e.g.,
IF
Programmer's Guide.
as the error program, enter the
CRASH
). An error program set-up example is provided in the
IF(ER=b1ØX)
www.comoso.com
and
TAS
Product
GT6K
GV6K
ERRORP CRASH
command; after the
ERRORP CLR
command
ERROR
Command Descriptions
or
TAS
in
TASX
Rev
6.0
6.0
ER
121
Advertisement
Table of Contents
