PI to Measurex Open
Interface to Measurex Systems

Version 3.17 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.
PTPXTCP.DOC

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

July 15, 19971

Table of Contents

Introduction......

PI Point Definition......

Point Parameters Definition......

Point Examples......

Profile Status Handling......

Time Stamps......

Software Configuration......

Hardware......

Software......

Rate Counter......

Interface IOStatus Codes......

Startup File......

Installation Checklist – DEC VMS......

MXO Interface Files......

Installation Tasks - DEC VMS......

Installation Checklist – NT......

MXO Interface Files - NT......

Installation Tasks......

Setting up the Interface as a Service......

Running the Interface in Interactive Mode......

Interface Startup and Shutdown Files......

Interface Operation......

Data Rate Monitoring......

Error and Information Logging -- VMS......

Error and Information Logging -- WinNT......

Error Messages......

Error Modes......

Appendix......

Glossary......

Revision History......

July 15, 19971

Introduction

The PI Measurex Open (MXO) interface connects OSI Software’s Plant Information (PI) system to Measurex LAN Devices that support Measurex’s ODX Protocol. The interface allows PI systems to access most data in nodes on Measurex LANs. It also supports PI outputs, which can be used to send data to the Measurex nodes.

This interface consists of a program running on the PI Server or PI API/PINet node making calls to/from the PI archive and communicating with the Measurex node via TCP/IP calls. The MXO interface can run on DEC VMS or Windows Intel NT computers.

The supported Measurex system configurations (from the older to the newer systems) are as follows:

1. PI to MX Server to Data Freeway nodes, Vision 2000 systems, etc.: The MX Server communicates to its Data Freeway nodes via Measurex's proprietary Data Freeway hardware and Omni operating system software. The protocol from the older systems is converted to ODX and communicated from the MX Server as ODX.

2. PI to Measurex Application Manager (AM): (AM release 1.0 and 2.0 or higher, also referenced as MXOpen release 94). This is a Peer to Peer connection in which the PI system communicates with only one Measurex AM node per PI interface process. The AM is still proprietary Omni operating software and communicates using ODX protocol. On some of the older units, memory mapping may be a problem for large amounts of profile tag retrieval. MX can supply the customer a ‘patch’ to solve the memory addressing of large amounts of profile data.

3. PI to MX Server to AM(s): The PI to MX Server connection utilizes ODX Protocol. The MX Server can then communicate with multiple AM’s.

4. PI to DaVinci: The newest generation of Honeywell/Measurex gauging system controls are on an NT platform and may or may not communicate with AM’s. In some cases, the AM logic is programmed to run on the NT and the NT box connects directly with the gauge. There are 2 scaled-down versions of DaVinci. One is MX Proline and the other is Micro CD Open. The Proline communicates directly with the gauge and the CD Open communicates CD logic to foreign gauging systems (ABB). In either case, the protocol available is ODX (MX Part Number: 3-5877-01 ODX Communication Software). (OPC, DDE and ODBC protocols are also supported by the DaVinci product line, but may require additional software from MX.)

In configurations 1 and 3, the connection is Peer to Peer with respect to the Measurex Server. Depending upon the configuration of the interface startup file (MXOn.COMfor VMS and MXOn.BAT for NT), the connection may be either Peer to Peer or Peer to Many with respect to individual Measurex nodes.

Thus, one PI interface can get data from and send data to multiple MX nodes through the MX Server. Or one individual interface process can be dedicated to obtain/send data from/to a single Measurex node that is connected to the MX Server.

Connection Options [†]
Measurex / For use with AM, this interface requires Measurex ODX software version 1.4 or higher. For use with the MX Server, it requires Server software version 1.2 or higher.
TCP/IP / TCP/IP support is required on the computer executing the interface. VMS -- certified with TGV Multinet on and DEC UCX. NT – Certified on MS TCP/IP stack for WinNT 3.51 and 4.0
Supported Features
Sign Up for Updates / Yes
Exception Reporting / Yes
PINet/PI API Support / Yes
Outputs / Yes
Vendor Software Required / No
Failover / No
Maximum Number of Points / Limited by capacity of Measurex Node
Uniint based / Yes* - modified version of uniint

Figure 1. Connection Topologies for P1 to Measurex Interface

Note:Beginning with version 3.0 of this interface: The box representing PI Host Process may also refer to a PI API node running the interface.

PI Point Definition

The MXO interface uses the startup file (MXOn.COMfor VMS and MXOn.BAT for NT) and PI point database to map PI tags to the corresponding Measurex symbol names and MX nodes. As shown in Figure 1, there are a number of connection topologies, which can be utilized. In all cases, the Measurex symbol name must be defined in the Measurex system before it can be accessed by this interface. For Data Freeway nodes, the symbol names are defined in the MX Server; for Application Manager nodes, the symbol names are defined intrinsically within the Application Manager.

Each PI point can be set up to be either an INPUT or OUTPUT tag. For the OUTPUT tags, the interface outputs the value of the tag when triggered by changes in the tag's value or status of the tag’s Source Tag.

The INPUT tags can be divided into SOLICITED and UNSOLICITED categories. Each category can be further subdivided into EVENT- or TIME-driven:

INPUT Tags
Solicited / event driven / PI requests a value for this tag from the Measurex node when the Event tag defined for these tag changes.
time driven / PI requests a value for this tag from the Measurex node at the repeat rate of the Scan Group in which this tag is placed.
Unsolicited / event driven / The Measurex node sends a value to PI for this tag whenever the specified Measurex event occurs in the Measurex system.
time driven / The Measurex node sends a value to PI for this tag at the defined repeat rate according to the Measurex’s clock.

Point Parameters Definition

When creating a PI data point to get data to/from the Measurex node, the point parameters have to be set up correctly in order that the MXO interface can correctly transform the PI formats into formats and tables understood by Measurex. The following is a description of the important parameters.

Point Source

The point source is any one-character value that is usually the same for all points of MXO interface. If a different point source is used, edit the file PISysExe:MXOn.COM(or \pipc\interfaces\MXO\MXOn.BAT) to change the character specified and run Point Src from the PI menu to define the character and establish the limits.

Notes:(1) n is the link number of the interface.
(2) The point source for each interface link should be unique within the PI System.

If the PI Server is running PI2 then the Point Source Table needs to be edited as shown below.

Location 1 / Location 2 / Location 3 / Location 4 / Location 5
1001 / 110000 / 0 / 0 / 0
99999 / 521024 / 99999 / 99 / 199999

Point Type

The interface supports the following PI2 point types. This is usually R (real) for data values, and I or D for counters, flags, etc. However, any PI point type can be used for any PI point.

The interface supports the following PI3 point types:Float16 and Float32, Int16, discrete D, and string tags. String tags can only be used when the interface is running on NT-Intel and sending data to a PI3 Server.

Notes:(1) If D or I is used for a real value and the value is less than 0 or greater than 32767, the point is given a status of either UNDERRANGE or OVERRANGES, respectively.
(2) Measurex status flags (in Measurex parlance, Ordinals) may be stored in either D or I type variables.

Location1

The first location contains the Process Number (PP) and the Measurex System Number (SSS) packed as:

(PP * 1,000) + SSS

i.e.PPSSS

Where:

  1. Process Numberrefers to the ASCII name (See description of /PROC in startup file item below.) of the group of process equipment associated with this PI tag. For PI Measurex ODX interfaces, PP=1 (there is only one Process Name per interface) since the connection is Peer to Peer with AM nodes.
  2. Measurex System Number matches the startup parameter in MXOn.COM(or MXOn.BAT).

The specific usage of these items depends upon the nature of the connection with Measurex and upon the startup file. See description of /MXO parameter in Software Configuration below.

Location2

The second location is used to specify the Variable Type (V), the Data Type (D) and the Array Element Number (AAAA) packed as:

(V * 100,000) + (D* 10,000) + AAAA

i.e.VDAAAA

where:

  1. Variable Type (V) specifies the type of variable referred to by the Measurex symbol name (reference the “Instrument Tag” below):

input / output
1 / Single value / Y / Single value
2 / Array: one element in a structure of equivalent values
3 / ODX / Scanning Display Profile Array: one element in a structure of equivalent values
4 / ODX / Scanning Reel Profile Array: one element in a structure of equivalent values
5 / ODX / Scanning Minislice Profile Array: one element in a structure of equivalent values
6 / ODX / Numbers stored in Measurex (v2.14 and higher)
7 / ASCII Strings (PI versions supporting string tags)

Variable types 3 through 6 are supported only for Peer to Peer Connections to Measurex AM Nodes via ODX. Variable types 3 - 5 provide are provided for the special information embedded in scanner based profiles (i.e., Scanner status, sensor status, and edge positions). In order to provide this additional information, the interface makes assumptions that the AM follows a Measurex symbol naming standard. (See Section on Profile Status Handling below).

Variable type 6 allows the interface to receive ASCII-converted number data from Measurex and store it as a number in the PI database. The interface does not support other types of ASCII data.

  1. Data Type (D) specifies the kind of data. Two data types are supported:

1 / Numeric Value
2 / Digital value (In Measurex terminology, an Ordinal value)
  1. Array Element Number (AAAA) specifies the correspondence of this PI point with an element within a Measurex array (Variable Type 2 to 5). The maximum Array Element Number for Variable Types 2 to 5 is now 1024.

Location3

The third location is used to set up an UNSOLICITED TIME where Measurex provides the time trigger:

MX Trigger Time Rate (RRRRR) in seconds:

RRRRR

where:

MX Trigger Time Rate (optional) specifies how often Measurex should send the data for this PI tag to PI. This field must be zero if PI Scan Group, PI Event or Measurex Event triggers are defined. This parameter is required for UNSOLICITED TIME INPUT tags.

Location4

The fourth location is used to set up a SOLICITED TIME where PI provides the time trigger:

Scan Group

Scan Group number (optional) specifies the Scan Group to which this point belongs. This parameter is required for SOLICITED TIME INPUT tags.

The user defines a scan list by specifying the time between executions for each scan list in the interface’s startup parameters (See MXOn.COMfor VMSorMXOn.BAT for WinNT). The scan lists defined thereby, are referenced in the Location 4 parameter by their sequential position (i.e., 1,2, 3, etc.) in the startup parameters. For example: if there are three Scan Groups each executing at a different rate, then there will be three Scan Groups specified in the startup parameters.

If the value for this PI tag should be requested at the rate specified by the third Scan Group time, then Location 4 contains a Scan Group value of 3.

This parameter will be ignored if other parameters defined in the PI tag specify time or event triggering.

Location5

Specifies the Input/Output Flag (F), the Measurex Processor Number (M) and the BTI Number (BBBB) packed as:

(F * 100,000) + (M * 10,000) + BBBB

i.e.FMBBBB

Where:

  1. Input /Output Flag: If flag isset to 1, tag makes outputs to the Measurex system upon changes in its value or other PI-defined trigger.
  2. MX Processor Number (optional) defines the ASCII name of the Measurex processor (LPN) associated with this point. It is used in conjunction with interface startup parameter /LPN=ProcessorName1 /LPN=ProcessorName2 etc. Processor Number references the nth item in the list of /LPN= startup parameters to provide the ASCII for the Processor name.
  3. BTI Number (optional) defines the ASCII name of the Measurex memory bank associated with this point. It is used in conjunction with interface startup parameter /BTI=BTIName1 /BTI=BTIName2 etc. BTI Number references the nth item in the list of /BTI= startup parameters to provide the ASCII for the BTI name.

Notes:(1) The LPN and BTI numbers are usually not required unless the Measurex symbol name is not unique within a Measurex LPN. In practice, the symbols of interest to PI are not likely to be so defined.

(2) If either LPN or BTI number is provided, then both must be provided.

The interface log file will report an error if Measurex can not uniquely resolve the symbol name; i.e., Measurex system has more than one symbol with the same name.

Instrument Tag

Measurex symbol name for input or output. Each PI tag must have a valid Measurex Symbol Name in the Instrument Tag field. When the interface is connected to an AM node, it will report instances of undefined Measurex symbol names.

Note:PI limits the Instrument Tag to 32 characters whereas Measurex allows up to 40 characters.

Symbols can not be verified when the interface is communicating via the MX Server with Data Freeway. This is because the MX Server does not support external symbol verification for Data Freeway. Thus, for Data Freeway nodes, the interface assumes all symbols to be properly defined in the MX Server.

Note:The MX Server sometimes has problems when attempts are made to access undefined symbols on Data Freeway nodes. As a result, it is suggested that the user verify the accuracy of the symbols for Data Freeway nodes by trying them at the MX Server.

If Measurex symbols are not unique within a node and require LPNx\BTIDx type specifications, do not specify the full Measurex variable in the instrument tag as LPNx\BTIx\Variable_Name. If the LPN and BTI are specified in Location 5, the interface will automatically prepend the LPN and BTI specification to the symbol name specified in the Instrument Tag.

Valid characters in symbol names are “_“,“$“,“0-9”, “a-Z”, and “.” . No embedded blanks are allowed.

Source Tag

PI tag (not case sensitive) used as the source of the data to be output to the Measurex Symbol specified by the Instrument Tag.

Notes:(1) To use this field requires site running PI V2.06 or higher.

(2) An alternative method for specifying a source tag is to include source = any valid PI Tagname in the extended descriptor.

(3) A source tag name is required for OUTPUT type of tags.

Extended Descriptor

This is limited to 80 characters. The following possible delimiters and symbol names must fit within the 80 characters.

  • /Tx = any defined Measurex Ordinal Symbol Name (optional). It specifies a Measurex event trigger that is used to trigger its transmission of unsolicited data to PI. It has maximum of 31 characters. This parameter is required for UNSOLICITED EVENT INPUT tags. The Measurex Symbol must refer to a Measurex Ordinal (i.e., digital flag).

Where:/Tx= may have the following values:

/T0 = / Trigger on 0 to 1 transition of Measurex variable
/T1 = / Trigger on 1 to 0 transition of Measurex variable
/T2 = / Trigger on any transition of Measurex variable
  • /Vx = any defined Measurex Symbol Name (optional). It specifies a Measurex variable, which provides the validity of the Measurex variable specified in the Instrument Tag Field. Maximum of 31 characters. This is useful for attaching status to any given Measurex value. Measurex Symbol can refer to any numeric data value, where: /Vx= may have the following values:

/V0 = / Value is valid if the value referenced by this Measurex symbol is 0
/V1 = / Value is valid if the value referenced by this Measurex symbol is not 0

If a variable is not valid, it is shown in PI as UNAVAIL.

  • event = any valid PI Tagname (optional; not case sensitive).

If an event tag is specified, it supersedes the Scan Group specification in Location 4. This parameter is required for SOLICITED EVENT INPUT tags. It specifies a PI triggered event. There will be an event whenever the specified Event Tag Name changes value of status. When the event= option is used, location4 = 1.

  • source = any valid PI Tagname(optional; not case sensitive).

It may be used for output tags to specify the PI tag that is the source of data for this tag. This parameter (or Source Tag) is required for OUTPUT tags.

Point Examples

The following PI point examples explain the point parameter definition specified above.

Profiles -- Unsolicited Event Input

PI tag for the 50th element of a Measurex display profile named P11_BWAR, which is, triggered by the Measurex event flag P1EOS.ORD ; Process #1, Measurex #1.