Fisher-Rosemount CHIP on NT/VMS/HP-UX

Fisher-Rosemount CHIP on NT/VMS/HP-UX
Interface to the PI System

Version 2.7.0.3 and greater

How to Contact Us

Phone / (510) 297-5800 (main number)
(510) 297-5828 (technical support)
Fax / (510) 357-8136
Internet /
World Wide Web /
Bulletin Board / (510) 895-9423
Telebit WorldBlazer modem (Hayes, MNP, or PEP compatible)
8 data bits, 1 stop bit, no parity, up to 14400 bps download
protocols: Xmodem, Ymodem, Zmodem, Kermit
Mail / OSI Software, Inc.
P.O. Box 727
San Leandro, CA 94577-0427
USA
OSI Software GmbH
Hauptstrae 30
D-63674 Altenstadt 1
Deutschland /
OSI Software, Ltd
P. O. Box 8256
Level One, 6-8 Nugent Street
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 OSI Software, Inc. Microsoft Windows, Microsoft Windows for Workgroups, and Microsoft NT are registered trademarks of Microsoft Corporation. Solaris is a registered trademark of Sun Microsystems. HPUX is a registered trademark of Hewlett Packard Corp. IBM AIX RS/6000 is a registered trademark of the IBM Corporation. DUX, DEC VAX and DEC Alpha are registered trademarks of the Digital Equipment Corporation.
FCHIPNT.DOC

 1997 OSI Software, Inc. All rights reserved
777 Davis Street, Suite 250, San Leandro, CA 94577

11/30/2000 4:36 PM1

Table of Contents

Introduction

PI Point Definition

Input-specific PI Point Parameters

Output-specific PI Point Parameters

Alarm Processing

8 - Bit Status Processing

16 - Bit Status Processing

Controller Mode Processing

PIDIFF and CHIP GENER

Installing CHIPtoPI

Installing CHIPtoPI on NT

Installing CHIPtoPI on HP-UX

Installing CHIPtoPI on VMS

Software Requirements

Software Installation

Configuring IORates and Performance Points

IO Rate Points Configuration

Step 1 – PI Point configuration on the PI Server

Step 2 – Configuration on the Interface Node

Performance Point Configuration

PI 2 PINET to PI 3 String Tag Support

Method of Operation

Setup Instructructions

The Automatic FTP Script

Setting up PI Batch File Interface on the PI 3 Home node

Setting up the Interface

Running the Interface

Running the Interface on NT

CHIPtoPI as an NT Service

CHIPtoPI Interactively, not as a Service

Running the Program on HP-UX

Running the Program on VMS

Picking up CHIP Point Database Changes

Sample Digital State Table

PI 2 Sample Digital State Table

PI 3 Sample Digital State Table

Appendix A: Linking/Re-linking CHIPtoPI on VMS

Appendix B: Installation of CHIPtoPI on VMS from a Separate Tape

Appendix C: Migrating from the PI-CHIP Interface to the CHIPtoPI Interface

The CHIPPTCONVERT Utility

Appendix D: Interface Distributions as Self-Extracting Executables

NT Installation

UNIX Installation

VMS Installation

Documentation Updates

Appendix E: File conversion utility for VMS save sets

Reblock

Installing REBLOCK

Useing REBLOCK

Sample Session on VMS node

VMS Set File Command

VMS BCK Save Set File

VMS Save Set .A or .B File

Appendix F: GNR2PI -- CHIPtoPI Point Creation Utility

GNR2PI on Windows NT

Using the PIConfig File

Using the PIDiff File

Appendix G: Failover

General Failover Overview

Microsoft Windows NT and Microsoft Windows 2000 Failover Overview

OpenVMS Failover Overview

General Failover Information

Enabling Failover on All Platforms

Failover Tag on All Platforms

OpenVMS Failover

General Requirements

Hardware Requirements

Software Requirements

Software Setup

Windows NT Failover

General Requirements

Hardware Requirements

Software Requirements

General Failover Strategy

Typical Configuration

Scenarios Covered

Multiple Interfaces on API node

Primary/Secondary Interface Failover

CHIPtoPI Interface Software Setup for Failover

Appendix H: Troubleshooting

communication failure for tag>x

Fail to initialize Chip, err: 9469, 36/253

CHIP internal operational status error: 44, Shared memory error

chip_util is unable to execute due to one of the above errors

Error Access Denied PID xx could not access the PID yy found in CH_Security.log

DevDB

Appendix I: Viewing the local CHIP Database

CHIP_UTIL

CHIPDIA

Appendix J: PI-Interface Configuration Utility CHIPtoPI Control

General

Debug Levels

Failover

Additional Arguments

11/13/184:36 PM1

Introduction

The Fisher-CHIP to PI interface moves data from the DH6200 series CHIP software to the PI System. The interface program reads the PI point database to determine which points to read from CHIP. It then scans the CHIP database and sends exception reports to the PI system. The interface can also send values from PI to the CHIP database.

This interface runs on Microsoft NT operating system, OpenVMS, and HP-UX 10.20. Also, the interface needs to reside on the same computer as the CHIP on NT, CHIP on VMS, or the CHIP on HP-UX software from Fisher. The CHIP software communicates with the PROVOX instrumentation from Fisher. The Fisher CHIP Programming Library option of CHIP is required on VMS platforms only (the VMS CHIP with the Programming Library is sometimes referred to as SuperCHIP). If the interface is to be run on Windows NT or HPUX, the programming library option is not necessary. See the CHIP User Guide from Fisher for more information about this software. The Fisher-Rosemount CHIP software software should be version P0.3 or later. The Fisher-Rosemount CHIP software on HP-UX software should be version P4.3 or later.

***NOTE, if you are running Fisher-Rosemount CHIP software version P4.3 or earlier, you will need to install and use the version of the Chiptopi interface specifically built for P4.3 or earlier. If you are running P5.0 or later, should run the version of the Chiptopi interface built for P5.0 and later. If you are running a version of the Chiptopi interface older than v1.2.0, and you wish to upgrade P4.3 or lower to P5.0 or greater, you will have to place a copy of chip_lib50.lib in the \winnt\system32 directory, and rename it to chip_lib.lib. You will also have to place a license_size50.dll in the \winnt\system32 directory, and rename it to license_size.dll. This makes it safe to upgrade to P5.0 with all builds of the Chiptopi interface.

The PI System can run on the same computer as CHIP. The PI System can also run on another computer with the CHIP computer as a PIAPI node. In this way, it is possible to have several CHIP systems on different computers sending data to a PI System. Also, running on a PIAPI node, the interface can put data into either a version 2.X PI server or a 3.X PI server.

This interface supports outputs to the PROVOX highway and supports automatic data-collection failover on VMS. Failover for Windows NT and Windows 2000 using Microsoft Cluster Server has not yet been tested. This interface does not support highway outputs or failover on HP-UX.

When reading values from CHIP, questionable status (a status code of 8 from CHIP routine Access_Point) is treated the same as good status. Questionable status occurs during conditions such as loss of controller redundancy that do not affect the values. PROVOX module failures are recorded in CHIP as communication failures. Tags with communication failures are recorded in PI with a status of "Bad Input".

Supported Features
Sign up for updates / Yes
Exception reporting / Yes
PINet/PI API / Yes
Outputs / Yes
Vendor software required / Yes
Failover / Yes*
Maximum points / limit by resource
Uniint based / Yes

*Failover is currently supported only on VAX and Alpha VMS, and has not yet been tested on Windows NT and Windows 2000.

*** Users migrating from the PI-CHIP Interface on VMS to the CHIPtoPI Interface see Appendix C: Migrating from the PI-CHIP Interface to the CHIPtoPI Interface for detailed information on the CHIPPTCONVERT Utility.

***** NOTE: THE OLD VMS BASED CHIP INTERFACE WILL NO LONGER BE THE PRIMARY CHIP INTERFACE. We will be shipping chiptopi to all new chip customers. Currently, chiptopi provides failover on VMS. Version 1.2 of the old VMS based PI-CHIP interface is included on this tape in the backup saveset CHIP_VMS.bck or those customers who are not prepared to migrate to CHIPtoPI.

PI Point Definition

A PI point or tag is a single parameter from a CHIP point. For example, a process variable and a set point are part of the same point in the Fisher system. In the PI System, these parameters are stored as two separate tags. The following PI point attributes determine how values are interpreted as they are moved from CHIP to PI or PI to CHIP.

Point Source

The point source is any one-character value, for example F. The point source must be defined in the point source library before interface operation on version 2.X of the PI system. Also, the point source used in the PI tag definition should match the point source used in the interface startup file.

Source tag

For outputs, the tag you are creating is only a pointer tag. The name of the tag, containing the values to be sent to CHIP, must be entered here. If this field remains empty, the pointer tag itself contains the values to be sent.

Instrument tag

If Location1 is 0, the Instrument tag field should contain the CHIP tag name. For compatibility with previous versions of PI-CHIP, this field or the Extended Descriptor field can contain the CHIP tag name.

Point Type

This is usually R/float16/float32 for analog points, I/int16/int32 or D for digital points, modes, alarms, and pulse counts. However, any PI point type can be used for any CHIP point. For instance, an analog CHIP point may be stored in a PI point with a type of I/int16/int32. The value is rounded off in the PI System in this case.

When the interface is running on Windows or UNIX, and writing data to a PI3 home node, negative integer values are now able to be scanned, whereas they previously were not. If the interface runs on PINet or a PI2 home node, this feature is not available. (2.7.0.3).

Extended Descriptor

The Extended Descriptor can be used to specify a number of attributes for the CHIP interface tag. If Location1 is 0 and the CHIP tag name is not defined in the Instrument tag field, the first 16 characters of the Extended Descriptor should contain the CHIP tag name.

Also, the interface supports event based inputs. The syntax for defining an event-based point is to add the following in the Extent 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 CHIP for all the event inputs associated with this event tag. A new event is defined as a snapshot event with time stamp greater than the existing snapshot time. The event based input tags are useful for batch analysis.

You can also use the Extended Descriptor to specify the bit to extract in the LCP Status Word, or the EDCD statuses. Use the syntax:

PI2 Server: BIT=X,where X is the bit number from 1 to 16.

PI3 Server: BIT=X,where X is the bit number from 1 to 32.

If the BIT option is not specified for a LCP Status Word tag or if the BIT option is set to 0, the whole status word is stored into PI.

You can also use the Extended Descriptor to specify the Occurrence number for point type 100 DDP Highway Outputs. Use the syntax:

DDP=X, where x is the occurrence number

Location1

This is the CHIP DBI (database index). If Location1 is 0, the CHIP tag name should be in the beginning of the Extended Descriptor or in the Instrument Tag. Note that the interface will convert the CHIP tag name to its corresponding DBI upon startup. If, at any time, the DBI for any tag changes, the affected PI tag will need to re-added to the interface, or the interface will have to be stopped and restarted. To cause the tag to be re-added to the interface, modify a benign tag attribute field, such as the descriptor. The interface will pick up the change, and re-add the tag to the interface, and re-obtain the DBI. This behavior will be modified in a future release of the interface.

Location2

This is the CHIP point type for inputs and local outputs (see Table B-6 of the CHIP User Manual, UM4.10:DH6215). The sign of this parameter determines the direction of data transfer from CHIP to PI. If this value is positive, the value is transferred from CHIP to PI. If this is the negative of the CHIP point type, values are sent from PI to CHIP.

Location3

This determines which CHIP parameter is associated with this PI tag for local inputs and outputs. Location2 determines how this parameter is interpreted (see table below).

Location4

This parameter determines the scan class of the tag. The number of scan classes and the scan frequencies are specified in the interface startup command file. A value of 1 in Location4 assigns this tag to the first scan class specified in the startup file; a value of 3 assigns the tag to the third scan class.

Location5

This is the CHIP System Number or the interface ID number. It is used when there is more than one interface running on different computers. In that case, this parameter differentiates between points with the same DBI on different CHIP systems. If the interface ID number is specified in the interface startup command file, only points with Location5 matching the ID number are loaded. If the startup command file does not specify an interface ID number or it specifies -1, all the tags with matching point source are loaded, i.e. Location 5 are ignored.

UserInt1

This parameter determines whether a conversion factor is to be applied to CHIP Point Type 31 CV5 to CV8 input values. The default behavior is to apply no conversion to the CV5 to CV8 input values. If UserInt1 = 1, and the PI tag is a floating point tag, then the CV value will be converted from percent to floating point value (effectively dividing the value by 256). This feature requires that the PI-API be version 1.3.x or greater. (2.1.8)

These point attributes also affect the interface program

• Point Type
• Scan
• Exception Deviation
• Exception Minimum Time
• Exception Maximum Time
• Digital Start Code and Digital Number (PI 2.X)
• Digital State Set (PI 3.X)

Since this interface does exception reporting, the Compression Minimum Time should be less than the scan time for the interface in most situations. The exception reporting algorithm sends values from consecutive scans. If the Compression Minimum Time is too large, the second of these two values will never be recorded. Use the Exception Minimum Time only if it is necessary to throttle data from especially noisy points. The Scan attribute can be used to stop data collection.

The following point attributes do not apply to CHIP points.

• Square Root
• Convers
• TotalCode

Input-specific PI Point Parameters

The interface program recognizes the CHIP point types and parameters listed in this table. The first PI Pointtype listed is most like the Fisher CHIP database point type. If there are two listed, and they are separated by a comma, both pointtypes are recommended. If the second value is in parentheses, it is second choice for matching the Fisher CHIP database point type.

Local Inputs
CHIP Point Type (Location2) / CHIP Parameter / Location3 / Recommended PI Pointtype
PI 3 PI 2
1 / PV / 1 / Float16 (Int16) / R (I)
Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (int16) / D (I)
2 / Count / 1 / Int16 / I
Alarm / 5-10 / Digital (int16) / D (I)
4 / PV1 / 1 / Float16 / R
PV2 / 2 / Float16 / R
5 / PV / 1 / Float16 / R
SP / 2 / Float16 / R
IVP / 3 / Float16 / R
Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (int16) / D (I)
Output Tracking / 35 / Float32, Digital / R, D
Integral Tracking / 36 / Float32, Digital / R, D
Setpoint Tracking / 37 / Float32, Digital / R, D
7 / PV / 1 / Float16 / R
SP / 2 / Float16 / R
IVP / 3 / Float16 / R
Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (int16) / D (I)
Bias or Ratio / 11 / Float16 / R
8 / PV / 1 / Float16 / R
SP / 2 / Float16 / R
IVP / 3 / Float16 / R
Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (int16) / D (I)
Bias / 11 / Float16 / R
Ratio / 12 / Float16 / R
9 / Value / bit number, 1-4 / Digital (Int16) / D (I)
Mode / 5 / Digital (Int16) / D (I)
10 / Mode / 4 / Digital (Int16) / D (I)
Number UV's / 13 / Int16 / I
Operation Number / 14 / Int16 / I
Step Number / 15 / Int16 / I
Phase Number / 16 / Int16 / I
Unit State / 17 / Int16 / I
Hold Phase Number / 18 / Int16 / I
Operation Complete / 19 / Int16 / I
Unit Status / 20 / Int16 / I
Operation Timer / 21 / Int16 / I
State Timer / 22 / Int16 / I
Step Timer / 23 / Int16 / I
Iteration / 24 / Int16 / I
Fail Index / 25 / Int16 / I
OAR / 26 / Int16 / I
OAR Sequence No. / 27 / Int16 / I
Message Number / 28 / Int16 / I
Message Param 1 / 29 / Float16 / R
Message Param 2 / 30 / Float16 / R
Activity Point DBI / 31 / Int16 / I
Highway Address of Console / 32 / Int16 / I
Unit Variable #n / 100 + n(note 1) / Float (note 1)
11 / Mode / 4 / Digital (Int16)
In/out of Service / 13 / Digital, Int16 / D (I)
Off Scan / 14 / Int16 / I
SP Number / 15 / Int16 / I
PV Number / 16 / Int16 / I
Group Status / 17 / Digital (Int16) / D (I)
Fail Index / 18 / Int16 / I
12,13 / Mode / 4 / Digital (Int16) / D (I)
In/out of Service / 13 / Digital, Int16 / D, I
Off Scan / 14 / Digital, Int16 / D, I
Discrete Value / 15 / Int16 / I
14 / Mode / 4 / Digital (Int16) / D (I)
In/out of Service / 13 / Digital, Int16 / D, I
Off Scan / 14 / Digital, Int16 / D, I
SP Number / 15 / Int16 / I
PV Number / 16 / Int16 / I
DCD Status / 17 / Digital (Int16) / D (I)
Input Channel Status / 18 (note 4) / Digital, Int32 / D, I
Output Channel Stat / 20 (note 4) / Digital, Int16 / D, I
Interlocks Configured / 21 (note 4) / Digital, Int16 / D, I
Condition – Status / 22 (note 4) / Digital, Int16 / D, I
Condition – Last Fail / 23 (note 4) / Digital, Int16 / D, I
Condition – Override / 24 (note 4) / Digital, Int16 / D, I
Miscellaneous Flags / 25 (note 4) / Digital, Int16 / D, I
Setpoint Disables / 26 (note 4) / Digital, Int32 / D, I
18 / PV / 1 / Float32 (Int32) / R (I)
Local DDP / 171-186 / Float32 (Int32) / R (I)
19 / Real Value / 1 / Float32 (Int32) / R (I)
ASCIIMSG / 34 (note 5) / String / N/A
21 / Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (Int16) / D (I)
Activity State / 13 / Digital (Int16) / D (I)
Activity Status / 14 / Int16 / I
Iteration Count / 17 / Int16 / I
Procedure Index / 24 / Int16 / I
Process Index / 25 / Int16 / I
Hold Process Index / 26 / Int16 / I
Grade Index / 27 / Int16 / I
Point Set Number / 28 / Int16 / I
Activity Index / 29 / Int16 / I
Statement Index / 31 / Int16 / I
Fail Value / 32 / Int16 / I
State Timer / 33 / Int16 / I
Batch ID / 34 (note 5) / String / N/A
31 / Mode / 4 / Digital (Int16) / D (I)
Alarm / 5-10 / Digital (int16) / D (I)
In/out of Service / 13 / Digital, Int16 / D, I
Off Scan / 14 / Digital, Int16 / D, I
Fail Index / 17 / Int16 / I
State / 18 / Int16 / I
Status Word / 19 (note 2) / Int16 / I
UserDefined integer (2.5.9.0) / 20 (note 2) / Int16 / I
CV #n / 100 + n (note 3) / Float32 (Int32) / R (I)

Note 1: n is between 1 to 32 for Unit Variables. Uvs 1-8 use Float64, Uvs 9-32 use float16.

Note 2 : for LCP Status Words and User-defined integers, you can extract a single bit from the Status Word with the BIT keyword in the Extended Descriptor. The PI tag in this case can be a Integer, Digital, or Real Point Type. If you don’t use the BIT processing option, the entire Status word being returned. Since the value can exceed the maximum integer value of 32767, it is recommended that the PI2 tag be defined as Point Type Real and High Precision, and the PI3 tag be defined as an int32 tag.

Note 3: n is between 1 to 12 for the CVs.

Note 4: 16-bit statuses with Extended Descriptor field = 0 or 17 (record the whole status) must be Full Precision Real tags on PI 2 or int32 (float32), otherwise the value could result in an Over/Under Range value. To specify just one bit, you must specify the bit # in the Extended Descriptor field, in the form BIT=x.
To read the first bit set to ON from the 8-bit statuses, specify BIT=10 in the Extended Descriptor field. (2.5.4.0)
Note 5: To scan ASCIIMSG and BATCHID string tags on a VMS PINet and send them to a PI3 server, you need to run the PIFTP process and install the BatchFile interface on the PI3 server or on an API node. This is documented below in a section titled “FTP String Files to PI 3 Home Node”.