Bailey DCI System Six
Interface to the PI System

Version 1.2.4.2
Rev B

How to Contact Us

Phone / (510) 297-5800 (main number)
(510) 297-5828 (technical support)
Fax / (510) 357-8136
E-mail /
World Wide Web /
Mail / OSIsoft
P.O. Box 727
San Leandro, CA 94577-0427
USA
OSI Software GmbH
Hauptstrae 30
D-63674 Altenstadt 1
Deutschland / OSI Software, Ltd
P O Box 8256
Symonds Street
Auckland 1035 New Zealand
OSI Software, Asia Pte Ltd
152 Beach Road
#09-06 Gateway East
Singapore, 189721

Unpublished – rights reserved under the copyright laws of the United States.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii)
of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013

Trademark statement—PI is a registered trademark of OSIsoft, Inc. Microsoft Windows, Microsoft Windows for Workgroups, and Microsoft NT are registered trademarks of Microsoft Corporation. Solaris is a registered trademark of Sun Microsystems. HPUX is a registered trademark of Hewlett Packard Corp.. IBM AIX RS/6000 is a registered trademark of the IBM Corporation. DUX, DEC VAX and DEC Alpha are registered trademarks of the Digital Equipment Corporation.
PI_BaSystSix.doc

 1997-2005 OSIsoft, Inc. All rights reserved
777 Davis Street, Suite 250, San Leandro, CA 94577

Table of Contents

Introduction

Reference Manuals

Supported Features

Diagram of Hardware Connection

Principles of Operation

Installation Checklist

Interface Installation

Naming Conventions and Requirements

Interface Directories

The PIHOME Directory Tree

Interface Installation Directory

Interface Installation Procedure

Installing the Interface as an NT Service

Installing the Interface Service with PI-Interface Configuration Utility

Installing the Interface Service Manually

Digital States

PointSource

PI Point Configuration

Point Attributes

Tag

PointSource

PointType

Location1

Location2

Location3

Location4

Location5

Convers

InstrumentTag

ExDesc

Scan

Shutdown

Output Points

Trigger Method 1 (Recommended)

Trigger Method 2

Performance Point Configuration

Configuring Performance Points with PI-ICU (NT-Intel)

Configuring Performance Points Manually

I/O Rate Tag Configuration

Monitoring I/O Rates on the Interface Node

Configuring I/O Rate Tags with PI-ICU (NT-Intel)

Configuring I/O Rate Tags Manually

Configuring the PI Point on the PI Server

Configuration on the Interface Node

Startup Command File

Configuring the Interface with PI-ICU

basystsix Interface Tab

Command-Line Parameters

Sample PIFUP6.bat File

Interface Node Clock

Security

Starting / Stopping the Interface

Starting Interface as a Service

Stopping Interface Running as a Service

Buffering

Configuring Buffering with PI-ICU (NT-Intel)

Configuring Buffering Manually

Example piclient.ini File

Appendix A: Error and Informational Messages

Message Logs

Messages

System Errors and PI Errors

Revision History

1

Bailey DCI System Six Interface to the PI System1

Introduction

The Bailey DCI System Six Interface to the PI System provides an interface between the Plant Information (PI) System and the following Bailey systems: Bailey DCI System Six database, Bailey Conductor NT (Console) and Conductor UX (Server) via the Data Access Server (DAS). Conductor NT is the new name for the System Six PWC. Conductor NT can communicate to Infi90 (Harmony Rack and Harmony area controllers), System Six (Harmony DCU), and Freelance controllers. Conductor UX is the new name for the AP6400 and can only communicate to Harmony DCU. The former Bailey System Six system now is analogous to Conductor NT or Conductor UX communicating to Harmony DCU.

The interface runs on Microsoft Windows NT 4.0 or higher. It uses the DMC Data Access Server Interface routines to connect to the Bailey systems. The DMC Data Access Server software must be installed prior the installation of the Bailey DCI System Six Interface. Communication to the Bailey systems is done via TCP/IP. The Bailey DCI System Six Interface can run on a PI-API node or on the PI home node.

Note:Harmony refers to the line of Bailey controllers. Conductor refers to the consoles. Symphony refers to the overall product line which contains Harmony controllers, Conductor consoles, and other components. Maestro NT is an SQL server based historian.

Reference Manuals

OSIsoft
  • PI Server manuals
  • PI-API manual
  • UniInt End User Document
Bailey Controls Co.
  • Data Access Server TCP/IP Programmer’s Guide, Bailey Controls Co., System Division USA - Customization, Version S5R1

Supported Features

Feature / Support
Part Number / PI-IN-BA-SYS6-NTI
Platforms / NTI (4, 2000, XP)
APS Connector / No
Point Builder Utility / No
ICU Control / Yes
PI Point Types / Integer/Float/Digital/String
Sub-second Timestamps / No
Sub-second Scan Classes / No
Automatically Incorporates PIPoint Attribute Changes / Yes
Exception Reporting / Yes
Outputs from PI / Yes
Inputs to PI: Scan-based / Unsolicited / Event Tags / Scan-based
Maximum Point Count / unlimited
Uses PI-SDK / No
PINet to PI 3 String Support / No
*Source of Timestamps / PI Server machine
History Recovery / No
Failover / No
*UniInt-based / Yes
Vendor Software Required on PI-API / PINet Node / No
*Vendor Software Required on Foreign Device / Yes
Vendor Hardware Required / No
Additional PI Software Included with Interface / No
*Device Point Types / Integer/Float/String

* See paragraphs below for further explanation.

Source of Timestamps

The clock on the computer running the PI Server provides the source of timestamps for the values sent by Bailey DCI System Six to the PI System interface. The Interface writes a timestamp that reflects the time at which it receives data from the DAS Server.

UniInt-based

UniInt stands for Universal Interface. UniInt is not a separate product or file; it is an OSIsoft-developed template used by our developers, and is integrated into many interfaces, such as the Bailey DCI System Six to the PI System interface. The purpose of UniInt is to keep a consistent feature set and behavior across as many of our interfaces as possible. It also allows for the very rapid development of new interfaces. In any UniInt-based interface, the interface uses some of the UniIntsupplied configuration parameters and some interface-specific parameters. UniInt is constantly being upgraded with new options and features.

The UniInt End User Document is a supplement to this manual.

Vendor Software Required

Data Access Server for TCP/IP software

Data Access Server TCP/IP Programmer’s Guide, Bailey Controls Co., System Division USA - Customization, Version S5R1

Device Point Types

The interface receives values from the Data Access Server as strings. Depending on the data type and configuration of the PI-Tag the value is either written as String to PI or the interface uses standard functions to try to translate the value to an integer or float value.

Diagram of Hardware Connection

1

Bailey DCI System Six Interface to the PI System1

Principles of Operation

At startup the interface checks all command line parameters. If one of them is out of range, the interface generates an error message and stops. If all parameters are correct, the interface will run the initialization.

During the initialization, the interface tries up to 10 times to connect to the Bailey device, trying at one minute intervals.

Values are demanded from the DCS in a scan-based manner. The WindowsNT part sends a demand to the Data Access Server, which attempts to retrieve data from the Bailey DCI System Six database. Tags are requested in packets of up to 150 tags[1].

1

Bailey DCI System Six Interface to the PI System1

Installation Checklist

For those users who are familiar with running PI data collection interface programs, this checklist helps you get the Bailey DCI System six Interface to the PI System interface running. If you are not familiar with PI interfaces, you should return to this section after reading the rest of the manual in detail.

  1. Install the PI-Interface Configuration Utility (which installs PI-SDK and PI-API)
  2. Verify that PI-API has been installed.
  3. Install the interface.
  4. Define digital states if extended validation is required.
  5. Choose a point source. If PI 2 home node, create the point source.
  6. Configure PI points.
    Location1 is the interface instance.
    Location2controls the extended validation.
    Location3is not used.
    Location4 is the scan class.
    Location5input=0 or output=1.
    ExDesc is not used.
    InstrumentTag is the TAG.ATOM.
  7. Configure performance points using the PI-ICU utility.
  8. Configure I/O Rate tag using the PI-ICU utility.
  9. Configure the interface using the PI-ICU utility or edit startup command file manual. It is recommended to use PI-ICU whenever possible.
    /AP=fpxdc1:51000defines the connection.
  10. Set up security.
  11. Start the interface without buffering.
  12. Verify data.
  13. Stop interface, start buffering, start interface.

1

Bailey DCI System Six Interface to the PI System1

Interface Installation

OSIsoft recommends that interfaces be installed on PI Interface Nodes instead of directly on the PIServer node. A PI Interface Node is any node other than the PI Server node where the PIApplication Programming Interface (PI-API) has been installed (see the PIAPImanual). With this approach, the PI Server need not compete with interfaces for the machine’s resources. The primary function of the PIServer 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, see the 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 shut down for maintenance, upgrades, backups, or unexpected failures.

In most 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 a power failure.

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 interfaces as manual services that are launched by site-specific command files when the PI Server is started. Interfaces that are started as manual services are also stopped in conjunction with the PI Server by site-specific command files. This typical scenario assumes that Bufserv is not enabled on the PI Server node. 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. See the UniInt End User Document for special procedural information.

Naming Conventions and Requirements

In the installation procedure below, it is assumed that the name of the interface executable is PIFUP6.exe and that the startup command file is called PIFUP6.bat.

It is customary for the user to rename the executable and the startup command file when multiple copies of the interface are run. For example, one would typically use PIFUP61.exe and PIFUP61.batfor interface number 1, PIFUP62.exe and PIFUP62.bat for interface number 2, and so on. When an interface is run as a service, the executable and the command file must have the same root name because the service looks for its command-line arguments in a file that has the same root name.

Interface Directories

The PIHOME Directory Tree

The PIHOME directory tree is defined by the PIHOME entry in the pipc.iniconfiguration file. This pipc.ini file is an ASCII text file, which is located in the WinNT directory. A typical pipc.ini file contains the following lines:
[PIPC]
PIHOME=c:\pipc
The above lines define the \pipc directory as the root of the PIHOME directory tree on the C: drive. OSIsoft recommends using \pipc as the root directory name. The PIHOMEdirectory does not need to be on the C: drive.

Interface Installation Directory

Place all copies of the interface into a single directory. The suggested directory is:

PIHOME\interfaces\BaSystSix\

Replace PIHOME with the corresponding entry in the pipc.ini file.

Interface Installation Procedure

The PI-BaSystSix interface setup program uses the services of the Microsoft Windows Installer. Windows Installer is a standard part of Windows 2000. When running on Windows NT 4.0 systems, the PI-BaSystSix setup program will install the Windows Installer itself if necessary. To install, run the BaSystSix_x.x.x.x.exe installation kit.

Installing the Interface as an NT Service

The PI-Bailey DCI System six Interface interface service can be created, preferably, with the PI-Interface Configuration Utility, or can be created manually.

Installing the Interface Service with PI-Interface Configuration Utility

The PI-Interface Configuration Utility provides a user interface for creating, editing, and deleting the interface service:

Service Configuration
Service Name

The Service to Add box shows the name of the current interface service. This service name is obtained from the interface executable.

Display Name

The Display Name text box shows the current Display Name of the interface service. If there is currently no service for the selected interface, the default Display Name is the service name with a “PI-” prefix. Users may specify a different Display Name. OSIsoft suggests that the prefix “PI-” be appended to the beginning of the interface to indicate that the service is part of the OSI suite of products.

Service Type

The Service Type indicates whether the interface service will start automatically or need to be started manually on reboot.

  • If the Auto option is selected, the service will be installed to start automatically when the machine reboots.
  • If the Manual option is selected, the interface service will not start on reboot, but will require someone to manually start the service.
  • If the Disabled option is selected, the service will not start at all.

Generally, interface services are set to start automatically.

Dependencies

The Installed services list is a list of the services currently installed on this machine. Services upon which this Interface is dependant should be moved into the Dependencies list using the button. For example, if API Buffering is running, then “bufserv” should be selected from the list at the right and added to the list on the left. Often interface services also depend on a vendor program, such as the Fisher-Rosemount chipservice. To remove a service from the list of dependencies, use the button, and the service name will be removed from the “Dependencies” list.

When the PI Interface is started (as a service), the services listed in the dependency list will be verified as running (or an attempt will be made to start them). If the dependent service(s) cannot be started for any reason, then the PI interface service will not run.

Note: Please see the PI Log and Operating System Event Logger for messages that may indicate the cause for any server not running as expected.

- Add Button

To add a dependency from the list of Installed services, select the dependency name, and click the Add button.

- Remove Button

To remove a selected dependency, highlight the service name in the Dependencies list, and click the Remove button.

The full name of the service selected in the Installed services list is displayed below the Installed services list box.

Create

The Create button adds the displayed service with the specified Dependencies and with the specified Startup Type.

Remove

The Remove button removes the displayed service. If the service is not currently installed, or if the service is currently running, this button will be grayed out.

Start or Stop Service

To Start or Stop an interface service, use the Start button and a Stop button on the ICU toolbar. If this interface service is not currently installed, these buttons will remain grayed out until the service is added. If this interface service is running, the Stop button is available. If this service is not running, the Start button is available.

The statusof the Interface service is indicated in the lower portion of the PI-ICU dialog.

Installing the Interface Service Manually

One can get help for installing the interface as a service at any time with the command:
PIFuP6.exe –help

Change to the directory where the PIFuP6.exe executable is located. Then, consult the following table to determine the appropriate service installation command.

NT Service Installation Commands on a PI Interface Node or a PI Server node
with Bufserv implemented
Manual service / PIFuP6.exe –install –depend “tcpip bufserv”
Automatic service / PIFuP6.exe –install –auto –depend “tcpip bufserv”
NT Service Installation Commands on a PI Interface Node or a PI Server node
without Bufserv implemented
Manual service / PIFuP6.exe –install –depend tcpip
Automatic service / PIFuP6.exe –install –auto –depend tcpip

When the interface is installed as a service on the PI Server node and when Bufserv is not implemented, a dependency on the PI network manager is not necessary because the interface will repeatedly attempt to connect to the PI Server until it is successful.

Note: Interfaces are typically not installed as automatic services when the interface is installed on the PI Server node.

Check the Microsoft Windows NT services control panel to verify that the service was added successfully. One can use the services control panel at any time to change the interface from an automatic service to a manual service or vice versa.

1

Bailey DCI System Six Interface to the PI System1

Digital States

For more information regarding Digital States, refer to the Data Archive Manuals.

PI 2 Home Node

Digital states are defined by running the Digtl Statdisplay from the PI menu. The states must be contiguous for each status type and may be anywhere within the DigitalStateTable outside of the range 193 – 320, which is reserved for OSIsoft. The digital states need to be defined prior to point configuration. The digital state sets described in the PI3 sections below should be entered into the PI 2 Digital State Table.