GSE Systems D/3



GSE D/3 TrendR Interface

to the PI System

Version 1.0.6.0

How to Contact Us

|Phone |(510) 297-5800 (main number) |

| |(510) 297-5828 (technical support) |

|Fax |(510) 357-8136 |

|E-mail |techsupport@ |

|World Wide Web | |

|Mail |OSIsoft |OSIsoft, Ltd |

| |P.O. Box 727 |P O Box 8256 |

| |San Leandro, CA 94577-0427 |Symonds Street |

| |USA |Auckland 1035 New Zealand |

| | | |

| |OSIsoft GmbH |OSIsoft, Asia Pte Ltd |

| |Hauptstra(e 30 |152 Beach Road |

| |D-63674 Altenstadt 1 |#09-06 Gateway East |

| |Deutschland |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. HP-UX 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.

( 1997 - 2005 OSIsoft, Inc. All rights reserved

777 Davis Street, Suite 250, San Leandro, CA 94577

Table of Contents

Introduction 1

Reference Manuals 1

Supported Features 1

Diagram of Hardware Connection 2

Principles of Operation 5

Installation Checklist 5

Interface Installation on Windows 7

Naming Conventions and Requirements 7

PI-SDK & PI-API 7

Interface Directories 8

The PIHOME Directory Tree 8

Interface Installation Directory 8

Installing the Interface as an NT Service 8

Installing the Interface Service Manually 8

Interface Node Clock 9

Windows Time Zone Settings 9

Time Synchronization with the D/3 9

History Recovery 9

Digital States 10

PointSource 11

PI Point Configuration 13

Instrument Tag 13

Point Source 13

PointType 13

Numerical & Discrete 13

Strings 13

Location1 (Interface ID number) 13

Location2 (History recovery) 14

Location4 (Scan class) 14

ExDesc 14

Scan 14

Shutdown 14

Startup Command File 17

PID3.bat 17

PI - D/3 Startup File Utility 19

PI - D/3 Point Builder Utility 21

Interface Operation 23

Startup & Shutdown 23

Troubleshooting 23

Log files 23

Debug mode 23

Revision History 25

Introduction

The PI - D/3 Interface provides one-way communication with the GSE D/3 v10 distributed control system. The interface reads the PI point database to determine which points to read from the GSE Data Historian Service (DHS) Provider.

Note: The D/3 Software must be version 10.0 or later. Because D/3 data is collected using the TrendR mechanism, users must purchase a TrendR license from GSE.

Reference Manuals

OSIsoft

• UniInt End User Document

• PI Data Archive Manual

• PI-SDK Installation Instructions

Supported Features

|Feature |Support |

|Part Number |PI-IN-GSE-D3TR-NT |

|Platforms |Windows (NT4, 2000, XP, 2003) |

|APS Connector |No |

|Point Builder Utility |Yes |

|ICU Control |No |

|PI Point Types |PI 3: Float16, Float32, Float64, Int16, Int32, |

| |Digital, String |

|Sub-second Timestamps |No |

|Sub-second Scan Classes |No |

|Automatically Incorporates PI Point Attribute Changes |Yes |

|Exception Reporting |Yes |

|Outputs from PI |No |

|Inputs to PI: Scan-Based / Unsolicited / Event Tags |Scan-based |

|Maximum Point Count |None |

|Uses PI-SDK |Yes |

|PINet to PI 3 String Support |No |

|* Source of Timestamps |PI server or D/3 |

|* History Recovery |Yes |

|* Failover |No |

|* UniInt-based |Yes |

|* Vendor Software Required on PI-API / PINet Node |Yes |

|* Vendor Software Required on Foreign Device |Yes |

|Vendor Hardware Required |No |

|* Additional PI Software Included with Interface |Yes |

|Device Point Types |Analog and digital |

* See paragraphs below for further explanation.

Source of Timestamps

By default, the interface will use the PI Server time to timestamp incoming D/3 data. Optionally, the timestamps provided by the D/3 may be used to timestamp the data which is stored in the PI Data Archive. This is done simply by adding the /dt option to the interface startup file (see batch file discussion below). WARNING: Users must be aware that the PI Server will not accept data possessing timestamps which exceed the PI Server time by more than 10 minutes. If the interface detects that the time offset is greater than 10 minutes, it will override the /dt option and use PI server time to timestamp the data.

UniInt-based

UniInt stands for Universal Interface. UniInt is not a separate product or file; it is used exclusively to develop OSIsoft interfaces. The purpose of UniInt is to provide consistent behavior across as many of our interfaces as possible. It also allows for the rapid development of new interfaces. In any UniInt-based interface, the interface uses some of the UniInt-supplied 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

The customer is required to purchase the following software from GSE:

• D/3 TrendR DHS Provider

The DHS Provider must be installed on the same computer where the interface will run. Without the DHS provider, the interface will not be able to connect to the D/3.

Additional PI Software Included with Interface

Included in the setup kit are two setup utilities; The first utility creates an interface startup file and the second utility helps to build PI-D/3 points on the PI server. For more details, see the following sections entitled PI-D/3 Startup File Utility and PI-D/3 Point Builder Utility.

Diagram of Hardware Connection

[pic]

Principles of Operation

At startup the interface evaluates the command-line parameters to get the PI server name, D/3 node name, user name, and password. Additionally, the interface ID number, scan frequencies, timestamp source, and history recovery settings are determined. If all required parameters are found, the interface attempts to connect to the D/3 and PI server.

The interface then queries the PI Point Database to determine which PI points are to be associated with the interface. Once all the interface points have been added the interface’s internal lists, data collection may be begin.

Input

This interface connects to the D/3 system via an OLE DB provider known as the D/3 DHS Provider. All data is retrieved by polling the D/3 through the use of the DHS Provider’s GET LAST VALUE commands.

Outputs

The D/3 interface does not support output points. In other words, data may be collected from the D/3 but not sent to the D/3.

Installation Checklist

For users who are familiar with running PI interfaces, this checklist serves as a useful reminder for the primary installation steps. However, if you are not familiar with PI interfaces, you should return to this section after reading the rest of the manual in detail.

1. Run the PI-SDK setup kit. This will install the PI-API and PI buffer server as well.

2. Run the PI D/3 interface setup kit (pid3setup.exe).

3. Check that PI D/3 has been installed as an automatic service. Assign administrator privileges to the service PID3. This is necessary for the interface to start automatically upon reboot.

4. Synchronize the interface clock with the D/3 clock using the net time command.

5. Run the utility (pid3BatFileMaker.exe) to create the interface startup file (pid3.bat).

6. Set up PI security for the interface node, if necessary (i.e. PI trust table).

7. Choose a point source. Do not use the characters R, T, L, C, G, Q, 9, or @.

8. Run the utility (pid3PointBuilder.exe) to build PI points on the PI server.

9. If building PI points using tools other than the pid3PointBuilder tool, assign the following PI point attributes accordingly:

Location1 is the interface instance number.

Location2 specifies if the point should undergo history recovery.

Location3 is not used.

Location4 is the scan class or update rate (0 – 4).

InstrumentTag contains the alias name of the TrendR tag.

10. Reboot the computer. Allow the interface service to start and check the pipc.log file for the proper startup messagesa and any error messages.

11. Confirm that the D/3 points are actively collecting data by using a PI client such as DataLink or ProcessBook. Confirm that the PI values correspond to those on the D/3 system.

12. Confirm that the PI buffer service is actively working and that data is passing through the buffer (i.e. bufutil.exe).

Interface Installation on Windows

OSIsoft recommends that interfaces be installed on PI-API nodes instead of directly on the PI Server node. A PI-API node is any node other than the PI Server node where the PI Application Programming Interface (PI-API) has been installed (see the PI-API Installation Instructions 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-API node (once again, see the PI-API Installation Instructions 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-API 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 pid3.exe and that the startup command file is called pid3.bat_new.

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 pid31.exe and pid31.bat for interface number 1, pid32.exe and pid32.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.

PI-SDK & PI-API

The PI-SDK (Software Development Kit) and PI-API (Application Programming Interface) must be installed prior to installation of the interface. The PI-SDK and PI-API setup kits are included in the interface distribution.

Interface Directories

The PIHOME Directory Tree

The PIHOME directory tree is defined by the PIHOME entry in the pipc.ini configuration file. This pipc.ini file is an ASCII text file, which is located in the WinNT or Windows 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 PIHOME directory 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\GSE D3 TrendR\

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

Installing the Interface as an NT Service

To install the interface, run the interface setup file. This will unpack the interface executable, the startup file utility, PI D/3 point builder utility, and the interface documentation. The setup kit will install the interface to run as an automatic Windows service. The user must assign administrator privileges to the PID3 service for it to function properly.

NOTE: The interface service is installed with a dependency on the PI buffer server. Consequently, the interface service will not start unless the buffer server is running. The PI buffer server allows the interface to collect and store data in the event that the PI server becomes unavailable. The PI buffer server is installed as part of the PI-API.

Installing the Interface Service Manually

Change to the directory where the pid3.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 |Pid3.exe –install –depend “tcpip bufserv” |

|Automatic service |Pid3.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 |Pid3.exe –install –depend tcpip |

|Automatic service |Pid3.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 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.

Interface Node Clock

Windows Time Zone Settings

The correct settings for the time and time zone should be set in the Date/Time control panel. If local time participates in Daylight Savings, from the control panel, configure the time to be automatically adjusted for Daylight Savings Time. The correct local settings should be used even if the interface node runs in a different time zone than the PI Server node.

Make sure that the TZ environment variable is not defined. The currently defined environment variables can be listed by going to Start | Settings | Control Panel, double clicking on the system icon, and selecting the environment tab on the resulting dialog box. Also, make sure that the TZ variable is not defined in an autoexec.bat file. When the TZ variable is defined in an autoexec.bat file, the TZ variable may not appear as being defined in the System control panel even though the variable is defined. Admittedly, autoexec.bat files are not typically used on NT, but this does not prevent a rogue user from creating such a file and defining the TZ variable unbeknownst to the System Administrator.

Time Synchronization with the D/3

The interface computer MUST have its clock synchronized with the D/3 clock. Failure to do this will result in improper operation of the interface. To do so, execute the following command from a Windows command prompt of the interface computer:

C:\> net time \\D3name /set /yes

History Recovery

The PI-D/3 interface is able to recover historical data from the D/3 on a point-by-point basis. This mechanism allows the interface to undergo disconnection with the D/3 for a limited time without any loss of data.

History recovery is performed upon startup of the interface and upon re-connection to the D/3.

To enable this feature, the user must specify the maximum number of days over which the data recovery should extend. This is done by adding /hr=n to the pid3.bat file, where n is the maximum number of recovery days. The value of n cannot exceed 5 days and must be a whole number.

For example, adding /hr=3 to the pid3.bat file will cause the interface to recover up to 3 days of data should the interface or D/3 become unavailable.

IMPORTANT: Data is recovered for the time period starting at the last timestamp in the PI Data Archive. For this reason, all PI points marked for history recovery should have their Shutdown attribute set to zero. Otherwise, history recovery will only extend to the point at which the SHUTDOWN state was written to the archive.

Not all points will undergo history recovery. Only those marked with a non-zero Location2 will be processed (see Location2 in PI Point Configuration).

Digital States

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

PI digital states are discrete values represented by strings. These strings are organized in PI as digital state sets. Each digital state set is a user-defined list of strings, enumerated from 0 to n to represent different values of discrete data. For more information about PI digital tags and editing digital state sets, see the PI Data Archive Manual for Windows NT and Unix manual.

An interface point that contains discrete data can be stored in PI as a digital tag. A Digital tag associates discrete data with a digital state set, as specified by the user.

• Control_Block_Manual digital set: Local, Manual, Auto, Remote, Compout, CompsetP

• Control_Block_Operator digital set: Local, Operator, Auto, Remote, Compout, CompsetP

System Digital State Set

Similar to digital state sets is the system digital state set. This set is used for all tags, regardless of type to indicate the state of a tag at a particular time. For example, if the interface receives bad data from an interface point, it writes the system digital state bad input to PI instead of a value. The system digital state set has many unused states that can be used by the interface and other PI clients.

There are no interface-specific System Digital State Set states for this interface.

PointSource

The PointSource is a single, unique character that is used to identify the PI point as a point that belongs to a particular interface. For example, one may choose the letter D to identify points that belong to the PI-D/3 interface. To implement this, one would set the PointSource attribute to D for every PI Point that is configured for the PI-D/3 interface. Then, if one uses /ps=D on the startup-command line of the PI-D/3 interface, the interface will search the PI Point Database upon startup for every PI point that is configured with a PointSource of D. Before an interface loads a point, the interface usually performs further checks by examining additional PI point attributes to determine whether a particular point is valid for the interface. For additional information, see the /ps argument.

Several subsystems and applications that ship with PI 3 are associated with default point source characters. The Totalizer Subsystem uses the point source character T, the Alarm Subsystem uses G and @, Random uses R, RampSoak uses 9, and the Performance Equations Subsystem uses C. Either do not use these point source characters or change the default point source characters for these applications. Also, if one does not specify a point source character when creating a PI point, the point is assigned a default point source character of L. Therefore, it would be confusing to use L as the point source character for an interface.

PI Point Configuration

The PI point is the basic building block for controlling data flow to and from the PI Data Archive. A single PI point must be built for each D/3 tag requiring historical data collection. Use the point attributes below to define what data to transfer.

Instrument Tag

This field contains the alias name of the TrendR point.

Point Source

All points defined within the PI Point Database for use with the PI D/3 interface must share a common point source. The point source can be any single, alpha-numeric character not currently used by another interface. Do not use the characters R, T, L, C, G, Q, 9, or @ as these are reserved for other PI processes.

PointType

Numerical & Discrete

The PI point type should be compatible with the D/3 field data type.

|D/3 Data Type |PI Point Type |

|Real |Float16, Float32, Float64 |

|Integer |Int16, Int32 |

|Discrete |Digital (requires digital state set) |

Strings

This interface supports string data from the D/3 when the PI server is PI3.

Exception testing for strings is specified by the exception max point attribute. Any positive value in the exception max field will cause a string comparison to be done with the last string sent to PI. If the strings differ, then the new value will be sent to PI. To turn exception reporting off, set the exception max attribute to zero.

Location1 (Interface ID number)

Location1 contains the interface number. The interface number must match that specified in pid3.bat file by the parameter /ID=n, where n is a positive integer. This allows several instances of the interface to be active while still using a single point source character.

Location2 (History recovery)

A non-zero Location2 indicates that a point is marked for history recovery. Typically, points of special importance are chosen for history recovery. Please read History Recovery for more information regarding proper setup of this feature.

Location4 (Scan class)

Location 4 is the scan class number. Scan classes are defined by including /f=hh:mm:ss in the command file pid3.bat where hh, mm, and ss represent hours, minutes, and seconds respectively. The scan class specifies the rate at which a D/3 tag is polled for new data. The scan class number is determined by the order of definition within the command file. The following example declares scan classes of 1 minute, 30 seconds, and 10 seconds:

/f= 00:01:00 /f=00:00:30 /f=00:00:10

Consequently, setting location4 to 1 would indicate the point should be polled at rate of 1 minute. Similarly, setting location4 equal to 2 or 3 would specify a polling rate of 30 or 10 seconds respectively.

ExDesc

This is the extended descriptor attribute. The extended descriptor is limited to 80 characters.

Performance Points

For UniInt-based interfaces, the extended descriptor is checked for the string “PERFORMANCE_POINT”. If this character string is found, UniInt treats this point as a performance point. See the section called “Performance Points.”

Scan

By default, the Scan attribute has a value of 1, which means that scanning is turned on for the point. Setting the scan attribute to 0 turns scanning off. If the scan attribute is 0 when the interface starts, SCAN OFF will be written to the PI point. If the scan attribute is changed from 1 to 0 while the interface is running, SCAN OFF will also be written to the PI point after the point edit is detected by the interface.

There is one other situation, which is independent of the Scan attribute, where UniInt will write SCAN OFF to a PI point. If a point that is currently loaded by the interface is edited so that the point is no longer valid for the interface, the point will be removed from the interface, and SCAN OFF will be written to the point. For example, if the PointSource of a PI point that is currently loaded by the interface is changed, the point will be removed from the interface and SCAN OFF will be written to the point.

Shutdown

The Shutdown attribute is 1 (true) by default. The default behavior of the PI Shutdown subsystem is to write the SHUTDOWN digital state to all PI points when PI is started. The timestamp that is used for the SHUTDOWN events is retrieved from a file that is updated by the Snapshot Subsystem. The timestamp is usually updated every 15 minutes, which means that the timestamp for the SHUTDOWN events will be accurate to within 15 minutes in the event of a power failure. For additional information on shutdown events, refer to PI Data Archive for NT and UNIX.

Note: The SHUTDOWN events that are written by the PI Shutdown subsystem are independent of the SHUTDOWN events that are written by the interface when the /stopstat=Shutdown command-line argument is specified.

One can disable SHUTDOWN events from being written to PI when PI is restarted by setting the Shutdown attribute to 0 for each point. Alternatively, one can change the default behavior of the PI Shutdown Subsystem to write SHUTDOWN events only for PI points that have their Shutdown attribute set to 0. To change the default behavior, edit the \PI\dat\Shutdown.dat file, as discussed in PI Data Archive for NT and UNIX.

Bufserv

It is undesirable to write shutdown events when Bufserv is being used. Bufserv is a utility program that provides the capability to store and forward events to a PI Server, allowing continuous data collection when the Server is down for maintenance, upgrades, backups, and unexpected failures. That is, when PI is shut down, Bufserv will continue to collect data for the interface, making it undesirable to write SHUTDOWN events to the PI points for this interface.

Startup Command File

Command-line arguments can begin with a / or with a -. For example, the /ps=F and –ps=F command-line arguments are equivalent.

The interface startup file name has a .bat extension. The Windows continuation character is a carat (^) and allows one to use multiple lines for the startup command. The maximum length of each line is 1024 characters (1 kilobyte). The number of flags is unlimited and the maximum length of each flag is 1024 characters.

The included utility (pid3BatFileMaker.exe) aids in configuring the PI-D/3 interface startup command file. This utility is discussed in a later section.

PID3.bat

The command line parameters used in the startup file (pid3.bat) are described in the following table:

|Parameter |Description |

|/loc |The location/node name of the D/3 Server |

|/un |The D/3 user name |

|/pw |The D/3 user password |

|/host:5450 |The node name of the PI3 server. The port number 5450 should be appended to the host name for |

| |PI3 servers and separated by a colon (e.g. PIServerName:5450). |

|/f=hh:mm:ss,hh:mm:ss |Each scan class is defined with a "/f=". The value before the comma is the scan class and the |

| |value after the comma is the offset from midnight for scheduling the scan class. The classes are|

| |established in the order they are listed on the command line. |

| |(e.g. /f=30,5 - gives a scan class of 30 seconds with a 5 second offset. |

| |/f=1:30,5 or /f=90,5 - will give a scan class of 90 seconds with a 5 second offset. |

| |/f=1:10:0,30:0 - will give a scan class of 70 minutes with a 30 second offset.) |

|/id=# |This number is the interface number and corresponds to the location1 PI point attribute. This |

| |number is also concatenated to the message header. It is used to uniquely identify messages |

| |written by the interface to the pipc.log file. |

|/hr=n |Indicates that history recovery should be performed with an upper limit of 'n' days. |

| |The value 'n' must be a whole number less than or equal to 5. Note: This setting only affects |

| |those points with a non-zero location2 parameter. |

|/dt |Causes timestamps for data values to be taken directly from the D/3. |

The following is an example interface startup command file:

REM pid3.bat

REM

REM This command file passes the required parameters to the process PID3

REM

REM required command line arguments:

REM

REM /loc= location of D/3 DHS Server

REM /un= D/3 DHS user name

REM /pw= D/3 DHS user password

REM

REM /host= PI server name

REM /ps= point source for D3 interface

REM /id= ID appended log messages

REM /f= hh:mm:ss (scan class definition)

REM

REM optional arguments:

REM

REM /dt Causes timestamps to be taken directly from the D/3.

REM Without /dt, the D/3 time is adjusted to PI server time.

REM

REM /hr=n Turns on history recovery and specifies n as the

REM maximum number of past days to recover.

REM

REM /db Causes the interface to send additional debug messages

REM to the file pipc.log

REM

REM Place a space between each argument and no spaces within the arguments.

REM

pid3 /ps=h /hr=3 /id=1 /host=PIserver:5450 /loc=D3server /un=d3manager /pw=alpha /f=00:00:05 /f=00:00:15 /f=00:01:00 /dt /db

REM

REM

REM end of pid3.bat

NOTE: The startup file pid3.bat must be placed in the directory where the interface was installed.

PI - D/3 Startup File Utility

The startup parameters for the PI- D/3 interface must be specified in the batch file pid3.bat. In order to facilitate the creation of this file, a utility (pid3BatFileMaker.exe) is included with the interface distribution kit. The user interface for this utility is shown in Figure 3. Note that the startup file created is a text file. Future changes to the file can be easily made using a text editor such as Notepad.

Figure 3. Utility to create the interface startup file pid3.bat.

PI - D/3 Point Builder Utility

A PI point building utility (PID3PointBuilder.exe) is distributed with this interface.

This utility first prompts the user to enter the D/3 node name, D/3 user name, and D/3 user password as shown in Figure 1.

Figure 1. Opening screen for PI-D/3 Point Building Utility.

This D/3 login information is necessary to request group and tag information from the DHS Provider.

Afterwards, the user is presented with a screen displaying all the groups found on the D/3 node (see Figure 2). The following three steps should be followed to build PI points.

1. Select the D/3 tags to build PI points for.

2. Choose the PI Server and enter PI point attributes to be used.

3. Click on the "Build selected point(s)" button to create the points within PI.

Figure 2. Main screen of PI-D/3 point building utility.

Interface Operation

Startup & Shutdown

The setup kit installs the interface to run as an automatic Windows service. As with all Windows services, it can be started and stopped from the Control Panel Services applet.

Troubleshooting

Log files

The interface will write normal operational messages as well as error messages to the file pipc.log. The messages contained within this log file that pertain to the PI - D/3 interface will be prefixed with "PID3-n", where n is the interface number specified in the startup file.

Debug mode

If more detailed error messaging is required, the interface may be run in debug mode. To do so, simply add the switch “/db” to the command line within the pid3.bat file. When in debug mode, the interface will write additional, descriptive messages to the pipc.log file.

Revision History

|Date |Author |Comments |

|21-Mar-2000 |BG |Version 1.0.0.0 |

|09-Jun-2005 |BG |Version 1.0.6.0 |

|24-Jun-2005 |MKelly |Fixed page numbering, TOC, section breaks. Added missing items |

| | |for supported features table. Made Final. |

| | | |

| | | |

| | | |

-----------------------

D/3 DHS

Provider

GSE D/3

PI D/3

Interface

PI API

PI Server

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download