Professional Documents
Culture Documents
1 2 3 4 5 6 7 8 9 10 11 Simatic: Manual
1 2 3 4 5 6 7 8 9 10 11 Simatic: Manual
Preface, Contents
Quick Start 1
AS View 3
PCS 7/APACS+ OS DBA
Plant View 4
Batch
Users Guide for V6.1 PC Station View 5
Object Attributes 9
Advanced Topics 10
Edition 11/2005
A5E00595269-01
Safety Guidelines
This manual contains notices you have to observe in order to ensure your personal safety, as well as to
prevent damage to property. The notices referring to your personal safety are highlighted in the manual
by a safety alert symbol, notices referring to property damage only have no safety alert symbol. The
notices shown below are graded according to the degree of danger.
Danger
! indicates that death or severe personal injury will result if proper precautions are not taken.
Warning
! indicates that death or severe personal injury may result if proper precautions are not taken.
Caution
! with a safety alert symbol indicates that minor personal injury can result if proper precautions are not
taken.
Caution
without a safety alert symbol indicates that property damage can result if proper precautions are not
taken.
Notice
indicates that an unintended result or situation can occur if the corresponding notice is not taken into
account.
If more than one degree of danger is present, the warning notice representing the highest degree of
danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a
warning relating to property damage.
Qualified Personnel
The device/system may only be set up and used in conjunction with this documentation. Commissioning
and operation of a device/system may only be performed by qualified personnel. Within the context of
the safety notices in this documentation qualified persons are defined as persons who are authorized to
commission, ground and label devices, systems and circuits in accordance with established safety
practices and standards.
Prescribed Usage
Note the following:
Warning
! This device and its components may only be used for the applications described in the catalog or the
technical description, and only in connection with devices or components from other manufacturers
which have been approved or recommended by Siemens.
Correct, reliable operation of the product requires proper transport, storage, positioning and assembly
as well as careful operation and maintenance.
Trademarks
All names identified by ® are registered trademarks of the Siemens AG.
The remaining trademarks in this publication may be trademarks whose use by third parties for their
own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and
software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency.
However, the information in this publication is reviewed regularly and any necessary corrections are
included in subsequent editions.
Training Centers
Siemens Technical Training Center provides extensive training for all levels of plant
personnel to ensure optimal performance from APACS+ and PCS 7 control
systems. Classes include extensive hands-on activities using appropriate
equipment, making the training directly and immediately applicable.
On-line information is available: http://www.sea.siemens.com/sitrain
Siemens also offers a number of training courses to familiarize you with the
SIMATIC S7 automation system. Please contact your regional training center or
our central training center in D 90327 Nuremberg, Germany for details:
Telephone: +49 (911) 895-3200.
Internet: http://www.sitrain.com
Nürnberg
Plant view: the upper panes of the window depict the plant view. The upper left
pane, sometimes called the technological view, provides the hierarchical plant
view, where objects are represented as folders that can be expanded to reveal
their contents or closed to show uncluttered hierarchical relationships. The
upper right pane typically shows details about objects selected in the left pane.
Tabs on the right pane switch between general characteristics of the selected
objects' attributes, some of which are subject to editing and selection.
Physical objects: the lower panes provide hierarchies and details associated with
the physical equipment that makes up the automation system (AS), such as
controllers and I/O modules, and the PCs that provide the data collection,
monitoring, operator interfaces, and data storage. When a controller has been
selected in the left pane, for example, the right pane displays the function
blocks that make up the controller.
Dragging and Dropping Objects: the program typically supports moving objects
from one quadrant to another by dragging and dropping.
Unique Naming
The DBA utility requires objects to have unique names. The name of an object is its
complete hierarchy name. The DBA utility enforces this requirement by adding a
suffix to a name that would otherwise not be unique.
If you create a folder, for example, its default name is Folder. If you create another,
its default name is Folder1, and so forth:
Renaming Objects
Objects can be renamed by right-clicking and selecting Rename from a context
menu.
Colors
Blue--a read-only value, object or attribute cannot be edited.
Green--an object has changed and will not be updated in the target OS until the
change has been compiled.
Cautions
The DBA Utility Overwrites Edits Made with SIMATIC Picture Tree Manager
The DBA utility overwrites manual edits made in SIMATIC Picture Tree Manager.
Do not use the Picture Tree Manager when using DBA to create the Picture Tree.
Instead, edit picture trees with the DBA utility.
Steps
1. Creating a New WinCC Batch Project 6.1
2. Creating a DBA Project
3. Adding APACS+ AS Nodes to a Project
4. Adding an OS to a Project (PC station definition)
5. Adding Applications to an APACS+ OS Batch Single Station Architecture
Adding Applications to an APACS+ OS Batch Multiple Station Architecture
6. Creating the Plant View
7. Adding a Process Cell to the Plant View
8. Adding Batch Type
Adding a Phase Type
Adding a Parameter to a Phase Type
Adding an Equipment Property Type
Adding Process Tag Types
Adding a Unit of Measure
Adding an Enumerated Data Type
3. Select the .xml file associated with the legacy project. The default name is 4-
mationSession.xml. Click the Open button.
A Command Status window opens and shows the progress of the import.
4. Ensure that the hierarchy settings in the project match the settings used in the
original DBA 4-mation session (in the topic Ensuring Unique Object Names see
Hierarchy Settings for details). Failure to match the original hierarchy results in
the creation of duplicate symbols in existing graphics.
5. For each root folder in the plant view, right click and select the Edit Folder
Properties feature to associate the folder with a PCS 7 OS server application
6. Associate the folder with the same OS Server application as in the legacy
application. Do this by checking the appropriate OS under Assigned
Components and clicking the OK button:
7. Repeat steps 5 and 6 for each root level folder in the plant view.
8. Set the OS Area level setting in the Hierarchy Settings to level 2, as shown
below:
Notice
If you do not first delete the existing symbols from the graphics, the new symbols
will not be placed.
3. If you have created custom graphics in your old project, add folders to the
picture tree having the same names as these graphics. If you do, when you
compile the project, the DBA utility automatically associates these .pdl files
with the folder names in the PCS 7 OS picture tree.
Block Icons
All block icons have be updated in V6.1 to provide support for the following:
• Name field back-lighting when there is navigation to a picture using loop-in-
alarm
• Alarm group display replacement to support alarm lock
• A new attribute to define where a faceplate opens
Faceplates
All faceplates for V6.1 have been updated to provide support for the following:
• Alarm group replacement to support alarm lock
• Alarm lock icon
• Buttons to increase or decrease controller output and setpoint
• Selection of one- or two-step faceplate operation (two-step operation provides
a confirmation dialog box)
• Pinable icons to keep faceplates open when a new picture is opened
Opening
The utility opens by default to the most recently closed project. No project is
displayed when the utility is first run.
To open another existing project from the DBA utility program:
Select File > Open Project
An Open dialog box appears.
Browse as necessary and select the project of interest (DBA Utility projects
have the file extension .dba)
To open a recently opened project from the DBA utility program:
Select File, then select the description of a recently opened file, as shown
below:
Saving
A project can be saved while underway by any of the following actions:
Select File > Save Project
or
Press the Ctrl + S keys
or
Click the save button from the toolbar:
A project must be saved before the first compile to an OS. The Save Project As
window appears if you attempt to compile a project that has not been saved.
Saving Project as
This function saves the current project under a different name at a specified
location.
Select File > Save Project As and select an appropriate location. Note that the
utility supplies the filename extension .dba.
Siemens recommends saving projects in the SIMATIC Manger Project folder to
simplify backups.
Closing
Select File > Close to close a project. If any changes were made since the project
was last opened, the utility gives you an opportunity to save your work before it
closes.
Exiting
Select File > Exit to leave the utility completely. If you try to exit from a project with
unsaved changes, the utility cautions you and gives you an opportunity to save
your changes before exiting.
3. Click the Generate I/O Tags checkbox to generate I/O tags automatically from
the I/O modules in the configuration without inserting HMI comments for each
of them.
4. Click the Generate Global Tags checkbox to generate global tags
automatically from the global variables except for those variables that are
ARRAY type or already exposed by other HMI comments.
5. Click the Write Alarm Acknowledgements and Alarm Lock Status to the
Controller check box to write alarm acknowledgements and alarm lock status
to the controller. Leaving this box unchecked is useful if controller security has
been turned on, or if you want to prohibit writes to the controller for any other
reason.
6. Select the System Path Browse button (or enter the resource names and
system paths and press the OK button). The system path is typically
x:\Program Files\ProcessSuite\4-mation.
For information about the HMI Overlay File see HMI Comment Injection (HMI
Overlay File).
7. The APACS+ Browser window opens, showing all possible offline databases
stored in the folder. The illustration below shows a typical APACS+ resource
selected through the browser:
The default project name is New. An asterisk following the name indicates that the
project contains changes that have not been saved:
The PCS 7 OPC Server AS Properties dialog box opens (its fields are initially
empty):
2. On the General tab, click the Generate... (browse) button to select the CSV
file that contains the OPC Server configuration.
An AS Node Name field is automatically filled in, but can be edited as
necessary.
3. Click the Connection tab to configure the connection to the OPC Server as
follows:
The Delimiter field, a string value, specifies the delimiter used to group
similarly named tags into objects. This only affects tags that are not already
grouped by the OBJECTINSTANCE column (described in TAGS Header
Format Recognized by the CSV Processor, below).
For example:
The CSV file may include the following tags that are not yet grouped by the
OBJECTINSTANCE column:
PIC100_PV
PIC100_SP
PIC100_V
If the delimiter is set to “_”, the tags will be grouped into a tag structure called
PIC100 with individual elements named PV, SP, and V.
Values in the Min Tags Per Struct and Max Tags Per Struct fields provide
further hints. Tag structures with less than Min Tags Per Struct or more than
Max Tags Per Struct will not be created.
You can provide the Exclusions field string values of instance names to
exclude from processing (see the screen capture above for an example).
These are provided in a comma-separated list.
Element Description
ADDRESS Required column that specifies the address of the tag. This must be complete.
NAME Required column that specifies the name of the tag.
TYPE Required column that specifies the type of WinCC Tag to create (for example, . BIT,
DWORD, TEXT8, etc.)
DESCRIPTION Optional column that specifies a description of the tag. This is unused by default,
but can be referenced by the DBATypeSystem for #comment tags.
OBJECTINSTANCE Optional column that is used to group multiple tags into an instance of an object of
the specified name. Note no checking is done to make sure all instances of objects
have the same number of tags or the same tags with the same name and type.
OBJECTTYPE Optional column that is used to specify the type name of the object. All objects
should specify the same value, but the consistency is not checked. If no type is
specified, then no WinCC tag structure will be created.
PATH Optional column that is used to define hierarchy to the Tags and Objects which can
be used by the picture tree wizard.
EXTERNAL Optional column that specifies if the tag is Internal or External. If "0", then Internal,
otherwise External.
INITVALUE Optional column that specifies the START VALUE of the tag.
PERSIST Optional column that specifies if the tag should be persisted. Default is false.
SYNC Optional column that specifies if the tag should be synchronized to the redundant
partner. Default is false.
Element Description
MSGNAME Required column that specifies the name of the message. This is required by the
DBA but not used by WinCC.
REFERENCE Required column that specifies how the MSG should be attached to an object. The
following list defines the options:
empty: Attach to all tags with the NAME that matches the CMT attribute.
OBJECTTYPE name: Attach to all tags with the NAME that matches the CMT
attribute that is part of the objects of the specified TYPE.
OBJECTINSTANCE name - Attach to all tags with the NAME that matches the
CMT attribute that is part of the objects of the specified INSTANCE name.
other: Attach to all tags with the NAME that matches the reference string.
ENABLED Optional column that specifies if the message is enabled or not. Default is TRUE.
CTRTRIGGERTAG Required column that specifies the tag in the controller that triggers the message.
This must refer to an absolute tag name. This value will be monitored by the
EventStateCalc engine and when the condition is present, will set the condition in
the TRIGGERTAG.
CTRTRIGGERBIT Optional column that specifies the bit of the CTRTRIGGERTAG that triggers the
message. Default is 0. This value can also contain complex comparison logic to be
described by the EventStateCalc engine design document.
TRIGGERTAG Optional column that specifies the tag that will trigger the message.
TRIGGERBIT Optional column that specifies the bit of the TRIGGERTAG that triggers the
message. Default is 0.
ACKTAG Optional column that specifies the tag that will maintain the ACK state of the
message.
ACKBIT Optional column that specifies the bit of the ACKTAG for this particular message.
DISABLETAG Optional column that specifies the tag that will maintain the DISABLED state of the
message
DISABLEBIT Optional column that specifies the bit of the DISABLETAG for this particular
message.
P1 to P10 Optional columns that specify the P1 - P10 attributes of the message.
Notice
BOOLEAN TRUE columns can be specified as -1, 1, true, or t.
FALSE columns can be specified as 0, false, or f.
Notice
The line numbers in the sample file provided below are included only for reference
(and to show where CRLFs actually occur), These line numbers do not appear in
the actual file. In the table below, to facilitate viewing, line breaks have been
inserted in the Line Content column. As a result, It would not be possible to extract
the Line Content lines with a simple copy-and-paste operation and process them
with the CSV Processor without first removing these line breaks.
illustration
The DBA utility responds by displaying a Command Status window, which includes two
progress bars, one labeled Command, the other labeled Step. When the procedure
finishes, the Command portion indicates this with the notation Done. The illustration
below is typical, but can vary according to type of AS
node:
The Command Status Step section shows a progress bar at 100% when the
procedure finishes.
3. To see a log of the loading or updating process, click the Show Details button.
Loading controller object results in a detailed display of controller object
characteristics. This display appears in the lower-right quadrant of the DBA utility's
main window::
The Show Details feature is especially useful to confirm that a small change to a
controller node is reflected in the project. The button also leads to a function that
archives the displayed details as a text file.
An alternative to step 2, above, is to select from the menu bar Run > Update
Controller Objects. Doing so updates all AS nodes marked as changed, not just
the selected nodes.
See the advanced topic, Controller Objects.
Notice
If Close When Complete is enabled, the Command Status window
automatically closes, unless the Show Details box is checked or there are errors
or warnings.
Notice
If you change the name or type of an object, the original object appears in the list
as deleted. The new object's name and type appear with the status of Add.
By default the edit box is empty and no injection occurs. If the edit box points to a
properly formatted comma-separated variable (CSV) file, then the information from
that file is inserted into the 4-mation export file before it gets processed by DBA. As
a result, HMI comments of any type can be inserted into any part of the controller
configuration without modification to the existing controller configuration.
• Lines beginning with a semicolon (;) are regarded as comments and ignored.
• The injection processor supports the EXCLUDEMBRCOMMENTS comment
command, which for the DBA utility, in effect removes existing HMI comments
from the MBR. This comment can be added to any line in the CSV injection file.
PIC_100 SINGLE_LOOP
VA_100 VALVE_A
PLANT_A HMI:|GLOBAL1|:TYPE=REAL
AA_100 HMI:START:TYPE=BOOL
If Tagname is not present, DBA logs a warning to identify the tagname that
could not be found. DBA also posts warnings/errors if the HMIComment TYPE=
Defined Type File either does not exist or has errors. These warnings and
errors include the associated tagname. If an HMI comment is currently in the
Controller Configuration, DBA posts a warning, identifying the tagname for
which a duplicate HMI comment exists. DBA then uses the comment found in
the controller configuration.
PLANT_A: The line PLANT_A (PLANT_A is the name of the Resource/ACM)
causes DBA to add the HMI comment HMI:|GLOBAL1|:TYPE=REAL to the
Resource Sheet. DBA creates a tag in the OS for this global variable. The
Resource Sheet in this example is called PLANT_A.
AA_100: The line AA_100 causes DBA to add the HMI comment
HMI:START:TYPE=BOOL to the sheet PLANT_A.AA_100 where PLANT_A is
the Resource Name and AA_100 is the Program Block instance name. The tag
START of type BOOL is created when DBA compiles to the OS.
Notice
Every folder must have an OS assigned somewhere in its ancestry. See Assigning
an OS to a Plant View Folder.
You can combine the automated and manual methods, renaming as necessary.
The illustrations below show, on the left, a plant view with three unpopulated
folders: Folder, Folder1, and Folder2. Below the folders are three templates
created with the auto-assign function: Templates, Templates1, and Templates2.
The illustration on the right shows the result of dragging the contents of the
templates into the folders, leaving the templates empty.
The illustration below shows the same plant view after the empty templates have
been deleted.
When the cursor hovers above a folder, the cursor becomes a plus (+) sign,
There are some restrictions to drag and drop operations regarding batch projects.
Phase (PHASE_AFB), Unit (UNIT_AFB) and batch parameter (for example,
INBOOL_AFB) block types can not be dragged to ordinary plant view folders.
These are special blocks used for linking to components in a process cell. Refer to
the appropriate topics under the title Adding Batch Components to a Process Cell
for details concerning the use of these blocks.
If you attempt to drag a batch block to a an ordinary plant view folder, the following
message is displayed:
This similar message is also displayed if you attempt to drag multiple controller
objects (including an entire AS node) and at least one of the controller objects is a
batch block:
Lifebeat Monitor
Notice
For the PCS 7 Lifebeat Monitoring System to operate correctly, the
RESOURCE_STATUS_AFB block for each controller must be mapped to the PCS
7 OS.
If you have a valid Simatic APACS+ DBA Batch license installed and have created
a process cell, objects will be auto-assigned to the process cell. In addition to
assigning the objects, the program creates unit classes and instances
corresponding to each UNIT_AFB block in the 4-mation Configuration. It also
creates phase types and phase Instances corresponding to each PHASE_AFB
block in the 4-mation configuration. Refer to the discussion of Process Cell
Attributes in Adding a Process Cell to the Plant View for details regarding the
strategy the DBA utility uses in creating phase types.
• Select the object and press the keyboard Delete key (one object at a time).
• Select the object and press the keyboard Delete key (when done from plant
view detail list view, this technique allows multi-deletion).
• Drag a symbol from the plant view and drop it on an AS list view (one object at
a time).
Notice
The folder name and the picture name as displayed in DBA should be kept the
same to avoid confusion for those maintaining the system.
The bottom right pane provides a Value column for entering the PC station
name, Node_052 in the example below:
4. If your system architecture includes more than one PC station, you can add
and name them now or return to this step later.
After a PC station is added, you can add an application to it.
See Adding Applications to an APACS+ OS Batch Single Station Architecture and
Adding Applications to an APACS+ OS Batch Multiple Station Architecture.
2. Right-click the PC station and select Add Application from the context menu:
4. In the Offline MCP File value field, use the browse button to find the name
of the current DBA project. This DBA project resides on the system performing
engineering functions. In the architectural drawing above, this is Node_065.
5. In the Online MCP File value field, browse to or enter the network address of
the online or target .MCP file. In the architectural drawing above, this file
resides in Node_077:
1. Right-click the PC station that is destined to be the OS server and select Add
Application from the context menu:
3. In the Offline MCP File value field, use the browse button to find the name
of the current DBA project. This DBA project resides on the system performing
Note: Before specifying the MCP file for a standby OS server, you must first
create a dummy or placeholder OS project so that the MCP file exists.
4. In the Online MCP File value field, browse to or enter the network address of
the offline or target .MCP file. In the architectural drawing above, this file
resides in Node_079.
Note: If this field is not filled in correctly before a Simatic batch compile with
the Download selected, the DBA utility displays a warning. The WinCC Project
Duplicator creates the Online MPC file automatically when it deploys the
Offline MCP file. When first setting up the system, it is preferable to perform as
OS compile only, then deploy the project to the online target using the WinCC
Project duplicator. It is also possible to create a dummy or placeholder project
on the online node, which is replaced when the WinCC Project Duplicator
deploys the offline project.
7. Repeat these steps for every OS sever or OS server pair in your system.
Note: It is not necessary to configure OS client applications.
4. Use the browse button if it is available or enter information directly. Check the
OK button to register any changes.
Notice
Multiple OS nodes can not be assigned to the same .mcp file.
If you press Rename, the OS name becomes selected, editable text. Type the
desired name and press the Enter key or move the cursor off the edit box and
click.
• All of the archive tags available in the WinCC project. This cached information
is useful for browsing archive tags in Batch Phase and Process Tag
parameters. Note that the archive tags are configured in the WinCC Project
using WinCC Explorer and the Tag Logging editor. See Configuring WinCC
Tags for Archiving.
• All of the alarm types and classes that have been configured in the WinCC
project (using the OS Project Editor).
A cache is maintained for each OS in the DBA project, and it is updated by DBA
automatically every time an OS is compiled. It is also possible to update this cache
manually. To update the cache manually:
1. Locate the PC station containing the OS of interest.
2. Right-click the OS application.
3. Select the Refresh OS Cache option.
Refer to the discussion of process cell attributes in Adding a Process Cell to the
Plant View for information on how the DBA utility creates phase types as a result of
a drag-and-drop operation.
Drag-and-Drop Tip
It is possible to create a phase type and instance with a single drag-and-drop by
dragging the phase onto a unit or equipment folder. This action creates a phase
type in the folder and an instance of the phase type in the process cell folder.
4. Click the parameter in the phase and select the Attributes tab:
The limits of an instance of a phase type can be modified to reflect the actual
limits of the phase parameter.
Description: A free-form text description of the parameter.
Setpoint ID: An optional field for entry of an integer identifier that an external
program using the Simatic Batch API can use to identify the parameter.
To update all instance of the unit class, refer to Updating All Instances of Unit
Class, Phase Type, and Process Tag Type.
0 = StainlessSteel
1 = Ceramic
2 = Teflon.
Procedure
1. Expand the process cell to display the Process Tag Type. Right-click the
Process Tag Type folder. A Context Menu appears:
7. After renaming the enumerated values, select them in turn and assign them
values. The following illustration shows the enumerated data type Plant State
with an enumerated value Hold given the value 3:
Having been defined and assigned values, the enumerated data types are
available as data types in parameters.
Exporting
1. Expand the process cell to reveal the batch types folder.
Note: Standard data types, such as integer, are automatically included for all batch
projects and therefore are not available for import/export.
4. Use the selection button to move batch types between the lists:
5. If you only wanted to export the enumerated data type Plant State, for
example, the Selected Batch Types list would look like the following:
Importing
If an imported batch type has the same name as an existing batch type, the
program renames the type it is importing rather than overwriting the existing object.
In the topic Program Operations and Conventions see the subtopic Unique Names.
1. Expand to process cell to reveal the batch types folder.
2. Right-click the batch types folder.
A context menu appears:
Note: Standard data types, such as integer, are automatically included for all batch
projects and therefore are not available for import/export.
Author: A free-form text field for identifying the engineering entity that created the
process cell.
Comment: Free-form text field to annotate the process cell in any way.
Description: A free-form text description of the process cell.
The attributes Reuse Existing Type and Reuse Existing Type with Same Name
determine the strategy that the DBA utility uses automatically to create unit
classes and phase types. This strategy applies during
• automatic assignment of an AS node to the plant view
• dragging and dropping an AS unit or phase block to the process cell or
batch type folder.
Reuse Existing Type: This attribute determines the strategy for DBA to use when
it detects that a potentially new unit class or phase type exists that matches an
existing unit class or phase type (all parameters are identical to those of an
existing type, but the type name of the new type is different from the existing
type). You select the reuse strategy by selecting the drop-down list of attribute
values:
• Prompt: The DBA utility never automatically creates a new types. When it
detects a type match, it prompts you, asking whether to reuse the existing
type or to create a new one.
• Yes: The DBA utility always reuses existing types when it detects a type
match.
• No: The DBA utility never reuses existing types when it detects a type
match.
Reuse Existing Type with Same Name: This attribute determines the strategy for
DBA to use when it detects that a potentially new unit class or phase type exists
that matches an existing unit class or phase type (all parameters are identical to
those of an existing type AND the type name of the new type is the same as the
name for an existing type). You select the reuse strategy by selecting the
drop-down list of attribute values:
• Prompt: In this case, DBA will never automatically create a new type.
When it detects that a new type matches an existing type, you will be
prompted as to whether to reuse the existing type or to create a new type.
If you respond yes, the existing type is reused. If you select no, a new type
is created. The type name is the same as the existing name, with a number
attached to make it unique.
• Yes:In this case, DBA always reuses existing types when it detects a type
match.
• No: In this case, DBA always creates a new type, even if it detects an
existing type with identical parameters.
1. Right-click a batch component and select Add Neutral Folder. Folders are
created by a context menu selection available in batch components that
support folders. The following illustration, for example, shows the context menu
for the process cell:
Comment: Free-form text field to annotate the neutral folder in any way.
Description: A free-form text description of the folder.
This action adds a new unit class to the process cell and adds an instance of
the unit to the folder where it was dropped:
Note that while in some cases the DBA utility allows objects to be dragged to the
Objects tab for a particular plant view folder, in addition to allowing objects to be
dragged to a plant view folder. However, batch unit blocks must always be
dragged directly to the plant view. If you try to drag a batch unit to the Objects tab
to the right of the plant view, the following message is displayed:
2. Select the appropriate UNIT_AFB block from the AS configuration and click the
OK button.
The runtime name appears in the Value field:
Unit Class:The class of the unit. You must select a unit class when you create a
unit manually (step 2 in Manually Creating a Batch Unit, above). To change,
click the drop-down button in the Value field ( ) and select among the
3. Select the equipment property to be added to the unit and click the OK button.
Note that dragging and dropping may create a new phase type CHARGE as well
as an instance of the phase in UNIT1. Refer to the discussion of process cell
attributes in Adding a Process Cell to the Plant View for details regarding how
phases types are created when an instance is dragged and dropped.
Note that while in some cases the DBA utility allows objects to be dragged directly
to the Objects tab, in addition to allowing object to be dragged to a plant view
folder. However, batch phase blocks must always be dragged directly to the plant
view. If you try to drag a batch phase block to the Objects tab to the right of the
plant view, the following message is displayed:
Charging:
6. Select each parameter in turn and enter its attributes in the right pane under
the Attributes tab.
Setpoint: The default setpoint for the value. Note that the entry in this field must be
consistent with the data type of the parameter. For Booleans and enumeration,
a drop-down list is used to change the setpoint:
Lower Limit/Upper Limit: These attributes indicate the default lower and upper
limits of the parameter instance for the data types float and integer.
Note in the illustration above the OS>>, Archive>>, and Type>> buttons are
available to aid your selection by filtering or limiting the number of tags
displayed. In addition, clicking column title bars, for example Tag Name,
toggles the column sorting between ascending and descending values for tag
name. The Columns>> button leads to a checklist that determines which tag
characteristics are listed in columns.
Author: A free-form text field for identifying the engineering entity that created the
equipment module.
Comment: Free-form text field to annotate the equipment module in any way.
Description: A free-form text description of the equipment module.
Prerequisites
• The process tag type must exist before you can add an instance of it. See
Adding Process Tag Types.
• If the process tag is to be used for archiving, tags to be archived must have
been previously configured using the WinCC Tag Logging Archives function.
See Configuring WinCC Tags for Archiving.
Procedure
1. Create a process tag type instance if necessary in the process cell hierarchy.
Select and right-click the unit.
A context menu appears.
5. Select each parameter in turn and enter its attributes in the right pane under
the Attributes tab.
Description: A free-form text field for a description of this instance of the phase.
Runtime Name: This is a linkage to the controller parameter block (for example,
InReal, InBool, etc.)
Setpoint: The default setpoint for the value. Note that the entry in this field must
be consistent with the data type of the parameter. For Booleans and
enumeration, a drop-down list is used to change the setpoint:
Lower Limit/Upper Limit: These attributes indicate the default lower and upper
limits of the parameter instance for the data types float and integer.
WinCCArchive: This attribute is only present if the parameter type indicates
Archive = yes. If this attribute is not present and is required, you must change
the Archive attribute in the corresponding parameter type and update all
instances of the type.
Prerequisites
Determine which OS Server is to be used for a tag logger. If this server has not
been configured in the DBA utility program, configure it before proceeding. See
• Adding Applications to an APACS+ OS Batch Single Station Architecture
• Adding Applications to an APACS+ OS Batch Multiple Station Architecture
• The tags to configure in the WinCC archive are created by the DBA utility when
the project is compiled. Compile the OS containing the WinCC Tags to be
archived before completing the following procedure.
1. It is necessary to run WinCC Tag Logging so that it runs concurrently with the
DBA utility. Select Start > Simatic > WinCC > Windows Control Center 6.0.
The Control Center opens. If the Control Center does not open to the current
project, close the displayed project and open the current project.
2. Select Tag Logging from the icons available in the left pane.
The Tag Logging window opens.
3. Using the Archives icon in the top left pane, create an archive and add WinCC
Tags to the archive. Use the Archive Wizard to automate this process. Refer
to WinCCc on-line help for details.
4. Return to the DBA utility program and refresh the OS cache by right-clicking
the OS node and choosing Refresh OS Cache in the context menu. Refer to
Updating OS Cache.
Add the tags you wish to archive. In the topic Adding a Phase see the subtopic
Assigning a WinCC Archive Tag.
3. Click the checkbox next to the batch server and click the OK button.
Related topics
Procedures
Notice
If you are compiling a DBA project that includes a single OS Server, be sure that
the WinCC runtime is not active. If you are compiling a DBA project that includes
multiple OS Servers, be sure that the WinCC Explorer is either closed, or, if
running, does not contain an opened WinCC Project.
To compile all OSs in the DBA Utility Project, do any of the following:
• Select Start Compilation
• Press the F5 key
OS Compile Options
Entire OS: Compiles the entire OS project. This is the only option available the first
time an OS is compiled. It is also the only option available the first time an OS
is compiled after upgrading the DBA utility program. When Entire OS is
selected, all tags, alarms, structures and elements created by the DBA utility
are deleted and replaced with new objects during the compilation.
Changes: This is the default option for a previously compiled project. Only
changes made since the last compile are compiled.
The following options are ordinarily checked:
Tags and Messages: If this box is checked, all tags and messages are created. In
most cases this should be checked.
Create/Update Block Icons: If this box is checked, .pdl files are updated as part of
the compile process.
Picture Tree: If this box is checked, the picture tree or trees of the PCS & OS
Server are updated.
When the selection of options is satisfactory, click the Compile button.
An error related to duplicate or missing symbols produces a Command
Status... error message. See Checking for Duplicate and Missing Symbols.
The result of a compilation is written to a log, which can be stored as a text file on a
hard disk drive or other secondary memory. The log is visible by clicking the Show
Details checkbox.
The Save button saves the timestamp, message, and level information displayed
when the Show Details button is clicked. A Save As dialog box opens for saving
this information in a .LOG file.
If an OS requires recompiling, the new or changed objects are rendered in green.
In the illustration below, Area1 has changed because new objects have been
added beneath it. Note that only folders that have added or deleted items will be
marked as changed (colored green). Folders that contain an item that was modified
will not be marked as changed since only the item changed, not its parent folder.
In addition, the top level folder that is assigned to an OS will be marked as
changed if any of its subfolders or items are changed.
Recompiling this OS results in a message in the log like the one shown in the
following fragment from a log file:
Object attributes listed in the right pane can be sorted in ascending or descending
alphanumeric order (a toggle) by clicking column headers. For example, to sort by
value, click the column header cell labeled Value. To switch between ascending
and descending order, click the header cell again.
See also:
Importing and Exporting Object Attributes
Object Attribute Editor
Alarm Attributes
Graphics Attributes
Alarm Priority
There is an alarm priority attribute for every alarm that can be generated for an
object.
Each alarm that can be generated for the object can be assigned a unique priority,
from 0 to 16 (where 16 is the highest priority and 0 the lowest).
To change the alarm priority, click on an alarm priority object from the Detail pane
of the OS view and enter a value from 0 to 16
The WinCC Alarm Logging feature determines the Alarm Classes and Alarm
Types that are available for an object. See the on-line help file linked to this topic
for more information: Start > Simatic > WinCC > Window Control Center 6.0 >
Alarm Logging
Message Class
An alarm class setting determines the message class for every message that can
be generated by an object. A pulldown list shows all defined message classes in
the WinCC alarm logging function.
Message Type
A message type setting determines the message type (within a selected message
class) for every message that can be generated for an object. A pulldown list
shows by number all of the message types defined for the selected class. The DBA
utility program reads this type number but cannot read the words or phrases
associated with the number. To determine these, you must examine them from the
WinCC Explorer:
1. Select Start > Simatic > WinCC > Window Control Center 6.0 > Alarm
Logging.
A list of message classes appears in the upper right pane of the display
(Alarm, Warning, Tolerance, etc):
3. Select the Message Type of interest (such as Tolerance High) and click the
Properties button.
A Type window opens and reveals the type number.
Returning to the DBA utility, a Type attribute contains a pulldown menu that allows
selection by number of a type supported by a message class. In the illustration
below, the class is Warning and the available types are Type1, Type2 and Type3.
Use the procedure listed above to determine the meaning of these types.
Note: The alarm and class pull-down menus are only available for controller
objects that meet these conditions:
• The objects have been assigned to a folder.
• The folder has been assigned to an OS.
• The OS has been assigned to an OS server.
• The OS server has been compiled at least once.
OR
• The Updating OS Cache function has been enabled for the OS server.
You can reduce the information displayed by unchecking the Show... buttons. You
can begin editing immediately by clicking the Value cell for the object of interest
and replacing the current value with a new value. You may, however, wish to filter
and sort the objects first.
The Category << and Name>> buttons filter (hide) an object's attributes object to
make it easier to focus on the attributes of interest.
Click the Category<< button to uncheck (hide) attribute types. If you were
interested only in alarm priority, for example, uncheck the other types. Click the
Category<< button again to register your choice.
Any action that reduces the number of objects displayed is recorded in the title bar
(see 1, below). Note, too, that you can sort the displayed objects by column value
by clicking the column heading. To sort by name for example, click the heading
labeled Name (see 2, below). Clicking a column once provides an ascending sort;
clicking again toggles to a descending sort. This feature is especially useful if you
want to see alarms sorted by priority value.
The Name<< button provides additional filtering. To display only the L - Priority,
for example, click the Name<< button and uncheck all but the L - Priority box.
Then click Name<< again to apply the filter.
Clicking Export or Import opens a dialog box for entering a file name. The default
directory for exports and imports is the directory used as a source for the controller
objects.
"ASTagName","ASTagPath","OSTagName","Category","Name","Description","Value"
"RMSC_532","""RMSC_532"","""",0","RMSC_532","Alarm Priority","Alarm
Disabled","Alarm Disabled","0"
"RMSC_532","""RMSC_532"","""",0","RMSC_532","Alarm Priority","Bad
Quality","Bad Quality","0"
"RMSC_532","""RMSC_532"","""",0","RMSC_532","Graphics","SF","Symbol
File","@Bailey Symbols.pdl"
"RMSC_532","""RMSC_532"","""",0","RMSC_532","Graphics","SN","Symbol
Name","@BAILEY_RMSC/1"
"RMSC_533","""RMSC_533"","""",0","RMSC_533","Alarm Priority","Alarm
Disabled","Alarm Disabled","0"
Required columns
If a file is created or edited and then used to import object attributes, the required
columns are
ASTagName: the name of the AS object whose attribute is being defined (for
example, SINGLE_LOOP). This name corresponds to the string found in the
Name column of the AS View tab's AS Objects List View (on the right). This
is a required field for AS object changes, and should be left blank for non-AS
object changes.
ASTagPath: the address of the AS object whose attribute is being defined (for
example, LC.LC_PUR.X2320.SINGLE_LOOP). This name corresponds to the
string found in the AS Address column of the AS View tab's AS Objects List
View (on the right). This is a required field for AS object changes, and should
be left blank for non-AS object changes.
OSTagName: the OS tag that is created by the DBA and is used only to reference
objects that are non-AS objects such as batch objects (for example,
Process$Cell/X2320/SINGLE_LOOP). This is a required field for non-AS
object changes.
Category:This column is the category of the attribute being defined (for example,
Graphics) and is related to the Category column of the attribute editor tab
(top right). This is a required field. Case must be correct.
Name: This column is the name of the attribute being defined (for example,
DecimalPlacesPV) and is related to the Name column of the attribute editor
tab (top right). This is a required field. Case must be correct.
Description: the description of the attribute being defined (for example, PV
Decimal Places To Display) and is related to the Description column of
the attribute editor tab (top right). This is an optional field, but allows the user to
customize the descriptions of attributes which are unchangeable through the
DBA interface.
Value: the value of the attribute being defined (for example, 2) and is related to the
Value column of the attribute editor tab (top right). This is a required field.
In summary
ASTagName, ASTagPath, and OSTagName columns locate the object to be
changed.
Category and Name columns locate the specific attribute on the selected object to
be changed.
Description and Value columns define the new values to be written into the DBA
database.
Log Files
If you want to retain a log file recording the results of an import, select the Details
button while the import is in progress and the percent-complete window is
displayed. Save the results when the import is complete.
interest. Click the heading again to toggle between ascending and descending
sorts.
• Include All Resources - list all controller objects loaded. To list objects for a
specific controller, ensure that the checkbox is unchecked, and select the
controller in the Controller objects list.
• Include Assigned - can be used in conjunction with Include All Resources,
lists all controller objects for the selected resource, even if they have been
assigned to the picture tree (if they have been assigned to the picture tree,
they won't normally show up in the list unless this box is checked).
• Include Only Changes - list all controller objects that have changed (been
added or modified) since the most recent update-controller-objects operation. If
you Update Controller Objects then check this box and Update Controller
Objects again, the list of controller objects is empty.
Notice
These checkboxes control how the program runs and are independent of individual
projects. If you make changes to these checkboxes and exit the project, the
changes remain in force when you reopen the project or open a different project.
This is true even if you exit a project and elect not to save changes.
Clicking an error in the Validation Results window opens the plant view hierarchy
as necessary to locate and display the tag that failed validation.
Correcting Duplicate Object Errors
The usual remedy for duplicate objects is to apply the techniques described in
Ensuring Unique Object Names. Then click the Validation Results tab and click
the Validate button again to ensure that the remedy worked.
Correcting Missing Tags Errors
The validate function also checks for missing tags, which are marked as objects
not found in the controller. This includes changes to tag names, physical paths, or
types. A missing-tag error can also be caused by selecting a different source option
than the one used to create the current picture tree.
Note that a tag can be both missing and duplicate. This can happen if an object
has been removed from a controller and its name conflicts with another object's
name. Missing tags are rendered in blue. Duplicated tags are rendered in red and
must be resolved or the propagation fails.
Invalid Symbols Detected during Compile
In the case of a compile error, a Command Status... error message appears.
When you close Command Status... error message, the window associated with
Invalid Symbols is visible in place of the AS View:
The Validate Results button does not validate the batch equipment module, a
function performed elsewhere. See Batch Validation.
If controller objects contain identical structures and function blocks, usually a few
characters of uniqueness text make it possible for PCS 7 OS to distinguish among
them. When you right-click an AS resource and select the function Auto Assign
Resources to the Plant View, the DBA Utility provides an opportunity to apply a
prefix or suffix to the folder and picture names as they are created in the working
template. Applying a prefix or suffix does not by itself create unique OS tag names.
Hierarchy Settings
The functions for controlling hierarchy settings are found by selecting File >
Properties and the Hierarchy tab. The Hierarchy window opens. Functions
invoked through this window create unique OS tag names.
But note that existing folder names are not truncated automatically if their
name exceeds the Max Characters limit. Note also that the Max Level and
Max Characters limitation do not apply to hierarchies created with the Auto
Assign Resources to the Plant View button.
• Include in Name checkbox determines whether the folder name in the plant
view is added to the OS tagname.
• With Separator A backslash character is an optional separator. A backslash
is always inserted before the original tagname. When With Separator is
checked, a backslash is inserted between folder names as well.
• OS Area determines a level in the hierarchy that is the root of the picture trees.
This is derived from the plant hierarchy. In the illustration below, the OS Area
checkbox selects Level 1. Level 1 corresponds in the plant view as Process
Cell and Plant. The resulting PCS 7 OS shows Process Cell and Plant at the
top of the hierarchy.
This section describes the first two steps in this process, defining an HMI Comment
in 4-mation and building a Defined Type File.
The following table defines terms used within this section:
Term Definition
4-mation HMI Comment A standard 4-mation comment with a very specific format. It can
be entered on any 4 mation configuration sheet type except
structured text. There are two categories of 4-mation HMI
Comment:
Individual Variable HMI Comment
Structured Variable HMI Comment
Individual Variable HMI Comment A 4-mation HMI Comment or Defined Type Variable Comment
that defines an Individual OS Variable to be created in the OS.
Not all attributes are supported when used as a 4-mation HMI
Comment.
Structured Variable HMI Comment A 4-mation HMI Comment that defines a Structured OS
Variable to be created in the OS. The TYPE attribute must be
defined and reference a valid Defined Type File.
Defined Type File A formatted ASCII file that defines a Structured OS Variable
Type and associated Messages. The file consists of the
following formatted lines:
Defined Type Instruction Comment
Defined Type Variable Comment
Defined Type Message Comment
Defined Type Instruction Comment A line in a Defined Type File that provides instructions other
than variables and messages to the DBA utility during the
propagation process (e.g. @INCLUDE lines to include other
Defined Type Files).
Defined Type Variable Comment A line in a Defined Type File that specifies an attribute of an OS
structure. Every instance of the structured OS tag creates a
single OS tag with the following name:
StructuredTagName.AttributeName
where the StructuredTagName is the name of the structured
tag and AttributeName is the name of the attribute created
by the Defined Type Variable Comment.
Defined Type Message Comment A line in a Defined Type File that specifies a message in the
OS. Every instance of the structured OS tag creates a message
associated with that particular instance.
Individual OS Variable A single tag in the OS created in response to Individual
Variable HMI Comments either as 4-mation HMI Comments or
as Defined Type Variable Comments.
Structured OS Variable A structured tag in the OS created in response to Structured
Variable HMI Comments.
Structured OS Variable Type A structured tag definition in the OS. One structured OS tag
definition is created in response to multiple Structured Variable
HMI Comments that have the same TYPE attribute.
Notice
1. The ionub characters "[" and "]" and the user-defined global variable
characters "|" and "|" are not required for communications. However, they
should be used in the HMI comments to aid in identifying the type of
variable since they are used and seen when referencing the variables in
the 4-mation software. The iochan "%", the embedded global variable
character "#", and the array element characters "[" and "]" are required for
communications and must be used. See Variable Source Syntax.
2. Note that only the comment text appears in the edit field above the cells in
4-mation in the form of attribute=parameter. The comment delimiters are
not visible.
Except for I/O channel or global variables, the HMI comment should refer only to
variables or standard function blocks on the sheet containing the HMI comment.
Although it is possible to refer to variables on other sheets if their path is started at
the program level, using this syntax should be avoided for two reasons:
• The variable type cannot be determined, which could possibly produce an
incorrect reference to the variable.
• The HMI comments become very long and difficult to read
The following image shows an example of a Structured Variable HMI Comment in
4-mation for the SINGLE_LOOP function block:
Notices
• This comment is a single line within 4-mation.
• The OS tag name is PI_1000 since the TAG / ALIAS attribute was not specified.
• The I/O channel description entered in the 4-mation Configuration software is not
available as a softlist parameter and therefore cannot be referenced using the ">"
syntax for the DESC attribute. However, the ENGH, ENGL, and UNITS are
obtained from the IO channel softlist values.
Solution 2:
The second solution is to configure several 4-mation HMI Comments with the same
source field value as follows:
(*HMI:%PI_1000:TYPE=REAL:DESC=Flow pressure*)
(*HMI:%PI_1000:ENGH=>%PI_1000.MaxScale*)
(*HMI:%PI_1000:ENGL=>%PI_1000.MinScale*)
(*HMI:%PI_1000:UNITS=>%PI_1000.EngUnits*)
When multiple HMI comments are written, the source field in each case must be
identical.
Solution 3:
The third solution is to configure a single 4-mation HMI Comment of the TYPE
"SAIC" and is as follows:
*HMI:%PI_1000:TYPE=SAIC:DESC=Flow pressure*)
The I/O channel type codes can be obtained from the [CHAN_TYPE_DEFS]
section of the APACS MODULE.INI file.
Notice
Note PCS 7 OS Option DBA automatically configures the ENGH, ENGL, and
UNITS when this method is used.
Solution 4:
The fourth solution works only for I/O Channels and does not require any 4-mation
HMI Comments. In the 2 – Define Picture Tree DBA configuration step, check the
Auto-Generate I/O Tags checkbox and then press the Load Controller Objects
button. This button processes the APACS+ controller configuration and builds the
list of controller objects that is displayed in the Controller Objects list box. All the
IO Variables are included in the list, allowing any one or more IO variables to be
assigned to the picture tree. This solution automatically configures the DESC,
ENGH, ENGL, and UNITS from the appropriate IO Channel softlist values.
Notice
This comment is a single line within 4-mation and placed on a sheet that has a
discrete local variable called OOS
Line Code
01 ;DEFINEDTYPE:SINGLE_LOOP
02 ;SCHEMAVERSION:1.0.0
03 [4.00 - 6.0 PCS 7]
04 HMI:TAG_STRUCTURE=SINGLE_LOOP_AFB
05
06 HMI:"SINGLE_LOOP_AFB":TAG=#blocktype:TYPE=TEXTREF
07 HMI::TAG=#areaname:TYPE=TEXTREF
08 HMI:@StripEnclosingApostrophes(VALUE;.DESC.VALUE):TAG
=#comment:TYPE=TEXTREF
09 HMI::TAG=#graphic:TYPE=TEXTREF
10 ; Include common controller information
11
12 HMI:@INCLUDE(CONTROLLER_COMMON[4.00 - 6.0 PCS 7])
13 ; Include alarm mapping information
14
15
16 HMI:@INCLUDE(ALARM_MAP[4.00 - 6.0 PCS 7])
Notice
The line numbers in the code sample provided above are included only for
reference and do not appear in the actual Defined Type File
Defined Type Files can be viewed and changed using any standard ASCII file
editor or the Defined Type File Editor. The Defined Type File Editor can be started
by selecting Start > Programs > Simatic > DBA >Defined Type Editor. See
Defined Type File Editor.
;DEFINEDTYPE:SomeName
where SomeName is replaced with the string that represents the name of the
Defined Type File. This is the string that is defined in the TYPE attribute of the
Structured Variable HMI Comment. This string value MUST match the name of the
Defined Type File as follows:
SomeName.HMI
;SCHEMAVERSION:1.0.0
HMI:TAG_STRUCTURE=SomeName
where SomeName is replaced with the string that represents the name of the OS
structured tag type. This value can be different than the Defined Type Name
directive as shown in the example. No spaces are allowed in this line and
SomeName must be a valid OS structured tag type name.
Comment Directive
Any line that starts with a semicolon (;) is considered a comment and is ignored by
the DBA utility. The only exclusions to this rule are the special Defined Type Name
and Schema Version directives.
Include Directive
Any line that starts with HMI:@INCLUDE is an include directive. The include
directive is used to create modular defined type files. Every include directive line in
a defined type file line is replaced with the contents of the specified section of the
specified defined type file. The include directive includes the specification of the
specific product and version of the section to include and uses the following syntax:
where FileName is the name of the defined type file to insert (without extension)
and Product and ProductVersion define the section to use.
The included file can also contain include directives. The DBA utility supports
nesting of include directives to a maximum of five levels deep. The HMI file for a
single-loop controller, for example, includes by reference two other HMI files as
shown by lines 12 and 16.
The included Defined Type File needs to exist in the same directory as the
including file, normally in the C:\Program
Files\Siemens\Obj\APACS+\Templates directory.
HMI:source{{:attribute=parameter}...}
where the information in braces is optional and the colon (:) separated fields
consist of the following:
• The first field contains the characters HMI and is required.
• The second field contains the source of the OS variable and is also required.
• Optional additional fields contain attribute information for the variable.
The Defined Type Variable Comment must be contained on a single line in the
Defined Type file. There is no line continuation support. The source and parameter
fields can be functions and use the Defined Type File Function syntax of
@FunctionName. This is described in the Built-in Functions and User Defined
Functions sections.
MSG:message:attribute=parameter:...
where multiple attribute / parameter pairs are separated by a colon (:) and consist
of the following:
• The first field contains the characters MSG and is required.
• The second field contains the string value of the Message and is also required.
• Additional fields contain attribute information for the message some of which
are required.
The following table lists the attributes supported for PCS 7 OS messages:
the table below for the class that you would like to use. Once you have selected
a class, formulate the "Class=" entry in the defined type file by entering the
description specified in the table. For example, if you would like to use class 3,
Tolerance, specify Class="Tolerance". [Note: The possible classes are
ultimately dependent on the Alarm Logging configuration of your WinCC
Project. If you have changed the list of available classes, use the Alarm
Logging configuration tool in WinCC Explorer to determine which classes are
available
Class Description
1 Alarm
2 Warning
3 Tolerance
4 PLC Process Control Messages
5 OS Process Control Message System
6 Preventive Maintenance
7 Process Message
8 Operating Message
9 Request for Operator Input
10 Operator Input Message
16 Status Message
17 System, must be acknowledged
18 System, need not be acknowledged
Type= the type of the message. The value of this attribute depends on the class of
the message and the type within the class that you would like to use. The
following are the default types, along with their associated classes, provided
when the OS Project Editor is used during the creation of your WinCC Project.
(Refer to Creating a New WinCC Project for details.) Refer to the table below
for the type that you would like to use. Once you have selected a type, the
"Type=" entry in the defined type file is constructed as follows: add the
"Message Type" number from the table entry to the word "Type". For example,
if you would like to use as "Tolerance High" the type, select
Class="Tolerance" and Type="Type37" (note that there are no spaces
between the word "Type" and the Message Type number (in this example, 37).
Note: The possible types that are available for each class are ultimately
dependent on the Alarm Logging configuration of your WinCC Project. If you
have changed the list of available types for one or more classes, use the Alarm
Logging configuration tool in WinCC Explorer to determine which types are
available for each class.
5 72 Error
6 89 Maintenance
7 106 Process Message
8 122 Process Message
9 139 Request for Operator Input
10 156 Operator Input Message
16 253 Status PLC
16 254 Status OS
17 257 Process control system
17 258 System messages
18 273 Process control system
18 274 Operator input message
MessageTag= the data manager tag name that defines the runtime state of the
message. Usually set to an internal DWORD tag called EventRaw#1. The tag
defined in CalcMsgTag is used as the source tag to drive the value of
EventRaw#1. If an external tag is used directly, the Alarm Lock feature will
not work.
CalcMsgTag= the message source tag used to generate messages outside of the
controller. See the section titled Generating Alarms Outside of the Controller for
more details and an example.
CalcMsgBit= the bit position or specific condition of the CalcMsgTag that will
trigger a message. See the section titled Generating Alarms Outside of the
Controller for more details and an example.
MessageBit= the bit of the MessageTag value that triggers the message.
AckTag= the data manager tag name that is used at runtime to acknowledge the
message. Usually set to an internal DWORD tag called EventAck#1. The tag
defined in CalcAckTag attribute is the target tag driven by the value of
EventAck#1
AckBit= the bit of the AckTag that is set when acknowledged.
CalcAckTag= the message acknowledgement target tag used optionally to
acknowledge messages outside of the controller. See the section titled Storing
Alarm Acknowledgements and Alarm Lock Outside of the Controller for more
details and an example.
CalAckBit= the bit position or specific condition of the CalcAckTag that will
acknowledge the message. See the section titled Storing Alarm
Acknowledgements and Alarm Lock Outside of the Controller for more details
and an example
DisableTag= internal tag that's used to suppress a message. Usually set to an
internal DWORD tag called EventDisable#1. This attribute must be provided
if CalcMsgTag and/or CalcAckTag attributes are used, even if this tag is not
used in the HMI to suppress the message. The high word of this tag causes the
Alarm Lock status to be persisted and synchronized. If the Alarm Lock feature
is used, this attribute must be provided as well.
DisableBit= the bit of the DisableTag value that suppresses the message.
Invert= any non-zero value inverts the message triggered when the message bit
defined by MessageTag and MessageBit attributes is 0 instead of 1. If this
attribute is not provided, by default, the message will be triggered when the
message bit is 1.
message field or EventText= the text of the message. Displayed as the
Event column in the Alarm Logging tool in PCS 7 OS. This can include
replacement strings.
ChargeName= this optional field is displayed as the Batch Name column in the
Alarm Logging tool in PCS 7 OS.
Operation= this optional field is displayed as the Operation column in the Alarm
Logging tool in PCS 7 OS.
Freen= this optional field is displayed as the Freen column in the Alarm Logging
tool in PCS 7 OS where n is replaced with 1-5.
ProcessValuen= this optional field is displayed as the ProcessValuen column in
the Alarm Logging tool in PCS 7 OS where n is replaced with 1-10.
The area text of the message is automatically defined by the value of the
#areaname structured variable HMI comment. This value cannot be changed
manually.
EXA:description:attribute=value:...
where multiple attribute / value pairs are separated by a colon (:) and consist of the
following:
• The first field contains the characters EXA and is required.
• The second field contains description of the Extended Attribute.
• Additional fields contain attribute information for the Extended Attribute some of
which are required.
The following table lists the supported Extended Attributes:
AttributeName= name of the extended attribute. Required.
DisplayName= the alias of the extended attribute that will actually display in the
DBA’s GUI. AttributeName value is used if not provided.
Category= category to group different kinds of extended attributes. Required.
Type= type of the extended attribute value. Required .The following types and
APACS+ standard data types can be used as the value:
Type Description
Integer nteger type
Int Same as Integer
Boolean Boolean type
Bool Same as Boolean
Example
The following EXA Comment, extracted from SINGLE_LOOP.HMI, adds the
DecimalPlacesPV attribute to the DBA. This addition makes it possible to assign
the start value of DecimalPlacesPV tag:
Example
If the following attributes and values are used, a PV tag value greater than 50
triggers the analog alarm:
MessageTag=EventRaw#1:MessageBit=12:CalcMsgTag=PV:CalcMsgBit=ANA
LOG;GT;50:
CalcMsgTag can be any analog or discrete tag. CalcMsgBit has the following
formats depending on the type of the alarm condition:
Examples:
Examples:
Controller:
the Alarm Lock status is written to. The following example shows the format of
these Extended Attributes:
EXA:"Controller Event Lock Tag
1":Category="ControllerEventLockTag":AttributeName=EventLockT
ag1:Value=P_OOS:Type=String:Visible=0:
EXA:"Controller Event Lock Tag
2":Category="ControllerEventLockTag":AttributeName=EventLockTag2:
Value=S_OOS:Type=String:Visible=0:
The Alarm Lock status is written to P_OOS and S_OOS tags in this example.
When the Write Alarm Acknowledgements and Alarm Lock Status to the
Controller check box is cleared, Extended Attributes of category
ControllerEventLockTag are ignored, and the Alarm Lock status will be
available only to the OS. The high words of the alarm disable tags declared by
DisableTag and DisableBit attributes in the message comments are actually
used to persist and synchronize the Alarm Lock status. For this reason, the alarm
disable tag always has to be DWORD type and synchronized and persisted.
DisableTag and DisableBit attributes are required in each message comment
if CalcMsgTag and/or CalcAckTag attributes are used or the Alarm Lock feature
is used.
@FunctionName({parameter,...})
where FunctionName is the name of the function and parameter is one or more
parameters. A function can be one of the built-in Defined Type File Functions or a
User Defined Function. All functions return a value that is used for that field or
parameter. The function logic is defined in the VBScript language and must be
XML compliant.
Parameters to a function can be passed as described in the following table:
A parameter type is specified by prefixing the parameter with one of the parameter
types followed by a semicolon (;). For example, the first parameter of the following
function call is passed to the function as a constant and is not to be interpreted as
anything else:
SelectCase4(CONSTANT;HIGH_HIGH,VALUE;.ALARM.ALARM1_TYPE,
ADDRESS;.ALARM.ALARM1_LIMIT)
The second parameter of the example is converted to the specific value of the AS
controller object before calling the function. In this case, the value of the
ALARM1_TYPE softlist value of the ALARM block on the current sheet is passed.
The third parameter of the example is converted to the APACS+ Communication
System Tag Name before calling the function. For example, if the current sheet is
ACM1.Sheet1.Sheet2,
ACM1.Sheet1.Sheet2.ALARM.ALARM1_LIMIT
The first parameter to any function is hidden and provides a reference to the Node
that is being processed. This is commonly referred to as the this pointer or
reference.
The DBA utility converts the Defined Type File into an XSL file before applying it to
any 4 mation HMI Comment. This process of converting the Defined Type File into
XSL is called compiling. The Defined Type File only needs to be compiled once no
matter how many 4 mation HMI Comments reference it. Applying the compiled
Defined Type File to an instance of a 4-mation HMI Comment involves the XML
transformation of the XML node within the exported AS configuration. The functions
of the Defined Type File make use of the XML node and its relatives. An
understanding of the 4 mation XML export format is required to write significant
custom functions and is not described in this document.
For examples of how these functions are used, please see the Defined Type Files
for the Standard Function Block Library.
Line Code
01 [SCRIPT:VBScript]
02 Function GetCurrentDate(oThis)
03 ‘ Return the current date as a string.
04 GetCurrentDate = CStr(Now())
05 End Function
06 Function CalcVolume(oThis, sLength, sWidth, sHeight)
07 CalcVolume = sLength * sWidth * sHeight
08 End Function
09
10 [/SCRIPT]
In this example, line 01 and 10 indicate the start and end lines of the script block.
There can only be one (1) script block per Defined Type File. The function names
must be unique among all script functions defined in all included files. The text in
the script block must be VBScript. The first parameter must be oThis. This is a
reference to the CBOTEXT XML node that is being propagated, however it does
not have to be used. The example GetCurrentDate() function uses the
VBScript function Now() to return the current time. The CalcVolume() function
takes three (3) dimensions and calculates the volume. The script could even
access an external COM object using the VBScript CreateObject() function
including the ActiveX Data Object (ADO) object to read a database.
Using a namespace, a script in an HMI file can be run within its own scope, so
scripts on different included HMI files will not conflict. For example, the following
text can be added to the end of an HMI file to define functions to be executed
during the Update Controller Objects call:
[SCRIPT:VBScript:SM]
function FixUpAddress(nodelist,sPathToBlock,sAddress)
end function
[/SCRIPT]
The functions can be invoked during the resolution of the APACS address for each
HMI lines as follows:
HMI:@SM.FixUpAddress(.,.EffectStat):TAG=E_ST65_128:TYPE=RAW:
Notice that the script block defined the script namespace as SM. Therefore it is
required to specify the namespace in the function call. Also notice that the first
parameter is implicit in the function specification to be the 'this' pointer back to the
HMI Comment.
Variable Description
.localvar Individual local variable on current sheet
Default alias: localvar
.localvar[element] Individual local variable array element on
current sheet
Default alias: localvar_index1{{_index2}...}
|globalvar| Individual user-defined global variable
Default alias: globalvar
|globalvar|[element] Individual user-defined global variable array
element
Default alias: globalvar_index1{{_index2}...}
#globalvar Individual embedded global variable
Default alias: globalvar
Requires TYPE= attribute
.[ionub] Individual I/O nub on current sheet.
Default alias: ionub
.[ionub][element] Individual I/O nub array element on current
sheet
Default alias: ionub_index1{{_index2}...}
.fbinst.param Individual softlist parameter of function block
on current sheet
Default alias: fbinst.param
Requires TYPE= attribute
.fbinst.[ionub] Individual I/O nub of function block on
current sheet
Default alias: fbinst.[ionub]
Requires TYPE= attribute
.fbinst.[ionub][element] Individual I/O nub array element of function
block on current sheet
Default alias:
fbinst.[ionub]index1{{_index2}…}
%iochan Individual I/O channel variable
Default alias: iochan
%iochan.param Individual I/O channel softlist
Default alias: iochan.param
Requires TYPE= attributeparameter
.fbinst. References a standard or derived function
block on the current sheet as a defined-type.
(trailing period required)
Default alias: fbinst
HMI:source{{:attribute=parameter}...}
Attribute Descriptions
TYPE= Individual variable APACS+ data type or defined-type variable
standard or derived function block type or I/O channel type.
TAG or ALIAS= The name to be used as the HMI database tagname. If not specified,
the default ALIAS as described in the Variable Source Syntax section
is used.
DESC= Variable description or comment (only for Individual Variable HMI
Comments)
REV= Revision string used to select a specific version from a Defined Type
File. A single Defined Type File can define multiple versions of the
structure based on this attribute. (only for Structured Variable HMI
Comments)
Var Property= Any value other than 4 creates an internal tag in the PCS 7 OS.
Omitting this attribute or setting the value to 4 creates an external
tag.
INTERNAL Same as VarProperty= <any value other than 4>
EXTERNAL Same as VarProperty=4.
Sync= Any non-zero value for this attribute synchronizes the value of the
internal tag with the redundant OS server.
Sync="RSTA=EventCalculator" This special value synchronize the value of an internal tag used as an
alarm acknowledgement tag.
Sync="RAW" Special internal tag used as an alarm trigger tag.
Persist= Any non-zero value for his attribute ensures that the value of the
internal tag persists when the OS server restarts.
Persist="RSTA=EventCalculator This special value ensures that the value of an internal tag used as an
alarm acknowledgement tag persists when the OS server restarts
Persist="RAW" Special internal tag used as an alarm trigger tag.
Attribute Descriptions
HL or ENGH= Engineering high value (default is variable data type specific)
LL or ENGL= Engineering low value (default is variable data type specific)
UNITS= Engineering units text
Attribute Descriptions
ON= ON state message text (default = ON if no OFF message)
OFF= OFF state message text (default = OFF if no ON message)
Attribute Descriptions
LEN= Maximum string length value
Parameter Description
value Use the specified value (must not start with ".")
Text or " " Use the specified text
^ or ^text Current sheet instance when used on a sheet. For the ALIAS, DESC, and
UNITS attributes in a defined-type file, the carat is replaced with the
appropriate parameter value passed down from the associated defined-
type HMI variable and the optional specified text is added.
>.localvar Get local variable localvar initial value
>.param In defined-type file, get the associated standard function block or I/O
channel softlist parameter param initial value
Notice
changes made to an .HMI file are not compiled unless the changes are registered
by the Loading (Updating) Controller Objects function
The Defined Type File Editor creates, edits, and displays ASCII files that define
structured OS variable types and associated messages.
The advantage to using the Defined Type File Editor instead of an ASCII text
edited program is that the Defined Type File Editor parses ASCII text that makes
up defined types so that syntax, properties, and values are easily identified and
edited.
The editor is designed for staff with advanced skills and familiarity with Windows-
based programs. It supports copy-and-paste, for example, but has no menu
commands for functions that select, select all, copy, and paste. It is assumed that
the person using the program is familiar with the keystrokes that invoke these
functions.
The editor supports the following Windows file-handling functions:
It is assumed that the person using the program is familiar with these commands,
too.
Opening an Existing File with the Defined Type Editor (General Tab)
The Defined Type File Editor can be started by selecting Start > Simatic > DBA >
Defined Type Editor.
Open an .HMI file by selecting File > Open and moving if necessary to the
directory containing the .HMI file of interest, typically C:\Program
Files\SIEMENS\DBA\APACS\Templates. Select and open the file.
The file opens in the "General" view, where the file is parsed so that its structure is
revealed. The left pane of a typical file is shown below (this has been derived from
the code provided for the single-loop defined type file in the section titled Defined
Type File Layout and Syntax).
The right pane contains two columns, labeled Property and Value corresponding to
the object selected in the left pane. If the object #blocktype <variable> were
selected in the left pane shown above, the right panel would be as follows:
Elements in the Value column can be changed by clicking and editing them. There
is no syntax or value checking, just as a plain ASCII editor would not check syntax
and value for source code. Edits are reflected in the objects in the left pane.
;DEFINEDTYPE:SINGLE_LOOP
;SCHEMAVERSION:1.0.0
[4.00 - 6.0 PCS 7]
HMI:TAG_STRUCTURE=SINGLE_LOOP_AFB
HMI:"SINGLE_LOOP_AFB":TAG=#blocktype:TYPE=TEXTREF:
HMI::TAG=#areaname:TYPE=TEXTREF:
HMI:@StripEnclosingApostrophes(VALUE;.DESC.VALUE):TAG=#comment:TYPE
=TEXTREF:
HMI::TAG=DecimalPlacesPV:TYPE=DWORD:VarProperty=0:
HMI::TAG=DecimalPlacesOUT:TYPE=DWORD:VarProperty=0:
; Include common controller information
HMI:@INCLUDE(CONTROLLER_COMMON[4.00 - 6.0 PCS 7])
; Include alarm mapping information
HMI:@INCLUDE(ALARM_MAP[4.00 - 6.0 PCS 7])
EXA::Category="Graphics":AttributeName=DecimalPlacesPV:Value=2:Type
=Integer:MinInclusive=0:MaxInclusive=6:Permission=RW:Vis
EXA::Category="Graphics":AttributeName=DecimalPlacesOUT:Valu
e=2:Type=Integer:MinInclusive=0:MaxInclusive=6:Permission=RW
:Vi
The EXA: lines shown above have been broken for purposes of illustration. In the
editor each is rendered properly as a single, continuous line terminated by a single
ASCII carriage-return code.
This ASCII rendition can be edited, and any edits are reflected in objects when the
display is toggled to the General mode. It may be necessary to click the menu
selections View > Refresh to update the display.
In the HMI format mode, it is possible to paste one or more lines of HMI defined
type file ASCII text into a file, then switch to the General mode to edit specific
values.
Advanced Options
The advanced options (View > Advanced options) of Defined Type Editor are
reserved for use by Siemens staff or by customers troubleshooting applications
under close supervision of Siemens staff.