Nidec Digitax ST Indexer, Руководство пользователя, Страница: 126 / 132

126
SM-Applications Modules & Motion Processors User Guide
Issue Number: 4
Table 13-4 Status Parameters
Parameter Description Range Default
Pr 88.01
Error Code / Reset
Section 5.7 on page 47 0-9999 N/A
Pr 88.02
Task In Error
Section 5.7 on page 47 0-50 N/A
Pr 88.03
POS Resource Monitoring
Section 5.7 on page 48 0-1 0
Pr 88.04
Free Resource for Motion Engine
Tasks
Section 5.7 on page 48 0-95 N/A
Pr 88.05
Motion Engine Peak Resource Detect Section 5.7 on page 48
0-95 N/A
Pr 88.06
CLOCK Task Resource Monitoring
Section 5.7 on page 48 0-1 0
Pr 88.07
Free Resource for Clock Task
Section 5.7 on page 49 0-95 N/A
Pr 88.08
Clock task peak resource detect
Section 5.7 on page 49 0-95 N/A
Table 13-5 Second Processor Error Codes
Error
Code
Reason
Trip
Drive?
ERROR
task?
Prog
Halted?
39 User program stack overflow Yes No Yes
40 Unknown error - please contact supplier Yes No Yes
41
Parameter does not exist. User has attempted to read or
write a non-existent parameter in the DPL program.
May Yes Yes
42 Attempt to write to a read-only parameter. May Yes Yes
43 Attempt to read from a write-only parameter. May Yes Yes
44
Parameter value out of range. (User has written an illegal
value to a parameter within a DPL program.) If parameter
#MM.17=0 the value written will be automatically limited
and no error will occur.
May Yes Yes
45 Invalid synchronization modes Yes No Not Run
46 Unused N/A N/A N/A
48
RS485 not in user mode. Occurs if user attempts to use a
user-mode RS485 DPL command but the RS485 port is
not in a user-mode.
Yes Yes Yes
49
Invalid RS485 configuration. For example, invalid mode.
Yes Yes Yes
50 Maths error - divide by zero or overflow. May Yes Yes
51
Array index out of range. E.g. arr%[20] where arr% has
only been DIMensioned to 19 elements.
May Yes Yes
52
Control word user trip. Instigated by setting the trip bit in
the control word #90.11
Yes No No
53
DPL program incompatible with target. For example,
downloading a program compiled for UD70.
Yes N/A N/A
54
DPL task overrun. This occurs if the DPL code within a
real-time task (e.g. POS0) cannot be completed in time.
Use parameter
#88.02 to identify the task in which this
error occurred. Check that the task scheduling rate is
correct and that there are no loops in the task. This can
also occur as a result of external influences such as a
large burst of data coming in over CTNet.
This problem may be overcome by changing the CTNet
priority so that it is lower than the POS tasks. This,
however, may cause the CTNet task to be starved. Refer
to parameter
Pr 81.44
on page 41 for further
information.
May Yes Yes