Documentos de Académico
Documentos de Profesional
Documentos de Cultura
278589
Introduction ................................................................................................................................................................. 1-3 Overview ................................................................................................................................................................... 1-3 Understanding Atomic Blocks and Buffers ....................................................................................................... 1-3 Configuring Atomic Blocks and Buffers ........................................................................................................... 1-3 Using maxDPUTools ......................................................................................................................................... 1-3 Using the Graphical Configurator...................................................................................................................... 1-4 Atomic block Categories ....................................................................................................................................... 1-5 Atomic block/Buffer Overview by Category ......................................................................................................... 1-6 Alarm Tag Atomic Blocks ................................................................................................................................. 1-6 Analog Math Function ....................................................................................................................................... 1-7 Buffers ............................................................................................................................................................... 1-7 Modulating Control Logic ................................................................................................................................. 1-7 Discrete Logic .................................................................................................................................................... 1-7 Grouping Atomic Blocks ................................................................................................................................... 1-8 State Logic ......................................................................................................................................................... 1-8 Steam Compensation ......................................................................................................................................... 1-8 Understanding Attributes ....................................................................................................................................... 1-8 Attribute Categories ........................................................................................................................................... 1-8 Using Referencing to Interconnect Controls ........................................................................................................ 1-10 Referencing by Attribute Category .................................................................................................................. 1-10 Reference Subscriptions .................................................................................................................................. 1-10 Reference Syntax ............................................................................................................................................. 1-11 Understanding Data Types................................................................................................................................... 1-12 Boolean ............................................................................................................................................................ 1-12 Integer .............................................................................................................................................................. 1-12 Enumerated ...................................................................................................................................................... 1-13 Float ................................................................................................................................................................. 1-13 String ............................................................................................................................................................... 1-13 Absolute Time ................................................................................................................................................. 1-13 Relative Time................................................................................................................................................... 1-13 Commands ........................................................................................................................................................... 1-13 COMMAND function blocks .......................................................................................................................... 1-14 Edge Trigger function block command outputs ............................................................................................... 1-14 Complex Data Type ............................................................................................................................................. 1-14 Standard Complex Data ................................................................................................................................... 1-14 Forceback......................................................................................................................................................... 1-14 Incremental Control Data................................................................................................................................. 1-14 Family Ties ...................................................................................................................................................... 1-15 Using Buffers to Define Hardware ...................................................................................................................... 1-15 I/O Addressing ................................................................................................................................................. 1-16 Creating or Editing the I/O Inventory .............................................................................................................. 1-16 I/O Module Types and Associated Signals .......................................................................................................... 1-16 Digital Input Modules ...................................................................................................................................... 1-16 Digital Output Modules ................................................................................................................................... 1-17 High Level Analog Input Modules .................................................................................................................. 1-17 Thermocouple/Millivolt Analog Input Module ............................................................................................... 1-17 Resistance Temperature Detector (RTD) Input Module .................................................................................. 1-17 Analog Output Modules................................................................................................................................... 1-17 Four-channel Position Adjusting Type (PAT) ................................................................................................. 1-18 Counter/Timer (Pulse) Module ........................................................................................................................ 1-18 Positioning Modules ........................................................................................................................................ 1-18 HART capable Modules .................................................................................................................................. 1-18 Using Buffers to Create Simulated I/O Environment .......................................................................................... 1-19 Using Hierarchical Groups .................................................................................................................................. 1-19 Copying and Pasting Groups ........................................................................................................................... 1-20
Metso Automation
1- 1
278589
Group Attributes .............................................................................................................................................. 1-20 Setting Atomic block and Group Execution Rates and Priorities ........................................................................ 1-20 Selecting Execution Rate ................................................................................................................................. 1-21 Selecting Execution Priority ............................................................................................................................ 1-21 Executing Blocks Using Priority Order ........................................................................................................... 1-22 Executing Blocks Using Hierarchical Order .................................................................................................... 1-23 Using Hierarchical Scheduling with Absolute Priorities ................................................................................. 1-24 Using the DpuAtomList Utility ....................................................................................................................... 1-25 Using Custom blocks To Create Custom Applications........................................................................................ 1-26 Understanding Standard Objects ......................................................................................................................... 1-26 Objects That Monitor Functions ...................................................................................................................... 1-27 DPU Battery Related Object (DPU4E Only) ................................................................................................... 1-27 DPU Fan Related Object (DPU4E Only) ......................................................................................................... 1-28 Alarm Related Objects ..................................................................................................................................... 1-29 Security Related Objects .................................................................................................................................. 1-29 _timesync Object ............................................................................................................................................. 1-29 SBPLimit Object.............................................................................................................................................. 1-29 Using Alarm-Related Atomic Blocks and Buffers to Configure Alarming ......................................................... 1-35 Buffer Alarming............................................................................................................................................... 1-35 Viewing Alarms in a maxSTATION ............................................................................................................... 1-36 Base Attributes .................................................................................................................................................... 1-36 Table 1-5. Common Abbreviations Used in Attribute Tables ......................................................................... 1-38
Metso Automation
1- 2
278589
Introduction
Overview
Understanding Atomic Blocks and Buffers
This reference guide provides descriptions for more than 60 atomic blocks and buffers available with maxDPU based systems. Use atomic blocks and buffers to create point databases implementing specific process control strategy. Use atomic blocks for control and data acquisition. Use buffers to define the I/O inventory and specify signal conditioning and linearizations or create a simulation database. An atomic block is a software object that encapsulates specific engineering functionality, such as a PID, an Auto/Manual toggle switch, or an AND gate. Atomic Blocks are normally grouped into larger objects to encapsulate increased functionality. Groups of atomic blocks constitute a custom function block object. Custom function blocks can be applied in hierarchical levels (HID levels) to form increasing levels of control system functionality. These HID levels can then be assigned to a particular DPU. Atomic Blocks, buffers, and custom function blocks are part of a DPMS (Distributed Point Management System), a Microsoft Access-style database and client/server that composes a Distributed Processing Unit (DPU). The DPMS manages its point database, provides master scheduling, and executes the objects composing its database, among its various functions. A large process control application may be composed of multiple DPMS residing in as many DPUs.
Using maxDPUTools
Use maxDPUTools to: Create one or more configurations consisting of points and buffers Install the configuration(s) and load them into their respective DPUs
Metso Automation
1- 3
278589
Use maxDPUTools to install an entire configuration at one time (full installation) or to install any part of the configuration down to a single atomic block, an incremental installation. See Publication 278595, maxDPUTools User's Guide.
A point configuration, represented graphically, consists of diagrams representing all or portions of groups associated with a selected configuration. Groups are drawn on A size (8.5 in x 10 in) (21.6 cm x 25.4 cm) or B size (11 in x 17 in) (27.9 cm x 43.2 cm) sheets, which can be printed on any default printer accommodating these two paper formats. Logic diagrams appearing on sheets consist of a collection of boxes representing atomic blocks or custom blocks. In a point configuration, atomic blocks and custom block elements are connected or wired to attributes associated with other controls (atomic blocks, groups, custom blocks) using reference pointers. To show referencing graphically, logic diagrams show interconnecting lines entering and leaving boxes. Lines entering a box on the left are inputs and lines leaving a box on the right are outputs. An output emerging from one control may become another control's input. You may use the Graphical Configurator to make online changes to a configuration as you experiment with new wiring schemes. As you rearrange the objects, add, delete or otherwise change wiring, their positions are stored back into the DPMS. You may also make changes to the DPMS point configurations. Select individual controls, such as atomic blocks, groups, and elements within custom blocks to change attribute values. Other configurator tools let you add and delete atomic blocks and groups in a configuration on line. These become permanent parts of the online DPMS but are not part of the offline database unless uploaded. To retain any online edits or organization changes, the DPMS must be uploaded to the offline database using maxDPUTools or the next install will return the DPMS to its unorganized state. The current release of Graphical Configurator cannot be used to:
Metso Automation
1- 4
278589
In addition to these eight general categories, the analog math functions, modulating control logic and discrete logic categories contain subcategories. The following table lists atomic blocks by categories and subcategories.
Metso Automation
1- 5
278589
Metso Automation
1- 6
278589
Use the Analog Tagger (ATAG) atomic block to assign a tagname, scaling, alarming, and value forcing capability to any analog point, and use the Digital Tagger atomic block to apply similar capabilities to digital points. These atomic blocks are typically used to assign tagnames and alarming capabilities to individual signals entering buffers and to points related to PID-related atomic blocks. See Chapter 3, "Atomic block Category: Buffers," and Chapter 4, "Atomic block Category: Modulating Control Logic." Chapter 7 discusses key features of each atomic block, such as value forcing using the Mode and ForcedVal parameters, configuring a snooze alarm, creating custom alarm text, and other features. Parameters included with this atomic block allow you to assign a tagname to a point, set alarm and range high and low limits, range clamping, and various alarm behaviors.
Buffers
Use buffers to define the I/O inventory and specify signal conditioning and linearizations. Most currently available I/O modules are represented by an associated buffer type. See also, "Using Buffers to Define Hardware."
Discrete Logic
This chapter defines six sets of general purpose discrete logic atomic blocks and two special purpose atomic blocks. Most of these atomic
Metso Automation
1- 7
278589
blocks use boolean parameters that are set to true or false to derive the expected results. See Chapter 5.
State Logic
This consists of atomic blocks that provide controls for on/off devices and sequence operation.
Steam Compensation
This consists of atomic blocks that provide steam property values or apply steam properties for process measurement compensations. (The flow compensation atomic blocks also provide compensation for air and gas flows.)
Understanding Attributes
The data stored in an atomic block is organized as a set of attributes. For each atomic block and buffer, this reference guide presents a collection of tables listing attributes. Tables are organized by various attribute categories, such as inputs, output, parameters, and so forth. See next section. The tabular detail shows three informational columns, listing the name of each attribute, data types associated with each attribute, and a brief description of the attribute. All atomic blocks have some attributes in common. All attributes have subattributes. Subattributes include category, description, reference, and several others. Some of the others are attrwriteable, attrreadable attrminval etc.
Attribute Categories
Attributes may be divided into the following categories: General Inputs Parameters All atomic blocks have required foundation attributes. Inputs are values that are usually obtained by referencing another attribute. Parameters are similar to inputs except it is expected that referencing other attributes is unlikely and that the local
Metso Automation
1- 8
278589
value is used. They are predominantly used to configure the atomic block. Outputs Outputs are values that are the result of the function or operation with which they are associated. They are predominantly used to generate data for other atomic blocks to use. These are similar to outputs except it is not expected that these are connected to inputs. They are predominantly used to monitor the atomic blocks execution. When defining a user object you are free to define your own attributes. They can be categorized as any of the above or you may define your own categories for your own purposes. All attributes have the sub-attribute Quality. The behavior of atomic blocks may be based on the Quality of its inputs. Use the QualityForce atomic block to force a quality change on a value as it is passed through. 0 = good data quality 1 = doubtful data quality 2 = substitute data quality 3 = bad data quality Methods direct an atomic block to perform a special function. Methods include commands to change mode or target value, etc. Because pure method values do not exist after the method is executed, they cannot be read back. Attributes that are used to receive commands from the HMI that will initiate some action within the atomic blocks algorithm.
Status
Custom
Quality
Methods
Commands
Table 1-2 lists attribute categories listed in this publication for each atomic block. Categories, such as General and Quality, are common to all atomic blocks and are not listed with each atomic block type. The table lists information about referencing, read/write characteristics and configuration information. Most of these attribute categories are viewable in configuration utilities, such as maxDPUTools, Graphical Configurator, and Point Browser. Table 1-2. Attribute Categories and Characteristics
Metso Automation
1- 9
278589
Shown in Graphical Configurator When Referenced* When Referenced When Referenced When Referenced When Referenced
*Attribute is shown on the Graphical Configurator as a quill protruding from the atomic block bit map in Detail Mode before any attributes are referenced or exposed.
Output:
Parameter:
Status:
Use referencing: to read an attribute within the same control containing the reference to read attributes within other controls to read attributes within controls located in other configurations
Reference Subscriptions
Metso Automation
1- 10
278589
All inputs have several sub-attributes to represent their data. The local (default) value and the reference pointer fields are configurable. The working value is always retrieved by following the reference pointer. The following three cases apply to input references: 1. When a reference pointer is not specified, the default for the pointer is to point to the local value. 2. Optimized subscriptions use the reference pointer to pick a value in the DPU database (local memory) eliminating the need to subscribe to the Software Backplane. This takes the same amount of processor time as retrieving a local value. See Table 1-2. 3. Unoptimized subscriptions use the pointer to pick a value from a location, which must be interpreted. These would include - points outside the DPMS (including peer to peer communication), - references to attributes of a different type (e.g. time type input referenced to a floating point value), - some status type attributes that are not stored, and - (at least at present) sub-attributes of input attributes. Values by unoptimized subscriptions may not update every scan during periods of high DPU activity.
Reference Syntax
The meaning of the following characters describes the construction of a reference field entry. See Publication 278597, maxDPUTools Users Guide, Using Referencing to Interconnect Controls, for a more extensive discussion of reference syntax. Character Character Description Slash Number Sign Single Dot Meaning
/ #
Hierarchical level separator Designates the beginning of a relative ID number My child (also designates the beginning of an attribute name) Sibling (child of my parent) (note that ../../ designates an aunt/uncle (child of my grandparent)) The next hierarchical level above with a child whose name matches the generic name following the next slash (/) Follow the reference of the attribute referenced. This reference construct is not recommended because it resolves on download
..
Double Dot
Caret
Follow
Metso Automation
1- 11
278589
only, does not reconstruct the connection for any subsequent edits in the DPU database.
Boolean
Boolean data can only have the values True and False. It represents two state conditions such as: active/not active; on/off; alarm/no alarm.
Integer
Integers are whole numbers with no fractional component. They may be range-restricted according to use.
Metso Automation
1- 12
278589
Enumerated data is another variation of Integer or Boolean where there is a meaning assigned to a list of values, which is severely restricted to those having special meaning to the function. Example: mode in the auto/manual atomic block may be set to 0=manual 1= auto
Float
Real or floating point data is used to represent a value in a continuum of a range of possible values. They are not restricted to whole values and may differ from other floats by very small increments. (Behind the scenes, most data is actually stored in this format. Consequently, you may occasionally see fields where integer and even Boolean values are sometimes misrepresented as floats).
String
Generally used for text.
Absolute Time
Absolute time is a special type of data, displayed in a standard time format. It is derived from the local clock, synchronized to the system master clock.
Relative Time
Relative time is another variation of float that enables it to be read by a standard input reference.
Commands
Commands are a special type of input to a function block that causes an action by the block when the command is written. To initiate this one time (scan) action, the command value is time stamped. The value represents an enumerated input to command one of a set of actions or a floating input to set a value entry (the input determines the application of the value). Normally the input is written by maxVUE functions (that includes the time stamp for the write event). But the input could be referenced to a COMMAND function block output (.OUT01 - .OUT16) or an edge trigger (EDGEANY, EDGEFALL, EDGERISE) function block command output (.CMDOUT).
Metso Automation
1- 13
278589
The COMMAND function block combines (up to four command inputs) and translates the commands to values that match the requirements of the inputs that reference its outputs while passing the time stamp of the active input command. Its inputs are also normally written by maxVUE functions but could also be referenced.
Forceback
To avoid having upstream components run away (wind up) when the downstream components are unable to respond a concept called forceback is used to impose limits on the master source. The special value Status is used to describe the limit being imposed. RHI RLO VAL STAT
Metso Automation
1- 14
278589
Family Ties
Two special connections of atomic blocks require a special means of complex and even bi-directional communication. Participation master and members must be able to keep tabs on one another that they do through the master demand connection. Sequence master and steps have to pass status and active state information to one another, which they do through the chain--complex connection.
Metso Automation
1- 15
278589
Up to 45 I/O Modules or up to 255 I/O addresses may be assigned to each DPU. I/O addresses are used to access I/O modules or channels of I/O modules. Each digital I/O module supports 16 bits with one address. Analog modules generally use one address per channel. I/O Analog and Digital Modules and associated signals are defined and configured and become part of a DPU I/O inventory list.
Metso Automation
1- 16
278589
Two relay output types 240 VAC, 130 VDC Form A relay 10 channel 240 VAC, 130 VDC Form C relay
Metso Automation
1- 17
278589
Positioning Modules
Customizable control via program language. Each module has 8 digital inputs, 8 digital outputs, 4 analog inputs, and 4 analog outputs, along with a selection of termination module types available for various types of signal conditioning. Refer to the maxPAC Positioning Module Programming Guide and the maxPAC Hardware Reference Guide for additional details.
Metso Automation
1- 18
278589
more information such as maintenance data or environmental conditions. This data is now readily available to the users with the advent of the HART interface. Metso Automation has several versions of maxPAC I/O cards that support the HART interface: Analog Input Card has the ability to receive 4-20 ma field signals, as well as, HART Communications on each of 8 channels. Analog Output Card has the ability to drive 4-20 ma field signals, as well as, HART Communications on each of 8 channels. Transceiver Card performs HART Communications on each channel. The eight channels on this card can be connected in any order to various 4-20 ma field signals that are connected to a HART field device.
Refer to the maxPAC Hardware Reference Guide 278596 for more detail of the hardware interface and interconnection. Refer to the HART Configuration Guide 278715 for more details of the communications programming.
Metso Automation
1- 19
278589
A hierarchical organization may contain up to eight levels. The highest level of organization, which may represent an overall area of a control environment, may be labeled Unit1. Unit1 may have a subgroup called Control. Control may have subgroups, such as Boiler Control, Generation Control, etc. Using a configuration tool, such as maxDPUTools, it is best to define group hierarchies before defining individual atomic blocks. When you open maxDPUTools and define a configuration name, you may begin to establish desired group hierarchies under the DPU tab. The left pane of maxDPUTools shows a configuration tree structure similar to Windows Explorer. Each time you add a group, the new group appears in the tree structure. A group is placed at the level of the hierarchy that is currently selected. The selected level is the parent." When you add a group to the parent level, a new child group is placed under the parent. Controls placed in the same group are called siblings. Groups may be referenced by relative index number. When you add a group, the relative index is selected incrementally by default, which you may manually change The Relative index for each group or control must be unique within a group. See Publication 278595, maxDPUTools User's Guide.
Group Attributes
The Group atomic block uses only parameter and general attributes. The Gname parameter is already configured when you open the newly created atomic block, showing the name you entered when you created the group. You may also give the group a tagname and description.
Metso Automation
1- 20
278589
See Selecting
Scheduling attributes are configured with default settings that you may change in maxDPUTools during database configuration or online using Point Browser. These attributes taken together create a point database scheduling table. Changing the service priority, service time base, schedule type or committing a Function Block causes the schedule tables to be rebuilt. All Atomic Function Block execution is halted while the schedule tables are re-built (20 to 70 milliseconds). Atomic Function Block execution resumes immediately after the schedule tables are rebuilt. Use the DpuAtomList utility, accessible from the maxSTATION, to read the schedule tables from a DPU, present them on screen and save them to a file. The utility lists Atomic Function Blocks in execution order for each time class. This tool only works with DPU version 2.0 or later. See Using the DpuAtomList Utility.
Metso Automation
1- 21
278589
change the execution order set the ScheduleType attribute in the DPMS object to 0 for priority order or 1 for hierarchical order. With either execution order, you may set the ServicePriority attribute to 0 to remove a group and all of its children from the schedule tables. Additionally, setting an Atomic Function Block to priority 0 causes it to be removed from the schedule table. This may be useful when you need to disable a part of a configuration temporarily while adding new functionality to an active DPU. maxDPUTools will no longer default group priority to zero.
Metso Automation
1- 22
278589
Hierarchical execution uses the ServicePriority attribute in combination with HID structure to determine an execution order. Additionally, hierarchical execution may also incorporate absolute priorities that take precedence over the hierarchical position. See next section, Using Hierarchical Scheduling with Absolute Priorities. Hierarchical execution looks at all of the Atomic Function Block children and group children one level down from the parent. Groups and Atomic Function Blocks with a higher priority are executed before groups and Atomic Function Blocks with a lower priority. All branches of the tree are scheduled in this manner. The result is that a group with high priority will have all of its children execute before the children of a lower priority group. Hierarchical execution is illustrated in the following figure and the accompanying table. See Figure 1-1 for an illustration of a configuration using absolute priorities. Note: all groups and Atomic Function Blocks are assumed to be in the normal time class.
Root Priority 50
Group A Priority 50
Group B Priority 20
Group C Priority 40
Atom 1 Priority 21
Atom 2 Priority 20
Atom 3 Priority 70
Atom 4 Priority 40
Atom 5 Priority 41
Figure 1-1. Illustration depicts a configuration using hierarchical execution. See figure 1-for an illustration depicting a configuration using absolute priorities.
Metso Automation
1- 23
278589
Note that DPMS always runs first in the normal time class. Children of a group always execute before the group. This example shows the importance of the group priority attribute. In pre-2.0 versions of the DPU the group ServicePriority attribute was ignored.
Root Priority 50
Group A Priority 50
Group B Priority 20
Group C Priority 40
Atom 1 Priority 21
Atom 2 Priority 99
Atom 3 Priority 70
Group D Priority 1
Atom 4 Priority 41
Atom 6 Priority 50
Metso Automation
1- 24
278589
Note that the children of Group D are executed first since it has an absolute priority. When non-absolute priorities are the same, the following are used to resolve the hierarchical execution order: X position on the Graphical configuration sheet, then relative index, then service handle.
To view the execution rates and priorities for points within a selected DPU: 1. Click the down arrow next to the maxDPU list field to view a list of available DPUs created from the DPUlist.ini file.
Metso Automation
1- 25
278589
2. After selecting a DPU, click the Get Block List button to start the schedule acquisition process. Since the program reads at a leisurely pace, it may take 20 or 30 seconds for the schedule data to be presented. The data is listed with the first block to be executed at the top and the last executed block at the bottom. The type of block, its tag, and service priority is shown. 3. To save the data read from a DPU, click the Write To File button. The schedule data will be written to a file in the c:\temp folder. The file will be named atomlist_[dpu ip address].txt. If a file for this DPU already exists, it is overwritten.
Custom controls may be nested up to four levels deep as part of a hierarchical structure. A Custom block is defined as part of a user object, to which you assign a name during the configuration process. When you create and name the user object, the name appears in maxDPUTools tree directory pane where you may click on it, similar to a group node, to reveal its contents.
Metso Automation
1- 26
278589
full of discussion of Point Browser. User objects appear in the tree directory under the Service by Station subfolder as follows: _AlmEvtText _AlmTagText _p(BattAlarm) _p(Fan Alarm) _p(NetAlarm) _pQueOvrn) _DPMS _DPMS.Root (GRP) _Backup _Security_Custom (Security) _Security_MCS (Security) _TimeSync (TimeSync) SbpLimit
These objects, which contain preconfigured values, are a standard part of all configurations. Their associated attributes should not be edited.
Metso Automation
1- 27
278589
The following is an example of the DPU Events dialog with both DPU Fan and DPU Battery alarms.
Metso Automation
1- 28
278589
_timesync Object The _timesync standard object is the control center of the time
synchronization process. The family of utilities that support time synchronization reference attributes that are members of the _timesync object. See Publication, 278605, maxDPU Auxiliary Functions Users Guide, Chapter 5, for a full of discussion of time synchronization.
SBPLimit Object
Metso Automation
1- 29
278589
Starting with Release 3.4 for the DPU4E and Release 4.2 for the DPU4F, a new function was added that is called the SBPLimit atom. This new atom allows configuration, display and alarming of Software Backplane usage restrictions. The restrictions were added to preserve the functioning of control logic under any network loading conditions. Note that the restrictions are on external accesses. Incoming subscriptions can also come from inside a DPU in the form of unoptimized subscriptions. IncomingSubs statistic includes both internal and external subscriptions. A strict priority is enforced on the usage of the DPU Central Processor: 50% Guaranteed to control logic Existing Loop priority subscriptions such as peer-peer communications Existing Normal priority subscriptions for display update Existing Background subscriptions New loop subscriptions New normal subscriptions New background subscriptions
Some goals of the restrictions include: No amount of communications load will cause failover No amount of incoming traffic can affect control logic New incoming traffic will not interrupt peer-peer communications No one station can dominate the bandwidth of the DPU No one program within a station can dominate use of station bandwidth Any restriction violations shall be clearly diagnosed and alarmed
There are a number of types of restrictions on incoming traffic: Total Incoming Subscriptions to a DPU limits the total to a number that can be handled by the DPU under any loading conditions Limits by connection priority loop (high), normal (medium), and background (low) insures that a lower priority connection cannot consume all available bandwidth preventing higher priorities from being serviced. Each program on the software Backplane has one or more connections. By limiting connection subscriptions, more bandwidth can be offered to higher priority connections (such as maxVUE) than lower priority connections (such as maxSTORIAN). Limits by station limits the number of subscriptions from any single station to the DPU.
Metso Automation
1- 30
278589
Limit to outgoing references a restriction on the total traffic (peer-peer) that can be generated by a single DPU Limit to unoptimized subscriptions a logical connection between internal objects in a DPU that take work each time the block is executed. In an optimized subscription, the destination object directly accesses the source of data. An unoptimized subscription is access to data that is not stored, but that must be computed each time it is accessed.
Setting the Limits: All limits can be set in maxDPUTOOLS using object \system\SBPLimit. Usable defaults are set for each parameter. NOTE: increasing the default limits can have adverse consequences to the performance of the DPU. The default parameters were tested to insure that the control algorithms have at least 50% of the CPU time available, that all communications is handled in a timely manor, and that the Sequence of Event timing meets the specification. Consult the factory if it becomes necessary to increase these limits.
Metso Automation
1- 31
278589
Specifies the High Alarm value for total external incoming subscriptions processed by a DPU. Default Value 8000 The DPU may be stressed at this limit. Specifies the Hard limit value at which any new subscription will be rejected. Default Value 10000 a value larger than this is not recommended. Specifies the High Alarm value for subscriptions from any particular station (DPU or maxSTATION). Default Value 4000 - No station should consume more than half the capacity of the DPU. Specifies the Hard limit value for subscriptions from any particular station (DPU or maxSTATION). Above this level any new subscription from that station will be rejected. Default Value 5000 - No station should consume more than half the capacity of the DPU Specifies the High Alarm value for subscriptions from any particular SBP connection running at Loop Priority. Default Value 180 - Loop Subscriptions are used for DPU to DPU communications. The number is small since they are handled at 1/4 second resolution. Specifies the Hard limit value for subscriptions from any particular SBP connection running at Loop Priority. Above this level any new subscription from that station will be rejected. Default Value 200 - Loop Subscriptions are used for DPU to DPU communications. The number is small since they are handled at 1/4 second resolution. Specifies the High Alarm value for subscriptions from any particular SBP connection running at Normal Priority. Default Value 1500 - Normal Subscriptions are primarily used for maxVUE and browser communication. Specifies the Hard limit value for subscriptions from any particular SBP connection running at Normal Priority. Above this level any new subscription from that connection will be rejected. Default Value 2000 - Normal Subscriptions are primarily used for maxVUE and browser communication. 2000 values from a single DPU should be considered extreme. Specifies the High Alarm value for subscriptions from any particular SBP connection running at Background Priority. Default Value 2000 - Background Subscriptions are primarily used by maxSTORIAN communication.
HardLimTotalSub
HiLimStnSub
HardLimStnSub
HiLimConnLoop
HardLimConnLoop
HiLimConnNorm
HardLimConnNorm
HiLimConnBgnd
Metso Automation
1- 32
278589
HiLimOutRef
Default Value 3000 - Background Subscriptions are primarily used by maxSTORIAN communication. 3000 values from a single DPU exceed the possible real point count by more than a factor of 2. Specifies the High Alarm value for External References. (Those containing a '[') Default Value 450 - 1/4 second data may lag significantly if external references exceed this value. Specifies the Hard limit value for External References. (Those containing a '[') Above this level any new outgoing requests will be set to BAD_REF quality and not processed.
HardLimOutRef
HiLimUnOptRef
Default Value 500 - Values above 500 are not recommended in fully loaded DPUs. Specifies the High Alarm value for Internal Unoptimized References. Default Value 720 - 1/4 second data may lag significantly if unoptimized references exceed this value. Specifies the Hard limit value for Internal Unoptimized References. Above this level any new internal unoptimized reference requests will be set to BAD_REF quality and not processed.
HardLimUnOptRef
Default Value 800 - 1/4 second data may lag significantly if external references exceed this value.
The DPU will annunciate alarms for exceeding any of the above limits. The format of these alarms is:
UnOpt Ref High %#22% High Alarm for Unoptimized References reached. %#22% is substituted by the current count of Unoptimized references. High Alarm for External References reached. %#21% is substituted by the current count of External references. High Alarm for External station or connection subscriptions. %#23% is substituted by the current count of external subs from the highest user. %#24% is substituted by the name of the station or the station name and connection number (Name:##) corresponding to %#23% High Alarm for Total Subscriptions reached. %#26% is substituted by the current count of total subscriptions.
Metso Automation
1- 33
278589
%#23% is substituted by the current count of external subs from the highest user. %#24% is substituted by the name of the station or station name and connection number (Name:##) corresponding to %#23% Hard Limit for Total Subscriptions reached. %#26% is substituted by the current count of total subscriptions. Hard limit for Unoptimized References reached. %#22% is substituted by the current count of unoptimized refs. Hard Limit for External References reached. %#21% is substituted by the current count of External refs.
Note: Only Top station statistics are visible unless expert mode is turned on in the browser. Name and connect Ids are of the form NAME:##.
Metso Automation
1- 34
278589
If the atomic block does not have a Tagname the alarm parent group Tagname will be used in the alarm last. Another possibility is that the HID and generic name of the point may show up in the alarm list. One atomic block capable of alarming will only have at most one entry in the alarm list. A group may present more than one alarm to the list if it has more than one un-tagged alarm reporter calling it the alarm parent.
Buffer Alarming
Buffers may also produced alarms when associated I/O cards experience a problem. Each I/O buffer has a FailoverTyp attribute used to determine the action taken if the DPU can no longer communicate with the associated I/O card. Three possible FailoverTyp settings are: non-critical (0), normal (1), critical (2). All buffers will be in one of these classifications. The default is noncritical. Three attributes in the backup object determine what action is taken for card failures in each classification (ThreshNonCrit, ThreshNormal, and ThreshCritical). Each of these three attributes has three possible actions based on exceeding the threshold. The following are the possible codes and actions:
Metso Automation
1- 35
278589
Default for Classification Normal
Fail One
Do Nothing
Non-Critical
ThreshNonCrit (default value = 2 Do Nothing) can be set to one of the three threshold values shown in the above table. The action will only pertain to the I/O cards where FailoverTyp is set to the default of noncritical (0). ThreshNormal (default value = 2 Do Nothing) can be set to one of the three threshold values shown in the above table. That action will only pertain to the I/O cards where FailoverTyp is set to Normal (1). ThreshCritical (default value = 2 Do Nothing) can be set to one of the three threshold values shown in the above table. That action will only pertain to the I/O cards where FailoverTyp is set to Critical (2).
Base Attributes
All atomic blocks include base attributes that are generally not configurable. Attributes appearing on the following list that are
Metso Automation
1- 36
278589
configurable are ServicePriority and ServiceTimeBase. See "Setting Atomic block and Group Execution Rates and Priorities." The base attributes are listed here for reference.
Attribute Name _COMMIT AltDescp AnyAlarm AttrBadRef AttrBool AttrCmd AttrCnt AttrEnum AttrExternRef AttrFlags AttrHasRef AttrMaxVal AttrMinVal AttrNormRef AttrOptRef AttrOptRefCnt AttrOptRefId AttrReadable AttrState AttrWireable AttrWriteable BaseAttrCnt Category Data DataIdx DELSVC Descp EngrSec Idx INHERIT MARKDEL Name ObjType OperSec Quality Ref RefTurn SbpQuality SCHEDULE Service SvcCntBrowse SvcCntInputs SvcCntOutputs SvcHandle SvcParent SvcPassword SvcPntTickCnt SvcPriority SvcRelIdx SvcSecLevel SvcStatus SvcTimeBase SvcType SvcUpdateTime SvcVersion SvcX Data Type VAR_EMPTY VAR_PCHAR VAR_FLOAT VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_PCHAR VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_PCHAR VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_PCHAR VAR_LONG VAR_LONG VAR_EMPTY VAR_PCHAR VAR_LONG VAR_LONG VAR_EMPTY VAR_EMPTY VAR_PCHAR VAR_PCHAR VAR_LONG VAR_LONG VAR_PCHAR VAR_PVARIANT VAR_LONG VAR_EMPTY VAR_PCHAR VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_LONG VAR_PCHAR VAR_LONG VAR_FLOAT VAR_LONG Description Commit A Service Attribute Alternate Description No Alarm=0 Alarm=1 Attribute has bad ref Attribute is boolean Attribute is a command Count of Attributes Attribute enumerations Attribute has external ref Attribute Flags: RWONXBWBSCH Attribute is referred to Attribute maximum value Attribute minimum value Attribute has normal ref Attribute has optimized ref Attribute optimized refcount Attribute opt ref client Id Attribute is readable Attribute is stateful Attribute is wireable Attribute is writeable Count of Base Attributes Attribute Category Attribute Data Attribute Data Index Delete A Service Attribute English Description Attr engineer security level Attribute Index Inherit Parent SvcProperties Mark A Service for Delete Attribute Name Object Type Attr operator security level Attribute Quality Attribute Reference Attribute Reference Turns Attribute Quality in detail Schedule A Service Universal name for Object Count of Output Members Count of Input Members Count of Output Members Service Handle Service Parent Handle Service Password Service Load Factor Service Priority Service relative ParentIndex Service Security Level Service Commited Status Service Time Base for SchdQue Service Type Service Last Update Time Service Version Service X loc on Page Category Method Subattr General Subattr Subattr Subattr Status Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Subattr Status Subattr Subattr Subattr Method Subattr Subattr Subattr Method Method Subattr Standard Subattr Subattr Subattr Subattr Subattr Method Status General General General General General General General Standard Standard General General Standard General General General General
Metso Automation
1- 37
278589
General Subattr Method
Metso Automation
1- 38