Nidec Digitax ST Indexer, User Manual

Page: 112 / 132

112
SM-Applications Modules & Motion Processors User Guide
Issue Number: 4
11 Diagnostics
This chapter details the following:
•
Run-time errors and trip codes
• Handling of run-time errors
• CTNet network status
• Support
11.1 Run-time Errors
A run-time error is an error which occurs in a specific operation of the Second
Processor.
It can happen as a result of an error in the execution of the user’s DPL
program (such as trying to write to a parameter that doesn't exist, or trying to divide a
value by zero), a misconfiguration (such as incorrect CTNet setup) or a system error
such as processor overload or
watchdog time-out.
The action taken when an error occurs may be one or more of the following:
•
User program may be halted or prevented from starting
• Drive may be tripped on SLx.Er (where x is the slot number) with the run-time error
code placed into Pr xx.50
• Drive may be tripped on another SLx.*** code.
• The DPL ERROR task may be executed (if it exists).
Which of these occurs depends upon the type of error and the setting of the global run-
time trip enable parameter Pr
xx.14 . This is detailed in section 11.3, below.
11.2 Drive Display Trip Codes
The table below shows the possible trip codes that will be displayed on the drive when
an error is detected in the Second Processor which instigates a drive trip. Remember,
not all run-time errors instigate a drive trip.
Table 11-1 Drive Trip Display Codes
Slot Where Trip Was Initiated Fault Description
Slot 1 Slot 2 Slot 3
SL1.HF SL2.HF SL3.HF Hardware
Fault
The drive has detected that an option module is
present, but is unable to communicate with it.
SL1.tO SL2.tO SL3.tO Watchdog
Timeout
Indicates a user program which has utilised the
watchdog feature has failed to issue the WDOG
command within 200ms.
SL1.Er SL2.Er SL3.Er Error Run-time trip generated by the Second Processor
either due to a user DPL program error or some
other event. The actual error code is placed into
Pr
xx.50 .
SL1.nF SL2.nF SL3.nF Not Fitted Module was disconnected while operational, or
module has crashed. This trip will also occur if a
drive slot is configured for a Second Processor, but
the module is not fitted in the slot.
SL1.dF SL2.dF SL3.dF Different
Fitted
This trip will occur when an Second Processor is
fitted to a slot previously occupied by another
solutions module, or is fitted to a previously unused
slot.