OSIsoft Honeywell PHD Interface to the PI System
Honeywell PHD
Interface to the PI System
Version 2.1.0.0 to 2.3.0.7
Document Revision A
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 |OSI Software, Inc. |OSI Software, Asia Pte Ltd |
| |P.O. Box 727 |152 Beach Road |
| |San Leandro, CA 94577-0427 |#09-06 Gateway East |
| |USA |Singapore, 189721 |
| | | |
| |OSI Software GmbH |OSI Software, Ltd |
| |Hauptstra(e 30 |P. O. Box 8256 |
| |D-63674 Altenstadt 1 |Level One, 6-8 Nugent Street |
| |Deutschland |Auckland 3, New Zealand |
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.
PI_HWPHD.doc
( 2000-2004 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 4
Principles of Operation 5
Installation Checklist 7
Interface Installation 9
Naming Conventions and Requirements 9
Interface Directories 9
The PIHOME Directory Tree 9
Interface Installation Directory 10
Interface Installation Procedure 10
Installing the Interface as an NT Service 10
Installing the Interface Service with PI-Interface Configuration Utility 10
Installing the Interface Service Manually 12
Digital States 15
PointSource 17
PI Point Configuration 19
Point Attributes 19
Tag 19
PointSource 19
PointType 19
Location1 21
Location2 21
Location3 22
Location4 22
Location5 22
InstrumentTag 23
ExcDesc 23
Scan 23
SourceTag 24
Shutdown 24
UserInt1 25
Output Points 25
Trigger Method 1 (Recommended) 25
Trigger Method 2 26
PIPHDPtBld 26
Performance Point Configuration 27
I/O Rate Tag Configuration 29
Monitoring I/O Rates on the Interface Node 29
Configuring I/O Rate Tags with PI-ICU (NT-Intel) 29
Configuring I/O Rate Tags Manually 30
Configuring the PI Point on the PI Server 31
Configuration on the Interface Node 31
Startup Command File 33
Configuring the Interface with PI-ICU 33
hwphd Interface Tab 36
Command-line Parameters 38
Example PI-phd.bat File 42
PI-PHD Interface System Administration 45
Starting the PI-PHD interface 45
Automatic Service Startup 45
Manual Service Startup 45
Interactive Startup 45
Stopping the PI-PHD Interface 45
Registering the PI-PHD Interface as a Windows NT Service 46
Manual Services 46
Automatic Services 46
Removing the PI-PHD Interface as a Windows NT Service 46
Status, Warning, and Error Messages 46
Interface Node Clock 47
Security 49
Starting / Stopping the Interface 51
Starting Interface as a Service 51
Stopping Interface Running as a Service 51
Buffering 53
Configuring Buffering with PI-ICU (NT-Intel) 53
Configuring Buffering Manually 56
Example piclient.ini File 58
Appendix A Error and Informational Messages 59
Message Logs 59
System Errors and PI Errors 59
Appendix B: Troubleshooting 61
Introduction
The Honeywell PHD Interface (PI-PHD) provides two-way communication with a Honeywell PHD System. The interface program reads the PI point database to determine which points to read from and write to the Honeywell PHD System. This interface may run on a TPS Node, which contains the PHD API from Honeywell or a PHD Client node that connects to the Honeywell PHD System. The customer must be running a Honeywell PHD System.
The PHD System must be at version 100 or higher, and the LCN must be at version 520 or higher. More information can be found in the Totalplant Process History Database Electronic Documentation 100 rev 1 12 AUG 1997.
This version of the interface includes:
1. Reads data from and writes data to a Honeywell PHD system.
2. Point database utility to build csv files from the PHD system to use with PIConfig to create and edit the PIPoint database.
3. History recovery
Reference Manuals
OSI
• UniInt End User Document
• PI Data Archive Manual
• PI-API Installation Instructions
Vendor
A set of manuals in electronic format is available from Honeywell that may be of interest. These manuals are:
• Totalplant Process History Database Electronic Documentation 100 rev 1 12 AUG 1997
• PHD System Manual Document number PIM 030.1 (including a PHD API discussion)
Supported Features
|Feature |Support |
|Part Number |PI-IN-HW-PHD-NTI |
|Platforms |NTI |
|APS Connector |No |
|Point Builder Utililty |No |
|ICU Control |Yes |
|Sub-Second Scan Classes |No |
|PI Point Types |float64 / float 32 / float16, int16 / int32 / |
| |digital / string |
|Automatically Incorporates PI Point 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 |
|* Source of Timestamps |PHD / Configurable |
|* History Recovery |Yes |
|Failover |No |
|* UniInt-Based |Yes |
|* Vendor Software Required on PI-API |Yes |
|Additional PI Software Included with Interface |No |
* See paragraphs below for further explanation.
Source of Timestamps
The timestamps for the data comes from the PHD. The interface calculates the time difference between the PHD and the PI server every 1 minute. This offset is applied to the PHD time stamps prior to sending the data to PI.
With version 1.5 of the interface, the timestamp usage is configurable by adding a startup parameter in the pi-phd.bat file.
/ts=x
0 - default. Use PHD Timestamps and apply difference of PHD server time and PI Server time.
1 - Use PHD Timestamps without applying time difference. This is only done if PHD server time is behind PI server time. If PI server time is behind PHD server time, the timestamps will be adjusted to PI server time.
2 - Do not use PHD Timestamps. Send last value in each scan and use the PI server time.
History Recovery
The PI-PHD Interface retrieves data from PHD for points flagged for history recovery during the time when the interface has been down and no data was collected. Set location 3 to 1 for points that you want history recovery done. The history parameter, /hi=MAX, must also be passed in pi-phd.bat where MAX is the maximum time period the interface will go back in time to retrieve history. The time period must specify whether the period is in minutes, hours, or days as well as specify the number of those periods to go back. Some example time ranges are: 2d (two days), 24h (24 hours), 60m (sixty minutes). If no maximum time period is specified or the time period entered is invalid then the default of two days will be used.
History recovery will be started at interface startup or after a communication failure has occurred and is then resumed between PI and PHD. Data will be retrieved from the PHD starting from the last good value in the PI archive up to the current time, or the MAX recovery time specified in PI-PHD.bat. If good data is not found before the MAX recovery time, an I/O Timeout will be written to the point at the MAX time.
If the /hi parameter is not passed then no history recovery is done.
Failover
There is no Failover for this interface.
UniInt-Based
UniInt stands for Universal Interface, and it is an OSI-developed template used to create many of our interfaces. UniInt is not a separate product or file, it is solely a template used by our developers, and is integrated into the 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. UniInt is constantly being upgraded with new options and features. In any UniInt interface, UniInt uses some of the supplied configuration parameters, and some parameters are interface-specific features of the interface.
The UniInt End User Document is a supplement to this manual.
Vendor Software Required
PHD Server and ‘C’ API from Honeywell.
If interface is to be run on a node other than the PHD Server, the Honeywell PHD Client must be installed on this node.
The PI-PHD Interface is connected to a PHD system that must be at version 100 or higher. The PI-PHD Interface runs on the same NT as the PHD system. If an LCN is connected to the PHD system, the version of the LCN must be 520 or higher.
Diagram of Hardware Connection
[pic]
Principles of Operation
The Honeywell PHD Interface (PI-PHD) provides two-way communication with a Honeywell PHD System. The interface program reads the PI point database to determine which points to read from and write to the Honeywell PHD System. This interface may run on a TPS Node, which contains the PHD API from Honeywell or a PHD Client node that connects to the Honeywell PHD System. The customer must be running a Honeywell PHD System.
The PHD System must be at version 100 or higher, and the LCN must be at version 520 or higher. More information can be found in the Totalplant Process History Database Electronic Documentation 100 rev 1 12 AUG 1997.
Each PHD value includes a “confidence level” between 0 and 100. A useable value is always available if the confidence number is between 0 and 100. One hundred indicates high quality, 0 represents an uncertain result. If no value is available at all, the confidence level becomes -1.
Starting with interface version 2.2.6, the UserInt1 point attribute is used to interpret the PHD confidence factor.
The UserInt1 point attribute will be used to specify the minimum confidence. The default setting for this parameter will be zero, that is, the value is returned if the confidence is zero or greater. If the PHD confidence is below the UserInt1 value, the PI-PHD Interface returns “Bad Input.”
Starting with interface version 2.2, virtual tags on the PHD server can be read.
This version of the interface includes:
4. Reads data from and writes data to a Honeywell PHD system.
5. Point database utility to build csv files from the PHD system to use with PIConfig to create and edit the PIPoint database.
6. History recovery
Installation Checklist
For those users who are familiar with running PI data collection interface programs, this checklist helps get the PI-PHD interface running. If you are not familiar with PI interfaces, return to this section after reading the rest of the manual in detail.
This should have enough detail to get the interface running quickly by an experienced installer.
The typical example below is followed by sections of the document that describe these steps in more detail. If a particular step does not apply, delete the step here and the corresponding section that follows. Remember to put the following sections in the order in which they are in the Checklist (so for this example, the Installation section, then the connection section, then Digital States, etc)
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.
On and Off are required in the System Digital State Table.
5. Choose a point source. If PI 2 home node, create the point source.
6. Configure PI points.
Location1 is the interface instance.
Location2 is the direction. 1 for inputs, 2 for outputs, 3 output timestamp, 4 output timestamp and value.
Location3 is 1 if History Recovery is to be done on this point.
Location4 is the scan class.
Location5 is not used.
ExDesc is the PHD tag to output a timestamp to. This is for when location2=4 that outputs both a value and a timestamp
InstrumentTag is the PHD tag to read or write to.
7. Configure performance points.
8. Configure I/O Rate tag.
9. Edit startup command file by running the PI-ICU to configure interface.
10. Set interface node clock. (Note that this should be deleted if you are running on VMS.)
11. Set up security.
12. (Interface-specific steps, IE: Test the FTP mechanism for PINet to PI 3 string support. See Appendix B for more information.)
13. Start the interface without buffering.
14. Verify data.
15. Stop interface, start buffering, start interface.
Interface Installation
OSI recommends that interfaces be installed on API nodes instead of directly on the PI Server node. An 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 CPU time. 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 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 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 pi-phd.exe and that the startup command file is called pi-phd.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 pi-phd1.exe and pi-phd1.bat for interface number 1, pi-phd2.exe and pi-phd2.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.ini configuration 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. OSI 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\HWPHD\
Replace PIHOME with the corresponding entry in the pipc.ini file.
Interface Installation Procedure
In the installation procedure below, assume that interface number 1 is being installed and that all copies of the interface will be installed in the same directory.
1. Copy the interface files from the installation media to c:\pipc\interfaces\HWPHD\. Create the directory if necessary.
2. If necessary, rename the command file so that it has the same root name of the executable.
3. Alter the command-line arguments in the .bat file as discussed in this manual.
4. Try to start the interface interactively with the command:
pi-phd.bat
If the interface cannot be started interactively, one will not be able to run the interface as a service. It is easier to debug interactively started processes because error messages are echoed directly to the screen. Once the interface is successfully running interactively, one can try to run it as a service by following the instructions below.
Installing the Interface as an NT Service
The PI-PHD 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:
[pic]
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 [pic] 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 [pic] 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.
[pic] - Add Button
To add a dependency from the list of Installed services, select the dependency name, and click the Add button.
[pic] - 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 [pic] and a Stop button [pic] 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 status of the Interface service is indicated in the lower portion of the PI-ICU dialog.
[pic]
Installing the Interface Service Manually
One can get help for installing the interface as a service at any time with the command:
pi-phd.exe –help
Change to the directory where the pi-phd1.exe executable is located. Then, consult the following table to determine the appropriate service installation command.
|NT Service Installation Commands on a PI-API node or a PI Server node |
|with Bufserv implemented |
|Manual service |pi-phd.exe –install –depend “tcpip bufserv” |
|Automatic service |pi-phd.exe –install –auto –depend “tcpip bufserv” |
|NT Service Installation Commands on a PI-API node or a PI Server node |
|without Bufserv implemented |
|Manual service |pi-phd.exe –install –depend tcpip |
|Automatic service |pi-phd.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 spin its wheels until it connects to PI.
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.
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 Stat display from the PI menu. The states must be contiguous for each status type and may be anywhere within the Digital State Table 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 PI 3 sections below should be entered into the PI 2 Digital State Table.
For more information, see the DA manual.
PI 3 Home Node
Digital State Sets
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.
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.
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 H to identify points that belong to the Honeywell PHD interface. To implement this, one would set the PointSource attribute to H for every PI Point that is configured for the Random interface. Then, if one uses /ps=H on the startup-command line of the Random interface, the Random interface will search the PI Point Database upon startup for every PI point that is configured with a PointSource of H. 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.
Case-sensitivity for PointSource Attributes
In all cases, the point source character that is supplied with the /ps command-line argument is not case sensitive. That is, /ps=H and /ps=h are equivalent.
PI 2 Server Nodes
The following point source characters are reserved on PI 2 systems and cannot be used as the point source character for an interface: C, ?, @, Q, T. 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.
Before a PI point with a given point source can be created, the point source character must be added to the PI 2 point source table. For example, if point source P is not defined in the PI 2 point source table, a point with a point source of P cannot be created. This prevents the user from accidentally creating a point with an incorrect point source character.
Defining a Point Source Character in the PI 2 Point Source Table
1. Enter PI by typing the following command from a VMS command prompt:
@pisysexe:pi
2. Select the PointSrc option from the menu.
3. Select New from the menu.
4. Assign a point source next to the Code: field. Also, assign minimum and maximum values for the Location1 to Location5 attributes.
| |Location1 |Location2 |Location3 |Location4 |Location5 |
|Minimum |1 |1 |0 |1 |-20000000 |
|Maximum |20000000 |4 |1 |20000000 |20000000 |
5. Select “Save” from the menu.
PI 3 Server Nodes
No point source table exists on a PI 3 Server, which means that points can be immediately created on PI 3 with any point source character. 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 PIDataArchive. A PIPoint or tag is a single parameter of a PHD point. A single point is configured for each measurement value that needs to be archived. Use the point attributes below to define what data to transfer. For example, a process variable and a setpoint are part of the same point in the Honeywell system; however, in both the PI and PHD systems, parameters are stored as two separate tags.
Point Attributes
Tag
A tag is a label or name for a point. Any tag name can be used in accordance to the normal PI point naming conventions.
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. All points defined in the PI database used by the PHD interface must share a common point source. The point source is a one character variable, for example H. Edit the startup file PI-PHD.bat to specify the point source. For additional information, see the /ps command-line argument and the “Point Source” section.
PointType
Typically, device point types do not need to correspond to PI point types. For example, integer values from a device can be sent to floating point or digital PI tags. Similarly, a floating-point value from the device can be sent to integer or digital PI tags, although the values will be truncated.
PI 2 Server Nodes
Scaled real, full-precision real, integer, and digital point types are supported on PI 2 Servers. For more information on the individual point types, refer to the Data Archive (DA) section of PI System Manual I.
PI 3 Server Nodes
Float16, float32, int16, int32, digital, string, and blob point types are supported on PI 3 Servers. For more information on the individual point types, see PI Data Archive for NT and UNIX.
Usually, the PI point type should match the PHD parameter type. Use Float16 or Float32 for real points, Int16 or Int32 for integer Points and Digital for enumeration. Any PI point type can be used when it does not match the PHD point type.
The interpretation of a PHD character string depends on the PI point type. For digital PI tags, the first 12 characters of the string are treated like a digital state string. For real and integer PI tags, the string variable is treated as an ASCII representation of the value. An exception is for time stamp outputs as described under Location5 below. The strings can also be put into a PI String tag for PI3 systems. String tags are not supported for PI2 systems.
The following tables show the interpretation of the PHD parameter types and PI point types for Inputs and Outputs.
Table 1: PHD Parameter Types to PI Points Type: Interpretation for Inputs
|PHD Parameter Type |PI Point Type |Input Interpretation |
|Real |Real |Real |
|Real |Integer |Integer |
|Real |Digital |Digital State Code from Real Number Rounded to Integer |
|Real |String |Real value string |
|Integer |Real |Real |
|Integer |Integer |Integer |
|Integer |Digital |Digital State Code |
|Integer |String |Integer value as string |
|Enumerated/Ordinal |Real |Ordinal Value as Real |
|Enumerated/Ordinal |Integer |Ordinal Value as Integer |
|Enumerated/Ordinal |Digital |Ordinal Value as Digital State |
|Enumerated/Ordinal |String (PI3 only) |Ordinal value string |
|ASCII String |Real |ASCII Representation of Real |
|ASCII String |Integer |ASCII Representation of Integer |
|ASCII String |Digital |First 12 Characters as Digital State String |
|ASCII String |String (PI3 only) |String (PI3 only) |
Table 2: PI Point Type of Source Point to PHD Parameter Type: Interpretation for Outputs
|PI Point |PHD 3000 | |
|Type of Source |Parameter Type |OutPut Interpretation |
|Real |Real |Real |
|Real |Integer |Real Number rounded to Integer |
|Real |Enumerated/Ordinal |Real Number rounded to Integer |
|Real |ASCII String |ASCII Representation of Real to 2 decimal places |
|Integer |Real |Real |
|Integer |Integer |Integer |
|Integer |Enumerated/Ordinal |Ordinal Value |
|Integer |ASCII String |ASCII Representation of Integer |
|Digital |Real |Digital State Value (0*1*2*..state) as Real Number |
|Digital |Integer |Digital State Value (0*1*2*..state) |
|Digital |Enumerated/Ordinal |Digital State Value (0*1*2*..state) as Ordinal Value |
|Digital |ASCII String |Digital State String |
|String(PI3) |Real |String converted to Real number |
|String(PI3) |Integer |String converted to Integer number |
|String(PI3) |Enumerated/Ordinal |String converted Ordinal Value |
|String(PI3) |ASCII String |String |
If the input values read from the PHD have a bad status, the “Bad Input” digital state is sent to the PI point.
If the PI point for Outputting to the PHD is in a “not normal state” NO value is sent.
The values of PI points are in a “not normal state” if:
For real points the status value is other than 0 referring to the Digital State Table (for example, SHUTDOWN,I/O TIMEOUT, BAD INPUT, Under Range, OverRange).
For integer points, the value is a Digital State string.
For Digital points when the value is not within its digital state set.
Location1
Location1 is the node number. This node number must match that specified in PI-PHD.bat. NodeNumber associates PI points with a particular interface.
Location2
|Direction of Data Transfer |Location2 |
|Input |1 |
|OutPut |2 |
|Output Time Stamp of Source Point to PHD point. The PHD point must be type Integer or String. |3 |
|Output Time Stamp of Source Point to a PHD point and a Normal Output. A PHD point must be in the |4 |
|extended descriptor specifying a PHD point to send the timestamp to. This PHD point must type | |
|Integer or String. The PHD tag in the Instrument tag field will receive the value of the Source | |
|point tag. | |
This is the direction of data transfer. Use 1 for inputs from the PHD and 2 for outputs to the PHD.
Use 3 to send the timestamp of the most recent PI value of the source tag to a string or time parameter. The time format is:
DD-MM-YY hh:mm:ss
Use 4 if you want to do a normal output and also send the time stamp to another PHD point at the same time. The Point.param for the time PHD point must be specified in the Extended Descriptor field.
Note: For interface to have the authority to send data to the PHD, the interface has to be started by a user in the PHD_PUTDATA group.
Location3
Location3 is used to indicate whether History Recovery should be done for the point.
1. 0 = no history recovery
1 = perform history recovery
Location4
Scan-Based Inputs
For interfaces that support scan-based collection of data, Location4 defines the scan class for the PI point. The scan class determines the frequency at which input points are scanned for new values. For more information, see the description of the /f flag in the section called “The Startup Command File”.
This is the Scan list number that corresponds to the scan frequency specified in the interface startup file. The interface sends and receives values for a list of PHD parameters in each message. You can control the grouping of parameters into lists by assigning Location4, which is the scan class, to a number from 1 to 256.
Scan classes are defined in the interface startup file. Each scan class defines an update period. This location code defines which scan class period is used to update the point lists. For example, if the following scan classes are specified in the interface startup command files as follows:
/f=00:00:05 /f=00:00:15 /f=00:01:00 /f=00:01:00,00:00:05
then,
ScanClass = 1 for frequency of 00:00:05 (5 seconds), ScanClass = 2 for a frequency of 00:00:15 (15 seconds) and ScanClass=3 for a frequency of 00:01:00 (1 minute) which will trigger on the minute, and ScanClass=4 for a frequency of 00:01:00 (1 minute) which will trigger 5 seconds after the minute.
Location 4 is ignored if using event based reads as described in the extended descriptor section.
Trigger-Based Inputs, Unsolicited-Inputs, and Output Points
Location 4 should be set to zero for these points.
Location5
Location5 is not used at this time.
InstrumentTag
For a PI 2 Server, the instrument tag attribute is limited to 32 characters. For a PI 3 Server, the instrument tag is limited to 32 characters if UniInt was not compiled to use the PI-SDK and to 1 Kilobyte if UniInt was compiled to use the PI-SDK.
This field must contain the PHD point name if that name does not match the PI tag name.
ExcDesc
The Extended Descriptor can be used in conjunction with the Location2 parameter. When outputting both a value and a timestamp (Location2 = 4), you must specify the PHD point in the Extended Descriptor field to receive the timestamp. This PHD point must be an integer type or string type.
The extended descriptor is also used to specify event based scanning for an input. The syntax for defining an event-based point is to add the following in the Extended Descriptor of the input point:
EVENT=PI tag name, where the PI tag name is the name of the event trigger tag.
Every time the interface receives a new event for the event tag, the interface will read the PHD for all the event inputs associated with this event tag. A new event is defined as a snapshot event with a time stamp greater than the existing snapshot time.
For a PI 2 Server, the extended descriptor is limited to 80 characters. For a PI 3 Server, the extended descriptor is limited to 80 characters if UniInt was not compiled to use the PI-SDK and to 1 Kilobyte if UniInt was compiled to use the PI-SDK.
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.”
Trigger-Based Inputs
For trigger-based input points, a separate trigger point must be configured. An input point is associated with a trigger point by entering a case-insensitive string in the extended descriptor (ExDesc) PI point attribute of the input point of the form:
keyword=trigger_tag_name
where keyword is replaced by “event” or “trig” and trigger_tag_name is replaced by the name of the trigger point. There should be no spaces in the string. UniInt automatically assumes that an input point is trigger-based instead of scan-based when the keyword=trigger_tag_name string is found in the extended descriptor attribute.
An input is triggered when a new value is sent to the Snapshot of the trigger point. The new value does not need to be different than the previous Snapshot value to trigger an input, but the timestamp of the new value must be greater than (more recent than) or equal to the timestamp of the previous value. This is different than the trigger mechanism for output points. For output points, the timestamp of the trigger value must be greater than (not greater than or equal to) the timestamp of the previous value.
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.
For this interface, Scan is usually ON for all points. Edit the Point Attribute to OFF to make the interface Delete it from its lists of points. Change the SCAN back to ON when you want the point added back to the Interface. The digital state SCAN OFF is written to a point when its scan flag is turned OFF.
SourceTag
The source tag field contains the PI point for outputs. The format is:
tagname
where:
tagname is the name of a PI tag that provides the value for the output point. Use this feature to send values from Performance Equations or other interfaces to the PHD. If the OUTPUT PI point is its own source, then do not use the Source Tag field
For Outputs to the PHD, the Source tag and the Output tag should be the same point type and have the same zero and span. Warning messages are written if the SOURCE tag and the Output tag do not match. If the source for the output is different from the output tag, the output value sent is put in the output tag.
Shutdown
PI 2 Server Node
The Shutdown attribute is not used if the server node is a PI 2 system. For information on configuring shutdown events for PI 2, see Data Archive (DA) section 4.2.3 of PI System Manual I.
PI 3 Server Nodes
The shutdown attribute is used only if the server node is a PI 3 system.
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 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 shutdown, Bufserv will continue to collect data for the interface, making it undesirable to write SHUTDOWN events to the PI points for this interface.
UserInt1
Starting with interface version 2.2.6, this attribute is used to interpret the PHD confidence factor.
Each PHD value includes a “confidence level” between 0 and 100. A useable value is always available if the confidence number is between 0 and 100. One hundred indicates high quality, 0 represents an uncertain result. If no value is available at all, the confidence level becomes -1.
The UserInt1 point attribute will be used to specify the minimum confidence. The default setting for this parameter will be zero, that is, the value is returned if the confidence is zero or greater. If the PHD confidence is below the UserInt1 value, the PI-PHD Interface returns “Bad Input.”
Output Points
Output points control the flow of data from the PI Data Archive to any destination that is external to the PI Data Archive, such as a PLC or a third-party database. For example, to write a value to a register in a PLC, one would use an output point. Each interface has its own rules for determining whether a given point is an input point or an output point. There is no de facto PI point attribute that distinguishes a point as an input point or an output point.
Outputs are triggered for UniInt-based interfaces. That is, outputs are typically not scheduled to occur on a periodic basis. There are two mechanisms for triggering an output.
Trigger Method 1 (Recommended)
For trigger method 1, a separate trigger point must be configured. The output point must have the same point source as the interface. The trigger point can be associated with any point source, including the point source of the interface. Also, the point type of the trigger point does not need to be the same as the point type of the output point.
The output point is associated with the trigger point by setting the SourceTag attribute of the output point equal to the tag name of the trigger point. An output is triggered when a new value is sent to the Snapshot of the trigger point. The new value does not need to be different than the previous value that was sent to the Snapshot to trigger an output, but the timestamp of the new value needs to be more recent than the previous value. If no error is indicated, then the value that was sent to the trigger point is also written to the output point. If the output is unsuccessful, then an appropriate digital state that is indicative of the failure is usually written to the output point. If an error is not indicated, the output still may not have succeeded because the interface may not be able to tell with certainty that an output has failed.
Trigger Method 2
For trigger method 2, a separate trigger point is not configured. To trigger an output, write a new value to the Snapshot of the output point itself. The new value does not need to be different than the previous value to trigger an output, but the timestamp of the new value must be more recent than the previous value.
Trigger method 2 may be easier to configure than trigger method 1, but trigger method 2 has a significant disadvantage. If the output is unsuccessful, there is no tag to receive a digital state that is indicative of the failure, which is very important for troubleshooting.
PIPHDPtBld
A utility called PIPHDPtBld.exe is used to build a file called PIPHDPtBld.csv that contains all points from the Honeywell PHD point database. For each point, the PIPHDPtBld.csv contains the PHD tagname, descriptor, engineering unit, zero, span, and pointtype. If the PI and PHD tag names are the same, then nothing is required to be entered into the PI instrument tag field. Conversely, if the PI and PHD tag names are different then the PHD tag name must be entered in the PI instrument tag field.
The example below is a PIPHDPtBld.txt. It is a PIConfig file that reads the PIPHDPtbld.csv file. Nothing needs to be entered into the instrument tag field as the PI and PHD tag names are the same.
*create tags from piphdptbld.csv
@table pipoint
@ptclass classic
@mode create,t
*modify following for site specific settings
@modify pointsource=H,location1=1,location2=1,location4=1
@istru tag,descriptor,engunits,zero,span,pointtype
@input piphdptbld.csv
If the PI and PHD tag names are different, the user should import the PIPHDPtbld.csv into Excel and create a separate column containing the PI tag name. The tags can be created using the PI SMT tools or the file can be exported back to ASCII and PIConfig run.
An example PIPHDPtBld.txt for this situation is shown below:
*create tags from modified piphdptbld.csv
@table pipoint
@ptclass classic
@mode create,t
*modify following for site specific settings
@modify pointsource=H,location1=1,location2=1,location4=1
@istru tag,instrumenttag,descriptor,engunits,zero,span,pointtype
@input piphdptbld.csv
Performance Point Configuration
One can configure performance points to monitor the amount of time in seconds that it takes an interface to complete a scan for a particular scan class. The closer the scan time is to 0 seconds, the better the performance. The scan time is recorded to millisecond resolution
Performance point configuration is the same on all operating system platforms. Performance points are configured as follows.
1. Set the extended descriptor to:
PERFORMANCE_POINT
or to:
PERFORMANCE_POINT=interface_id
where interface_id corresponds to the identifier that is specified with the /id flag on the startup command line of the interface. The character string PERFORMANCE_POINT is case insenstive. The interface_id does not need to be specified if there is only one copy of an interface that is associated with a particular point source.
2. Set Location4 to correspond to the scan class whose performance is to be monitored. For example, to monitor scan class 2, set Location4 to 2. See the /f flag for a description of scan classes.
3. Set the PointSource attribute to correspond to the /ps flag on the startup command line of the interface.
4. Set the PointType attribute to float32.
I/O Rate Tag Configuration
The total rate (events per minute) that the PI-PHD interface sends data to the Snapshot can be measured. The interface calculates a 10 minutes average (i.e. it counts the total number of snapshot events over a 10-minute period and then divides by 10 minutes). IORates for individual tags cannot be measured at this time. An exception is a value that has passed the exception specifications for a given PI point. Since 10-minute averages are taken, the first average is not written to PI until 10 minutes after the interface has started. One I/O Rate tag can be configured for each copy of the interface that is in use.
For instructions regarding implementation of IORates, see the description of the /ec flag of the startup command file under the section entitled “Startup Command File.”
Monitoring I/O Rates on the Interface Node
For NT and UNIX nodes, the 10-minute rate averages (in events/minute) can be monitored with a client application such as ProcessBook.
Configuring I/O Rate Tags with PI-ICU (NT-Intel)
The PI-Interface Configuration Utility (PI-ICU) provides a user interface for creating and managing IORates Tags.
[pic]
PI-ICU currently allows for one I/O Rate tag to be configured for each copy of the interface that is in use. Some interfaces allow for multiple I/O Rates tags.
Enable IORates for this Interface
The Enable IORates for this interface check box enables or disables IORates for the current interface. To disable IORates for the selected interface, uncheck this box. To enable IORates for the selected interface, check this box.
Tag Status
The Tag Status column indicates whether the IORates tag exists in PI. The possible states are:
• Created – This status indicates that the tag exist in PI
• Not Created – This status indicates that the tag does not yet exist in PI
• Deleted – This status indicates that the tag has just been deleted
• Unknown – This status indicates that the ICU is not able to access the PI Server
In File
The In File column indicates whether the IORates tag listed in the tag name and the event counter is in the IORates.dat file. The possible states are:
• Yes – This status indicates that the tag name and event counter are in the IORates.dat file
• No – This status indicates that the tag name and event counter are not in the IORates.dat file
Event Counter
The Event Counter correlates a tag specified in the iorates.dat file with this copy of the interface. The command line equivalent is /ec=x, where x is the same number that is assigned to a tag name in the iorates.dat file.
Tagname
The tag name listed under the Tagname column is the name of the IORates tag.
Snapshot
The Snapshot column holds the snapshot value of the IORates tag, if the IORates tag exists in PI. The Snapshot column is updated when the IORates/Status Tags tab is clicked, and when the interface is first loaded.
Right Mouse Button Menu Options
Create
Create the suggested IORates tag with the tag name indicated in the Tagname column.
Delete
Delete the IORates tag listed in the Tagname column.
Rename
Allows the user to specify a new name for the IORates tag listed in the Tagname column.
Add to File
Adds the tag to the IORates.dat file with the event counter listed in the Event Counter Column.
Search
Allows the user to search the PI Server for a previously defined IORates tag.
Configuring I/O Rate Tags Manually
There are two configuration steps.
Configuring the PI Point on the PI Server
PI 2 Server Nodes
A listing of the I/O Rate Tags that are currently being monitored can be obtained with the command:
@PISysDat:
Create an I/O Rate Tag using one of the existing I/O Rate Tags as a template.
PI 3 Server Nodes
Create an I/O Rate Tag with the following point attribute values.
|Attribute |Value |
|PointSource |L |
|PointType |float32 |
|Compressing |0 |
|ExcDev |0 |
Configuration on the Interface Node
For the following examples, assume that the name of the PI tag is phd001, and that the name of the I/O Rate on the home node is phd001.
NT Nodes
1. Edit/Create a file called iorates.dat in the PIHOME\dat directory. The PIHOME directory is defined either by the PIPCSHARE entry or the PIHOME entry in the pipc.ini file, which is located in the \WinNT directory. If both are specified, the PIPCSHARE entry takes precedence.
Since the PIHOME directory is typically C:\PIPC, the full name of the iorates.dat file will typically be C:\PIPC\dat\iorates.dat.
Add a line in the iorates.dat file of the form:
phd001, x
where phd001 is the name of the I/O Rate Tag and x corresponds to the first instance of the /ec=x flag in the startup command file. X can be any number between 2 and 34 or between 51 and 200, inclusive. To specify additional rate counters for additional copies of the interface, create additional I/O Rate tags and additional entries in the iorates.dat file. The event counter, /ec=x, should be unique for each copy of the interface.
2. Set the /ec=x flag on the startup command file of the interface to match the event counter in the iorates.dat file.
The interface must be stopped and restarted in order for the I/O Rate tag to take effect. I/O Rates will not be written to the tag until 10 minutes after the interface is started.
Startup Command File
Configuring the Interface with PI-ICU
Note: PI-ICU requires PI 3.3 or greater.
The PI-Interface Configuration Utility provides a graphical user interface for configuring PI interfaces. If the interface is configured by the PI-ICU, the batch file of the interface (pi-phd.bat) will be maintained by the PI-ICU and all configuration changes will be kept in that file. The procedure below describes the necessary steps for using PI-ICU to configure the PI-PHD Interface.
From the PI-ICU menu, select Interface, New, and then Browse to the
pi-phd.exe executable file. Then, enter values for Point Source and Interface ID#. A window such as the following results:
[pic]
“Interface name as displayed in the ICU (optional)” will have PI- pre-pended to this name and it will be the display name in the services menu.
Click on Add.
You should then see a display such as the following:
[pic]
Note that in this example the Host PI System is localhost, which means that the interface will be configured to communicate with the local PI Server. However, if you want the interface to communicate with a remote PI Server, you can do this by selecting ‘Connections…’ item from PI-ICU menu and make it your default server. If you do not see the remote node in the list of servers, you can add that in.
Once you add the interface to PI-ICU, near the top of the main PI-ICU screen, the Interface Type should be hwphd. If not, use the drop-down box to change the Interface Type to be hwphd.
Click on Apply to enable the PI-ICU to manage this copy of the PI-PHD Interface.
[pic]
The next step is to make selections in the interface-specific tab (i.e. “hwphd”) that allow you to enter values for the startup parameters that are particular to the PI-PHD Interface.
The PI-PHD ICU control has one screen for configuration. A yellow text box indicates that an invalid value has been entered, or that a required value has not been entered.
The next screenshot shows the one screen which is broken into 5 sections.
.
[pic]
Since the PI-PHD Interface is a UniInt-based interface, in some cases the user will need to make appropriate selections in the UniInt tab. This tab allows the user to access UniInt features through the PI-ICU and to make changes to the behavior of the interface.
If you want to set up the interface as a Windows Service, you can do that by using the Service tab. This tab allows you to configure the interface to run as a service as well as to start and stop the interface. You can also run the interface interactively from the PI-ICU. To do that go to menu, select the Interface item and then Start Interactive.
For more detailed information on how to use the above-mentioned and other PI-ICU tabs and selections, please refer to the PI-Interface Configuration Utility User Manual. In the next section we will describe the selections that are available from the hwphd tab. After you have made your selections on the PI-ICU GUI, you will need to press the Apply button in order for PI-ICU to make these changes to the interface’s startup file.
hwphd Interface Tab
Since the startup file of the PI-PHD Interface is maintained automatically by PI-ICU, you should use the hwphd tab to configure the startup parameters and not make changes in the file manually. The following is the description of interface configuration parameters used in the PI-ICU Control and corresponding manual parameters.
General Section
[pic]
1. PHD Server and Socket
This is the name of the PHD Server for the interface to connect to.
If not specified, the interface will connect to a local PHD server or if the PHD server is not local, the server specified in the environment variable PHD_HOST. This variable is defined when installing the Honeywell PHD Client.
The socket number is normally 3000
(/phdhost=x/socket number) For example, /phdhost=turboberry/3000
2. Tags to scan before 1ms pause
Pause 1 millisecond every x number of reads from the PHD server. The default is 1 in which the interface will pause 1 millisecond after reading a value from the PHD server. This is to alleviate high CPU problems. A setting of 0 will increase throughput, but you may have high CPU. You may need to set the value to above 1 to increase throughput with an acceptable CPU level. The command line equivalent is (/PE=x).
3. Pause before connecting to PHD
This specifies the number of seconds to wait before connecting to the PHD server. It allow the PHD server to load its points before the interface verifies that the points exist on the PHD server. (/SL=x)
4. Digital code to send if digital state lookup fails
This specifies what digital state to send to PI if the digital state lookup of the string fails. ie: /ds_err=290 will send the system digital code 290, “Bad Data” to the PI system. The default is 1. (/DS_ERR=x)
5. Timestamps
The timestamp settings are optional settings that determine what timestamp the interface will use when sending data to PI.
Use PHD timestamps and adjust for difference between PHD and PI time
The interface uses PHD timestamps and applies the difference of PHD server time and PI Server time. This is the default behavior. The command line equivalent is (/TS=0).
Use PHD timestamps without applying time difference
The interface uses PHD timestamps without applying a time difference. This is only done if PHD server time is behind PI server time. If PI server time is behind PHD server time, the timestamps will be adjusted to PI server time. The command line equivalent is (/TS=1).
Use the PI server time
The interface does not use PHD Timestamps. It sends the last value in each scan and uses the PI server time. The command line equivalent is (/TS=2).
6. Enable history recovery
Checking this box will enable the interface to do history recovery on startup. The maximum time to go back for history recovery is given in the text box. (/HI=x) Ex: x would be 2d for two days.
7. Enable debug messaging
Enables debug messaging in which detailed messages are written to the interface log file. (/DB)
8. Additional Parameters
In the space provided the user can enter any additional parameters that are not available through PI-ICU.
Command-line Parameters
Command-line arguments can begin with a / or with a -. For example, the /ps=M and -ps=M command-line arguments are equivalent.
The PI-PHD interface requires several command-line arguments for successful execution. For convenience, the arguments are defined in a startup command file called pi-phd.bat. The NT continuation character (^) allows one to use multiple lines for the startup command. A sample pi-phd.bat file is included on the installation disks. The command line in the pi-phd.bat file must be on a single line and cannot exceed 1024 characters.
Note: The UniInt End User Document includes details about other command line parameters which may be useful.
|Parameter |Description |
|/ts=x |Optional - settings for what timestamp to use. |
|Optional |0 – default. Use PHD Timestamps and apply difference of PHD server time and PI Server|
| |time. |
| |1 - Use PHD Timestamps without applying time difference. This is only done if PHD |
| |server time is behind PI server time. If PI server time is behind PHD server time, |
| |the timestamps will be adjusted to PI server time. |
| |2 - Do not use PHD Timestamps. Send last value in each scan and use the PI server |
| |time. |
|/hi=x |Flags the interface to do history recovery on startup. Pass the maximum time to go |
|Optional |back. Ex: 2d for two days. |
|/phdhost=x/socket number |This is the name of the PHD Server for the interface to connect to. |
|Optional |If not specified, the interface will connect to a local PHD server or if the PHD |
| |server is not local, the server specified in the environment variable PHD_HOST. This |
| |variable gets defined when installing the Honeywell PHD Client. |
| |The socket number is normally 3000 |
| |Ex: /phdhost=turboberry/3000 |
|/sl=x |The number of seconds to wait before starting. This will allow the PHD server to load|
|Optional |its points before the interface verifies that the points exist on the PHD server. |
|/pe=x |Pause 1ms every x number of reads from the PHD server. The default is 1 in which the |
|Optional |interface will pause 1ms after reading a value from the PHD server. This is to |
| |alleviate high CPU problems. A setting of 0 will increase throughput, but you may |
| |have high CPU. You may need to set the value to above 1 to increase throughput with |
| |an acceptable CPU level. |
|/ps=x |The /ps flag specifies the point source for the interface. x is not case sensitive and|
|Required |can be any single character. For example, /ps=P and /ps=p are equivalent. |
| |The point source that is assigned with the /ps flag corresponds to the PointSource |
| |attribute of individual PI Points. The interface will attempt to load only those PI |
| |points with the appropriate point source. |
|/ds_err=x |This flag specifies what digital state to send to PI if the digital state lookup of |
|Optional |the string fails. ie:ds_err=290 will send the system digital code 290, “Bad Data” to |
| |the pi system. The default is 1. |
|/id=x |Defines a unique identifier (#) between 1 and 99 for each version of the interface |
|Required |that is running. The identifier corresponds to location1 of the PI tag definition. |
| |The interface identifier is a string that is no longer than 9 characters in length. |
| |UniInt concatenates this string to the header that is used to identify error messages |
| |as belonging to a particular interface. See the section called “Error and |
| |Informational Messages” for more information. |
| |UniInt always uses the /id flag in the fashion described above. This interface also |
| |uses the /id flag to identify a particular interface copy number that corresponds to |
| |an integer value that is assigned to Location1. For this interface, one should use |
| |only numeric characters in the identifier. For example, |
| |/id=1 |
|/f=SS |The /f flag defines the time period between scans in terms of hours (HH), minutes |
|or |(MM), and seconds (SS). The scans can be scheduled to occur at discrete moments in |
|/f=SS,SS |time with an optional time offset specified in terms of hours (hh), minutes (mm), and |
|or |seconds (ss). If HH and MM are omitted, then the time period that is specified is |
|/f=HH:MM:SS |assumed to be in seconds. |
|or |Several time periods can be defined on a single command line (however, one must be |
|/f=HH:MM:SS,hh:mm:ss |careful not to exceed the 255-character limit of the command line). Location4 |
| |determines which time period is used. |
|Required for reading |Each instance of the /f flag on the command line defines a scan class for the |
|scan-based inputs |interface. There is no limit to the number of scan classes that can be defined. The |
| |first occurrence of the /f flag on the command line defines the first scan class of |
| |the interface, the second occurrence defines the second scan class, and so on. PI |
| |Points are associated with a particular scan class via the Location4 PI Point |
| |attribute. For example, all PI Points that have Location4 set to 1 will receive input |
| |values at the frequency defined by the first scan class. Similarly, all points that |
| |have Location4 set to 2 will receive input values at the frequency specified by the |
| |second scan class, and so on. |
| |Two scan classes are defined in the following example: |
| |/f=00:01:00,00:00:05 /f=00:00:07 |
| |or, equivalently: |
| |/f=60,5 /f=7 |
| |The first scan class has a scanning frequency of 1 minute with an offset of 5 seconds,|
| |and the second scan class has a scanning frequency of 7 seconds. When an offset is |
| |specified, the scans occur at discrete moments in time according to the formula: |
| |scan times = (reference time) + n(frequency) + offset |
| |where n is an integer and the reference time is midnight on the day that the interface|
| |was started. In the above example, frequency is 60 seconds and offset is 5 seconds for|
| |the first scan class. This means that if the interface was started at 05:06:06, the |
| |first scan would be at 05:06:10, the second scan would be at 05:07:10, and so on. |
| |Since no offset is specified for the second scan class, the absolute scan times are |
| |undefined. |
| |The definition of a scan class does not guarantee that the associated points will be |
| |scanned at the given frequency. If the interface is under a large load, then some |
| |scans may occur late or be skipped entirely. See the section called “Performance Point|
| |Configuration” for more information on skipped or missed scans. |
| |Wall Clock Scheduling |
| |Scan classes that strictly adhere to wall clock scheduling are now possible. This |
| |feature is available for interfaces that run on NT and/or UNIX. Previously, wall clock|
| |scheduling was possible, but not across daylight savings time. For example, |
| |/f=24:00:00,08:00:00 corresponds to 1 scan a day starting at 8 AM. However, after a |
| |Daylight Savings Time change, the scan would occur either at 7 AM or 9 AM, depending |
| |upon the direction of the time shift. To schedule a scan once a day at 8 AM (even |
| |across daylight savings time), one should use /f=24:00:00,00:08:00,L. The ,L at the |
| |end of the scan class tells UniInt to use the new wall clock scheduling algorithm. |
|/host=host:port |The /host flag is used to specify the PI Home node. host is the IP address of the PI |
|Optional |Sever node or the domain name of the PI Server node. port is the port number for |
| |TCP/IP communication. The port is always 5450 for a PI 3 Server and 545 for a PI 2 |
| |Server. It is recommended to explicitly define the host and port on the command line |
| |with the /host flag. Nevertheless, if either the host or port is not specified, the |
| |interface will attempt to use defaults. |
| |Defaults: |
| |The default port name and server name is specified in the pilogin.ini or piclient.ini |
| |file. The piclient.ini file is ignored if a pilogin.ini file is found. Refer to the |
| |PI-API Installation Instructions manual for more information on the piclient.ini and |
| |pilogin.ini files. |
| |Examples: |
| |The interface is running on an API node, the domain name of the PI 3 home node is |
| |Marvin, and the IP address of Marvin is 206.79.198.30. Valid /host flags would be: |
| |/host=marvin |
| |/host=marvin:5450 |
| |/host=206.79.198.30 |
| |/host=206.79.198.30:5450 |
|/stopstat |If the /stopstat flag is present on the startup command line, then the digital state |
|or |I/O Timeout will be written to each PI Point when the interface is stopped. |
|/stopatat= |If /stopstat=digstate is present on the command line, then the digital state, |
|digstate |digstate, will be written to each PI Point when the interface is stopped. For a PI 3 |
|default: |Server, digstate must be in the system digital state table. For a PI 2 Server, where |
|/stopstat= |there is only one digital state table available, digstate must simply be somewhere in |
|”Intf Shut” |the table. UniInt uses the first occurrence in the table. |
|Optional |If neither /stopstat nor /stopstat=digstate is specified on the command line, then no |
| |digital states will be written when the interface is shut down. |
| |Examples: |
| |/stopstat=”Intf Shut” |
| |The entire parameter is enclosed within double quotes when there is a space in |
| |digstate. |
|/ec=x |The first instance of the /ec flag on the command line is used to specify a counter |
|Optional |number, x, for an I/O Rate point. If x is not specified, then the default event |
| |counter is 1. Also, if the /ec flag is not specified at all, there is still a default |
| |event counter of 1 associated with the interface. If there is an I/O Rate point that |
| |is associated with an event counter of 1, each copy of the interface that is running |
| |without /ec=x explicitly defined will write to the same I/O Rate point. This means |
| |that one should either explicitly define an event counter other than 1 for each copy |
| |of the interface or one should not associate any I/O Rate points with event counter 1.|
| |Configuration of I/O Rate points is discussed in the section called “I/O Rate Tag |
| |Configuration.” |
|/sio |The /sio flag stands for “suppress initial outputs.” The flag applies only for |
|Optional |interfaces that support outputs. If the /sio flag is not specified, the interface will|
| |behave in the following manner. |
| |When the interface is started, the interface determines the current Snapshot value of |
| |each output tag. Next, the interface writes this value to each output tag. In |
| |addition, whenever an individual output tag is edited while the interface is running, |
| |the interface will write the current Snapshot value to the edited output tag. |
| |This behavior is suppressed if the /sio flag is specified on the command line. That |
| |is, outputs will not be written when the interface starts or when an output tag is |
| |edited. In other words, when the /sio flag is specified, outputs will only be written |
| |when they are explicitly triggered. |
|/q |When this flag is specified, data is queued on the NT system before it is transmitted |
|Optional |to the PI home node. Data is sent less frequently but in larger packets. This flag is |
| |recommended. |
| |The maximum queue size is 255 bytes for a PI 3 Server and 36 bytes for a PI 2 Server. |
| |For example, if the interface is running on a UNIX node and is communicating to a PI 2|
| |Server, then the maximum queue size is 36. The queue is flushed between scans if it is|
| |not filled. |
| |When the /q flag is specified in non-extended API mode, the PI-API sends integer |
| |values as 16-bit integers instead of 32-bit integers. Therefore, integer points will |
| |be limited to values between 0 and 32767. Values higher than 32767 need to be sent to |
| |floating-point PI tags. |
|/db |Enables debug messaging in which detailed messages are written to the interface log |
|Optional |file. |
Example PI-phd.bat File
The following is an example file:
REM pi-phd.bat
REM
REM this command procedure passes required -default parameters to
REM process piphd.
REM
REM
REM command line arguments:
REM /ps= required - point source character
REM /id= required - interface id number
REM /f= required - frequency
REM /host= optional - name of PI home node. Default is localhost:5450
REM /hi= optional - Flag to start History recovery and
REM maximum time to go back for History Recovery. ex:4d
REM /ts= optional - settings for what timestamp to use.
REM 0 - default. Use PHD Timestamps and apply difference
REM of PHD server time and PI Server time.
REM 1 - Use PHD Timestamps without applying time difference.
REM This is only done if PHD server time is behind PI server
REM time. If PI server time is behind PHD server time, the
REM timestamps will be adjusted to PI server time.
REM 2 - Do not use PHD Timestamps. Send last value in each scan
REM and use the PI server time.
REM /phdhost= optional - PHD Server Name/socket number.
REM This is the name of the PHD Server for the interface to
REM connect to.
REM If not specified, the interface will connect to a
REM local PHD server or if the PHD server is not local, the
REM server specified in the environment variable PHD_HOST.
REM This variable gets defined when installing the Honeywell PHD
REM Client.
REM The socket number is normally 3000
REM Ex: /phdhost=turboberry/3000
REM /sl= optional - The number of seconds to wait before starting. This will
REM allow the PHD server to load its points.
REM /pe= optional - The number of tags to read before pausing 1ms.
REM Default is 1. ie:pause 1ms after reading a value from the
REM PHD server. This is to alleviate high cpu problems.
REM /db optional - turns on additional debug messages
REM
REM /ds_err optional - This flag specifies what digital state to send to PI if
REM the digital state lookup of the string fails.
REM ie:ds_err=290 will send the system digital code 290, “Bad
REM Data” to the pi system.
REM The default is 1.
REM run string needs a space between arguments, no spaces within
REM argument.
REM
..\interfaces\HWPHD\pi-phd /ps=h /id=1 /host=localhost:5450 /f=00:00:30
REM
REM end of pi-phd.bat
PI-PHD Interface System Administration
Starting the PI-PHD interface
Automatic Service Startup
If the PI-PHD interface was configured as an automatic service in step 6 of the installation procedure, then the PI-PHD interface will automatically start after the NT system reboots. This configuration is useful in the event of a power failure.
Manual Service Startup
If the PI-PHD interface was configured as a manual service and the PI system was also configured as a manual service, then the PI-PHD interface can be started along with the PI System when the following command file is executed from the adm\ directory (assuming that step 6 of the installation procedure was completed):
pisrvstart.bat
If you wish to start a manual Piphdservice separately from the PI Data Archive, execute the following command from the HWPHD\ directory:
pi-phd -start
Interactive Startup
If both PI and the PI-PHD interface are started interactively, one can start both of them with the
pistart.bat
command file, assuming that step 8 of the installation procedure was completed.
Alternatively, one can start the interface independently of the PI Data Archive by typing the following command from the interfaces\ directory:
start "pi-phd" HWPHD\pi-phd.bat
Or one can issue the following command from the interfaces\ directory:
HWPHD\pi-phd.bat
When start “pi-phd”… command is used, a new MSDOS window is created.
Stopping the PI-PHD Interface
If the PI-PHD interface was configured as an automatic or a manual service in steps 5 and 6 of the installation procedure and if the PI system was also configured as an automatic or manual service, then the pi-phd service is stopped along with the PI system by executing the following command file from the adm\ directory:
pisrvstop.bat
This assumes that both steps 6 and/or 7 of the installation procedure have been completed.
Alternatively, one can stop the pi-phd service independently from stopping the PI system by executing the following command from the HWPHD\ directory:
pi-phd -stop
or one can stop the pi-phd service from the services control panel.
If the PI-PHD interface was started in interactive mode, one can stop the PI-PHD interface by, 1) selecting the MSDOS window that corresponds to the pi-phd interface, and 2) holding down the control key while typing the letter c (note that there is no pisitestop.bat file to correspond to the pisitestart.bat file).
Registering the PI-PHD Interface as a Windows NT Service
Manual Services
From the HWPHD\ directory, execute the command.
Without Bufserv:
pi-phd -install -depend tcpip
With Bufserv:
pi-phd -install -depend “tcpip bufserv”
Check the services control panel to verify that the pi-phd service has been added. See the PI-API Bufserv 1.x Release Notes for the installation instructions for Bufserv.
Automatic Services
From the HWPHD\ directory, execute the command:
Without Bufserv:
pi-phd -install –auto -depend tcpip
With Bufserv:
pi-phd -install –auto -depend “tcpip bufserv”
Check the services control panel to verify that the pi-phd service has been added. See the PI-API Bufserv 1.x Release Notes for the installation instructions for Bufserv. The PI-phd interface will now start automatically when the computer is rebooted.
Removing the PI-PHD Interface as a Windows NT Service
From the HWPHD\ directory, execute the command:
pi-phd -remove
Check the services control panel to verify that the pi-phd service has been removed.
Status, Warning, and Error Messages
Such messages will be written to the pipc.log file. This file should be checked to verify successful execution of the interface because not all error messages are echoed to the screen. The location of this file is determined by the PIHOME entry in the pipc.ini file, which is located in the WINNT directory (for more information, see the description of the subroutine pilg_putlog in the PI Application Programming Interface manual). For example, if the PIHOME entry is c:\PIPC, then the pipc.log file will be located in the c:\PIPC\dat directory.
Interface Node Clock
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.
Security
If the home node is a PI 3 Server, the PI Firewall Database and the PI Proxy Database must be configured so that the interface is allowed to write data to the PI Data Archive. See “Modifying the Firewall Database” and “Modifying the Proxy Database” in the PI Data Archive Manual.
If the home node is a PI 2 Server, the read/write permissions should be set appropriately in the pisysdat:piserver.dat file on the PI 2 home node. For more information on setting permissions on PI 2, see the pibuild:piserver.txt file on the PI 2 home node.
If the interface cannot write data to a PI 2 or PI 3 Server because it has insufficient privileges, a –10401 error will be reported in the pipc.log file. See the section “Error and Informational Messages” for additional information on error messaging.
Starting / Stopping the Interface
This section describes starting and stopping the interface once it has been installed as a service. See the UniInt End User Document to run the interface interactively.
Starting Interface as a Service
If the interface was installed a service, it can be started from the services control panel or with the command:
pi-phd.exe –start
A message will be echoed to the screen informing the user whether or not the interface has been successfully started as a service. Even if the message indicates that the service started successfully, make sure that the service is still running by checking in the services control panel. There are several reasons that a service may immediately terminate after startup. One is that the service may not be able to find the command-line arguments in the associated .bat file. For this to succeed, the root name of the .bat file and the .exe file must be the same, and the .bat file and the .exe file must be in the same directory. If the service terminates prematurely for whatever reason, no error messages will be echoed to the screen. The user must consult the pipc.log file for error messages. See the section “Error and Informational Messages” for additional information.
Stopping Interface Running as a Service
If the interface was installed a service, it can be stopped at any time from the services control panel or with the command:
pi-phd.exe –stop
The service can be removed by:
pi-phd.exe –remove
Buffering
Configuring Buffering with PI-ICU (NT-Intel)
Buffering is enabled through the PI-Interface Configuration Utility’s Tools>API Buffering… menu. Unless buffering is explicitly enabled, the PI-API will not buffer data, sending data directly to the home node.
The API Buffering… dialog allows the user to view and configure the parameters associated with the API Buffering (bufserv) process. The user can start and stop the API Buffering process from the Service tab:
[pic]
Service Tab
The Service tab allows for some API Buffering service configuration. For further configuration changes, use the Services applet.
Service Name
The Service name displays the name of the API Buffering Service.
Display Name
The Display name displays the full name associated with the API Buffering service.
Log On As
Log on as indicates the Windows user account under which the API Buffering service is setup to start automatically on reboot, or manually.
Password
Password is the name of the password for the Windows user account entered in the Log on as:above.
Confirm password
You must reenter the password again to verify you have typed it correctly both times.
Dependencies
The Dependencies lists the Windows services on which the API Buffering service is dependent.
Dependent Services
The Dependent services area lists the Windows services that depend on bufserv to function correctly.
Start / Stop Service
The Start / Stop buttons allow for the API Buffering service to be started and stopped. If the service is not created this box will show Not Installed.
After a change is made to any of the settings on the Settings tab, the OK button must be clicked to save these settings, and then the service must be stopped and restarted for the changes to be picked up by bufserv.
Service Startup Type
The Startup Type indicates whether the API Buffering service is setup to start automatically on reboot or manually on reboot, or is disabled.
• 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, the API Buffering service is set to start automatically.
Create/Remove Service
The Create / Remove buttons allow for the creation or removal of the API Buffering service. Clicking the Create button will cause the service to be created using the Log on as and passwords given. Once the service is created the Start / Stop buttons will be activated.
Settings Tab
The Settings tab allows for configuration of the 7 configurable settings used by API Buffering. Default values are used if no other value is provided.
[pic]
Enable API Buffering
Enables the API Buffering feature.
Maximum File Size
Maximum buffer file size in kilobytes before buffering fails and discards events. Default value is 100,000. Range is 1 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Send Rate
Send rate is the time to wait between sending up to MAXTRANSFEROBJS to the server (milliseconds). Default value is 100. Range is 0 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Primary Memory Buffer Size
Primary memory buffer size is the size in bytes of the Primary memory buffer. Default value is 32768. Range is 64 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Secondary Memory Buffer Size
Secondary memory buffer size is the size in bytes of the Secondary memory buffer. Default value is 32768. Range is 64 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Max Transfer Objects
Max transfer objects is the maximum number of events to send between each SENDRATE pause. Default value is 500. Range is 1 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Pause Rate
When buffers are empty the buffering process will wait for this number of seconds before attempting to send more data to the home node. Default value is 2. Range is 0 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Retry Rate
When the buffering process discovers the home node is unavailable it will wait this number of seconds before attempting to reconnect. Default value is 120. Range is 0 to 2,000,000.
The Use Default button places the default value into the text box. To keep this value, click the Apply button.
Max Theoretical Send Rate
This is the theoretical max send rate which is calculated like this:
max = MAXTRANSFEROBJS / SENDRATE * 1000
Default value is 5000. This value is automatically calculated for the user and can not be changed.
There are no additional steps needed to install buffering after installing the PI-API. The delivered PI-API library supports both buffered and un-buffered calls.
Configuring Buffering Manually
Buffering is enabled through the use of a configuration file, piclient.ini. Unless this file is modified to explicitly enable buffering, the PI-API will not buffer data, sending data directly to the home node.
There are no additional steps needed to install buffering after installing the PI-API. The delivered PI-API library supports both buffered and un-buffered calls.
Note: When buffering is configured to be on, the bufserv process must be started before other programs using the PI-API, so that these programs can access the shared buffering resources. Any program that makes a connection to a PI Server has this requirement even if it does not write to PI.
Configuration of buffering is achieved through entries in the piclient.ini file. The file is found in the dat subdirectory of the PIHOME directory (typically c:\pipc\dat) under Windows NT. This file follows the conventions of Microsoft Windows initialization files with sections, keywords within sections, and values for keywords. All buffering settings are entered in a section called [APIBUFFER]. To modify settings, simply edit the piclient.ini file in a text editor (Notepad on Windows) to the desired values.
The following settings are available for buffering configuration:
|Keywords |Values |Default |Description |
|BUFFERING |0,1 |0 |Turn off/on buffering. OFF = 0, ON = 1, |
|PAUSERATE |0 – 2,000,000 |2 |When buffers are empty the buffering process will wait |
| | | |for this long before attempting to send more data to the |
| | | |home node (seconds) |
|RETRYRATE |0 – 2,000,000 |120 |When the buffering process discovers the home node is |
| | | |unavailable it will wait this long before attempting to |
| | | |reconnect (seconds) |
|MAXFILESIZE |1 – 2,000,000 |100,000 |Maximum buffer file size before buffering fails and |
| | | |discards events. (Kbytes) |
|MAXTRANSFEROBJS |1 – 2,000,000 |500 |Maximum number of events to send between each SENDRATE |
| | | |pause. |
|BUF1SIZE |64 – 2,000,000 |32768 |Primary memory buffer size. (bytes) |
|BUF2SIZE |64 – 2,000,000 |32768 |Secondary memory buffer size. (bytes) |
|SENDRATE |0 – 2,000,000 |100 |The time to wait between sending up to MAXTRANSFEROBJS to|
| | | |the server (milliseconds) |
In addition to the [APIBUFFER] section, the [PISERVER] section may be used to define the default PI server and an optional time offset change that may occur between the client and server.
|Keywords |Values |Default |Description |
|PIHOMENODE |string |none |Windows default server is in pilogin.ini |
|DSTMISMATCH |0 – 2,000,000 |0 |The time that the server and client local time |
| | | |offset is allowed to jump. Typically, 3600 if the |
| | | |nodes are in time zones whose DST rules differ |
| | | |(seconds) |
Example piclient.ini File
NT
On Windows NT the default server information is stored in the pilogin.ini file so the piclient.ini would only have the [APIBUFFER] section. The BUFFERING=1 indicates that buffering is on. The MAXFILESIZE entry in Kbytes of 100000 allows up to 100 Megabytes of data storage. Do not use commas or other separators in the numeric entries. The retry rate is set to 600 seconds meaning wait 10 minutes after losing a connection before retrying.
On NT a piclient.ini file might look like:
[APIBUFFER]
BUFFERING=1
MAXFILESIZE=100000
; The PI-API connection routines have a 1 minute default timeout.
RETRYRATE=600
Appendix A
Error and Informational Messages
A string NameID is pre-pended to error messages written to the message log. Name is a non-configurable identifier that is no longer than 9 characters. ID is a configurable identifier that is no longer than 9 characters and is specified using the /id flag on the startup command line.
Message Logs
The location of the message log depends upon the platform on which the interface is running. See the UniInt End User Document for more information.
Messages are written to PIHOME\dat\pipc.log at the following times.
• When the interface starts many informational messages are written to the log. These include the version of the interface, the version of UniInt, the command-line parameters used, and the number of points.
• As the interface retrieves points, messages are sent to the log if there are any problems with the configuration of the points.
• If the /db is used on the command line, then various informational messages are written to the log file.
System Errors and PI Errors
System errors are associated with positive error numbers. Errors related to PI are associated with negative error numbers.
Error Descriptions on NT and Unix
On NT, descriptions of system and PI errors can be obtained with the pidiag utility:
\PI\adm\pidiag –e error_number
Appendix B:
Troubleshooting
To check the data on the PHD server there is a utility called PHDMAN.
Run PHDMAN on the PHD server and then enter show queue phdtagname.
The most recent values and their timestamps will be displayed.
Revision History
|Date |Author |Comments |
|28-Apr-97 |MMG |Preliminary document |
|21-May-97 |MMG |Updated preliminary document |
|5-Jun-97 |MMG |Updated preliminary document |
|11-Jun-97 |MMG |Updated preliminary document |
|17-oct-97 |MMG |Update preliminary document |
|7-nov-97 |MMG |Added install and startup requirements |
|23-Jan-98 |MMG |Change name to pi-phd |
|27-Jan-98 |MMG |Added note for sending data to PHD |
|17-Jul-98 |MMG |Change to reflect what is in version 1.1 of interface |
|23-Oct-98 |MMG |Change to reflect what is in version 1.3 of interface. History recovery,|
| | |and timestamps. |
|9-Apr-99 |MMG |Add software requirements |
|3-Aug-99 |MMG |Correct Hardware requirements. LCN not required. |
|1-Nov-99 |MMG |1.5.x version of interface. Added new startup parameter. /ts= |
|27-Jan-00 |MMG |Fix typo from PHD_PTDATA to PHD_PUTDATA |
|31-May-00 |MMG |Add new startup parameter /phdhost for when running on a PHD Client node,|
| | |not the PHD Server. |
| | |Add new startup parameter /sl=x to pause x number of seconds before |
| | |verifying points exist on the PHD server to allow the PHD server to load |
| | |it’s points. |
| | |Add new startup parameter /pe=x to pause 1ms every x number of reads to |
| | |alleviate High CPU problems. |
|24-Aug-00 |MMG |Version 2.1 location 2=4 now supported |
|6-Nov-00 |AKF |Formatting update to Manual Skeleton 1.04 |
|27-Jun-01 |MMG |Cleanup document after the new skeleton was used. |
|05-Sep-01 |HAB |Added ICU Control (2.1.x, doc rev A) |
|26-Nov-01 |MMG |Fixed the location2=4 section for outputting a timestamp and value. |
|17-Jul-02 |MMG |Add section on using the UserInt1 attribute to determine how to use the |
| | |confidence level returned with the PHD data. |
|07-Aug-02 |CG |Formatting; fixed headers & footers; added DS section |
|13-Feb-03 |MMG |Add virtual PHD tags are supported |
|18-Jun-03 |DC |Fixed headers and copyright date; changed /phdnode to /phdhost for |
| | |consistency |
|17-Sep-03 |MMG |Update version and copyright |
|30-Sep-04 |MMG |Update version. Take out PHD server has to be below version 200. Not |
| | |the case anymore. |
|5-Oct-04 |MMG |Update ICU control screen shot. Add /db to table of startup command |
| | |switches. |
|26-Oct-04 |MPK |Changed installation directory from pi-phd to HWPHD. |
|18-Nov-04 |MPK |Fixed headers and footers. |
|22-Nov-04 |MPK |Added new section for Configuring Interface with PI-ICU, Configuring |
| | |Buffering with PI-ICU, Configuring I/O Rate Tags with PI-ICU (NT-Intel) |
| | |and Installing the Interface Service with PI-Interface Configuration |
| | |Utility |
-----------------------
Status of the ICU
Status of the Interface Service
Service installed or uninstalled
1
4
3
2
5
7
6
8
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- why the school system is bad
- is the education system broken
- the school system is broken
- the education system is failing
- why the education system is good
- changing the school system essay
- the college system is broken
- calculator with the pi button
- how to cleanse the lymphatic system naturally
- the planets of the solar system song
- the organs in the circulatory system include
- label the conduction system of the heart