Model PDP Series 400 Maxdpu4F Hardware Guide: 278705 Rev. A5
Model PDP Series 400 Maxdpu4F Hardware Guide: 278705 Rev. A5
Model PDP Series 400 Maxdpu4F Hardware Guide: 278705 Rev. A5
Hardware Guide
278705 Rev. A5
Refer to this publication for complete and accurate information that helps you better operate and service Metso
Automation equipment. Your comments and suggestions are welcome.
Metso Automation
1180 Church Road
Lansdale, PA 19446
Attention: Manager, Technical Publications
Introduction .................................................................................................................................................................1-1
Distributed Processing Unit Functionality.................................................................................................................1-1
Model Numbers .................................................................................................................................................1-1
Distributed Processing Unit Hardware ..............................................................................................................1-2
Control Processor ..............................................................................................................................................1-2
Performance.......................................................................................................................................................1-2
I/O Bus Interface ...............................................................................................................................................1-2
Fully Self Describing Object Oriented Database...............................................................................................1-2
Fully Software Backplane Compliant................................................................................................................1-3
Sequence of Events............................................................................................................................................1-3
Distributed Processing Unit Specifications .......................................................................................................1-3
Powering the DPU .............................................................................................................................................1-3
Mounting the DPU ................................................................................................................................................1-4
Positioning the DPU in a Standard maxPAC Chassis .......................................................................................1-4
Positioning the DPU When Upgrading .............................................................................................................1-4
Mounting Procedures.........................................................................................................................................1-4
DPU Front Panel Controls and Features................................................................................................................1-5
Mode Switch......................................................................................................................................................1-5
maxNET Interface Ports ....................................................................................................................................1-5
Network Status LEDs ........................................................................................................................................1-5
Backup Port .......................................................................................................................................................1-5
Backup LED ......................................................................................................................................................1-5
Serial Port (Optional).........................................................................................................................................1-5
Reset Button ......................................................................................................................................................1-5
IOM Status LED................................................................................................................................................1-6
I/O Status LED ..................................................................................................................................................1-6
CP Status LED...................................................................................................................................................1-6
State LED ..........................................................................................................................................................1-6
Takeover Button ................................................................................................................................................1-6
IRIG-B Port (Optional)......................................................................................................................................1-6
Installing Windows CE and maxDNA Software onto the DPU CompactFlash Memory .................................... 5-1
Overview .................................................................................................................................................................. 5-1
Writing the CompactFlash Using the DPU4FSetup Utility .................................................................................. 5-1
Network Flash using Mode “E”........................................................................................................................ 5-2
Network Flash using Mode “C”........................................................................................................................ 5-3
Flash using a CompactFlash Reader/Writer ..................................................................................................... 5-3
Introduction
The DPU is also available with an optional serial port that may be accessed
by optional software running in a workstation. Together, they provide a
means for communicating with certain types of field devices (e.g., some
Programmable Logic Controllers).
As a station on maxNET, the DPU scans and processes information for use
by other devices in the maxDNA system. Each DPU performs:
Model Numbers
Model PDP401 – DPU4F #181550, #181555, or #181580
Control Processor
The DPU is comprised of a single printed circuit board that contains a
Pentium-class (AMD Geode) Control Processor and a dedicated micro-
controller for scanning I/O. There are also sockets on the board for 64
Mbytes (minimum) of CompactFlash and 128 Mbytes of DRAM.
Performance
A multi-speed processing system is built into the maxDPU4F, which allows
objects to be executed in three different time classes. From as fast as 10 msec
to 1/2 second. Up to 8,500 control objects (Function Blocks) can be executed
in the DPU. Note also that Function Blocks can be combined to create
libraries of Standard and Custom Blocks. A Function Block can be as small
as an Atomic Block, such as an AND or OR gate.
A data point management system (DPMS) keeps track of the object size and
the total execution time for each time class.
All information regarding the operation of the DPU is kept in DPU memory,
including: tag names, descriptions, tuning constants, alarm limits, etc. In
addition, all graphical configuration data (sheet number, object location,
wiring) is stored in the DPU.
Objects are stored in a fully hierarchical database, allowing for easy cut and
paste changes and protection of control strategies.
Sequence of Events
Each DPU includes a built-in Sequence-of-Events (SOE) recorder that can
monitor up to 512 discrete inputs. These inputs are scanned 1,000 times a
second and state changes are time stamped with 1 ms resolution and stored in
the DPU's 10,000-event buffer. Each input has a separately configurable
digital filter for contact debounce.
The DPU is designed to allow installation and removal with the +24 V dc
power supply turned on.
If the previous DPU was a DPU4E, the Ethernet cables that were plugged
into the termination panel can be plugged directly into the front panel of the
DPU card. Make sure that the settings of the Ethernet switch match the setup
file. See Chapter 5 for the configuration setup.
In all upgrade situations, the backup cable must be replaced with a DPU4F
backup cable (Metso Automation # 050292).
Mounting Procedures
Before mounting any hardware, refer to the cabling and field wiring sections
of Publication 278596, maxPAC Hardware Reference Guide, and Publication
278563, Model IOP Input/Output System Installation and Preparation.
To install the DPU in the rack, refer to Chapter 7 Starting the DPU.
Mode Switch
The Mode Switch is a 16 position rotary switch. It is read after a reset or
power up cycle of the DPU to determine its operational mode. The switch is
also read during online operation to allow setting of the mode to “Running”,
“Locked”, or “Offline”. See Chapter 3 for details.
Backup Port
A 100 MB Ethernet interface is provided to pass database information to a
hot standby DPU. A custom Category 5 Ethernet cable (Part #050292) is
used to connect both DPUs via this port. A status signals are also passed
between DPUs through this port to indicate which DPU is in control.
Backup LED
This LED shows the status of redundancy for DPUs configured as a backup
pair.
Reset Button
Pressing this button will cause the DPU to stop controlling and go through a
reset cycle. This should not be done casually as it can cause a severe
disruption to your process.
Refer to Chapter 3 for more detailed information on the use of this button.
CP Status LED
The CP Status LED reports the health of the Control Processor.
State LED
The State LED reports the current control state of this DPU.
Takeover Button
Pressing the Takeover button can force a previously inactive DPU to go
active. This should not be done casually as a manually forced takeover
occurs regardless of the inactive DPU’s ability to control. This can have
severe consequences to your process.
Refer to Chapter 3 for more detailed information on the use of this button.
Overview
All input/output connections are contained on the front DPU chassis panel.
The chassis contains:
Note: When using the Cisco Catalyst 2950 Ethernet Switches, the switch and
DPU must be set to Auto-Negotiate.
Backup Link
A 100 Mbps Ethernet link is used to pass database information between an
active DPU and an inactive standby DPU. A custom Category 5e cable
(Metso #050292) connects the DPU backup pair together via the backup
link’s RJ-45 connector. Secondary DPUs will typically be installed in the
lower chassis just below the primary DPUs.
Serial Port
The DPU front panel contains a serial port utilizing an 8-pin RJ45 style
connector.
Table 2-1 provides the pin-outs for the 8-pin port. The signal levels are
standard RS232.
If a Stand Alone DPU or DCM is used, there is a cable that converts the RJ45
to the standard DB9. The part number is Metso # 075113.
The serial port supports redundancy when a backup pair of DPUs is used.
The serial port is only operational if the DPU is “Active”. The RS232
drivers on the “Inactive” DPU are turned off. The use of this feature requires
a redundancy cable to connect between the two DPUs and the RS232 device.
(Metso Automation # 050355). This cable has an RJ45 for each DPU and a
common DB9 connector with male pins.
Overview
The DPU front panel contains a hexadecimal rotary switch and pushbuttons
for Reset and Takeover. The mode switch is used to determine the
operational mode of the DPU. Refer to this chapter for discussions of these
DPU front panel switches and buttons.
If the Reset button is pressed for less than 2 seconds, the DPU will save the
current configuration database and then reset itself (Soft Reset). If the Reset
button is depressed for longer than 3 seconds, the DPU will immediately
reset. (Hard Reset) NOTE: during normal operation the DPU continually
saves the configuration database to CompactFlash. For typical databases,
this will be done every 5 minutes. If a hard reset is performed, the DPU will
still contain a recent database and will attempt control once restored. This is
different from previous versions of the DPU where the configuration
database was not routinely saved. In previous DPUs, a Hard reset would
prevent the database save and the DPU would come up blank. To prevent
control or the use of a previous database, set the Mode Switch to “B” and the
DPU will clear the database during the boot cycle.
If the Takeover button is pressed on the inactive DPU of a DPU pair (backup
enabled), the inactive DPU will go active regardless of its health or mode
switch position as long as it is hot. A “hot” DPU is one that has a database
that matches that of the other member of its pair (including the case where
neither DPU has a database).
Once takeover occurs, the now inactive DPU will “warm” (synchronize) its
database from the now active DPU. This will force the inactive DPU’s
database to match that of the active DPU. When the inactive DPU becomes
“hot”, it will automatically go active if the active DPU’s quality is
significantly below the quality of the inactive DPU.
If you wish to guarantee that an inactive DPU goes active and stays active,
you must “kill” the currently active DPU. This can be done by either
unplugging the DPU from its chassis or by writing to the “ForceFatal”
attribute of the active DPU.
Overview
Refer to this chapter when you need to interpret the meanings of the 9 status
LEDs on the DPU front panel. At various times the LEDs flash green,
yellow, red or display no color to indicate the associated hardware’s
functional status. Discussions in the following sections explain what the
color changes may indicate under different DPU states.
All or some of the LEDs display a set of color codes associated with the
following DPU states:
After Reset
After a reset, the IOM and CP LEDs are Yellow, while all others are off.
Once Windows CE is loaded into memory the CP initializes the FPGAs. This
results in the IOM LED going red and the I/O LED going off. The CP then
releases the IOM processor that causes it to execute startup diagnostics. The
I/O LED changes colors rapidly while executing the diagnostics. When
complete the IOM LED turns green and the I/O LED goes off.
If the BIOS on the CompactFlash is different than the one stored in onboard
flash it will be written to the onboard flash. During this time the CP and
State LEDs will alternately blink red. DO NOT stop the DPU during this
period or the flash could become corrupt and the DPU will need to be
returned to the factory for repair. Once the BIOS is written, the DPU will go
through another reset cycle. Most updates will not require a BIOS change.
Next the CP goes yellow while rebuilding the database. This can be brief or
up to 30 seconds depending on the size of the stored database. The CP LED
then turns to blinking green/yellow. This is a “heartbeat” signifying that the
CP is operational. The State LED goes red temporarily and then to green.
The network “A” and “B” LEDs start off blinking yellow until the DPU
hears communication from another station in its domain. The LED goes
solid yellow and then to green. If the LED remains solid yellow, it signifies
that this DPU is receiving a message from another station and the message
shows that the other station does not hear this DPU.
** Each device (DPUs and Workstations) send messages that contain a list of all stations from which it is currently
receiving messages. If the DPU receives messages from a station that does not report receiving messages from it,
the DPU illuminates the Yellow LED. The problem may or may not be this DPU.
State See Below See Below See Below DPU not Operational
or LED Bad
AI 564 X
TC 564 X
RTD 564 X
AO 564 X
Counter Timer 564 X
AI maxPAC X X
TC maxPAC X X
RTD maxPAC X X
AO maxPAC X X
Counter Timer maxPAC X X
Overview
The DPU utilizes a CompactFlash for storing and retrieving all software and
configuration information for the DPU. The CompactFlash is non-volatile
and can be removed to allow updating or moving a configuration from one
DPU4F to another. The CompactFlash is a minimum of 64 Megabytes and is
industrial grade to allow for operation in harsh environments, as well as,
supporting a very large number of write cycles. If replacing the
CompactFlash, always use Metso part # 050263.
It is possible to update all of the DPU software in the field should it ever
become necessary to do so.
CAUTION : If the software update includes a change to the BIOS, the new
BIOS will automatically be written to a flash chip on the DPU4F the first
time the DPU is booted. The CP and STATE LED’s will quickly alternate
Red denoting that the BIOS is being written. DO NOT reset or power down
during this period since it will cause the BIOS to be corrupted. If this occurs,
the DPU will not boot and must be sent back to the factory for repair.
2. If the DPU is already installed, reset the DPU. If the DPU is not
installed, insert the DPU part of the way into the chassis short of making
connection to the backplane. Plug in the Network A and B cables and
then insert the DPU fully into the chassis securing it with the two
thumbscrews.
3. Wait until Backup, CP, and State LEDs blink yellow and off.
4. Use the DPU4Fsetup program to write the new software to the DPU.
Select the proper DPU from the pull-down list and select Primary,
Secondary or Stand Alone. Select the proper version of Software to be
installed. Use the “Read DPU Via Net” to bring up the network settings
and then use “Write DPU Via Net”.
5. When writing is complete change the mode switch to “F” and reset the
DPU.
2. If DPU is already installed, reset the DPU. If the DPU is not installed,
insert the DPU part of the way into the chassis short of making
connection to the backplane. Plug in the Network A and B cables and
then insert the DPU fully into the chassis securing it with the two
thumbscrews.
3. Wait until Backup, CP, and State LEDs blink yellow and off.
4. Use the DPU4Fsetup program to write the new software to the DPU.
Select the check box “Mode C DPU”. Do not use the “Read DPU Via
Net” since the configuration in the DPU is not valid. Set all
configuration parameters and version of Software to be used. Select
“Write DPU Via Net” to send the software and configuration file to the
DPU.
5. When writing is complete change the mode switch to “F” and reset the
DPU.
1. If the DPU is not installed, remove the CompactFlash by using the eject
button. If the DPU is installed, unscrew the thumbscrews and slide the
DPU out far enough to eject the compact flash. (You may need to
remove the network cables.)
2. Use the DPU4Fsetup program to write the new software to the DPU. If
the DPU was previously configured, select “Read Flash Card” to retrieve
DPU name, IP address and network settings. If the DPU was not
configured or you want to change the configuration, enter all of the
necessary parameters. Select the version of Software to be used. Click
on “Write Flash Card” to send the software and configuration file to the
card.
4. Insert the CompactFlash card into the DPU. Insert the DPU part of the
way into the chassis short of making connection to the backplane. Plug
in the Network A and B cables and backup cable. Then insert the DPU
fully into the chassis securing it with the two thumbscrews.
Overview
In a redundant configuration, two DPUs are connected to form a backup pair.
One DPU is designated as the primary unit and the other DPU the secondary
unit. The IP address of the secondary DPU is always one number greater than
the address of the primary DPU. The primary is always the even address
while the Secondary is the odd address.
Automatic Failover
Process control is automatically transferred from the primary DPU to the
secondary DPU when the primary DPU experiences a severe diagnostic
alarm or when communication between primary and secondary DPU is lost.
However, if the secondary DPU is itself experiencing a severe diagnostic
alarm, it will refuse control, unless the primary DPU loses power or is reset.
Each DPU monitors the state of its own health as well as that of its backup.
The DPU looks at things like the state of its CP, IOM and backup link. It
also checks to see if it can hear good messages from the other DPU over
Network A and B and over the backup link.
From this information, each DPU calculates a health value for itself. This
value, along with other information, is used by the DPU when it is deciding
whether or not it should take control away from the currently active DPU.
Manual Takeover
diagnostic alarm or a fatal alarm condition exists in the inactive DPU then
the Takeover button will be ignored. For a more complete discussion of
manual takeover, see Chapter 3, “Using the Takeover Button.”
Startup States
Refer to this chapter to learn how to:
If a backup DPU is present then, this DPU listens to the other DPU over the
backup link as to its current operation as Standalone or Redundant DPU. If
the other active DPU is set as a Redundant DPU (NOT Standalone) then, this
inactive DPU will erase its configuration/database and proceed to gather
configuration and database information over the backup link. This DPU will
move from an empty state to a warming state and then to a hot standby state
and becomes ready to assume control when commanded to take over.
Note: if a DPU is moved from one location to another where the IP Address
is different, the initialization file on the DPU CompactFlash needs to be
modified. Use the DPU4Setup utility to make the necessary changes. The
default setting on the utility is to automatically erase any configuration
databases. It is still advisable to set the Mode switch to ‘B’ before installing
the DPU in the new location to additionally guarantee that it will come up
cold.
1. Configure the DPU and install the software using the DPU4Fsetup
program. Refer to the Chapter titled Installing Windows CE and
maxDNA Software onto the DPU CompactFlash Memory. This program
will allow the user to configure the IP Address, DPU name, and other
configuration options. The proper version of software can also be
selected for installation on the CompactFlash. For the Redundancy
option select “Station is Stand Alone” so that a backup cable (Metso #
050292) or jumper plug (Metso # 081388) are not required.
2. Since the DPU was reset at the end of the software installation, wait until
the CP LED begins to blink Yellow/Green signifying that the DPU is
operational.
3. Use the DPU4F Detailed Status Display to verify that the DPU is
operational.
5. Acknowledge all system alarms from the DPU and make sure that they
all clear. (Process alarms should be evaluated to determine if the DPU is
operating properly and it is OK to proceed to Unfreezing outputs.)
1. Configure the Primary DPU and install the software using the
DPU4Fsetup program. Refer to the Chapter titled Installing Windows
CE and maxDNA Software onto the DPU CompactFlash Memory. This
program will allow the user to configure the IP Address, DPU name, and
other configuration options. The proper version of software can also be
selected for installation on the CompactFlash. For the Redundancy
option select “Station is a Primary DPU” for the first DPU and “Station
is a Secondary DPU” for the second.
2. Since the DPU was reset at the end of the software installation, wait until
the CP LED begins to blink Yellow/Green signifying that the DPU is
operational.
3. Verify that the status LEDs on the DPU front panel are in the proper
state:
5. Repeat steps 1 to 4 for the Secondary DPU. The Primary DPU should
remain Active Stand Alone and the Secondary should be Inactive Stand
Alone.
7. Load the Primary DPU using the maxDPUTOOLS utility program from
the maxSTATION.
8. Enable Backup and make sure the Secondary DPU properly warms up.
2. Make sure the active DPU does not have any severe outstanding alarms.
3. Disable Backup for the pair from either the DPU4F Detail Display or
maxDPUTOOLS.
4. Update the software on the inactive DPU using the instructions found in
the Chapter titled Installing Windows CE and maxDNA Software onto
the DPU CompactFlash Memory. (The preferred method for a hot
upgrade would be to use Network Flash Using Mode “E”.)
5. Since the DPU was reset at the end of the software installation, wait until
the CP LED begins to blink Yellow/Green signifying that the DPU is
operational. The State LED should be yellow, signifying that it is
inactive.
7. Once the DPU has ‘warmed’ (the pair is ‘hot), the following are the
expected states of the LEDs:
8. Acknowledge all alarms from the new DPU and make sure they clear.
10. Disable Backup for the pair from either the DPU4F Detail Display or
maxDPUTOOLS.
11. Update the software on the newly inactive DPU as was done for the other
DPU in step 4.
12. Since the DPU was reset at the end of the software installation, wait until
the CP LED begins to blink Yellow/Green signifying that the DPU is
operational. The State LED should be yellow, signifying that it is
inactive.
14. Once the DPU has ‘warmed’ (the pair is ‘hot), the following are the
expected states of the LEDs:
• ‘A’ Network – Green
• ‘B’ Network – Green if dual network and off if single network
• Backup – Green
• IOM – Green
• I/O – Green if any Redundant I/O, Off if no Redundant I/O
• CP – Blinking Green/Yellow
• State – Blinking Yellow/Off
15. Acknowledge all alarms from the new DPU and make sure they clear.
16. It is preferred, but not required, to have the Primary DPU be the active
DPU. This can be accomplished by forcing a Takeover to the Primary if
it is not already in that state.
17. From maxDPUTOOLS, make sure the DPU is not running with frozen
outputs.
18. Make sure there are no severe alarms coming from the DPU.
19. If points were placed in manual at the start of this upgrade, they can be
returned to normal operation.
1. Make sure the DPU that is to remain in place is active and there are no
severe outstanding alarms.
2. Disable Backup for the pair using the DPU4F Detail Display.
3. Pull the DPU being replaced far enough out of its chassis to disconnect
power.
4. Remove the Backup Cable, Network, “A” Cable, and Network “B” Cable
from the extracted DPU.
6. Either move the CompactFlash from the original DPU to the replacement
DPU or configure the new CompactFlash using the DPU4FSetup utility.
It is very important that the configuration file on the CompactFlash have
the proper DPU name and IP address and other configuration parameters.
7. The DPU should have been reset at the end of the previous step. When
booting is complete, the following are the expected states of the LED’s:
• ‘A’ Network – Green
• ‘B’ Network – Green if dual network and off if single network
• Backup – Yellow
• IOM – Green
• I/O – Off
• CP – Blinking Green/Yellow
• State - Yellow
8. Use the DPU4F Detail Display to verify the proper status of the new
DPU and make sure there are no outstanding alarms.
9. From the DPU4F Detail Display enable backup to permit the active DPU
to warm up the inactive DPU.
10. Once the DPU has ‘warmed’ (the pair is ‘hot’), the following are the
expected states of the LEDs:
• ‘A’ Network – Green
• ‘B’ Network – Green if dual network and off if single network
• Backup – Green
• IOM – Green
• I/O – Green if any Redundant I/O, Off if no Redundant I/O
• CP – Blinking Green/Yellow
• State – Blinking Yellow/Off
11. Acknowledge all alarms form the new DPU and make sure they clear.
DO NOT reset the active DPU since there is no available backup and all the
outputs will be reset. Pressing the reset button on the inactive DPU will
cause it to restart and, if capable, warm from the active. If it does not
properly warm, it should be replaced.
Alarm Annunciation
Diagnostic alarms originating at a DPU are posted as remote alarms on the
maxSTATION Alarm List. Refer to Publication 278558, Alarm Message
Reference Guide, for a description of these alarms. DPU front panel LEDs
also indicate certain fatal diagnostic alarms.
IRIG-B Interface
Overview
IRIG-B is an international time signal standard. Many vendors sell very
accurate clocks that generate IRIG-B signals. IRIG-B is also available as an
output from many GPS satellite receivers. Such IRIG time signals are
typically accurate to within microseconds.
The IRIG signal should be applied to both the primary and secondary of a
maxDPU4F pair to provide a redundant time source should one of the DPUs
fail.
The IRIG-B (B122) time signal is an amplitude modulated 1KHz sine wave.
Figure 1 shows a portion of a typical waveform. V1 and V2 represent the
peak-to-peak amplitudes of the two modulation levels.
IRIG-B Cabling
The IRIG-B input is transformer coupled within the DPU. The BNC
connector is not grounded at the DPU. To prevent ground loop problems, the
IRIG-B signal/coaxial cable should only be grounded at the IRIG source.
The IRIG-B input does not have surge or transient protection so care should
be taken to ensure that the IRIG cable is not routed through electrically
hostile (noisy) areas. Keep it away from field wires, motor wires and other
noisy signals. To reduce the likelihood of noise pickup, do not run the IRIG
cable parallel to noisy wires.
Since the IRIG input on the DPU is high impedance and the IRIG sources
have low output impedance (typically 50 or 600 ohms), the signal may be
applied in parallel to multiple DPUs via BNC “T” or “Y” connectors.
However, if that single cable is damaged, all of the parallel-wired DPUs
could lose their IRIG signal. For more redundancy in an installation use
separate outputs from the IRIG source and wire each output to only one
DPU. For even more redundancy, use more than one IRIG source with one
driving a primary DPU and the other driving the secondary.
Overview
The maxDPU4F contains a number of built in function blocks that are used
to configure and monitor some basic DPU features. These function blocks
are created automatically when the DPU starts (as opposed to being entered
by the user into maxDPUTOOLS and then being downloaded to the DPU).
They are contained within the System group and may be accessed by means
of the Point Browser.
The values of many important attributes are shown in the maxDPU4F Status
and Detail displays.
Backup – This function block contains attributes that control and monitor
how two DPUs function as a pair (i.e., backup mode or stand alone).
QueOvrn – This function block is used to generate an alarm in the event that
the Normal time class software queue overruns.
DCM – The DCM function block is used to describe the quality of the
maxLINKS connections that are made to a DCM (Distributed
Communications Module). A DCM is a special type of DPU that is used to
provide serial communications links to foreign devices (e.g., PLCs). Refer to
publication 278714, Distributed Communications Module, for more
information.
Backup
The Backup function block contains attributes that monitor and control how
two DPUs function as a pair (Backup mode or Stand Alone mode).
Attributes show the state, heath, and active/inactive status for both this DPU
and the other DPU of the pair. Two other attributes are used to display the
Time Since Boot and Time Since State Change of the DPU. Other attributes
are used to show the status of the DPU’s main memory (e.g., OK or memory
error detected) and, if possible, the reason for the last fatal error detected by
the DPU.
DPMS
The DPMS function block is a container for a broad mix of attributes
concerned with the basic operation of the DPU.
Some attributes are used to store information about the identity of the DPU
such as the name of the DPU, IP address, serial number, revision level of the
DPU assembly, revision level of the software and so on.
Another group of attributes is used to describe the current state of the DPU
so that the DPU Detail display can be animated. This group includes
attributes such as those for the color of the IOM, CP, I/O and State LEDs.
The fourth major group contains DPU operating parameters such as the
values used by three function block execution time classes (Normal, High,
and Critical).
DPUTemp
This function block is responsible for reporting the temperature of the DPU
as measured by an on-board sensor. In addition to the actual temperature,
this block also provides alarms with configurable limits.
The default values are consistent with the DPU’s operating temperature range
of 0 - 60°.
SBPLimits
The SBP Limiter is used to restrict (limit) the number of subscriptions to the
DPU. Limiting subscriptions increases DPU robustness and security. It also
protects against slow DPU response time (e.g., slow data update rate as seen
by maxVUE). The function block also generates alarms when the number of
subscriptions reaches a high alarm limit.
It is important to note that the SBP Limits function block only restricts new
subscriptions. It does not have any effect on existing subscriptions. To use a
very simple example, assume that a DPU currently has 100 subscriptions and
the SBP Limiter is configured to limit the total number of DPU subscriptions
to 120. This means that the DPU will accept no more than 20 additional
subscriptions. All subscription requests beyond this total will be rejected by
the DPU and the requestor will receive an appropriate error message. Now
assume that the DPU currently has 100 subscriptions. Further assume that
the user now configures the SBP Limiter to accept a total of only 50
subscriptions. The 100 existing subscriptions will not be effected. They will
still be honored and the requestors will still receive the data they want.
The SBP Limiter does not restrict immediate data reads or data writes. These
are always accepted by the DPU regardless of the limits configured for
subscriptions.
There are seven configurable limits that the SBP Limiter uses to restrict data
access. These are called Hard Limits and are listed below. When a Hard
Limit is reached, an alarm is generated and new subscriptions will be
rejected.
The alarm text that will appear for this limit is:
“Subs Limit xx by AAAA:cc” (where xx is the subscription count, AAAA is
the Station name, and cc is the connection number).
The alarm text that will appear for this limit is:
“Subs Limit xx by AAAA:cc” (where xx is the subscription count, AAAA is
the Station name, and cc is the connection number).
The alarm text that will appear for this limit is:
“Subs Limit xx by AAAA:cc” (where xx is the subscription count, AAAA is
the Station name, and cc is the connection number).
The alarm text that will appear for this limit is:
External Ref Limit xx (where xx is the count of external references).
The alarm text that will appear for this limit is:
Stn Subs Limit xx by AAAA (where xx is the count, AAAA is the Station
name).
The alarm text that will appear for this limit is:
Total Subs Limit xx (where xx is the count of total subscriptions to the
DPU).
The alarm text that will appear for this limit is:
UnOpt Ref Limit xx (where xx is the count of unoptimized references).
For each hard limit, the SBPLimiter function block also provides a
corresponding high alarm limit. The High Alarms are provided as a warning
that the subscriptions are approaching the hard limit values. The DPU does
not limit subscriptions when a High Alarm limit is reached.
The high alarm limits are listed below. Refer to the preceding text on Hard
Limits for descriptions of the high alarm limits.
HiLimConnBgnd
The alarm text that will appear for this limit is:
“Subs Limit High xx by AAAA:cc” (where xx is the subscription count,
AAAA is the Station name, and cc is the connection number).
HiLimConnLoop
The alarm text that will appear for this limit is:
“Subs Limit High xx by AAAA:cc” (where xx is the subscription count,
AAAA is the Station name, and cc is the connection number).
HiLimConnNorm
The alarm text that will appear for this limit is:
“Subs Limit High xx by AAAA:cc” (where xx is the subscription count,
AAAA is the Station name, and cc is the connection number).
HiLimOutRef
The alarm text that will appear for this limit is:
External Ref High xx (where xx is the count of external references).
HiLimStnSub
The alarm text that will appear for this limit is:
Stn Subs High xx by AAAA (where xx is the count, AAAA is the Station
name).
HiLimTotalSub
The alarm text that will appear for this limit is:
Total Subs High xx (where xx is the count of total subscriptions to the
DPU).
HiLimUnOptRef
The alarm text that will appear for this limit is:
UnOpt Ref High xx (where xx is the count of unoptimized references).
It is important to note that the user does not have to configure the SBPLimits
function block. Default values are automatically installed for both the hard
limits and the alarm limits. The default values have been carefully selected
to maximize functionality and to minimize the problems created by having
too many subscriptions. It is strongly recommended that the user does not
change the default values (especially for the hard limits).
There are a number of symptoms that can indicate that a DPU is overloaded
with subscriptions. These are:
6. DPU failover
If the user’s system experiences SBP Limiter alarms or has DPUs reject
subscriptions, the proper course of action is to go to the source (e.g., the
The first step in this process it to identify the offender(s) (those programs or
stations that are requesting too many subscriptions). The SBPLimits function
block provides statistics attributes for that purpose. These attributes display
the name (Id) and subscription count (Cnt) from the biggest subscribers.
Loop1Id and Loop1Cnt – provide the name (Id) and number (Cnt) of
subscriptions from the Loop priority connection with the highest number of
subscriptions.
Note that the Point Browser normally only displays the values for the biggest
subscribers (Loop1, Norm1 and Bgnd1). To see the values for numbers 2
through 5, select “Expert” in the Point Browser’s “View” selection box.
The identities and subscription counts for the top five workstations that are
subscribing to the DPU are shown by the following attributes.
Stn1Id and Stn1Cnt – show the name and number of subscriptions coming
from the workstation issuing the most subscriptions to the DPU.
Note that the Point Browser normally only displays the values for the
workstation issuing the most subscriptions to the DPU (Stn1Id, Stn1Cnt). To
see the values for numbers 2 through 5, select “Expert” in the Point
Browser’s “View” selection box.
After determining whom the biggest subscribers are, the next step is to
modify them to reduce the number of subscriptions they issue to the DPU.
The following list covers some basic methods for doing this.
Only as a last resort should the Hard Limits be increased. Increasing the
limits used by the SBPLimits function block runs the risk of overloading the
DPU.
Remember that the SBPLimits function block only causes the DPU to reject
new subscriptions. Subscriptions that already exist are not limited. In order
to reduce the number of subscriptions to a DPU to the configured limits, the
existing subscriptions will have to be reduced below the configured limits.
Existing subscriptions can be shed (eliminated) by either resetting the DPU
or by forcing unsubscribe. Unsubscribes may be forced by closing the
application that is issuing them (e.g., close the maxVUE displays, close
maxSTORIAN, etc.). When those applications are restarted, they will have
to issue new subscriptions to the DPU. Thus, they will come under the limits
configured in the SBPLimits block.