[noise]
In this video we will be configuring the PI to
PI Interface. This
PI ProcessBook display shows the data
on a source PI Server that I would like to bring over to
a destination PI Server.
So assuming that you have already
downloaded PI to PI and installed it on
your computer, you open
up the PI Interface Configuration utility
and start from a blank PI to PI
dot bat file.
You click open and we select the host PI
Server. This is our destination PI Server.
And the interface here
is installed on our source PI Server
and we will be pushing the data to the destination.
So the first thing to take
note of is the point source here; we have chosen
PI to PI and an interface ID of one.
We can also configure
our scan frequencies and add scan classes.
In the PI to PI tab
you enter the source host name; so this
is our source PI Server and I'll type in the name of it.
In the "history recovery" tab we specify
the history recovery parameters such as
the "history recovery only for forced
history recovery" mode.
Otherwise it would be "history recovery upon start-up and
reconnect".
In the "debug" tab we can
look at the interface status tag
on the receiving PI Server and set
the messages to be written to the logs.
In the "location" tab
you can specify overrides for
the location attributes for tags so
no matter what the tag attribute is it is overwritten
for the PI to PI Interface. This is
particularly used when running PI to PI within
collective. This would be used in a situation
where a primary PI collective node receives data directly
from a PI OPC Interface.
The points on the secondary PI collective node are
defined exactly as they are on the primary PI collective
node because they must have matching PI point
databases. Therefore, the overrides must be used
so that the points on the secondary are singed up for the
PI to PI Interface instead of the PI OPC
Interface. Please see the PI to PI User Guide
for more information on the PI to PI
Interface specific configurations.
In addition, "disconnect at start-up" is recommended
for faster start-up times. To do this
you must disable PI SDK and then
go back to "disconnect at start-up" and
we'll check that
and back at "disconnect at start-up" we will enable
that and chose a cache
path where the shared file will be located.
It's also recommended that the
PI Buffer Sub System be
used when sending data from the source PI
Server to the destination PI Server and the Interface
is configured on the source PI Server.
Next we'll create the service.
And we'll start the
Interface. Looking back at our PI
ProcessBook display the destination tag
on the destination PI Server is receiving
data from the source PI Server.
We recovered historical data for this tag using
PI to PI because the data of interest
are after the destination point was
created. If we wanted to recover history before
the destination point was created then we would
have to use the Backfilling with PI Config
procedure.