MaxDNA Alarm Messages

Alarm MessageReference Guide

277558 Rev A1

Metso Automation MAX Controls 277558 ii

Use this publication as a source for complete and accurate information that helps you better operateor service Metso Automation MAX Controls equipment. Your comments and suggestions arewelcome.

Metso Automation MAX Controls1180 Church RoadLansdale, PA 19446

Attention: Manager, Technical Publications

Copyright 1999-2001 by Metso Automation MAX Controls Inc.Printed in the United States of America

All rights reserved

Metso Automation MAX Controls 277558 iii

ContentsPart I General Introduction

Preface ............................................................................................................................................ v

Chapter 1......................................................................................................................................... 1Introduction.................................................................................................................................... 1

maxDNA System Alarm Classes ..............................................................................................................1Process Alarms ........................................................................................................................ 1System Alarms......................................................................................................................... 1

Alarm Configuration................................................................................................................................. 2Configuring Alarm Priorities ................................................................................................... 2

Viewing Alarm Messages ......................................................................................................................... 2Alarm Summary Display........................................................................................................................... 3

Alarm Summary Menu Buttons ............................................................................................... 3Alarm List Display................................................................................................................... 4

Printing Alarms Using Merged Events Program....................................................................................... 5Selecting Event Types ............................................................................................................. 6

Setting up EventMerge ............................................................................................................................. 7Selecting EventMerge Settings ................................................................................................ 8Printed Alarm Message Formats.............................................................................................. 9

Acknowledging and Silencing Alarms...................................................................................................... 9Using Keyboard Buttons........................................................................................................................... 9

Acknowledge and Silence........................................................................................................ 9Defeat .................................................................................................................................... 10Restore................................................................................................................................... 10

Defeating and Restoring Alarms............................................................................................................. 10Using maxVUE Runtime Display Buttons............................................................................................. 10

Chapter 2......................................................................................................................................... 1How to Interpret ............................................................................................................................. 1

Process Alarms.............................................................................................................................. 1

Control Block Alarms............................................................................................................................... 1High Level Analog Input Alarms.............................................................................................................. 2Data Block Alarms.................................................................................................................................... 3

Individual Alarm Cutouts ........................................................................................................ 4Troubleshooting Process Problems........................................................................................................... 4

Logged Process Alarm Format: ............................................................................................... 5

Chapter 3......................................................................................................................................... 1How to Interpret ............................................................................................................................. 1

System Alarms ............................................................................................................................... 1

Alarm Message Reference Guide

Metso Automation MAX Controls 277558 iv

System and Network Alarms.................................................................................................................... 1Logged System Alarms Format ................................................................................................2Troubleshooting System Problems ...........................................................................................2

Part II ............................................................................................................................................... 1Alarm Message............................................................................................................................... 1

Reference Guide............................................................................................................................. 1

Process Alarms......................................................................................................................................... 1

Part III .............................................................................................................................................. 1Alarm Message............................................................................................................................... 1

Reference Guide............................................................................................................................. 1

System Alarms ......................................................................................................................................... 1

Metso Automation MAX Controls 277558 v

Preface

The Alarm Reference Message Guide contains listings of all the processand system related alarm messages you are likely to encounter in theoperation of a maxDNA system.

Part I of this publication introduces you to all the maxDNA alarm types,alarm-related displays and alarm message formats appearing on displaysand on hard copy reports.

Part II provides a complete alphabetized listing of all the maxDNAprocess alarm messages along with text explaining what they mean. PartIII provides a similar listing for system alarms.

This publication assumes you have installed the maxSTATION runningsoftware Release 1.2.3 or later. This publication also assumes you arefamiliar with the maxSTATION and the various display environments.

For more information about related topics, refer to the followingpublications:

Book Title Book Number

maxSTATION Operator's Guide 277557

Metso Automation MAX Controls 277558 Part I 1-1

Chapter 1

Introduction

maxDNA System Alarm ClassesmaxDNA System lets you view two classes of alarms:

Process Alarms

System Alarms

Process Alarms

Process alarms consist of alarm messages associated with the processitself. These consist of two types:

Process Limit Alarms

Process limit alarms are caused by values exceeding theirassigned limits. Alarm information consists of time, pointtagname and its long description, alarm text associated with thealarm, current value of the point, alarm limit value, and the unitsof measure for the point in alarm.

Process Status Alarms

Process status alarms are generated by points and programs atDPUs. Alarm information consists of time, point tagname and itslong description, alarm type text and the alarm value.

System Alarms

System Alarms consist of alarm messages associated with the systemhardware. These consist of two types:

Station Diagnostic Alarms

Station diagnostic alarms are caused by maxSTATION orRemote Processing Unit (DPU, I/O boards) faults, such as weakbatteries, card failures, etc. Alarm information consists of time,



tagname of the station reporting the alarm, the device reportingthe fault, and the alarm text.

DPU Bus Network Diagnostic Alarms

This relates to two classes of alarms, DPU Bus related andmaxNET network related. DPU Bus network diagnostic alarmsare caused by cable breaks, token passing errors, failure ofstations to respond, etc. maxNET Network alarms are caused byFrame Switch or hub failures, Ethernet card failures, Ethernetcable breaks, or a failed target maxSTATION.

Alarm information consists of time, tagname for the DPU Busreporting the alarm (e.g. DPUBUS1), name of themaxSTATION involved in the fault, and the alarm text.

Alarm Configuration

You may set up alarms and events to be detected when you createconfigurations using maxTOOLS. The system then automatically detectsthe alarms and events, processes them, and identifies them for displayand acknowledgment, logging, analysis, and optional archiving.

Configuring Alarm Priorities

At time of configuration, you may give alarms one of six severity levels.(0 is the lowest prioritynot alarmed at alland 5 is the highestpriority.) Alarm severities can be used in conjunction with a temporaryfiltering function that you may configure using maxVUE Runtime tofurther classify, filter, and sort alarms for a more meaningfulpresentation of alarm conditions on alarm-related displays. See "AlarmSummary Display" for a listing of other filtering categories.

Viewing Alarm Messages

You may view alarms from the following standard and custommaxSTATION displays:

Alarm Summary

Alarm List

Other Display Types

Point Data Pop-up Faceplates

Point Detail displays

Introduction


Custom graphic displays

Alarm Summary Display

The Alarm Summary display shows filtered or unfiltered alarms (up to amaximum of 10,000) from all the DBMs databases (subsystems). Bydefault, a single Alarm Summary page displays up to 20 alarms,however, the window may be configured to display from 1 to 40 alarms;display buttons let you page up and down through the full list.

Click the Alarm Summary button on the Vertical Toolbar or on theOperator keyboard to access the display in a single keystroke. Each entryon the display lists the time, date, tagname, long description, value, limit,and acknowledge status of the alarm. Points may be selected in thesummary for display swap or control action. When selected, the tagnameof the selected point will appear on the Point Select button on theHorizontal Toolbar display.

Note: By default, the Alarm Summary display lists all alarms in theDBM database without filtering. Use the Temporary Filter SettingDisplay to set up and control how alarms are seen on the actual AlarmSummary displays.

You may filter alarms by type, the state of acknowledgment, and theseverity. See Publication 277557, maxSTATION Operator's Guide,"Filtering Alarms."

Alarm Summary Menu Buttons

The Alarm Summary Display includes six buttons at the bottom of thedisplay that let you view alarms filtered by various categories that youselect from the Temporary Filter Setting dialog box. See Publication277557, maxSTATION Operator's Guide, "Temporary Filter Setting."Table 1-1 relates the available filtering categories to maxDNA alarmclasses as described at the beginning of this chapter. You may click thefollowing buttons to display a filtered alarm list:

Click This To View This Display

All Display all alarm messages.Processdiagnostic\control

Display only process diagnostic and processcontrol alarms.

Process\systemdiagnostic

Display only system diagnostic and processdiagnostic alarms.

System diagnostic Display only system diagnostic alarms.Process diagnostic Display only process diagnostic alarms.



Process control Display only process control alarms.

Refer to the following Alarm Filtering Quick Reference Table for alisting of each filtering category that you may select, and thecorresponding alarm classes and types that come under this category.These correspond to choices available under the Alarm Type field fromthe Temporary Filter Settings dialog window in maxVUE Runtime.

Table 1-1. Alarm Filtering Quick Reference Table

Filtering Category(from Alarm Typefield)

Alarm Class Alarm Types

ProcessDiagnostic/Control

Process Process Limit, Process Status

Process/SystemDiagnostic

System,Process

System Diagnostic, Process LimitAlarm, Process Status Alarm

System Diagnostic System Station Diagnostic, HighwayNetwork Diagnostic

Process Diagnostic Process Process Limit Alarm, ProcessStatus Alarm

Process Control Process Process Limit, Process Status

All Process,System

Process Limit, Process Status,Station Diagnostic HighwayNetwork

Alarm List Display

The Alarm List display shows the most recent acknowledged andunacknowledged alarms (with the highest severity) of the maximum10,000 alarms from all the DBMs database (subsystems). By default, theAlarm List displays up to 20 alarms, however, the window may beconfigured to display from 1 to 40 alarms; the alarms appear inside awindow at the lower part of the Vertical Toolbar.

Because the Alarm List remains on the Vertical Toolbar display, younever lose sight of highest priority alarms. Unacknowledged alarms aredisplayed in their corresponding alarm severity color combination;acknowledged alarms are in white text on a black background.

Introduction


Figure 1-1. EventMerge Dialog Window

Printing Alarms Using Merged Events Program

In addition to viewing alarms on maxVUE Runtime displays, you mayprint merged events, which may include process and system alarms,using the EventMerge program. The EventMerge program acquiresfiltered events from all DBMs in the system and prints them in timeorder. To insure that events are printed in time order, they print after aconfigurable delay.

Events are directed to a local printer connected to a maxSTATIONparallel port. A printer must be attached to the maxSTATION in whichan instance of the EventMerge program is running.

You may create multiple instances of the program as a way to filter different event types. For instance, one instance may be configured toprint only sequence of events while another instance may be configuredto print all event types.

EventMerge can also send events to a file. (This feature is enabled bydefault in the Events.ini file.) See "Setting up EventMerge." Event filesare maintained in the \Custom\History folder. The program producesone file per day and overwrites files for the previous week.



Selecting Event Types

You may select the type of information to be logged via the EventMergedialog box which shows the last 500 alarms. To open this display at anOperator Station, create a button in the maxVUE Editor that may beadded to the Vertical or Horizontal Toolbar.

To create the button, use the following Live Data property:

Write Point Identifier = _Events.events where events is the name of theINI file. The Write Point Value should be set to 1 and the Type isInteger. All other button properties are optional. At this display you mayselect the following events for logging:

Event Type Type Code (Checkbox)

Process alarms PASystem alarms SYOperator actions OASequence of events SQProgram generated events PGEdit actions EA

To identify printed alarm and event types on a hardcopy report, refer tothe two-character type code. Use the following EventMerge dialog boxbuttons and checkboxes to select event filters and to control eventprinting options:

Button/Check Box Description

Start/Stop Print Starts or stops the transmission of alarms to theprinter. Pressing the button toggles the state.Note that the dialog box will continue to gainevents even though printing is stopped.

Purge Deletes the events in the dialog box. It does notdelete events that have already been sent to theprinter.

Re-Print All of the events in the dialog box that havebeen sent to the printer are sent again.

Event Filters A checkbox appears next to a list of each eventtype. Only selected event types are sent to theprinter, file and dialog window. The initialsettings are determined by assignments made inthe events INI file, but you may change thefilters while EventMerge is running. See nextsection.

Introduction


Setting up EventMerge

To set up the EventMerge program, you must edit the EventMerge INIFile to select configuration and connections for each EventMergeinstance. From this file, you may modify the default settings that appearon the EventMerge dialog window. The Events.ini file contains descriptions and default assignments for each command. See nextsection.

If you are satisfied with the current settings, it may only be necessary tochange the service names.The Events.ini file must be updated to includethe appropriate event service names for the target system.

The service name is typically _RTG_EVENT_dbm_name. Substitute thecorrect DBM name after _RTG_EVENT. (Check the RRS dialogwindow for a list of registered service names.)

To configure the INI file:

1. Copy the file, which resides in \Custom\Sbp, to a new name and thenmake the desired changes. The EventMerge program accepts oneinput parameter: the name of its INI file.

2. Edit the new file as desired.

3. After you create the new event INI, go back to the startup INI file,locate the file Events.ini and change it to match the new filename.

The following entry appears in the Startup.ini file (in\custom\sbp\startup.ini):

3, c:\MCS\Sbp\EventMerge.exe, EventMerge Events.ini, /Events.ini

Note: INI filename appears twice on the EventMerge line. Change bothoccurences.

4. Shutdown the Startup program that resides in each maxSTATION(StopStation) and restart to pick up changes in the Startup.ini file.The EventMerge INI file is only read during EventMergeinitialization.

Note: To create multiple instances of EventMerge make additionalEventMerge entries in the Startup.ini file. Each EventMerge instanceshould have its own customized events INI file by including a differentINI filename in each entry in the Startup.ini file.



Selecting EventMerge Settings

The event.ini file contains the following commands which you maychange as desired:

Command What It Means

Service The service names for the event providers must belisted here. The service name usually starts with"_RTG_EVENT_" followed by the DBM name.The maxrrs program shows the list of registeredservices.

SERVICE = _RTG_EVENT_DBM1SERVICE = _RTG_EVENT_DBM2SERVICE = _RTG_EVENT_DBM3SERVICE = _lss

PrintState The print state specifies whether events are sent tothe printer. Valid ; command values are ON or OFF.The print state can also be toggled from theEventMerge dialog box.

FileEnable The file enable specifies whether events are writtento a file in the Custom/History folder. This featurecan only be specified here (no dialog boxcapability). Valid command values are ON or OFF.If FileEnable is set to "ON" a file name for printedevents can be specified. The filename should notcontain an extension (.log is added by the program).If a filename is not specifed, "events" is used. Notethat EventMerge will append day text to the filename.

Delay Delay specifies how long the events are held in theevent list before being moved to the dialog windowand print file. Some delay is necessary so thatevents can be listed in time order. If DELAY iscommented out, a delay of 20 seconds is used. Adelay of less than 15 seconds is not recommended.

EventType Event types preceded by a semicolon will not beprinted or written to the event file.Event types can also be enabled/disabled from theEventMerge dialog box. The spelling of the Eventtype command values shown below should not bechanged.

Hid Up to 10 HID specifiers can be included here. (Notyet supported)

Introduction


Printed Alarm Message Formats

The format of printed alarm messages is different from the format usedon maxSTATION alarm displays. Logged messages appearing onhardcopy reports tend to include more information because the printedformat, unlike the more restricted maxSTATION screen format, canaccommodate larger fields. Refer to Chapter 3, "How to Interpret SystemAlarms," and Chapter 2, "How to Interpret Process Alarms," for a reviewof Alarm Summary display alarm message formats and how they differfrom hardcopy formats.

Acknowledging and Silencing Alarms

With only a single keystroke, you may acknowledge alarms using theoperator keyboard, the PC keyboard and from a variety of maxVUERuntime Displays at the maxSTATION.

Using Keyboard Buttons

The four alarm keys, colored yellow on the maxDNA operator keyboard,control alarms. Two of these keys, and , alsoappear on the standard Horizontal and Vertical Toolbar display. Usethese keys to temporarily stop alarms from occurring, , restoretheir function, , acknowledge them, , and silence theaudible annunciator, .

Acknowledge and Silence

Press the key to acknowledge the highest priorityunacknowledged alarm; this is the top alarm displayed in the alarm listdisplay on the Vertical Toolbar display. This key has the same effect asthe Ack button on the Alarm List display. On the PC keyboard, theequivalent key is . See the next section.

When a new alarm is detected, the maxSTATION can sound an audiblealarm in addition to posting the new alarm in the appropriate location inthe alarm list. The key lets you quiet the alarm with a singlekeystroke and has the same effect as the Silence button on the VerticalToolbar display. See "Using maxVUE Runtime Display Buttons."

The key only silences an audible alarm; the key both silences and acknowledges the top most alarm on the list.



Defeat

Defeats all alarms on the currently selected block. When implemented,the block will not alarm until it has been restored. Use of this key maybe restricted. On the PC keyboard, the equivalent key is .

Restore

Restores all alarms on the currently selected block so that it can alarmagain. On the PC keyboard, the equivalent key is . See nextsection.

Defeating and Restoring Alarms

You may temporarily defeat Control and Data Block alarms withoutchanging their triggering criteria. This permits individual process loopsand other control actions to be switched off during operating periodswhen the alarm would be of no use. An example of this would benuisance alarms that occur during startup or changes to part of thesystem. When normal operation resumes, the alarm features of thatfunction can be restored.

The Defeat capability eliminates clutter in alarm summaries andoperating views, simplifying the operator's view of the process. To besure operators do not overlook defeated alarms, the word defeatedappears in every faceplate, which displays that loop or controls action.

Note: You may only defeat process-related points; alarms related tosystem hardware points cannot be defeated.

Using maxVUE Runtime Display Buttons

From maxVUE Runtime displays, you may acknowledge and silencealarms from the standard Vertical and Horizontal Toolbars, AlarmSummary Display, Alarm List Display, and from Point Control pop-upsand digital Detail Displays. Refer to the following table:

Button Location Description

Ack Point Data Pop-up,Point Detail Display

Acknowledge Alarmcondition of the current point.

Ack Page Alarm Summary Acknowledges all alarms inthe currently displayed page.

Introduction


Button Location Description

*Ack Point Horizontal Toolbar Acknowledge any alarmwhich exists for the pointcurrently selected.

*Ack Top Alarm Summary,Alarm ListAcknowledge the top-mostalarm appearing at the top ofthe Alarm List window andthe Alarm Summary display.

**Silence Vertical Toolbar Silence an audible signaloriginating in amaxSTATION equipped witha sound board and speakers.The audible signal indicatesthat an alarm has occurred fora point assigned to a pre-defined hierarchical group.

* If an audible alarm is equipped, this action will silence the audible alarm.** The Silence key only silences an audible alarm; the Acknowledge key bothsilences and acknowledges the top most alarm on the list. maxSTATIONs notequipped with sound boards and speakers may be configured to silence alarmsoccurring at a maxSTATION playing the sound.

Note: Because and buttons, and the AlarmList window appear on the standard Vertical and Horizontal Toolbars,you may place these elements on every screen view in the system, ifdesired.

You may select individual alarms on the Alarm Summary display bypointing to an alarm and clicking the left mouse button. In response, thesystem displays the point tag name at the bottom of the display. Onceselected, the point can be acknowledged via the Ack point button.7Additionally, the Point Data, Control and Detail buttons will apply tothe selected point.


Chapter 2

How to InterpretProcess Alarms

A process alarm indicates that some portion of the process has gonebeyond its specified limits. When a point goes into alarm, the systemadds its tagname to the Alarm List and Alarm Summary displays, andindicates the alarm condition on appropriate point-related pop-updisplays.

Each of the standard maxDNA functional blocks stored in the DPUdatabase has many alarm states and control conditions built into them,which are set during the configuration process. This permits alarmingcapability and an interlocking capability with other user-ready and user-defined blocks.

Control Block Alarms

Control Blocks, stored in the DPU, can contain up to 16 independentlyadjustable alarms, which permit alarming and interlock capabilities notonly within the specific block originating the alarm but also in othercomputational blocks. The PID Control Block, for example, will alarmand set triggers (Alarm/Mode Word bits) for interlock upon thefollowing six conditions:

Process Variable HI Setpoint LO

Process Variable LO Deviation HI

Setpoint HI Deviation LO

(Refer to online help to reference Alarm/Mode Words associated witheach Control Block type.)



The PID Control Block will display an alarm if any of the input alarmconditions occur. (Refer to the next section.) This control block will alsoset triggers for individual interlocks upon the following other conditions:

Output HI.

Output LO.

Emergency down state induced by either operator or interlock toother conditions.

Receipt of a cascaded forceback signal.

Receipt of an external override signal.

Placed into manual through a hand station.

Placed into manual by operator.

Placed into manual by interlock from other control blocks.

Placed in automatic by either interlock or operator.

Placed into cascade by either interlock or operator.

Placed into computer mode by either interlock or operator.

High Level Analog Input Alarms

The DPU can scan up to 60 high level analog inputs every 125milliseconds. These fast-scan inputs, which are configured using AnalogInput Buffer (AIB) blocks, each have the following eight associatedalarm conditions:

Instrument Out of Range LO Alarm HI Instrument Out of Range HI Alarm (HI or LO) Instrument Out of Range (HI or LO) Any limit exceeded Alarm LO Link Failure (cannot commun-

icate with I/O module)

Note: Since AIBs cannot be independently alarmed, they do not appearon any alarm displays. AIBs may be read by Control and Data Blocks;should an AIB reach an alarm state, the Control and Data Block used tomonitor the AIB will actually go into an alarm state. To actually look atthe AIB alarm condition, you may have to look at the associated Controland Data Block detail display.

How to Interpret Process Alarms


Analog input alarms can help discriminate between reaching anoperational and safety alarm condition and the failure of an input device,such as a field sensor/transducer or the loss of an I/O module or channel.

Data Block Alarms

The DPU 248 Data Blocks each have the same eight input alarms listedfor the High Level Analog Inputs. This allows the same alarms to beapplied to other inputs by linking them to a Data Block. In addition, DataBlocks can each be used to perform any of the following alarm options:

Open thermocouple detection.

HI and LO alarm condition.

HI-HI and LO-LO alarms expressed either as an absolute value or asa delta from the HI or LO alarm value.

Rate-of-change alarms and rate-of-change clamps placed on inputsor outputs to detect unacceptable slew rates or to limit signal slewrates.

Adjustable hysteresis (% value) deadband for value-related alarms(HI, LO, HI-HI etc.) to prevent nuisance alarms as a variable hoversaround an alarm trip value.

Time Delay settings to suppress transient swings into alarm but notsustained alarm conditions.

Alarms built into each Data Block can be set up to trigger:

On single threshold crossing or on repetitive deltas.

Upon return to normal.

If acknowledged, but situation remains uncorrected for too long atime period.

Alarms can also automatically acknowledge when they return to normalbefore being acknowledged by the operator. These options enable theprocess engineer to alert operators to abnormal conditions whileeliminating the nuisance alarms that can obscure more important processinformation.



Individual Alarm Cutouts

An Alarm Cutout feature makes it possible to dynamically disable only aspecific type of alarm in a Data Block. These could be all LO alarms, allHI alarms, rising/falling, or all alarms. Cutout can be due to processvalue changes or system hardware conditions. For example, duringknown disruptive operations (start up or shut down), selective alarmscan be temporarily disabled to avoid masking more important realalarms. Yet you will be kept aware of other conditions of that samebypassed point, such as an open thermocouple.

These alarm cutouts are independent of the Alarm Defeat/Restoremechanism, and can be triggered either by operator command, by adiscrete signal, or induced by a program.

Any event, threshold of analog value, lapse of time, condition, state,sequence step (or completion) or command either within or outside ofmaxDNA can be used to trigger an alarm cutout.

A single event or logic result of several conditions or events (booleanexpression) can impact the alarm of a single Data Block, or anycombination of Blocks. Each Data Block can have its own independenttriggering circumstance.

Troubleshooting Process Problems

Process limit alarms and process status alarms appear together on theAlarm Summary display mixed in with system alarm messages. Theformat of displayed process alarms is somewhat different from theformat for station alarms and DPU Bus network alarms. (Refer toChapter 3, "How to Interpret System Alarms" for a description of systemalarm formats.)

Process limit alarms have the following format:

Message TextTime Date Tagname Description

Alarm Text AlarmValue

Limit

HH:MM:SS MM:DD:YY Up to 16characters

Up to 32 characters

Variable Character Lengths



Process status alarms have the following format:

Message TextTime Date Tagname Description

Alarm Text AlarmValue

Limit

HH:MM:SS MM:DD:YY Up to 16characters

Up to 32 characters

Variable Character Lengths

Note: The Limits field does not apply tostatus alarms.

Displayed process limit alarms and process status alarms are alsosomewhat different from each other. Process limit alarms report:

Time the alarm occurred.

Tagname of associated point.

Name of point and alarm message text under the Description field.

Alarm type.

Current value of the point.

Alarm limit value.

Units of measure for the point.

The process status alarms format is similar to the process limit alarmsformat as outlined above; however, because status alarms are associatedwith digital type points, the Summary Display Limits field does notapply and is not used.

Process alarm messages also appear in a hardcopy version that uses aformat somewhat different from the Alarm Summary Display format.Because the printed format can accommodate 133 characters per line,printed text may contain additional information. Refer to the followingfigure to learn how to recognize logged process alarms:

Logged Process Alarm Format:date/ time severity type alm/clr tagname description value

limitlongtitle

18 3 2 3 16 16 38 32

Process limit alarms report:

Date/time

Time the process alarm occurred.



Severity

Alarm severity ranging from 0 to 5; the severity number appears in athree-character field surrounded by asterisks: *5*

Type

When a process alarm is logged, the characters pa appear in this two-character wide field.

Note: The format for process alarms and edit actions is the same. AnEdit Action occurs when an operator takes some action involving apoint, such as a mode change or a configuration. When a Edit Action islogged, the characters ea appear.

Tagname

Tagname of associated point; the tagname is created when youconfigure a point using maxTOOLS.

Alm/clr

When an unacknowledged process alarm is logged, the characters almappear in this three-character wide field. If the alarm is acknowledgedor otherwise clears, the characters clr appear. If the line applies to anedit action, the field is blank.

Description

Process Alarm message text, such as HiHi LoLo; Range High; and soforth.

When this field applies to an edit action, the message text describesan attribute that was edited.

Value Limit

When this field applies to a process alarm, it reports the current valueof the point and the alarm limit value.

When this field applies to an edit action, it reports that the limit waschanged; the new limit value along with the previous value limitappear in this field.

Long Title

Long name of point.

To troubleshoot process alarms, you may access Point Data, Control, andDetail pop-up displays to learn more about points in alarm and to makequick adjustments to your process. When a process alarm occurs, thealarm message will also appear on these displays.



You may invoke these displays in maxVUE Runtime by selecting theappropriate button on the main menu Horizontal and Vertical Toolbars. See Publication 277577, maxVUE Operator's Guide.


Chapter 3

How to InterpretSystem Alarms

System and Network AlarmsSystem diagnostic status alarms inform you of maxDNA systemhardware and software problems. Problems detected within a specificmodule or station are classified as diagnostic failures. Problems withcommunications are referred to as highway network alarms. DPU Busnetwork alarms are further divided between DPU Bus network andmaxNET network communications problems. maxVUE Runtime SystemStatus displays show both alarm types.

System alarms appear along with process alarms on the Alarm SummaryDisplay and on the Alarm List. The format of displayed system alarms issomewhat different from the format for process alarms; refer to theprevious chapter for a description of process alarm formats.

System alarms have the following format:Time Date Tagname Text

Subsystem Name Message TextHH:MM:SS MM:DD:YY Up to 16characters

Variable Character Length

On the display, the subsystem reporting the fault and the message textappear together under the Description field. The three fields to the rightof this field Type, Value, Limit apply to Process alarms.

System alarm messages also appear in a hardcopy version that uses aformat somewhat different from the Alarm Summary display format.Because the printed format can accommodate 133 characters per line,printed text may contain additional information.

Refer to the following figure to learn how to recognize logged systemalarms:



Logged System Alarms Formatdate/time severity type alm/clr tagname description

Size of field 18 3 2 3 16 54

System alarm fields report:

Date/time

Time the system alarm occurred.

Severity

Alarm severity ranging from 0 to 5; the severity number appears in athree-character field surrounded by asterisks: *5*

Type

When a system alarm is logged, the characters sy appear in this two-character wide field.

Tagname

Tagname of associated point; the tagname is created when youconfigure a point using maxTOOLS.

Alm/clr

When an unacknowledged system alarm is logged, the characters almappear in this three-character wide field. If the alarm is acknowledgedor otherwise clears, the characters clr appear.

Description

Alarm message text.

Troubleshooting System Problems

When a system alarm occurs, read the message text to determine thenature of the problem. For a better understanding of what the messagemeans, refer to Part III of this book which provides an alphabetized listof all the maxDNA system messages and their meanings.

The most obvious way to pinpoint the source of a hardware or communi-cations problem is by looking up the tagname associated with themessage. When you configure the system hardware using maxTOOLSsoftware, you assign a unique tagname to each DPU Bus and to eachstation assigned to a DPU Bus. The maxDNA system references DPUBuses and stations by tagname.

When you create or update a system, the tagnames used in the logicalconfiguration of the system should also appear on labels attached to theactual physical device. This makes it easier to pinpoint the location of

How to Interpret System Alarms


the maxSTATION, DPU, I/O module, or DPU Bus reporting theproblem.

If you have a particularly large configuration consisting of multiple DPUBuses and many stations configured with each DPU Bus, system statusdisplays may also help you to pinpoint the location of a system problem.

System status displays are a collection of screens used to diagnoseproblems in your system. These consist of:

System Status Display

DPU Bus Map Display

DPU Bus Statistics Display

DPU Bus Station Status Display

Refer to Publication 277557, maxSTATION Operator's Guide, for moreinformation about these displays.

Metso Automation MAX Controls 277558 Part II II-1

Part II


Process AlarmsPart II consists of an alphabetic listing of all maxDNA Process Alarmmessages. The following pages contain the actual message text(appearing here in all upper case characters), the point or points whichcan generate the alarm, and a description of what each process alarmmessage means.

Process alarm message text for any given point appears in three versions:

16-character text used in alarm log

12-character text used in Alarm Summary displays

12-character text used in Detail pop-ups

All three versions are listed for each process alarm message entry.

Note: Points for which an alarm message is applicable include someControl Blocks, which are no longer supported by maxDNA, but weresupported by the Models 582 and 585 Operator Stations. Those pointsare identified using ** in the table.


Metso Automation MAX Controls 277558 Part II

II-2

ALM INT'LOCK ALM INRLOCK ALARM INLK

Point(s) which generate this alarm: ReversingMotor Controller (Cntrl Block)

Meaning: One of the Interlock inputsconfigured as an Alarm Interlock has becometrue. The motor will be turned off. This alarmmay cause the algorithm to go to the'stopping' state.

ALARM INTERLOC ALM INTERLOC ALM INTERLOC

Point(s) which generate this alarm: BinaryControl (Control Block)

Meaning: User-defined in Binary Control ModuleExCEL.

BACKED OVER BACKED OVER SEC ACTIVE

Point(s) which generate this alarm: Backup(Control Block)

Meaning: Control has been transferred to thesecondary DPU of a backup pair.

BACKUP BACKUP BACKUP

Point(s) which generate this alarm:**Receives (Control Blocks)

Meaning: This block is now receiving datafrom the backup DPU of a backup pair,becauseof a transfer of control in that pair.

BOTH LIMITS BOTH LIMITS BOTH LIMIT

Point(s) which generate this alarm:Valve/Breaker Controller (Control Block)

Meaning: Both limit inputs have become true.

CLOSED CLOSED CLOSED


Meaning: User-defined in Binary ControlModule ExCEL.

Process Alarms


COMM FAILED COMM FAILED COMM FAIL


Meaning: No data received from other station.

CONF ERROR CONF ERROR CONF ERROR

Point(s) which generate this alarm: All DataBlocks

Meaning: An illegal value has been enteredinto one of the editable fields of a DataBlock.

DEV HIHI DEV HIHI DV HL

Point(s) which generate this alarm: **RealAlarm (Control Block)

Meaning: The deviation has exceeded theconfigured HIHI limit.

DEV LIMIT DEV LIMIT DV

Point(s) which generate this alarm: PID(Control Block)

Meaning: 'Generic' alarm raised if the PIDalgorithm has raised a deviation limit alarmbut the condition cleared before it was logged.

DEV LOLO DEV LOLO DV HL


Meaning: The deviation has exceeded theconfigured LOLO limit.

DEVIATION DEVIATION DV

Point(s) which generate this alarm: **DataAcquisition (Control Block)

Meaning: The L3 limit is exceeded by any pairof inputs.



II-4

DEVIATION HI DEV HIGH DV


Meaning: Deviation between process variableand set point has exceeded the configured highalarm limit.

DEVIATION LO DEV LOW DV


Meaning: Deviation between process variableand set point has exceeded the configured lowalarm limit.

DEV HIGH DEV HIGH DV

Point(s) which generate this alarm: **EventCounter (Control Block)

Meaning: Output minus the specified deviationvalue has exceeded the configured deviationhigh alarm limit.

DEV LOW DEV LOW DV

Point(s) which generate this alarm: **EventCounter (Control Block)

Meaning: Output minus the specified deviationvalue has exceeded the configured deviation lowalarm limit.

DIGITAL ALRM DIGITAL ALRM ALARM

Point(s) which generate this alarm: Alldigital Data Blocks

Meaning: A digital data block has gone intoalarm.

DIGITAL INP DIGITAL INP ALARM

Point(s) which generate this alarm: DigitalStatus/Alarm (Control Block)

Meaning: The output bit of the point hasbecome true and the algorithm is configured toalarm.

Process Alarms


DISCREPANCY DISCREPANCY DISCREPANCY

Point(s) which generate this alarm:Sequencer, Ramp Gen (Control Blocks)

Meaning: Either the first control block in a'chain' of blocks (used to construct sequenceswith more than 8 steps) is not the same typeas the others in the chain; or the controlblock attempted to access a step which ishigher than allowed based on the number ofslots in the chain; or the control block wastrying to find the first 'off' step but eithercould not find it or its number was greaterthan 255.

DISCREP+TIM DISCREP+TIME DISC + TIME

Point(s) which generate this alarm:Sequencer, Ramp Gen (Control Blocks)

Meaning: A discrepancy alarm has occurred,and the time in a particular step has exceededthe allowed time.

DV HL DV HL DV


Meaning: 'Generic' alarm raised if the RealAlarm algorithm has raised a deviation limitalarm but the condition cleared before it waslogged.

DV RATE DV RATE DV R


Meaning: Input 1 rate of change has exceededthe configured limit.

FAIL FAIL FAIL





II-6

FAILED FAILED FAILED


Meaning: Control has been transferred to thebackup DPU of a backup pair; this controlblock is no longer in control.

FALLING FALLING FALLING

Point(s) which generate this alarm: AnalogData Blocks

Meaning: The output of the Data Block isdecreasing at a rate faster than theconfigured Rate-of-Change limit.

HIGH ALARM HIGH ALARM ALARM HIGH

Point(s) which generate this alarm: AnalogData Blocks, Analog Input Buffers

Meaning: Input value is greater than or equalto the configured high alarm limit.

HIHI ALARM HIHI ALARM HIHI ALARM


Meaning: Input value is greater than or equalto the configured high alarm limit.

INP 1 INP 1 INP

Point(s) which generate this alarm: AnalogControl Blocks

Meaning: Input 1 of this block is in alarm;see the input's Detail Popup to observe theexact alarm condition.

INP 2 INP 2 INP



Process Alarms


INP 3 INP 3 INP



INP 4 INP 4 INP



INP 5 INP 5 INP



INP 6 INP 6 INP



INP 7 INP 7 INP



INP 8 INP 8 INP




II-8


INPUT ALARM INPUT ALARM INP


Meaning: 'Generic' alarm raised if thecontrol block has raised an input alarm butthe condition cleared before it was logged.

I1 LIMIT I1 LIMIT INP

Point(s) which generate this alarm: Selectand 8-Pos Switch Control Blocks

Meaning: 'Generic' alarm indicating that thecontrol block has raised an input alarm forinput 1 but the condition cleared before itwas logged.

I2 LIMIT I2 LIMIT INP

Point(s) which generate this alarm: Selectand 8-Pos Switch Control Blocks

Meaning: 'Generic' alarm indicating that thecontrol block has raised an input alarm forinput 2 but the condition cleared before itwas logged.

INSTR HIGH INSTR HIGH INST HIGH


Meaning: Hardware failure alarm indicatingthat the input is greater than 5.5V on a 1V-5Vinput.

INSTR LOW INSTR LOW INST LOW


Meaning: Hardware failure alarm indicatingthat the input is less than 0.5V on a 1V-5Vinput.

Process Alarms


LEFT LIMIT LEFT LIMIT LEFT LIMIT

Point(s) which generate this alarm:Positioner (Control Block)

Meaning: The left limit input has become truewhile the motor is running in the reversedirection.

LINK FAILED LINK FAILED LINK FAIL

Point(s) which generate this alarm: DataBlocks

Meaning: The DPU has lost communication withthe I/O device; for example, if a Receive DataBlock can no longer communicate with the otherDPU.

LOLO ALARM LOLO ALARM LOLO ALARM


Meaning: Input value is less than or equal tothe configured low low alarm limit.

LOW ALARM LOW ALARM ALARM LOW


Meaning: Input value is less than or equal tothe configured low alarm limit.

NO MINIMUM SPEED NO MIN SPEED NO MIN SPEED



NO MFWD/MREV NO MF/MR NO MF/MR





II-10

NON CONGR INPT NON CNG INPT NON CNG INPT



NORMAL NORMAL NORMAL


Meaning: An alarmed condition has returned tonormal.

NOT CLOSED NOT CLOSED NOT CLOSED


Meaning: The 'closed' feedback input has notgone true within the specified time limit.



NOT OPEN NOT OPEN NOT OPEN


Meaning: The 'open' feedback input has notgone true within the specified time limit.

NOT OFF NOT OFF NOT OFF


Meaning: Within 2 seconds of the start/stopinput going false the motor forward (or motorreverse) input has not gone false; or the runfeedback input has not gone false within theconfigured time limit during the stopsequence.

Process Alarms




NOT OPEN/CLOSED NOT OP/CL NOT OP/CL



NOT OPN+CLSD NO OP+CLOSED NOT OP + CL


Meaning: Both 'open' and 'closed' feedbackinputs are false.

NOT READY NOT READY NOT READY


Meaning: The 'motor ready' input goes falsewhile the motor is running, or during startup.



NOT START NOT START NOT START



OPEN T/C OPEN T/C OPEN TC


Meaning: Hardware failure alarm indicating anopen thermocouple.



II-12

OUT INPUT OUT INPUT DV

Point(s) which generate this alarm: **DemandLimit Regulator (Control Block)

Meaning: Generic alarm indicating that thepoint has generated either an output > inputalarm or an output < input alarm, but thecondition cleared before it was logged.

OUTPUTINPUT OUTPUT > INP DV

Point(s) which generate this alarm: **DemandLimit Regulator (Control Block)

Meaning: Difference between the input to andthe output of the algorithm has exceeded theconfigured limit value.

POS'N TIMOUT POS'N TMOUT POS TIME


Meaning: The motor has been started and themaximum positioning time has been exceeded.

POS+BOTH LIM POS+BOTH LMS POS BOTH


Meaning: Maximum position time has beenexceeded and both limits are true.

POS+L LIMIT POS+LEFT LM POS LEFT


Meaning: Maximum position time has beenexceeded and the left limit is true.

Process Alarms


POS+R LIMIT POS+RIGHT LM POS RIGHT


Meaning: Maximum position time has beenexceeded and the right limit is true.

PV HIGH HIGH PV HIHI PV HL


Meaning: The process input value has exceededthe configured HIHI limit.

PV LOW LOW PV LOLO PV HL


Meaning: The process input value has exceededthe configured LOLO limit.

PV HIGH PV HIGH PV


Meaning: The process variable input (or input1) has exceeded the configured PV high limit.

PV HL PV HL PV


Meaning: Generic alarm indicating that thepoint has generated a PV high or low alarm,but the condition cleared before it waslogged.

PV LOW PV LOW PV


Meaning: The process variable input (or input1) is less than the configured PV lo limit.



II-14

PV RATE PV RATE PV R


Meaning: The process input value rate ofchange has exceeded the configured limit.

PV I1 HIGH PV I1 HIGH PV

Point(s) which generate this alarm:Overrides, 8 Pos Switch (Control Blocks)

Meaning: Analog input I1 is greater than theconfigured HI alarm value.

PV I1 LOW PV I1 LOW PV


Meaning: Analog input I1 is less than theconfigured LO alarm value.












Process Alarms























II-16













PV LIMIT PV LIMIT PV


Meaning: 'Generic' alarm indicating that thepoint has generated a PV limit alarm but thecondition cleared before it was logged.

RANGE HIGH RANGE HIGH OVERRANGE

Point(s) which generate this alarm: DataBlocks, Analog Input Buffers

Meaning: The input to the data block isgreater than the configured range high limit.

RANGE LOW RANGE LOW UNDERRANGE

Point(s) which generate this alarm: DataBlocks, Analog Input Buffers

Process Alarms


Meaning: The input to the data block is lessthan the configured range low limit.

RIGHT LIMIT RIGHT LIMIT RIGHT LIMIT


Meaning: The right limit input has becometrue while the motor is running in the reversedirection.

RISING RISING RISING


Meaning: The output of the data block isincreasing at a rate faster than theconfigured Rate-of-Change limit.

RUNBACK RUNBACK DV

Point(s) which generate this alarm: HardRunback (Control Block)

Meaning: The logic input calling for arunback has become true and the output of theblock is being decreased; or the limitassociated with the logic input calling forthe runback has been exceeded.

RUNDOWN RUNDOWN DV

Point(s) which generate this alarm: DemandLimit Regulator (Control Block)

Meaning: The logic input calling for arundown has become true and the output of theblock is being decreased to the limitassociated with the logic input calling forthe rundown.

RUN'G NO F/R RUN NO MF/MR RUN NO FF


Meaning: Either the motor forward input orthe motor reverse input goes false whilemotor is running.



II-18

RUNN'G NO RF RUNN NO RF RUN NO RF


Meaning: The motor running feedback inputgoes false while the motor is running.

RUNUP RUNUP DV

Point(s) which generate this alarm: DemandLimit Regulator (Control Block)

Meaning: The logic input calling for a runuphas become true and the output of the block isbeing increased to the limit associated withthe logic input calling for the runup.

SEC'Y FAIL SEC FAIL SEC FAIL


Meaning: No data being received from theother station; the last value that wasreceived came from the secondary DPU of abackup pair.

SEC'Y NO RDY SEC NOT RDY NOT READY


Meaning: There is a problem with thesecondary DPU of a backup pair, or the backuplink is not working; the secondary will not beable to assume control.

SEQ INT'LOCK SEQ INRLOCK SEQ INLK


Meaning: One of the Interlock inputsconfigured as a Sequence Interlock has becometrue. The motor will be turned off only if itis not already in the Running Forward orRunning Reverse states. This alarm may causethe algorithm to go to the stopping state.

Process Alarms


SEQUENC INTERLOC SEQ INTERLOC SEQ INTERLOC



SETPT CLAMP SETPT CLAMP SP

Point(s) which generate this alarm: PIDControl Block

Meaning: 'Generic' alarm indicating that thepoint has generated a setpoint clamp alarm butthe condition cleared before it was logged.

SETPT HI SETPT HI SP


Meaning: The setpoint is greater than thevalue configured in K5.

SETPT LO SETPT LO SP


Meaning: The setpoint is less than the valueconfigured in K4.

START START START


Meaning: User-defined in Binary Control ModuleExCEL.

START NO RF START NO RF START NO RF


Meaning: The run feedback input has not gonetrue within the configured time limit duringthe starting sequence of the motor.



II-20

START NO F/R ST NO MF/MR START NO FF


Meaning: The motor forward (or motor reverse)input has not gone true within 2 seconds ofthe start sequence of the motor.

TIME EXCEED TIME EXCEED TIME XCD

Point(s) which generate this alarm:Sequencer, Ramp Gen (Control Block)

Meaning: The configured time to move to thenext step of the ramp or sequence has beenexceeded.

TRIP TRIP TRIP



UNAVAIL FLD DEV UA FIELD DEVUA FIELD DEV



Metso Automation MAX Controls 277558 Part III III-1

Part III


System AlarmsPart III consists of an alphabetic listing of all maxDNA System Alarmmessages. The following pages contain the actual message text (appearinghere in all upper case characters), how the alarm impacts the DPU, thereporting device and a description of what each system alarm messagemeans.

Alarm Message Reference Guide System Alarms


Alarm Text Type CausesDPUFailover

ActivatesDPUOfflineContact

DPUAlarmSeverity

ReportingDevice

Description

24-BIT BUS PATH ERROR IN 1ST DATABASE

YES NO 43 DHW A test value written to the common database by backgrounddiagnostics was found to have been corrupted.

A CABLE IS BROKEN HighwayCommHWYn At one or more locations on the named highway, there is a

cable break; see the System Status display for that highwayto see which stations are reporting the break.

A STATION WENT DOWN OR CAME UP HWYn(name)

One of the highway stations has stopped passing token, orhas just started passing token again. (name) is the name ofthe station which could not pass the token to the stationwhich left the highway.

AI OR API LINEARIZATION ERROR YES NO 39 IOP Linearization range calculation error.ALARM LIST OVERFLOW RTP There are more process alarms present than the database is

sized to handle. An attempt at subsequent reconstruction isperformed, assuming that this might be a transitory problem.

ALM DLL COULD NOT Read DBMName (suchvas "DBM1 or "DBM2")

max-STATION

A session was allocated, but now the DBM is not respondingwith alarm list data.

ALM DLL COULD NOT START DBMName(such as "DBM1 or "DBM2") SESSION

max-STATION

This alarm occurs when trying to allocate an alarm sessionwith a DBM.

AP BECAME ACTIVE RTP The Real-Time Processor annunciates that the attachedApplications Processor has become active.


Metso Automation MAX Controls 277558 Part III

III-3



DPUAlarmSeverity

ReportingDevice

Description

AP CANNOT COMMUNICATE ONNETWORK A

APPL An Applications Processor has lost communications witha Real-Time Processor on Network A. Real-TimeProcessors regularly broadcast their status on both controlroom networks. All Graphics Processors will receive allReal-Time Processor broadcasts, even if the GraphicsProcessor and Real-Time Processor are in differentdomains. When a Graphics Processor ceases to receive abroadcasts from a Real-Time Processor on this network, itgenerates this alarm. This situation may be caused by anynumber of failures, such as a bad Ethernet card A in theApplications Processor, a bad cable, a bad Ethernet card Ain the Real-Time Processor, or a failed Real-TimeProcessor.

APPLICATIONS PROCESSOR SWITCHEDSERVERS

APPL The Applications Processor has either lost Control RoomNetwork communications with its current Real-TimeProcessor or has determined that a different Real-TimeProcessor in the same domain has a better data highwaystatus. This is a one shot alarm and does not persist.

AP CANNOT COMMUNICATE ONNETWORK B

APPL An Applications Processor has lost communications with aReal-Time Processor on Network B. Real-Time Processorsregularly broadcast their status on both control roomnetworks. All Graphics Processors will receive all Real-Time Processor broadcasts, even if the Graphics Processorand Real-Time Processor are in different domains. Whena Graphics Processor ceases to receive a broadcast from aReal-Time Processor on this network, it generates thisalarm. This situation may be caused by any number offailures, such as a bad Ethernet card B in the ApplicationsProcessor, a bad cable, a bad Ethernet card B in theReal-Time Processor, or a failed Real-Time Processor.





DPUAlarmSeverity

ReportingDevice

Description

BACKUP LINK CRC/FRAMEERROR NO NO 11 QUE There was a communications error (either a cyclicredundancy check failed, or there was a frame error) in thehigh-speed backup link between a backup pair of DPUs.

BACKUP LINK QUEUE OVERFLOW NO NO 13 QUE The inactive DPU of a backup pair is not keeping up withinformation coming over the backup link.

BACKUP LINK TIMEOUT NO NO 04 QUE The active DPU of a pair of backup DPUs is reporting thatthe inactive DPU didnt respond to a query within thetimeout period.

BATTERY #1 WEAK NO NO 02 IOP Battery #1 weak on DPU motherboard (model 555-2) orbattery weak for CMOS on the CPU board (models PSFand PDP).

BATTERY #2 WEAK NO NO 03 IOP Battery #2 weak on DPU motherboard. (model 555-2) orbattery pack weak on motherboard (models PSF and PDP).

BUFFER OVERFLOW DHWn One of the highway processor's communications buffers is not being emptied by the DBRT in the RTP. Willprobably require that the Real-Time Processor be reset.

BUFFER OVERFLOW YES NO 37 DHW The DPUs highway processors communications buffersare not being emptied by the CP. Will require that theDPU be reset.



III-5



DPUAlarmSeverity

ReportingDevice

Description

CAN'T COMMUNICATE WITH RTP VIANETWORK A

GP A Graphics Processor has lost communication with a Real-Time Processor on Network A. Real-Time Processorsregularly broadcast their status on both control roomnetworks. All Graphics Processors will receive all Real-Time Processor broadcasts, even if the Graphics Processorand Real-Time Processor are in different domains. Whena Graphics Processor ceases to receive a broadcast from aReal-Time Processor on this network, it generates thisalarm.This situation may be caused by any number offailures, such as a bad Ethernet card A in the GraphicsProcessor, a bad cable, a bad Ethernet card A in the Real-Time Processor, or a failed Real-Time Processor. Thisalarm will persist until either the problem is resolved or thenetwork database of the failed RTPs domain is purged. Refer to the Graphics Processor Operators Guide, Usingthe Real-Time Processor Selection Display, Clear Button.

CAN'T COMMUNICATE WITH RTP VIANETWORK B

GP A Graphics Processor has lost communication with a Real-Time Processor on Network B. Real-Time Processorsregularly broadcast their status on both control roomnetworks. All Graphics Processors will receive all Real-Time Processor broadcasts, even if the Graphics Processorand Real-Time Processor are in different domains. Whena Graphics Processor ceases to receive a broadcast from aReal-Time Processor on this network, it generates thisalarm. This situation may be caused by any number offailures, such as a bad Ethernet card B in the GraphicsProcessor, a bad cable, a bad Ethernet card B in the Real-Time Processor, or a failed Real-Time Processor.(continued on next page)





DPUAlarmSeverity

ReportingDevice

Description

CAN'T COMMUNICATE WITH RTP VIANETWORK B (continued from prior page)

This alarm will persist until either the problem is resolvedor the network database of the failed RTPs domain ispurged. Refer to the Graphics Processor OperatorsGuide, Using the Real-Time Processor SelectionDisplay, Clear Button

CANNOT ARBITRATE FOR SCSI BUS RTP The Real-Time Processor cannot request the use of theSCSI bus in order to communicate with its clients(Applications or Graphics Processors). This is most likelyto be a hardware fault such as a lose SCSI connector, adefective cable, etc.

CANNOT RE-SELECT SCSI INITIATOR RTP One of the Real-Time Processor's clients initiated a SCSItransaction; when the response was ready, the client wouldnot respond. This can be caused by either hardware,software, or a processor which is temporarily 'too busy'.

CMOS CLOCK VALUE IS INVALID YES NO 46 DHW During DPU startup, either the CMOS clock is notrunning, or the value of the year stored in the clock isbefore 1995.

CNTL LOG RESUMED nnn STATUS LOST RTP An overflow occurred in the memory buffer which storesstatus broadcast messages; thus, some messages have beenlost.

CONFIGURATION ROLLBACK RTP There was an error during the database installation phaseof Install; thus, this Real-Time Processor has rolled backto its previous configuration. The specific problem(s)which caused the rollback are detailed in a log file which isbuilt by the Configuration Builder during Install.

CONFIGURED HDI CARD(S) MISSING RTP During startup, this Real-Time Processor's database calledfor highway card(s) to be present which are not respondingto a startup request.



III-7



DPUAlarmSeverity

ReportingDevice

Description

CONTROLLER OR DPU RELOADING NO NO 09 IOP,SLOT,PFI

A reload of this DPU is currently underway.

CONTROLLER PROCESS ALARM LOGSUSPENDED

RTP Controller process alarm logging has been suspendedbecause of the overflow of the buffer containing thestatus broadcast messages.

COULD NOT OPEN THE EVENT DISKPARTITION

RTP There has been a failure of the hard disk partition inwhich the events are stored.

CPU FAILURE DHWn The highway processor's periodic diagnostic test of itsCPU detected a fault.

CPU FAILURE YES NO 48 DHW The highway processors periodic diagnostic test of itsCPU detected a fault.

CURRENT RTP IS NOT A PREFERREDSELECTION

APPL GP A Graphics or Applications Processor is currently usinga Real-Time Processor as a data server and that Real-Time Processor is not on its preferred server list. Thisalarm will persist until the station starts using apreferred Real-Time Processor as its current server.The switch to non-preferred server can happen either asa result of failure of all preferred servers, or manualswitch via the RTP Selection Display.

CURRENT YEAR IS OUT OF CONFIGUREDRANGE

RTP The time configuration file which has been producedand installed by the Configuration Builder is notcorrect; thus, this Real-Time Processor will roll backto its previous configuration. See the Install log filewhich is built by the Configuration Builder.

DAQD OR IOP DEADMAN TIMER TIMEDOUT

YES YES 18 IOP IOP timed out (periodic tasks not being scheduled).Millisecond interrupts have stopped.

DATA POINT RECEIVES IN LINKFAIL YES NO 25 IOP Data block receive in Linkfail condition; data is notbeing received by Data Block.

DEADMAN TIMER NOT REFRESHED DHWn This highway processor is reporting that its owndeadman timeout circuitry has not been refreshed.





DPUAlarmSeverity

ReportingDevice

Description

DH NEVER RECEIVED CP RESPONSE YES NO F0 DHW The highway CPU requested data from the CP in order torespond to a highway request; but, after a timeout period,the CP had not responded.

DMA TIMEOUT ON NETWORK SCSIOPERATION

RTP There is a fault in the SCSI bus of this WorkStation: aDMA operation was not completed within the requiredtimeout period. The most likely reason for this error is thatsome Graphics Processors in this WorkStation have thesame SCSI ID (look at CONFIG.INI in the \VUEsubdirectory to see). There may also be a hardware faultsuch as a lose SCSI connector, a defective SCSI cable, etc.

DPU BACKUP PAIR IS RUNNING ONSECONDARY

NO NO 07 SLOT In a DPU backup pair, the Secondary is currently active.After you determine that the Primary DPU is able to takecontrol, you can transfer control back via the pushbuttonon that DPU.

DPU EVENT QUEUE FLUSHED RTP The event queue of a DPU has been emptied; this eventwas received from that DPU.

DPU EVENT QUEUE OVERFLOWED RTP The event queue of a DPU has not been emptied fastenough by one or more Real-Time Processors; thus someolder events in the queue have been overwritten by newerevents, and the older ones will not be collected by thoseReal-Time Processors.

DPU FAILURE: ILLEGAL RETURN THRU 0 YES YES FE SLOT An internal failure has occurred in the DPU; this is a fatalerror.

DPU FAILURE: SRAM CHECKSUM ERROR YES YES FF SLOT There is a checksum error in the static RAM (the RAMwhich contains the operating system) of this DPU. This is afatal error (reported by model 555-2 only).

DPU IS OFFLINE NO NO 07 IOP The DPU is presently offline, so it is no longer updatingany process/control outputs. Check the state of the DPUkeylock and Interaction Page 9 to get the DPU backonline.



III-9



DPUAlarmSeverity

ReportingDevice

Description

DPU PROCESSOR FAN FAILURE NO NO 04 SLOT The cooling fan mounted on the CP of the PDP DPU hasfailed. Replace or repair the fan immediately to avoidoverheating.

DRAM CODE CHECKSUM ERROR YES YES FD SLOT The CP background diagnostics has detected an incorrectchecksum in the program logic stored in dynamic RAM(DRAM); the DPU will have to be reset.

DUPLICATE HIGHWAY STATIONNUMBERS

YES NO 46 DHW The highway processor received a message in which thehighway address of the sender was the same as its address.

DUPLICATE HIGHWAY STATIONNUMBERS

DHWn The highway processor received a message in which thehighway address of the sender was the same as its address.

ECC CORRECTED A ONE-BIT ERROR NO NO 11 DHW ECC logic detected and corrected a single-bit DRAM error(reported by model 555-2 only).

EVENT BARREL OVERFLOW RTP The event barrel of a Real-Time Processor has not beenemptied fast enough by its client Applications Processor;thus, some older events which had been stored in the barrelwill be lost.

EVENT DISK I/O ACCESS ERROR RTP This alarm indicates a problem occurred when the eventssubsystem tried to access the hard drive of the Real-TimeProcessor. If this alarm persists, then there might be aproblem with the hard drive.

EVENT QUEUE DATA LOSS QUE Event Queue overflow; dequeue rate is insufficient.EVENT QUEUE HAS BEEN RESET YES NO E2 QUE Event Queue reset.EVENTS BUFFER NEARLY FULL APPL The CURRENT volume is not mounted on the optical

drive, or the CURRENT volume is full and needs to beclosed out and replaced. The Event History buffer has beenstoring data and is nearly full.

EVENTS DATA LOSS EMINENT APPL Same as above message, but this is a second-level warningfor the Event History buffer.





DPUAlarmSeverity

ReportingDevice

Description

EVENTS DATA LOST APPL Same as above, but Event History data has now been lostand cannot be recovered.

ExCEL STACK CHECK ERROR NO NO 04 PFI As of the execution of a check command, the ExCELprocessor's stack was not empty (the check command teststhe state of the stack to permit debug of an ExCELprogram which is causing the alarm "User Stack no emptyat Restart" to be reported by PFI).

GENERIC SCSI I/O ERROR RTP There is a fault in the SCSI bus of this WorkStation. Thiscan be caused by either hardware, software, or a processorwhich is temporarily too busy.

GLOBAL IGAP COMPLETED HighwayComm

HWYn An IGAP (Initialize Go-Ahead Pointers) was completed onthis highway.

GP BECAME ACTIVE RTP The Real-Time Processor annunciates that the attachedGraphics Processor has become active.

GP HAS SWITCHED SERVERS APPL The Graphics Processor has either lost Control RoomNetwork communications with its current Real-TimeProcessor or has determined that a different Real-TimeProcessor in the same domain has a better data highwaystatus. This is a one shot alarm and does not persist.

HDI CARD(S) MISSING AND CARD(S)TIMEOUT

RTP An HDI card has failed during normal operation. This maybe a temporary condition due to this station's being IGAP'dout; if not, then the Real-Time Processor will have to bereset.

HIGHWAY STATION # DISCREPANCY NO NO 04 DHW This highway processor is reporting that the periodic checkof its highway address is failing.

HIGHWAY STATION # DISCREPANCY DHWn This highway processor is reporting that the periodic checkof its highway address is failing.



III-11



DPUAlarmSeverity

ReportingDevice

Description

HWYn TIMED OUT OR COMMUNICATIONCEASED

RTP This highway processor either stopped refreshing itsdeadman timer, or it failed to perform the periodichighway query issued by DBRT. Will probably require theReal-Time Processor to be reset.

I/O BUS ACCESS ERROR YES NO B0 PFI The DPUs programmed functions interpreter is unable tocommunicate with one or more modules on the I/O bus.

ILLEGAL ALGORITHM CODE YES NO 40 SLOT A control block contains an algorithm code which is notpart of the standard algorithm set.

ILLEGAL BUFFER POINTER VALUE YES NO 30 DHW The highway processor does a periodic check of the bufferpointers of its communication buffers; this alarm indicatesthat one or more pointers were outside the allowed range.Will require that the DPU be reset.

ILLEGAL BUFFER POINTER VALUE DHWn The highway processor does a periodic check of the bufferpointers of its communication buffers; this alarm indicatesthat one or more pointers were outside the allowed range.Will require the Real-Time Processor to be reset.

ILLEGAL OR NO APPLICATION OBJECT YES NO 17 PFI The application program area of the DPU is either emptybecause the DPU needs to be reloaded, or there is illegalobject code in that program area.

IOM CYCLE EXCEEDED 1 MSEC YES YES E8 QUE The IOM is unable to complete its scheduled processingeach millisecond. This condition occurs if either the IOMstops running or if it is configured with too many digitalterminal boards (16 in model PSF SFP, 25 in model PDP).

LOSS OF COMM WITH A GRAPHICSPROCESSOR

RTP This Real-Time Processor could no longer communicatewith one of its client Graphics Processors. The RTP'stimesync function generates this alarm if each GP does notperiodically issue time sync requests. This can be anEthernet communications problem, or a failure of aGraphics Processor. This is a one-shot alarm and does notpersist.





DPUAlarmSeverity

ReportingDevice

Description

LOSS OF COMM WITH AN APPLICATIONSPROC

RTP This Real-Time Processor could no longer communicatewith its client Applications Processor. The RTP's time syncfunction generates this alarm if the AP does notperiodically issue time sync requests. This can be anEthernet communications problem, or a failure of theApplications Processor. This is a one-shot alarm and doesnot persist.

maxSTATION LOST COMMWITH DBM ON NET A

OrmaxSTATION LOST COMMWITH DBM ON NET B

max-STATION

A maxSTATION has lost communications with a DBM onNetwork A or B. DBMs regularly broadcast their status onmaxNET Networks A and B. All maxSTATIONs willreceive all DBM broadcasts, even if the maxSTATIONand DBM are in different subsystems. When amaxSTATION ceases to receive a broadcast from a DBMon this network, it generates this alarm. This situation maybe caused by any number of failures, such as a badEthernet card A or B in the maxSTATION, a bad cable, abad Ethernet card A or B in the DBM, a failed DBM, or afailed frame switch or network hub.

MERGE COULD NOT READ Provider max-STATION

This alarm occurs when trying to connect to an alarmprovides (Alarm Summary or LSS).

MERGE RCV BAD ALARM FROM Provider(_DBM_ALM)

max-STATION

An error status was received from the provider, instead ofalarm data.

MERGE RCV BAD SBP STAT FROMProvider

max-STATION

This alarm occurs when connected to a provider, butunable to read alarm data.

MODEM JABBERHALT RELAYACTIVATED

YES NO 31 DHW The highway modem logic deactivated the relays whichconnect the modem's receiver/transmitter to the datahighway. This action will be taken if the highwayprocessor will not cease transmitting.



III-13



DPUAlarmSeverity

ReportingDevice

Description

MODEM JABBERHALT RELAYACTIVATED

DHWn The highway modem logic deactivated the relays whichconnect the modem's receiver/transmitter to the datahighway. This action will be taken if the highway processorwill not cease transmitting.

NO CLEAR-TO-SEND AFTERREQUEST-TO-SEND

NO NO 12 DHW The highway processor wanted to transmit, but its modemwould not activate CTS to permit transmission to begin.

NO CLEAR-TO-SEND AFTERREQUEST-TO-SEND

D

MaxDNA Alarm Messages

Documents

Transcript of MaxDNA Alarm Messages