Bailey Infi90 Interface to the pi system
Download 0.78 Mb. View original pdf
|
- Navigate this page:
- Bailey Infi90 Interface to the PI System 19Interface Installation
| –ciu# parameter. Location2 is the Bailey PCU (node) portion of the Bailey address. Location3 is the Bailey module portion of the Bailey address. Location4 is the Bailey block portion of the Bailey address. Location5 is the Bailey point type. ExDesc is not used. InstrumentTag is not used. Configure an IO Rate point. 11. Configure the startup command parameters by using the PI ICU or by manually edit the startup command file. OSIsoft recommends using the PI ICU whenever possible. Set the interface node clock. Setup security such that the Interface can write to the PI Server via a PI trust. Start the interface without PI API buffering. Verify data. Stop the interface, start PI API buffering, and restart the interface. Bailey Infi90 Interface to the PI System 19 Interface Installation OSIsoft recommends that interfaces be installed on PI Interface Nodes instead of directly on the PI Server node A PI Interface Node is any node other than the PI Server node where the PI Application Programming Interface (PI API) has been installed (seethe PI API manual) With this approach, the PI Server need not compete with interfaces for the machine’s resources The primary function of the PI Server is to archive data and to service clients that request data. After the interface has been installed and tested, Bufserv should be enabled on the PI Interface Node (once again, seethe PI API manual) Bufserv is distributed with the PI API It is a utility program that provides the capability to store and forward events to a PI Server, allowing continuous data collection when communication to the PI Server is lost Communication will be lost when there are network problems or when the PI Server is shutdown for maintenance, upgrades, backups, or unexpected failures. Inmost cases, interfaces on PI Interface Nodes should be installed as automatic services Services keep running after the user logs off Automatic services automatically restart when the computer is restarted, which is useful in the event of an interruption in electrical power. The guidelines are different if an interface is installed on the PI Server node In this case, the typical procedure is to install the PI Server as an automatic service and install the interface as an automatic service that depends on the PI Update Manager and PI Network Manager services Bufserv can be enabled on the PI Server node so that interfaces on the PI Server node do not need to be started and stopped in conjunction with PI, but it is not standard practice to enable buffering on the PI Server node Download 0.78 Mb. Share with your friends:
|