Yaskawa SmartTrac Fault Tables User Manual

Technical Manual

™

S

M

A

R

S

M

A

R

T

F

R

a

A

C

A

C

ulltt

u

T

a

A

bll

b

C

1

C

1

ess

e

10/17/00

Smart Trac

Faults.doc

Rev. # 19 Page 1 of 64

New Berlin

Technology Center

Product Development

Design

Document

Title: Fault Declarations

REV DATE NAME DESCRIPTION

0 04/23/98 J. Muszynski Original. 1 08/21/98 D. W. Karraker Split driver fault codes among known I/O drivers. Added sub-heading listing DPRAM faults. 2 12/04/98 D. W. Karraker Updated DPRAM and PCU faults 3 12/04/98 M. DuVal Added faults for PG-SC. Added cross reference column as to the actual error number shown in Smart Trac

Workstation SW 4 01/26/99 J. Cretney Added displayed fault codes to fault # 30016 through 30047 5 02/27/99 M. DuVal Added Smart Trac LAN fault table. 6 03/05/99 J. Cretney Merged C-Function Block Fault descriptions. Added decimal representation of fault codes. 7 03/22/99 M. DuVal Added more Smart Trac LAN fault codes. 8 03/23/99 T. Wiese Change LAN allocation errors from output to I/O 9 08/04/99 M. DuVal Added Operating System faults, Fault Range Map, and Document Revision. Removed unused sections. Reformatted

fault tables. Corrected documentation errors.

10 08/18/99 M. DuVal Include revisions from document design review. Added columns: Corrective Action and Assign Program Inputs. 11 09/10/99 T. Ellis Changed Assign Program Inputs to reflect correct values. Provided information for Corrective Actions. Document

clarification and corrections.

12 12/16/99 S. Mack Added new faults being declared by Function Blocks in MAG_WIND_V1_9 and MAG_STD_V1_9. Added to the

explanations of fault types.

13 12/20/99 D. W. Karraker Added individual CPF and OPE faults under Inverter Faults 14 01/05/00 M . DuVal Renamed references of MAG_CPB_V1_9 to MAG_STD_V1_9. Revised fault definitions in Function Blocks section

specific to MAG_STD_V1_9 library.

15 01/11/00 D. W. Karraker Added revision number for DPRAM driver to section 1.2 16 01/12/00 M. DuVal Minor changes to Function Blocks section. 17 01/31/00 D. W. Karraker Added inverter alarm codes 18 04/03/00 J. Nickel Added 2 fields to each fault code to indicate which list(s) the fault will be placed in by default: OLDEST or NEWEST.

Also added a column to indicate if the fault is considered a PRIORITY fault by default. Changed the description of

fault #77643 (CAVE Input). Changed legends of event codes 95736-95755 to include “Alm:”. Revised many of the

Corrective actions which were labeled ‘Consult Factory’. Added faults 12B08 – 12B0B, & 12B67. These are new

input faults for the DIAM_2, INRT_1, CTCW_0, CTCW_1 and POSR_0 blocks. Corrected some other typos in the

document. Added another Program Input called ‘FB_Setup’ for use to designate improper inputs to various block

inputs.

19 05/09/00 S. Mack DIAM_0 can declare NO_SYSTEM_CLOCK fault. DIAM_2 will declare DIAM_2_INPUT faults if sanity checks are

exceeded for NumberCalculation, RatedLineSpeed, S_RPM_at_M_RPM, MinDiameter, and MaxDiameter. Updated

Fault Document Revisions.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

1

10/17/00

Smart Trac

Faults.doc

Product Development

New Berlin

Technology Center

Design

Document

Title: Fault Declarations

REV DATE NAME DESCRIPTION

20 9/28/00 S. Mack Added PG_TACH Input fault. Fixed fault 11019 from REFQ to CTCW_1 Input fault.

Rev. # 19 Page 2 of 64

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

2

10/17/00

Smart Trac

Faults.doc

Product Development

New Berlin

Technology Center

Design

Document

Title: Fault Declarations

Table of Contents

1. FAULT NUMBER ASSIGNMENTS 4

1.1 Fault Range Map 6

1.2 Fault Document Revision 7

2. OPERATING SYSTEM 8

3. USER DEFINED FAULTS 20

4. FUNCTION BLOCKS 21

5. DRIVERS 30

Rev. # 19 Page 3 of 64

5.1 DPRAM Driver 30

5.2 STLAN Driver 33

5.3 Operator Driver 37

6. INVERTER 38

7. IO SUBSYSTEM 59

8. BOOT 64

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

3

10/17/00

Smart Trac

Faults.doc

Rev. # 19 Page 4 of 64

New Berlin

Technology Center

Product Development

Design

Document

Title: Fault Declarations

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 Bloc ks

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 cl assification levels cal led 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 deter mine if the s ystem 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.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

4

10/17/00

Smart Trac

Faults.doc

Rev. # 19 Page 5 of 64

New Berlin

Technology Center

Product Development

Design

Document

Title: Fault Declarations

Minor faults are logged, but do not halt the system. Minor faults can be cleared. Minor faults do not cause the task’s fault routine to run.

Function block setup faults (FB_SETUP) are those that indicate at least one input of a function block has been supplied with an illegal input.

Critical faults behave similar to major faults in the fact that execution is halted when a critical fault is encountered. The exception is, a critical fault cannot be cleared nor will the node be allowed to run until node power has been recycled.

The Application Engineer may determine the type of fault (i.e., Major or Minor) only for the User Defined faults. In the other category of faults, the types are predefined and cannot be changed by the Application Engineer .

1

Faults can be assigned to certain inputs such that the program can react when a fault occurs. These inputs are categorized in this document as Assign Program Input

The Fault Manager I/O Driver has a variable number of logic inputs (BOOLs). Each of these logic inputs will be set true if any of the faults pre-assigned to that logic input is declared. It will remain true until all faults assigned to that input have been reset. Any number of faults may be assi gned to any of the inputs. The Fault Manager Interface Card is the mechanism for defining the number of logic inputs, their symbols, and the list of fault codes assigned to that input. The default symbols used in the faults definition document are “Critical”, “Major”, and “Minor”. These symbol names and the faults assigned to them may be changed by the Application Engineer.

Faults can be displayed in up to three places in a Smart Trac AC1 system: twice in Smart Trac AC1 Workstation and once on the Digital Operator. Specifically, the workstation shows fault numbers in two places, a) Fault Manager Interface Card, and b) Control Node Monitor. Unfortunately, the same fault has a different number, depending on whether it is displayed in the Fault Manager or Control Node Monitor. Fault Manager sho ws the fault in decimal while Control Node Monitor shows the number in hexadecimal. This is a “feature” that was given to us by Xycom Automation. The Digital Operator does not display a fault number rather a Fault Legend. All tables in the ensuing sections have cross references for each fault.

.

Although fault numbers are displayed in Fault Manager and Control Monitor, a third column has been added to many of the tables in this document: Internal Fault No. An internal fault number is the number MagneTek development engineers use to identify a fault within a given piece of software and is of no consequence to the Application Engineer. The displayed fault is equal to the internal fault number + 65,536 (i.e. 10000 HEX). Internal fault numbers are not displayed.

1

Also known as ‘Define Outputs’ tab in Fault Manager Interface Card of Smart Trac AC1 Workstation software.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

5

10/17/00

Smart Trac

Faults.doc

Rev. # 19 Page 6 of 64

New Berlin

Technology Center

Product Development

Design

Document

Title: Fault Declarations

There are three columns following the description of each fault. These are labeled Priority Display, Newest List and Oldest List. Faults which are selected to be a Priority

Display will preempt the local operator from whatever it was doing with a display this fault when it happens. Those faults which are selected to be on the Newest List (and/or Oldest List) will be placed in the ‘newest’ (or ‘oldest’) list maintained by the fault manager. The Newest List can be thought of as a circular buffer that always contains the

newest faults that have been recorded on this drive. Any fault designated as to be placed on the Newest List will cause the oldest entry on this circular buffer to be discarded if the Newest List already filled to capacity. The Oldest List can best be thought of as a table with 20 slots. Any fault designated to be placed on the Oldest List will remain on this list until it is cleared via the local operator. If the Oldest List already filled up, and a fault designated to be placed on the Oldest List occurs, it will NOT be placed o n the Oldest List. This is done to preserve the fault history of the original event that may have caused many subsequent faults to occur.

1.1 Fault Range Map

This table summarizes all possible fault value locations.

Fault Type

Operating System N/A 0 to FFFF 0 to 65,535 User Defined Faults 00000 to 09999 10000 to 1270F 65,536 to 75,535 Reserved for future u se #1 10000 to 10999 12710 to 12AF7 75,536 to 76,535 Function Block Faults 11000 to 11999 12AF8 to 12EDF 76,536 to 77,535 Reserved future Communications Protocols 12000 to 19999 12EE0 to 14E1F 77,536 to 85,535 Driver Faults: DPRAM 20000 to 20099 14E20 to 14E83 85,536 to 85,635 Reserved for future d riv e r #1 20100 to 20199 14E84 to 14EE7 85,636 to 85,735 Driver Faults: STLAN 20200 to 20299 14EE8 to 14F4B 85,736 to 85,835 Reserved for future d riv e r #2 20300 to 20399 14F4C to 14FAF 85,836 to 85,935 Driver Faults: OPERATOR 20400 to 20499 14FB0 to 15013 85,936 to 86,035 Reserved for future d riv e r #3 20500 to 29999 15014 to 1752F 86,036 to 95,535 Inverter Faults 30000 to 39999 17530 to 19C3F 95,536 to 105,535

Reserved for future u se #2 40000 to 59999 19C40 to 1EA5F 105,536 to 125,535 Reserved for future hardware platform fau lts 60000 to 65535 1 E A60 to 1FFFF 125,536 to 131,071 Not Used N/A 20000 to 8FFFFFFF 131,072 to 2,415,919,103

IO Subsystem N/A 90000000 to 90000043 N/A

Internal Fault Range

(Decimal)

Displayed in Control Node

Monitor (Hex)

Displayed in Fault Manager Interface Card

(Decimal)

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

6

10/17/00

Smart Trac

Faults.doc

Rev. # 19 Page 7 of 64

New Berlin

Technology Center

Product Development

Design

Document

Title: Fault Declarations

1.2 Fault Document Revision

This table lists the latest version of each fault type. As developers make enhancements that affect faults, they should update the corresponding section and change the Software/Firmware (SW/FW) Version level accordingly. In this way, we can track whether this document has been properly updated.

SW/FW Type

ASIC-300 Workstation 4.2.4 Operating System and IO Subsystem (i.e., Kernel and Monitor) 4.2.0 Library: MAG_STD_V1_9 1.9 Library: MAG_WIND_V1_10 1.10 Library: MAG_PG_V1_7 1.7 Driver: DPRAM 1.7 Driver: STLAN 2.4 Driver: OPERATOR 1.10

Smart Trac AC1 Inverter Boot 1.2.0

SW/FW Version

G112131.DAT (R1) for G5+ G110200.DAT (R1) for G5 Parallel HP units

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

7

10/17/00

Smart Trac

Faults.doc

Product Development

New Berlin

Technology Center

Design

Document

Title: Fault Declarations

2. Operating System

The following section details fault numbers assigned to the Smart Trac AC1 Operating System.

Notes:

• Fault legend cannot be changed in this section.

• Internal fault values do not apply here. Operating System faults are not added with 10000 HEX.

• The Severity for every Operating System fault in this section is fixed in firmware. It cannot be changed

Display?

Priority

Newest

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

0 0 Not a fault 1 1 Not a fault 2 2 Invalid

3 3 Stack

4 4 Stack

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

Fault

Manager

Opcode

Overflow

Underflow

Operand code within program is unrecognized. Valid Opcodes are add, subtract, AND, OR, etc.

Program point er has gone past the end of the program stack. Stack is checked at the end of each program scan.

Program pointer has preceded the beginning of the program stack. Stack is checked at the end of each program scan.

8

List?

Yes Yes Yes Major

Oldest

List?

Severity

Program

Input

Major

Rev. # 19 Page 8 of 64

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Application program may be overburdened – reduce amount of logic placed in fast Tasks (15ms or faster) to slow Tasks (30 ms or slower). This may include reducing number of Program Units and/or program elements. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

5 5 Stack

66Call

7 7 Call Overflow Cannot process next Opcode

88Task

9 9 Operand

Fault

Manager

Corrupted

Underflow

Corrupted

Undrflow

Location of program stack has inadvertently changed. Stack is checked at the end of each program scan. Cannot process next Opcode because a program pointer has preceded the beginning of the program stack.

because a program pointer has gone past the end of the program stack.

A stack that contains code for each Task to be run is bad.

A computation is smaller than the smallest quantity the CPU can store.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Major

No Yes Yes Minor

Rev. # 19 Page 9 of 64

Oldest

List?

Severity

Program

Input

Major

Minor

Assign

Corrective Action

The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. Replace the SmartTrac CPU card. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. Replace the SmartTrac CPU card. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

9

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

A 10 Divide By

B11Result

C12Result

D 13 Invalid Result Fl oating point e rror: Compute d

E 14 Bad Address

Fault

Manager

Zero

Underflow

Overflow

Mode

An attempt was made to use ‘0’ as a divisor during computation.

Floating point error: 1) a computation is smaller than the smallest quantity the CPU can store; 2) An error condition occurred when an item was called from an empty stack. Floating point error: An error occurred when calculated data could not fit within the designated field.

result is incorrect or is not within bounds. Operand address mode is not recognized. Examples of correct addressing is Direct and Indirect.

Product Development

Design

Document

Display?

Priority

Newest

List?

No Yes Yes Minor Software used to create the application program

No Yes Yes Minor

Yes Yes Yes Major

Rev. # 19 Page 10 of 64

Oldest

List?

Severity

Program

Input

Minor

Major

Assign

Corrective Action

may have been old. (Earlier Kernel and library versions exhibited this problem.) Check the application program for use of zero during division. Check the application program for use of extremely large and/or small numbers for computation.

Check the application program for use of extremely large and/or small numbers for computation.

Check the application program for use of extremely large and/or small numbers for computation. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

10

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

F 15 Address

10 16 Data Unknown Operand type does not conform

11 17 Not used 12 18 Data

13 19 Bad Data Type Operand type cannot be used for

14 20 Bad Address An attempt has been made to

Fault

Manager

Mismatch

Address types are not equivalent. This prohibits a valid computation or comparison from taking place.

to any available form.

Operand types are not equivalent. This prohibits a valid computation or comparison from taking place.

this specific computation or comparison.

access data from an invalid memory location.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Major

Rev. # 19 Page 11 of 64

Oldest

List?

Severity

Program

Input

Major

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Valid types include byte, unsigned long, Boolean, float, etc.

Check application program for improper data type comparisons. Valid types include byte, unsigned long, Boolean, float, etc.

Check application program for improper comparisons. Example of this is attempting to compare a Boolean with a string pointer. Check memory allocation for this node in Smart Trac AC1 Workstation software. In Configure dialog box, make sure the following is true: Base Address = 0x300000, Base Memory Size = 0x100000, Retentive Address = 0xDC000, and Retentive Size = 0x3F00. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

11

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

15 21 Operand2

16 22 Operand1

17 23 Invalid Jump Calculated offset appears outside

18 24 Invalid

Fault

Manager

Invalid

Address

2nd operand code within program is unrecognized. Valid Opcodes are add, subtract, AND, OR, etc.

1st operand code within program is unrecognized. Valid Opcodes are add, subtract, AND, OR, etc.

the bounds of the program. Branch cannot be completed.

Address does not appear within NVRAM, DRAM, nor Task table.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Major

Rev. # 19 Page 12 of 64

Oldest

List?

Severity

Program

Input

Major

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. Replace the SmartTrac CPU card. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Check memory allocation for this node in Smart Trac Workstation software. In Configure dialog box, make sure the following is true: Base Address = 0x300000, Base Memory Size = 0x100000, Retentive Address = 0xDC000, and Retentive Size = 0x3F00. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

12

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

19 25 Float Error Floating point error: an unknown

1A 26 Fstack

1B 27 Fstack

1C 28 Bad Operand Based on the operand’s mode,

Fault

Manager

Overflow

Underflow

float error, which is detected only if all other floating point errors have not triggered a fault (underflow, overflow, float invalid). Float stack overflow. Float pointer has gone past the end of the float stack.

Float stack underflow. Float pointer has preceded the beginning of the float stack.

operand address is invalid.

Product Development

Design

Document

Display?

Priority

Newest

List?

No Yes Yes Minor

Yes Yes Yes Minor

Yes Yes Yes Major

Rev. # 19 Page 13 of 64

Oldest

List?

Severity

Program

Input

Minor

Major

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

13

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

1D 29 Operand

1E 30 Out of

1F 31 Action Invalid Based on what is encountered in

20 32 I/O Read Fail Could not read input image table

21 33 I/O Write Fail Could not write to output image

Fault

Manager

Negative

Memory

Situation where a value should not be negati ve. The SQRT, LOG and LN functions will declare this fault if their input is negative. Attempt to allocate memory for the program stack and initialize it to zero has failed.

the program, certain routines or ‘actions’ are processed. If the requested action does not match those that are available, this fault will be realized.

for an associated driver, i.e., Interface Card.

table for an associated driver, i.e., Interface Card.

Product Development

Design

Document

Display?

Priority

Newest

List?

No Yes Yes Minor

Yes Yes Yes Major

Rev. # 19 Page 14 of 64

Oldest

List?

Severity

Program

Input

Minor

Major

Assign

Corrective Action

Search your application program to ensure that only positive values can be input to the SQRT, LOG and/or LN functions.

The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. An Interface Card (driver) may be out of date. Check for valid installed hardware. For example, if using the STLAN driver, make sure an ARCNET card is part of the Smart Trac drive card stack. An Interface Card (driver) may be out of date. Check for valid installed hardware. For example, if using the STLAN driver, make sure an ARCNET card is part of the Smart Trac drive card stack. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

14

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

22 34 Bad C Call A functional call within the

23 35 String Overrun Length of text to be displayed

24 36 Negative Shift During conversion of a data type

25 37 Bad Coercion Invalid data type promotion, i.e.,

26 38 Bad Address

Fault

Manager

Mode

program failed. Specifically, the amount of information being placed on stack(s) will exceed limit.

exceeds maximum number of allowable characters.

(number), the argument used to specify how many places to shift was negative .

change a ‘double’ to a ‘byte’. Problem found when validating operand types. Incorrect mode used when processing oper and and data type.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Major

No Yes Yes Minor

Yes Yes Yes Major

No Yes Yes Minor

Rev. # 19 Page 15 of 64

Oldest

List?

Severity

Program

Input

Major

Minor

Major

Minor

Assign

Corrective Action

Application program may be overburdened – reduce amount of logic placed in fast Tasks (15ms or faster) to slow Tasks (30 ms or slower). This may include reducing number of Program Units and/or program elements. Avoid use of extremely long text. Function Block names and symbol names should be kept to a manageable length (< 64 chars). Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Check application program for data type mismatches. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

15

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

27 39 Bad Bit

28 40 Bad Data Size Mismatch found when

29 41 Bit Out of

2A 42 Bad Function

2B 43 Bad Lower

Fault

Manager

Number

Range

Ptr

Bound

Requested bit number is unavailable.

performing computation on 2 differing data types. Logical bit does not fit within bounds of data type. For example, an attempted was made to OR bit 0x0800 with a byte.

Pointer to a Function Block call is invalid. ‘C’ FB cannot be processed.

Index into an internal array has exceeded the lower bounds.

Product Development

Design

Document

Display?

Priority

Newest

List?

No Yes Yes Minor

Rev. # 19 Page 16 of 64

Oldest

List?

Severity

Program

Input

Minor

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Check application program for data type mismatches.

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

16

10/17/00

Smart Trac

Faults.doc

Product Development

New Berlin

Technology Center

Design

Document

Title: Fault Declarations

Display?

Priority

Newest

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

2C 44 Bad Upper

2D 45 Invalid

2E 46 Invalid P-code Invalid P-code instruction Yes Yes Yes Critical

2F 47 Not used … … …

… … … 7FF7 32759 Not used 7FF8 32760 User Task

Fault

Manager

Bound

DateTime

Hung

Index into an internal array has exceeded the upper bounds.

Invalid date or time has been specified.

Attempts to terminate a Task, or remove it completely from the processing que ue ha ve fa il ed .

List?

No Yes Yes Minor

Yes Yes Yes Critical

Oldest

List?

Severity

Program

Input

Minor

Critical

and

Major

Critical

and

Major

Rev. # 19 Page 17 of 64

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists..

Application program may be overburdened – reduce amount of logic placed in fast Tasks (15ms or faster) to slow Tasks (30 ms or slower). This may include reducing number of Program Units and/or program elements.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

17

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

7FF9 32761 No Startup FB No startup function block was

7FFA 32762 Breakpoint Set Breakpoint encountered in

7FFB 32763 Bad Offset

7FFC 32764 Task Overrun Task has taken too long to

7FFD 32765 Restart Failed A request to have a Task change

Fault

Manager

Range

configured for a user task.

program. Not really a fault but used for debug purposes.

Attempt to address data within memory is out of range.

complete. Applies to Cyclic and IoSync Tasks only.

from stop to start mode has failed.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Critical

Yes Yes Yes N/A

Yes Yes Yes Critical

Rev. # 19 Page 18 of 64

Oldest

List?

Severity

Program

Input

Critical

and

Major

Critical

and

Major

Critical

and

Major

Critical

and

Major

Critical

and

Major

Assign

Corrective Action

Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists. Application program may be overburdened – reduce amount of logic placed in fast Tasks (15ms or faster) to slow Tasks (30 ms or slower). This may include reducing number of Program Units and/or program elements. Check for valid installed hardware. For example, if using the STLAN driver, make sure an ARCNET card is part of the Smart Trac card stack.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

18

10/17/00

Smart Trac

Faults.doc

New Berlin

Technology Center

Title: Fault Declarations

Displayed Fault No.

Fault Legend Description

Control

Node

Monitor

7FFE 32766 Watchdog

7FFF 32767 Fatal Error Unrecoverable fault, usually

Fault

Manager

Timeout

One or more Program Units associated with a Task have not been completed within the ‘Watch Dog Timeout’ setting.

occurs during Driver startup.

Product Development

Design

Document

Display?

Priority

Newest

List?

Yes Yes Yes Critical

Rev. # 19 Page 19 of 64

Oldest

List?

Severity

Program

Input

Critical

and

Major

Critical

and

Major

Assign

Corrective Action

Extend the Watchdog Timeout for the faulted Task. Generally, do not exceed 3x the cyclic task’s value nor 300ms for an IoSync Task. Application program may be overburdened – reduce amount of logic placed in fast Tasks (15ms or faster) to slow Tasks (30 ms or slower). This may include reducing number of Program Units and/or program elements. Verify that there are no hardware problems on the PC used to create the application. Recompile and reload the program and reload it to the SmartTrac drive. The Smart Trac main CPU card may be faulty. If available, download a small test program to see if fault persists.

The informatio n co ntained in this docum e nt is the CONFIDENTIAL property of MagneTek Inc. File = N:\PROJECT\515\SmartTrac\DOCS\Faults.DOC Print Date: 10/17/00

19