Yaskawa SmartTrac Fault Tables - Manual (Page 5)

10/17/00
New Berlin
Technology Center
Smart Trac
Product Development
Design Document
Faults.doc
Rev. # 19 Page 4 of 64
Title: Fault Declarations
The information contained in this document is the CONFIDENTIAL property of MagneTek Inc.
File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00
4
1. Fault Number Assignments
Xycom Automation has allowed MagneTek to use any “internal” fault number, in the range of 0 to 65535, to identify declared faults. (Internal faults are elaborated on below.)
This document is meant to assign ranges of numbers to the different aspects of the project, which may need to declare faults. There are a vast number of faults and this should
eliminate need for having duplicate fault numbers.
Faults number ranges will be assigned to the following broad categories:
1. Operating System
2. User Defined Faults
3. Function Blocks
4. Communications
5. Drivers
6. Inverter (PCU)
7. Hardware
8. IO Subsystem
9. Boot
10. Future
It shall be the responsibility of software engineers controlling each category to:
1. Further sub-divide the range as they deem appropriate.
2. Keep a common header or include file, under file control, with assigned fault numbers.
3. Keep a Word Document , under file control, defining the fault.
Faults have classification levels called Severity. Severity is the level at which a fault should be interpreted by the operating system. When a fault condition is detected, the
software that declares the fault also reports its severity. Four types of faults can occur: major faults, minor faults, function block setup faults and critical faults.
Major faults can halt execution of the task or node. Most major faults can be manually cleared and the task and node restarted. Major faults stop execution until they are cleared
by a task’s program or by the operator. If a major fault is encountered, the fault routine is run and the first thing that the fault routine should do is call G_FLT (i.e. Get Fault
function block) to get the current fault code. Depending on the fault code, it should determine if the system should be shut down or clear the fault and restart execution. Call
C_FLT to clear the fault. Fault clearing can also be done externally by pressing RESET on the Digital Operator. (Typically, automatic clearing of major faults is not
recommended. Fault clearing should be initiated by the machine operator.) Major faults cleared by the Control Node Monitor will cause execution to begin from the start of the
program. If the Major fault is cleared after executing the fault routine, execution of the function block will restart at the point at which the fault was declared. This very important
to understand. For example in a structured text program, if a fault is declared on a certain line, then it is restarted on the following line.