Setup guide

OSx Migration Cookbook August 30, 2006

9 – Tags

Invalid Tag Types

Area and Unit

tags

External versus

internal tags

Migrating non-

networked tags

When creating install.tag files from OSx or APT, you might

inadvertently include tags of types that PCS 7/505 does not have

such as BATCH tags or custom tag types. DBA will happily add

these tags to its list. However, they will not be compiled to PCS7

and will produce warnings in the compile log file.

If there are AREA or UNIT tags in your install.tag files, AREA and

UNIT tag structures will be created for you by DBA in WinCC.

However, no symbol or faceplate is provided for these.

OSx has the concept of networked and non-networked tags.

Networked tags are those tags that have at least one attribute that is

tied to a PLC memory location. Non-networked tags have no ties to

any PLC. All their attributes represent data in OSx.

PCS 7 has a similar concept with external versus internal tags.

External tags are tied to PLC data, while internal tags are not. Just

as OSx tags can have networked and non-networked attributes, PCS

7 tag structures can have both external and internal tags.

The way to indicate that a tag is non-networked, is to leave the PLC

field blank in an install.tag file. DBA will not accept an install.tag

file whose first tag has no designated PLC. Even if you added non-

networked tags to an install.tag file whose first tag had a designated

PLC and managed to import them in DBA, the project would not

compile to WinCC.

If non-networked tags are an integral part of the OSx system and

must be migrated to PCS 7, then you will need to design and create

new tag structures in PCS 7 that are equivalent to the non-

networked tag types. Since in OSx, there is no distinction between

networked and non-networked tag types, you can clone one or more

of the networked tag structures for your non-networked tags. Just

make sure that all the elements in the new structures are designated

9 – Tags