LIB 500 Event List Operator s Manual

Transcription

1 1MRS MUM Issue date: Program revision: Documentation version: A LIB 500 Copyright 2000 ABB Substation Automation Oy All rights reserved. Notice 1 The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any error that may occur in this document. Notice 2 This document complies with the program revision v. 2.4 Notice 3 Additional information such as Release Notes and Last Minute Remarks can be found in the program distribution media. Trademarks Microsoft is a registered trademark of Microsoft Corporation. Windows NT is a trademark of Microsoft Corporation. LONWORKS is registered trademark of Echelon Corporation. Other brand or product names are trademarks or registered trademarks of their respective holders. All Microsoft products referenced in this document are either trademarks or registered trademarks of Microsoft Corporation.

2

3 1MRS MUM LIB 500 Contents Page Purpose and Description Features/Options System Requirements Events Event Functions Event Activation General Description Events Event Logging Event Viewing and Listing Event Handling Comments Event Reports Access to Basic View Tools Menu Toolbar Screen Display Default Event Text Event Text Layout Changing Event Texts Layout Scrolling Updating ABB Automation 3

4 LIB 500 1MRS MUM 4.9 Settings Settings Dialog Filters Comments Accessing the Comment Dialog Event Reports Starting the Print Event Reports Function User Authorization Searching Procedure Reading Events from HDB Files ABB Automation

5 1MRS MUM LIB Purpose and Description The purpose with the is to provide the user with information about events occurring in the system. Thus the user can make the right decisions and verify that taken measures are successfully performed. It is also possible to receive information about activities carried out by other users, operations of objects, acknowledging of alarms, editing of limit values, logging in etc. The presents the data in a structured way, for the convenience of the user. Each event is normally presented by displaying an event text line which describes the cause of the event in the process. Event text lines normally consist of a time stamp, object identification, a signal text and a text indicating the status. 1.2 Features/Options layout can be configured. There can be even more than 80 characters per line Printouts can also be configured to contain more than the standard 80 characters per line Scroll interval configurable from 10 pages to 100 pages. in steps of 10. Fast navigation in the list by using; jump to the last page, one page back or forward, or one interval backwards by using the scrollbar Possibility to navigate to previous day/next day or to day typed into input dialog User-friendly filters Updating/Frozen presentation modes Authorization support Help in all dialogs Additional comments can be given to the events, upto 250 characters per event Event Reports to printer on demand Possibility to display events either in log- or event order ABB Automation 5

6 LIB MRS MUM Figure 1., main view 1.3 System Requirements MicroSCADA Backbone of LIB ABB Automation

7 1MRS MUM LIB Events 2 Events Event is a wide term that also comprises alarm. The event activation and consequential actions are defined in the process database separately for each individual object. Typical examples of events are: Change or updating of an object value Change of alarm and warning state Change of reliability stamp Change of the alarm definition, alarm blocking, acknowledgement etc. When an event occurs in the system, the operator wants to receive an answer to the following questions (answers provided below each question). 1. What did happen? Change of the state of the object or an executed operation. 2. Where did it happen? A descriptive text (object identification, OI and object text, OX) comprising e.g. a device notation and the type of object or operation. 3. When did it happen? The point of time when the event occurred. If the event originates from a station providing a time stamp, this time stamp is used. Depending on the station, the time is on second or millisecond level. In other cases, the time stamp is the MicroSCADA system time with an accuracy of 10 milliseconds. 2.1 Event Functions The following functions can be activated by an event: Updating monitor pictures Automatic printout. Like alarms, events can cause automatic printouts on the event and alarm printer Registration is made in the history buffer, and in connection to this also in the Activation in the report database, e.g. automatic control operations, registration, report printout, etc. ABB Automation 7

8 LIB Events 1MRS MUM 2.2 Event Activation Depending on how crucial an object is, the following events in the object may activate an event printout, a registration in the history buffer, or an activity in the report database (from the least to the most crucial object): No activation. An alarm is activated and deactivated. The alarm or warning state changes The object value changes. The object value is updated, although it is not changed. 8 ABB Automation

9 1MRS MUM LIB General Description 3 General Description 3.1 Events This chapter explains the event logging functions and displays. When using the term event handing, attention is normally focused on the. The MicroSCADA system does not only focus on the. Event handling also comprises the event logging, the paper printouts from the event printer. Event handling is divided into two main groups: Event logging Event viewing The event presentation is divided into subgroups such as: Viewing events on display () Sequential listing to the printer Events are the activities that are registered by the MicroSCADA base system in the history database, HDB. There are two types of events; process events and internal events. The process events are events that belong to the supervised process such as indications, protecting events, alarm limits for measurements, tripped breakers, etc. Internal events are normally initialized by the system. The internal events are events that indicate disturbances in the supervision system. When an event occurs in the system then it is instantly printed on the event printer and stored in the history archive. The history archive is used when the is produced on the screen. The archive contains all dynamic information related to the event. All dynamic data from the history archive can be used to define filters. The history archive consists of the computers RAM and of the HDB files stored on the PC hard disk. The history database consists of history database files each containing events of one day. The files are named according to the date as APL_yymmdd.PHD, for example file APL_ PHD contains the events logged on 15-Jan The files are stored in the directory C:/SC/APL/nnn/APL_, where nnn is the name of the application. 3.2 Event Logging All activities in the supervised processes that are logged by the Base system are stored in the process database. The process database handles all registration of incoming and outgoing process data. The process database is located in the application; it is project specific but the main functions remain the same, regardless of the application. The events that are logged by the Base system and the database are stored on a mass storage (the hard disk). In other words, the Base system creates files on the hard disk where the events are stored. Every time when an event occurs in the system, the program writes a new item in the HDB. The item in the HDB is a snap-shot of the situation for the object in question when the event occurred. All dynamic data from the actual process point is stored in the HDB. ABB Automation 9

10 LIB General Description 1MRS MUM 3.3 Event Viewing and Listing The events can be viewed on the display by using the. The default display format of the is similar to the format for the sequential printouts. The user can define different filters to display specific events or additional information about the events. The can contain more information than the sequential printout. The sequential printouts to the event printer are sent to the event printer by the Base system instantly after the event has occurred in the application. The filters do not affect the sequential printouts. 3.4 Event Handling The event handling is based on the information in the HDB. In other words, the information displayed in the comes from the HDB. When the is displayed on the screen, files in the HDB on the hard disk are read and the content is organized into a chronological order. After the content has been organized, the events are displayed on the screen by using the format picture. The format picture retrieves the status text from a language dependent text file. The default language is English. The files are translated into local languages by the project engineer during the engineering. The Text translation Tool is used for the translation of the text files. 3.5 Comments Comments can be used for making remarks to events. The comments are available to all users and can give additional information. Comments can also be removed. 3.6 Event Reports The event reporting function is used for printing of events to a printer on demand. The user can select whether to print the event report with or without comments. 10 ABB Automation

11 1MRS MUM LIB 500 After the LIB 500 Base has been installed and prepared according to the instructions, the can be used in the process pictures. The functional description chapter will take the presentation of the events both on the display and on the printers into account. 4.1 Access to There are two ways of accessing the : Either by 1) using the shortcut button Reports menu: or by 2) selecting the in the Figure 2. Starting the from the Reports menu or by the dedicated button To be able to access the by clicking the shortcut button, the button has to activated first. To activate the shortcut button, copy bgu_events.pic from the library package lib4/base/event/use under the application uplmod4/use. When clicking the shortcut button, the picture is opened from the application (not from the library). The can be divided into three parts: Basic view (described in section 4.2) Tool menu (described in section 4.3) Toolbar (described in section 4.4) ABB Automation 11

12 LIB 500 1MRS MUM 4.2 Basic View Figure 3. The basic view of the Explanations to Figure 3: 1. Toolbar (can also be shown/not shown) 2. Tools menu 3. Date stamp for events presented on current page 4. Date from the first event to the last event that can be accessed by the scrollbar functions (13-15) and Previous Interval button 5. Actual page and total amount of pages 6. Line with event specific data 7. Object status symbol 8. Indication that the event also has caused an alarm 9. Comment marker, showing that there are additional remarks for the event 10. Settings information, used filters 12 ABB Automation

13 1MRS MUM LIB Settings information, mode for 12. Settings information, amount of pages loaded when scrolling 13. Settings information, time scroll 14. Scroll arrows for events, downwards 15. Scrollbox for scrolling events 16. Scroll arrow for events, upwards 4.3 Tools Menu Figure 4. The tool menu with the drop down menus The tool menu for the is available when the is active (shown on the screen). In order to make handling more efficient and convenient, the LIB 500 provides a set of tools. As the LIB 500 standard, tools are opened from the Tools drop down menu of the picture header bar. Items ending in three dots open a subdialog and those ending in a symbol > open a cascade menu or a submenu. The provides also a Toolbar as an alternative for the drop down menu. The toolbar does not contain all functions that can be found in the pull down menu The toolbar should be considered as a short-cut to the most used functions. ABB Automation 13

14 LIB 500 1MRS MUM Table 1 The options in the Tools menu: Tools Filters Settings Presentation Mode Comments Event Reports Go to Scroll Page Show Toolbar Help Description Opens a dialog where filters can be selected and edited Opens a dialog where event list texts and color settings can be changed Opens a dialog where the user can toggle between updating mode and frozen mode A dialog for adding or removing comments to events Printing of events on demand Opens a dialog where the user can: go to the latest events go to the end of the previous interval go to previous day go to next day go to day selected in a dialog Scrolls one page up or down Displays/hides the toolbar Opens the LIB 500 help dialog with general help 4.4 Toolbar The toolbar is a shortcut that can be used in parallel with the drop down menu. Figure 5. The toolbar The buttons in Figure 5 are: 1. Filters Settings 3. Presentation Mode (Updating or Frozen) 4. Comments 5. Event Report 6. Go to last events 7. Scroll one page up 8. Scroll one page down 9. Go to previous day 10. Go to selected day 14 ABB Automation

15 1MRS MUM LIB Go to next day 12. Go to previous interval 13. Help 4.5 Screen Display The information presented on the screen consists of several elements, which will be described in the following sections Default Event Text The default event text that describes the event consists of (see Table 2). a) status sign b) time stamp c) object identification d) signal name e) status text The status text is connected to the object value. Furthermore, the status text is event or customer specific. The most important task that the event text has is to give the operator information about the event. The supports a standard layout, which is designed to meet the demands of the normal event display. The standard layout is similar in the as well as for the sequential printouts. Table 2 The following is an example of the standard event text in the default layout: * yy:mm:dd hh:mm:ss:mss Object Id Signal Name Status :01: Green Bay F01-CB :01: Green Bay F01-CB :01: Green Bay F01-CB :01: Green Bay L1 * :01: Green Bay L1 Breaker Operation Breaker Operation Breaker Indication Current Measurement Current Measurement Open Execute Open Warning Alarm Explanations to Table 2: By default, the first column starts from the position 1 and the length is 1 character. The column presents the object status for the object in question. In version 2.4 and newer it is possible to configure the first column to be 2 characters wide including alarm indicator and status symbol. See further information in the LIB 500 Base Configuration Manual (1MRS MEN), Configuration Manual. ABB Automation 15

16 LIB 500 1MRS MUM The second column starts from the position 2 and the length is 21 characters. This column presents the time stamp of the event. The third column starts from the position 26 and the length is 20 characters. The column presents the object identification (OI). The length of the text is 30 characters. In version 2.4 it is possible to divide OI column to up to five columns. See further information in the LIB 500 Base Configuration Manual (1MRS MEN), Configuration Manual. The fourth column starts from the position 47 and the length is 20 characters. The column presents the object text (OX). The length of the text is 30 characters. The fifth column starts from the position 68 and the length is 13 characters. The column presents the status text. The default event text always gives an answer to the questions (What?, When? and Where?) described in section 1.2 About events. Thus, the event texts contain these basic data both on the screen and on the sequential event printouts. The event text will be the same in the and on the sequential event printers. Filters that are used in the presentation do not limit the normal printouts to the printer. The default event text will always fit on the display and on the paper printouts Event Text Layout See Settings/Common Columns and Event Columns folder how to change layout. However, different users do not pay attention to same kind of information. In some applications there is a need to change or to extend the event text. When extending the event text there may be some limitations that need to be taken into account. In some cases, the limitation can be the width of the matrix printer that is used as the event printer. The printing width is normally 80 characters and it is impossible to print more information. Then the alternative is to leave out some of the basic information. The event text layout can be configured according to the different needs of different applications or countries. The user can configure the event display to view information other than the default. The event text can be changed back to the default any time by using the Settings dialog. The additional information is displayed on the same line as the basic information as columns. The event text layout can be configured to allow displaying more information on the screen than what is listed to the event printer. The event text consists of two parts: common part and event specific part. Common part Event specific part Figure 6. A typical event line in the can be divided into two parts 16 ABB Automation

17 1MRS MUM LIB 500 The common part of the event text contains data that the user wants to display on all event views. The configuration of the common part can be changed in the Settings dialog box/common Columns folder. The event specific data is all data that is not common to other events. The event specific data consists of two parts, the status text and additional data. The status text displays the object status (Open, Close, Warning, Alarm etc.). The additional data is determined by the event. The additional data can be any attribute that is stored in the history buffer and the HDB. The event specific part and the header can be configured by the user. If the additional data is the same for all events, it can be written as a label text common to all columns. The following example shows a list with additional data, in this case the attributes RA (Event Number of Starting Event) and RB (Relative Time). At present, the RA and RB attributes are used only in the RP 571 protocol. The event specific data can be configured in the Settings dialog box/event Columns folder. Table 3 Event text when using one line (Note! Smaller font size): * Date Time Object Id Signal Name Status :01: Green Bay Dist Anr L1 Activated :01: Green Bay Dist Aus-Kom :01: Green Bay L1 Current Measurement Warning * :01: Green Bay L1 Current Measurement Alarm :01: Green Bay Dist Fehlesort km :01: Green Bay Dist Reaktanz ohm :01: Green Bay Dist Widerstand ohm :01: Green Bay Dist Anr L1 Deactivated :01: Green Bay F01- CB :01: Green Bay F01- CB :01: Green Bay F01- CB1 Breaker Operation Breaker Operation Breaker Indication Open Execute Open Explanations to Table 3: The first four columns belong to the common part of the event text: The first column starts from the position 1 and the length is 1 character. The column presents the alarm state of the event. The alarm indicator is configurable. The second column starts from the position 2 and the length is 23 characters. This column presents the time stamp of the event. The third column starts from the position 26 and the length is 20 characters. The column presents the object identification (OI). The text length is configurable up to 30 characters. ABB Automation 17

18 LIB 500 1MRS MUM The fourth column starts from the position 47 and the length is 20 characters. The column presents the object text (OX). The text length is configurable up to 30 characters. The last columns belong to event specific part of the event text: The fifth column starts from the position 68 and the length is 13 characters. The column presents the status text Changing Event Texts Events stored in the History Database cannot be changed. Event texts can be changed in the process database. The changes affect the new events. The texts can be edited using following tools: A) Object Navigator B) Standard Configuration Tool Event specific texts can be configured in form pictures and corresponding text files. Changes made to form picture files affect all concerned events that are displayed in. See further information in LIB 500 Base Configuration Manual (1MRS MEN), Configuration Manual. 4.6 Layout The is designed to be easy to understand and easy to use; the layout is clear and consistent. There are four types of navigation objects in the : a scroll box, the scroll arrows, the drop-down menus and the toolbar buttons. 18 ABB Automation

19 1MRS MUM LIB 500 Figure 7. An example of the layout 4.7 Scrolling Normally, the amount of events exceeds the amount that can be shown on one page. To enable navigation in the list, a scrolling function is needed. The list is divided into scroll intervals. A full scroll interval is the amount of events that are referenced from the history archive. The scroll intervals are configurable from 10 pages to 100 pages in steps of 10. The scroll bar (1 and 2) located on the right hand side, scrolls the list within the interval. Navigation in the list is carried out according to the following conventions (Figure 7); scroll box (2) within an interval scroll arrows (1) one line up/down (repositions all events one line up or down in the list without clearing the whole presentation window) scroll to last page ( home ) (3) scroll one page up (4) scroll one page down (5) ABB Automation 19

20 LIB 500 1MRS MUM scroll to previous day (6) scroll to day typed in the input box (7). Current day is given as default. If interval time limit is more than one day, input day is considered to be the last day of the interval. For example, if interval time limit is 3 days, and 17. March 1999 is given as input, events of March 1999 are included in the interval. scroll to next day (8) scroll to next/previous interval (9) Navigating between days equals to moving the time window forward or backwards when the interval time limit is more than one day. It is not possible to navigate to days past current day. 4.8 Updating If the is in the updating mode, the list will be updated when a new event occurs in the system. When the list is in the frozen mode (non-updating), a message is displayed that informs the user to proceed to the last events and change the mode into updating mode. When the is in the updating mode, 1/2 page is shown when the list is presented on the screen and all new events are presented on the remaining 1/2 page until the page is full. When the page is full it scrolls the page with 1/2 page and after that the new events will fill the page again. The update is not automatic when: 1. the user has scrolled the list and the focus is not on the latest events 2. the user has chosen the frozen mode 3. the time filters are active. In the cases mentioned above the displays a message to the user about new events in the system. After this the user may proceed to the Last Events. If time filters are on, the user is informed to reset the filters before changing to updating mode. 4.9 Settings Settings Dialog To use Settings, the authorisation level Control is required. The settings dialog is used when customizing the list. It is possible to change a large number of parameters in the list. The parameters can be grouped into several subgroups. The different subgroups are grouped into folder sheets. The folder sheets that are available are General and Common Columns. 20 ABB Automation

21 1MRS MUM LIB 500 The OK, Apply, Cancel and Help buttons are common for the different folders sheets. Table 4 The buttons function as follows: Button OK Apply Cancel Help Function Applies all pending changes and closes the dialog window Applies all pending changes but leaves the dialog window open. Discards all pending changes and closes the dialog window. Does not cancel or undo changes that have already been applied. Opens the help window General Folder Figure 8. Setting general settings ABB Automation 21

22 LIB 500 1MRS MUM Table 5 The General folder contains the following setting parameters: Setting Interval time limit Interval Length Time Out Scroll Order Day Break Toolbar Event Text Color Event Text Font Default Settings Explanation Interval time limit is the count of days that will be included in one interval. Interval length is the length in pages that will be presented when the list is opened. The interval length can have the following values pages. Time out is the maximum time for reading an interval. Sorting order of the events in Frozen mode. Define if a dotted line will be presented between events that have time stamps from different days. Define if the Toolbar will be presented when the list is opened. Define the color for the event text. Define the font for the event text. Default Settings load the default settings for the General settings. Interval time limit defines the count of days whose events are included in the interval. The interval length limit prevents the vertical scroll bar to become unusable due to large amount of events and reduce query times when counting the events of the interval. When the is in updating mode, events are sorted in order which they were written into history database, i.e. logging order. In frozen mode, order defined in Settings dialog is applied. The following settings can be selected in Scroll Order combo-popdown: LOG EVENT Events are sorted in logging order in Frozen mode Events are sorted in event time order in Frozen mode Common Columns Folder Figure 9. Setting Common Columns 22 ABB Automation

23 1MRS MUM LIB 500 The common part contains data that the user wants to display in all event rows. Table 6 The Common Columns folder contains the following setting parameters: Setting Number of Columns Column Attribute Column Label Start Position Length Default Settings Explanation Define the maximum number of columns that can be used in the event text row. The number of Columns can have the values Column number that is being edited at the moment. Define the attribute that will be presented in the current column. Define the label for the column. The text value is a free text string. The label will be printed as a label for the column. Define the start position for the column in question. The start position can be picked from a list. It is also possible to enter the value from the keyboard. Define the length for the column in question. The length can be picked from a list. It is also possible to enter the value from the keyboard. This button loads the default settings for the Common Columns settings. Event Columns Folder Figure 10. Setting Event Columns The event part contains data that the user wants to display as status for the events. ABB Automation 23

24 LIB 500 1MRS MUM Table 7 The Event Columns folder contains the following setting parameters: Setting Number of Columns Column Attribute Column Label Start Position Length Default Settings Explanation Define the maximum number of columns that can be used in the event text row. The number of used columns is NOT editable in the current version. Column number that is being edited at the moment. Define the attribute that will be presented in the current column. The attribute is NOT editable in the current version. Define the label for the column. The text value is a free text string. The label will be printed as a label for the column. Define the start position for the column in question. The start position can be picked from a list. It is also possible to enter the value from the keyboard. Define the length for the column in question. The length can be picked from a list. It is also possible to enter the value from the keyboard. If the length is defined to be zero (0), the length will be equal to the length of the text that will be presented in the column. This button loads the default settings for the Common Columns settings Filters Filters are used when the user wants to display or concentrate on specific information. Filters are activated from a subdialog in the list. The dialog contains standard filters that can be selected by the user. The filter dialog provides at least the following standard filters; all events, event time, per station, per feeder, per object. It is possible to change existing filters or add new filters that can be stored and reused by other operators. The filter dialog contains a specification form where the user can create or change existing filters. For more details about setting filters, please see the LIB 500 Base Configuration Manual (1MRS MEN), Alarm List and LIB 500 Base (1MRS MUM), Alarm List. The setting principals and functions are common for the Event and Alarm List, and therefore, they are described only once Comments The Comments function enables adding, reading and removing of additional comments to the events. These event specific comments are saved into history database with the event data. These comments can be read by all readers by opening the comment dialog. A dialog box, see figure 13, is then presenting the comment. The comments can also be printed, refer to the Event Reports section for details Accessing the Comment Dialog 1) By clicking on the Comments button in the toolbar or 2) by selecting Comments from the Tools menu and then clicking on an event line with or without 24 ABB Automation

25 1MRS MUM LIB 500 comment marker, the Comments dialog is opened. In Figure 3 events with comment markers are shown. Figure 11. The Comments dialog Button/field Remove comment Comment text: OK Cancel Help Function Removes the comments from the Comment Text: field The field where to add and read comments Closes the dialog and accepts changes Discards all changes and closes the dialog window. Opens the help window Adding a Comment Open the Comments dialog as described earlier in Accessing the Comments dialog. Point at the event to which the comment is to be added. Then when an event is selected, the Comments dialog appears. Write the comment to dialog and press OK. Comment lines are preserved as typed. Press Enter after each line. If no comment text given, no comment mark is displayed in the. Reading and Changing a Comment Open the Comments dialog as described earlier in Accessing the Comments dialog. Select the event for which the comment is to be read or changed, (it is then assumed that this event already is equipped with a comment marker). Removing a Comment Open the Comments dialog as described earlier in Accessing the Comments dialog. To remove the comment, open the comment dialog and press Remove Comment button. ABB Automation 25

26 LIB 500 1MRS MUM Used Format for Comments The comment text is saved as TEXT data type in the EX attribute of the event with a length of 255 characters separated ASCII 10 (new_line). Event data is saved in History Database (HDB) Event Reports The Print Event Reports dialog prints the currently listed events to the matrix printer, that is configured as a transparent printer in MicroSCADA. The whole or a selected page/-s can be printed. The printout contains the same data as the. Comments can also be included Starting the Print Event Reports Function The Print Event Reports function is started either from 1) the Event Reports button in the toolbar or 2) from the Tools menu and selecting Event Report... (see Figure 4). Figure 12. The Print Event Reports dialog Button/field To Print Comments Page Range OK Cancel Help Function Select printer Prints eventual comments Select to print the full venet list with all pages or selected pages, (from to range) The first and last pages are given as a default, but the desired pages can be entered into the fields. Performs the printing Discards all changes and closes the dialog window without printing Opens the help window Transparent printers found in the printer mapping vector of the current application can be selected from the combo box in the upper left part of the dialog. Please note, that if 26 ABB Automation

27 1MRS MUM LIB 500 no transparent printers are found, the OK button of the dialog is not available and the events cannot be printed User Authorization The default authorization group for the is Event_Handling. Table 8 The authorization group consists of the following three levels: Auth. level (min.) Engineering (2) Control (1) View (0) Operations allowed Editing station and bay lists of the filters Select filters All other operations 4.14 Searching Procedure Reading Events from HDB Files All the events that are inside the history time limit (defined in Settings dialog) are read into the list until the history length limit is reached. When history length limit has been exceeded, the reading of the events is stopped and the Previous interval button is activated. If the interval is full when new event occurs, the oldest event of the interval is moved to the previous interval. ABB Automation 27

28

29 1MRS MUM LIB 500 Index Page A B C D E F G H Activation...7 alarm state...17 authorization group...27 basic view...12 cascade menu...13 comments...10, 24, 25 Common Columns...22 common part...16 configuration...17 Control (1)...27 default event text...15, 16 Engineering (2)...27 event activation...8 Event Columns...23 event handling...9, 10 event line...16 event logging functions...9 event presentation...9 event reporting...10 Event Reports dialog...26 event specific part...16 event text layout...16 event text line...5 filters...10, 24 folder sheets...20 frozen mode...20, 22 General folder...22 history archive...9 history database...9, 22, 24, 26 ABB Automation

30 LIB 500 1MRS MUM I L N O P R S T U V internal events... 9 interval length limit interval time limit layout... 5, 18 navigation... 5, 19 navigation objects object identification... 16, 17 object status... 15, 17 object text... 16, 18 parameters printouts... 5, 7, 10 process database... 9 process events... 9 Registration... 7 Remove Comment scroll interval... 5, 19 scrolling sequential printouts setting parameters settings standard filters Starting the...11 status text... 15, 16, 17, 18 subdialog submenu time filters time stamp... 16, 17 Transparent printers updating mode... 20, 22 View (0) ABB Automation