Tip:
Highlight text to annotate it
X
[noise]
In this video we will configure
a tag on the destination PI Server
to receive data from the tag on the source PI
Server. So in this PI ProcessBook
display, we can see the source PI
Server data and we already have a
PI to PI interface
configured and running. Configurations
are unique to every situation so please
download the PI to PI user manual at the
tech support download center website.
Chapter seven shows
the PI Point
Configuration. We recommend referring to this while configuring these
points.
To configure the PI tag on the
destination PI Server we'll open PI System Management
Tools and go to the Point Builder. The
tag name must be unique on the PI Server and the first character must
be alphanumeric. Next we'll specify the point
source of the PI to PI
interface; this should match the point source on the PI
to PI interface in the ICU.
In the "archive" tab we can configure exception and
compression similar to any other tag. In the
"classic" tab we configure location one to
match the interface ID listed in the PI
Interface Configuration Utility. Location four
should specify the scan class for this
particular tag.
Please refer to the charts
listed in chapter seven of the PI to PI User
Guide to determine how to set location
two, three, and five based on
your needs for this tag.
Location
two adjust the timezone differences and
clock drift, location three is used for
tag level debugging, and location five
is used to specify the write mode for sending archive
data to the receiving PI Server.
In the "instrument" tag we enter the
tag name of the source tag on the
source PI Server.
We can also enter the tag name
in the "extended descriptor"
or the tag names can
match each other. In addition, user
one can be used to specify the point
ID of the source tag.
We also configure the security for
the point
and save it.
Now by this
point the interface has picked up the new
tag and if we look back to our PI ProcessBook display,
we can see that the destination tag
is receiving data from the source PI Server
therefore we know that we have successfully configured
a PI to PI tag.