Moore ICI - OSIsoftcdn.osisoft.com › interfaces › 1369 › PI_MrICIVMS_VAX… · Web...

Moore ICIInterface Documentation

Version 1.6 and greater

PI-IN-MR-ICI-VAX OSI Software, Inc.

How to Contact UsPhone (510) 297-5800 (main number)

(510) 297-5828 (technical support)

Fax (510) 357-8136

Internet [email protected]

World Wide Web

http://www.osisoft.com

Bulletin Board

(510) 895-9423Telebit WorldBlazer modem (Hayes, MNP, or PEP compatible)8 data bits, 1 stop bit, no parity, up to 14400 bps downloadprotocols: Xmodem, Ymodem, Zmodem, Kermit

Mail OSI Software, Inc.P.O. Box 727San Leandro, CA 94577-0427USA

OSI Software GmbH Hauptstrae 30 D-63674 Altenstadt 1Deutschland

OSI Software, Ltd.P. O. Box 8256Level One, 6-8 Nugent StreetAuckland 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.

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.

document.doc

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

Table of ContentsIntroduction.................................................................................................1

PI Point Definition.......................................................................................3

Point Source............................................................................................3Point Type...............................................................................................3Location1.................................................................................................3Location2.................................................................................................3Location3.................................................................................................5Location4.................................................................................................5Location5.................................................................................................6UserInt1...................................................................................................7UserInt2...................................................................................................7Square Root Code...................................................................................7Exception Specs......................................................................................7Additional Tag Configuration Descriptors................................................7Point Attributes Not Used by Interface....................................................8

Model 320 ICI Hardware Configuration......................................................9

Configuring the ICI...................................................................................9RS-232C Cable Setup...........................................................................10Terminal Server Setup...........................................................................10I/O Port Configuration............................................................................11

Hardware Configuration...........................................................................12

Configuring the ICI.................................................................................12DR11-W Data........................................................................................12

February 1998 iii

DR11-W and MV-DR11-W Cabling.......................................................13

Hardware Configuration...........................................................................14

Configuring the ICI.................................................................................14RS-232C Cable Setup...........................................................................14Terminal Server Setup...........................................................................15I/O Port Configuration............................................................................15

Software Configuration.............................................................................16

PI Software............................................................................................16Point Source.......................................................................................16Rate Counter......................................................................................16Interface Files.....................................................................................16Moore#.Com.......................................................................................17MooreDetach.Com.............................................................................18MooreLink.Com..................................................................................19

Moore Products Company Supplied Software.......................................21HLL Communication Files..................................................................21LIL Communication Files....................................................................22

VAX SYSGEN Parameters....................................................................22

Interface Operation...................................................................................23

Startup...................................................................................................23Shutdown...............................................................................................23Information and Error Messages...........................................................23ICCSTS or ICISTS Timeouts.................................................................24Using the Moore Products Interactive Utility..........................................24

Installation................................................................................................26

Interface...................................................................................................28

Interface Point List.................................................................................28Output Data...........................................................................................28Input Data..............................................................................................28

iv OSI Software, Inc.

Scanning Principles...............................................................................29Time Stamp........................................................................................29

Local Instrument Link (LIL)....................................................................29High Level Link (HLL)............................................................................29

LIL Address Selection (Minus 1).........................................................31Data Format Selection (Switch 2).......................................................31Switch Legend....................................................................................34BAUD Rate Table, SW 2 Switch Settings........................................34

February 1998 v

List of FiguresFigure 1. ICI 320 Serial Port Board..................................................................................................31

Figure 2. Data Set/Data Terminal Connections.................................................................................32

Figure 3. ICI 320 MPU Board Dip Switch........................................................................................32

Figure 4. Blowup of ICC Piggyback Board......................................................................................33

Figure 5. Setting of Jumpers W8 and W9.........................................................................................33

Figure 6. Front Panel, ICI 2.0 or 2.5.................................................................................................34

vi OSI Software, Inc.

IntroductionThe Moore ICI Interface provides bi-directional transfer of data between the Moore Products Company's Local Instrument Link (LIL) and Hi-Level Link (HLL) global databases, and the Plant Information (PI) System. Communication between the DEC VAX or ALPHA computer and the HLL global data base is accomplished using either:

Moore Products Company's Mycro Model 3932 Independent Computer Interface (ICI) or Mycro Model 3934 ICI.

The Mycro Model 3932 ICI (commonly referred to as an ICI-2.5) uses an RS-232C serial link to the VAX or ALPHA computer. The Mycro Model 3934 (commonly referred to as an ICI-2.0) uses a high-speed 16 bit parallel interface that allows direct memory access (DMA) data transfer. Communication to an ICI-2.0 is only supported on VAX computers.The ICI-2.0 and the ICI-2.5 provide identical functionality. Communication between the VAX or ALPHA computer and the LIL global database is accomplished via Moore Products Company's Model 320 ICI. The Model 320 ICI uses an RS-232C serial link to the VAX or ALPHA computer. The interface can run on a VAX or ALPHA containing either the PI Home Node or a PINet node.The Moore ICI Interface consists of:

A single executable program and A number of associated utility programs for configuring, starting, and stopping the interface.

There may be one or more ICI's connected to the PI System. However, there may only be one ICI-2.0 connected per VAX. The PI system can communicate with ICI-2.0's, ICI-2.5's, and Model 320 ICI's concurrently. Every ICI requires its own copy of the interface program. If either an ICI-2.5 or a Model 320 ICI is to be shared by other processes residing on the VAX or ALPHA, then each process must have the VMS SHARE privilege. Multiple processes that communicate with an ICI-2.0 do not need the VMS SHARE privilege. Outputs require the VMS SYSLCK privilege.The interface uses Moore Products Company's HLL ICI Communications Software Package to communicate with the ICI-2.0 and the ICI-2.5. Use of an ICI-2.0 also requires a Moore parallel I/O driver. Moore Products Company's LIL ICI Communications Software Package is used to communicate with the Model 320 ICI. The ICI's are respond only devices and are dependent upon the VAX for issuing commands. OSI Software, Inc. now distributes both the Moore Products Company’s HLL and LIL Communications Software with the PI-Moore ICI interface. Inputs from an ICI are scanned on a periodic basis. Outputs are sent out to an ICI whenever an

February 1998 1

Moore ICI Version 1.6 Interface Documentation

output value changes.

Supported Features

Sign up for Updates Yes

Exception Reporting Yes

PINet Yes

Outputs Yes

Vendor Software Required Yes

2 OSI Software, Inc.

PI Point DefinitionThe following information is necessary for defining a PI point to be read from or written to either the Moore LIL or HLL global databases. There may be one or more PI points associated with each global data base channel. A channel can hold up to 16 bits of data; one or more bits combined can be used to hold separate pieces of data. Conversely, a single PI point can be the resultant of two global data base channels.

Point SourceAll points defined in the PI Database to be used by the Moore ICI Interface must share a common point source. The point source is any one-character value; for example M. The point source must be defined in the point source library before interface operation (see Software Configuration).

Point TypeThe interface supports all three PI point types, real R, integer I, and discrete D. Multiple discrete alarm and status bits are processed to form individual PI digital points.

Location1The first location is the number of the ICI that either the HLL or LIL is connected to. There can be up to 99 ICI's interfaced to the PI system.

Location2The second location is the HLL or LIL global data base address. More than one tag can share a single PI address. This applies to both inputs and outputs. The HLL address must be specified if: the value of the tag is either an input from, or an output to a HLL device, such as

a MMLC or MDAS. the value of the tag is an input or an output from a LIL device, such as a Mycro

352, but it has been added into the HLL global database.The HLL address specifies the High Level Link #, Satellite #, Slot #, and Channel #. The HLL address is in the form of:LSSTTCCCwhereL = HLL numberSS = Satellite numberTT = Slot numberCCC = Channel number

February 1998 3


Therefore, the address of a point that is located on HLL #1, Satellite #9, Slot #16, Channel #138 is:address = 10916138

An ICI 2.5 can contain a Multi-Loop controller. Loops are always on slot 16 (Multi-Loop controller), and a Multi-Loop controller can have 64 loops per slot. Each loop consists of 4 channels, a PV, SP, output, and status/mode tag: 1 - process value 2 - set point 3 - controller output 4 - controller status/modeTo calculate the channel for a PV:channel = loop_number * 4 - 3Therefore, the address of a loop PV that is located on HLL #1, Satellite #9, Loop #23 is:address = 10916089 (channel = 23 * 4 – 3 = 89)

Likewise, to calculate the channel for the SP on the same loop:channel = loop_number * 4 – 2, or simply add 1 to the PV channel numberAnd the address for the SP on the same HLL, Satellite, and Loop is:address = 10916090 (channel = 23 * 4 – 2 = 90) or (channel = PV for same loop + 1)

Note There can be:1 - 4 HLL's on an ICI1 - 15 Satellite Stations on an HLL1 - 16 Slots on a Satellite Station1 - 256 Channels on a SlotIf the value of the tag is an input from or an output to an LIL device, such as a Mycro 352, then its LIL global database address must be specified. The address specifies the Station # and Channel#. The address is in the form of:SSCCCwhereSS = Station numberCCC = Channel numberTherefore, the address of a point that is located on Station #13, Channel #22, and Parameter #1 is:address = 13022Note, there can be:1 - LIL per ICI2 - 64 Stations on a LIL1 - 256 Channels on a Station1 - 256 Parameters on a ChannelOnly parameter 1 will be read from or output to.


Location3The third location indicates whether the PI tag will be the result of adding two input values together or if the tag is an output. If the PI tag is the resultant of two values, Location3 should be 1. If the PI tag is to be the resultant of two values, and if the resultant is to be divided by 100, Location3 should be 2. This applies to various data obtained from Mycro 382's. Both integer and real tags can be the resultant of two input values. The maximum allowable value for an integer is 32767. If the PI tag is to be an output, Location3 should be 3. If the PI tag is none of the above, Location3 should be 0.0 - single value1 - combine two values together2 - combine two values together, divide total by 1003 - tag is an output value

Location4The fourth location is used for digital points only. It is used to specify how the interface will convert an integer value into a digital state. It is used when reading or outputting controller, alarm, or status information. Location4 may take on the following values:> 0 bits are specified as decimal digits0 word is a discrete digital-1 controller source/modeThe controller source/mode is determined for MMLC, Mycro 351, and Mycro 352 loops.Location 4 > 0:Up to 5 bits can be specified. The bits can be specified in any order; i.e. bits 5,6,7, and 8 could be specified as 08050706. To specify a single bit (2-state tag), enter the bit number. To specify 2 bits, enter 100 times the first bit plus the second bit. For example, bits 7 and 8 can be specified as 0708. In this example, the PI tag is a digital state tag according to the following truth table:

bit 7 bit 8 PI value

0 0 0

0 1 1

1 0 2

1 1 3

Specify a 3-bit value as b1b2b3 (e.g. 080706). A 3-bit value has 8 possible states. A 4-bit value would be specified as b1b2b3b4 (e.g. 05060708) and has 16 possible states.It is up to the user to set up the appropriate truth table for a digital state tag. The states for all possible combinations must also be entered into the digital state table.Location 4 = -1:The controller source/mode tag uses bits 1,2,3,5,6,7,8,9, and 10 contained within the Loop Status Word for each loop.

February 1998 5


A simplified truth table is:

H E/M O R Cmp Con I/E S L A/M Pi

Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Val Mode

0 0 0 0 0 X X 0 1 0 0 Local/Man

0 0 0 0 X 0 X 0 1 0 0 Local/Man

0 0 0 0 0 X X 0 1 1 1 Loc/Auto

0 0 0 0 X 0 X 0 1 1 1 Loc/Auto

0 0 0 0 0 1 X 0 0 0 2 Cons/Man

0 0 0 0 0 1 X 0 0 1 3 Cons/Auto

0 0 0 0 1 0 X 0 0 0 4 Comp/Man

0 0 0 0 1 0 X 0 0 1 5 Comp/Auto

X X X X X X X 1 X X 6 Sync

X 1 X X X X X 0 X X 7 Eman

X 0 1 X X X X 0 X X 8 Override

1 0 0 X X X X 0 X 1 9 Hold

0 0 0 1 X X 0 0 X 1 10 Ramp

All Other Bit Combinations 11 Offline

Where0 = Logic 01 = Logic 1X = either state, does not affect logicThe twelve digital states listed above must be entered into the digital state table if you are storing the mode in a digital tag.

Location5The fifth location is used to indicate whether an input or output point is specified to be reverse acting. For inputs, the value in engineering units will be equal to: value = 100. - value. For outputs, value = 100. - value, and the value is then converted back to counts (128 - 3840). The requirements for specifying a point to be reverse acting are: the square root field must be 0, the point must be Real, and the Zero and Span must be 0. and 100. respectively. The most likely case for specifying a point to be reverse-acting is for reverse-acting controller outputs (the signal from the controller which is an input).0 = not reverse acting1 = reverse acting

Extended DescriptorThe extended descriptor is used to identify input points whose input values have a range other than the standard 128-3840 counts. If the instrument zero is NOT 0 counts


or the instrument span is NOT 4095 counts, the string %RAW must be contained somewhere within the Extended Descriptor. In addition, the instrument zero must be specified in the UserInt1 field and the instrument span must be specified in the UserInt2 field. For example, a non-standard controller might send a 16-bit signed integer to the interface. In this case, the %RAW string, along with the corresponding values in UserInt1 and UserInt2 string, allows an input range of -32768 – 32767 counts from the instrument. Note that the instrument zero and instrument span are unrelated to the tag attributes zero and span, which are in engineering units.

UserInt1This field must contain the instrument zero of the point if the Extended Descriptor contains the string %RAW.

UserInt2This field must contain the instrument span of the point if the Extended Descriptor contains the string %RAW.

Square Root CodeThe square root code is used by the interface to take the square root of, or squaring output and input data. The requirements for specifying square root extraction or squaring are: the point must be Real and Location5 must be set equal to 0.

Square Root Code Result

0 raw value

1 square root of value

2 value squared

Exception Specs.The Moore ICI interface employs exception reporting. The exception deviation, minimum time, and maximum time should be specified to control system loading. It is recommended that both the exception and compression times be set equal to 0 to make sure that all scanned values go through exception reporting, and that all exceptions go through compression reporting.

Additional Tag Configuration DescriptorsThere are additional tag configuration parameters that are not unique to the Moore ICI interface but are required for proper operation. These parameters are listed below: Tag Name Descriptor Typical Value Engineering Units Starting Digital State Code Number of Digital States

February 1998 7


Filter Code Archiving Flag Compression Flag Resolution Code Compression Deviation Compression Minimum Time Compression Maximum Time Zero Span

Point Attributes Not Used by Interface Totalization Code Scan Flag Conversion Factor UserReal1 UserReal2


Model 320 ICI Hardware ConfigurationConfiguring the ICI

Before you can configure the ICI you must remove the three card assembly from the casing. Remove the front panel by flipping the door down on the front panel and removing the screw. The card assembly can then be removed. The MPU is the bottom board, the middle board is the link board, and the top board is the serial port board. Remove the screws which attach the boards to one another so that you can get at the jumpers and switches located on the MPU and the serial port boards. The cable adaptor board (otherwise known as the data set/data terminal board) is connected to terminal C which is located on the back of the casing. The selection of RS-232C or RS-422 is determined by the jumper positions of

W5 and W6 on the serial port board. RS-232C must be selected to be compatible with the VAX. RS-232C is selected by pins 2 and 3 for jumpers W5 and W6. Refer to Figure 1 which is a schematic of the serial port board.

Two possible cable pinouts are possible as determined by the connector used on the cable adaptor board which mounts on terminal strip C. Figure 2 shows the wiring of that board and the required pinouts for the ICI to appear as either a data set (DS or DCE) or a data terminal (DT). If the ICI is configured as a DS then the DB25 female connector is used. If the ICI is configured as a DT then the DB25 male connector is used. Configure the ICI as a DS if the cable used is a straight cable. Configure the ICI as a DT if the cable used is a null modem.

Figure 2 shows the required placement of the jumpers W1 and W2 for setting flow control to either DSR or CTS. Set the jumpers; the setting must match that in the terminal server. Remove both jumpers if no flow control is to be used.

Set the baud rate of the ICI to match the baud rate of the VAX. A baud rate of 19200 is recommended. This is done by setting the W7 jumper to the proper setting. Refer to Figure 1.

Enable the null data response function. This is done by setting Switch 3 on the MPU board to the open position. Refer to Figure 3.

Enable the response delay function. This is done by setting Switch 4 on the MPU board to the open position. Refer to Figure 3.

Set the operational mode to BINARY by setting Switch 5 on the MPU board to the closed position. Refer to Figure 3.

The Model 320 ICI provides send command security. Depending upon what security level is chosen, information contributed by the computer to the ICI is restricted. The security level is set from Switches 1 and 2 on the MPU board. See Figure 3. If the computer is going to both read and output data, the recommended security level is RECORD. If the computer is to read data only, the recommended security level is PARAMETER.

February 1998 9


The data format of the computer port should be set to odd parity and 8 data bits. This is done by setting Bit 8 of Switch 2 (SW2-8) to the open position and Bit 4 of Switch 2 (SW2-4) to the open position. Switch 2 is located on the serial port board. Refer to Figure 1.Note Closed is synonymous with on, open is synonymous with off.

RS-232C Cable SetupThe computer is connected to the ICI using the appropriate connector located on terminal strip C. The desired RS-232C signal from the computer which is to drive the ICI CTS input line is jumper selectable by W1 when using the data set connector and by W2 when using the data terminal connector. The jumper may be removed completely to always enable the signal. Refer to Figure 2 for a schematic of the cable pinouts. If the connection between the VAX and the ICI is directly to a serial port on the VAX then only the TRANSMIT DATA, RECEIVE DATA, AND SIGNAL GROUND are required. If the connection between the VAX and the ICI is through a terminal server the communication cable must be configured to use CTS or DSR flow control.

Terminal Server SetupIf the Model 320 ICI is to be connected to a terminal server, you must log into the server and enter several setup commands. Setup commands can be entered by logging directly into the server in local mode or using the NCP program to log into the server from the VAX.You must set each characteristic in the server's permanent and temporary databases. Use the define command to change the permanent database and then the set command to change the temporary data base. An example of the setup commands using the define command is given below. The same commands would then have to be entered using the set command.define port 9 speed 19200define port 9 parity odddefine port 9 character 8define port 9 autobaud disableddefine port 9 modem disableddefine port 9 flow ctsdefine port 9 flow enableddefine port 9 autoconnect disableddefine port 9 autoprompt disableddefine port 9 access remotedefine port 9 break disableddefine port 9 broadcast disableddefine port 9 inactivity disableddefine port 9 interrupts disableddefine port 9 loss disableddefine port 9 message disableddefine port 9 password disableddefine port 9 pause disableddefine port 9 verification disableddefine server name Rocky !This must match the node specified in!LAT$SYStartup.com


Note If the ICI is connected to the VAX via a terminal server, it is recommended that either CTS or DSR flow control be used in the terminal server to prevent loss of data during transmission of data. Which type of flow control you use depends upon pin configuration of the cable. Flow control is enabled by the command: define port 9 flow CTS (or DSR).Once the terminal port has been defined in the server, it then must be defined in the VAX. Add the following commands in SYS$Startup:LAT$SYStartup.Com after the code for execution of the LAT control program SYS$System:Latcp. This will configure the port each time a reboot is done.CREATE PORT LTAX: /NOLOGSET PORT LTAX: /APPLICATION/NODE=node name/PORT=PORT_ZwhereLTAX: is the VMS device name of the terminal server port with X being a numbernode name is the name of the terminal serverZ is the port number on that nodeThe commands can also be entered into the system by running program Latcp. This means that the terminal server port will be immediately defined without having to wait for a reboot. Execute Latcp by typing:$run SYS$System:LatcpThen enter in the above create port and set port commands.

I/O Port ConfigurationA command procedure is provided in Moore's LIL ICI Communications Software Package to configure the interface port. The name of the command procedure is LCITT.Com. All required SET TERM commands are executed in this procedure. The logical assignment of the ICI number (ICn) to the port name is done in this procedure as well. The command to run this procedure is listed below and should be included in PISysExe:Moore#.Com.$@SYS$Manager:LCITT LTAX: 19200 Icnwhere n is the number of the ICI on a node, and n can be from 1 - 99.LTAX: is the terminal server port name. If no terminal server is going to be used, the port name will be TXAX: or TTAX:.

February 1998 11


Hardware ConfigurationConfiguring the ICI

1. Enable the null data response function. This is done by setting bit 2 of switch 2 to ON.

2. Enable the response delay function. This is done by setting bit 1 of switch 2 to ON.

3. Set the operational mode to NORMAL with switch 5. This specifies BINARY transmission of data.

DR11-W DataThe ICI-2.0 requires a DR11-W or equivalent parallel communications controller to communicate with the VAX. The DR11-W is offered by DEC for UNIBUS-based VAX computers. The MV-DR11-W is offered by MDB Systems for Q-Bus-based VAX computers. The MV-DR11-W should be used with the following switch settings. A Moore Products Company parallel I/O driver is required for both Q-Bus or UNIBUS-based VAX computers. The part number for the software is ASM 3934S002-2.

Name Setting

W Link-M Closed

B Link Closed

DMA THRTL Closed

AOO Open

W Enable Open

N Cycle Closed

MDB EIR REG Closed

4 LEV INTR Open

22 B ADRS Closed

Self Test Closed

Long Test Closed

Scope Closed

It should be noted that the ICI-2.0 will effectively limit the I/O transfer rate, regardless of the DMA THRTL and N Cycle switches.


DR11-W and MV-DR11-W CablingThe DR11-W and the MV-DR11-W are cabled in the same manner. The following instructions refer only to the MV-DR11-W controller.The ICI-2.0 is connected to the MV-DR11-W controller with two 40-conductor cables using 40-pin BERG-type flat cable connectors. Pin 1 of the ICI should connect to pin A on the MV-DR11-W, pin 2 to pin B, etc. Note that pin 1 on the ICI-2.0 is away from the printed circuit board but pin A of the MV-DR11-W is toward the printed circuit board.If straight cables (pin 1 to pin 1) are used, the ICI connections should be plugged into their sockets as intended, with the keys fitting the matching slots. However, the MV-DR11-W connections should be plugged in upside- down, with the keys toward the board rather than in the matching slots. This may require the keys to be filed down.

February 1998 13


Hardware ConfigurationConfiguring the ICI

The ICI-2.5 must be configured as listed below. Before the configurations can be set however, the ICI front panel cover must first be removed. Set the ICI-2.5 as a Data Set (DS) device if the cable used is a straight cable. Set

the ICI-2.5 as a Data Terminal (DT) device if the cable used is a null modem. See Figure 4 which contains a blowup of the of the piggyback board of the ICI's Interface Computer Assembly (it is the top board but is labeled as board 5). Before pulling the piggyback board and the ICI Interface Computer Assembly board, turn the power off to the ICI and unplug the ribbon cable from the piggyback board. Use a wrist strap grounded to the ICI unit before sliding the card assembly most of the way out. If the ICI is directly connected to a serial port in the VAX then set the W8 jumper either to the DS or DT position and remove the W9 jumper. If the connection is to be made through a terminal server then set both the W8 and W9 jumpers either to the DS or DT positions. A jumper is set to the DS position if the line dividing the two sections of the jumper is parallel to the front edge of the card. It is set to the DT position if the line is perpendicular to the front edge of the card.

The following settings are made on the front panel of the Interface Communication Computer, see Figure 5. Set the baud rate of the ICI-2.5 to match the baud rate of the VAX. A baud rate of

19200 is recommended. This is done setting bit 3 to ON and bit 4 to OFF of switch 2.

Enable the null data response function. This is done by setting bit 2 of switch 2 to ON.

Enable the response delay function. This is done by setting bit 1 of switch 2 to ON.

Set the operational mode to BINARY with switch 5.Note ON corresponds to the 1 state and OFF corresponds to the 0 state.

RS-232C Cable SetupThe RS-232C cable plugs into a DB25 female connector located in the rear of the ICI-2.5.If the connection between the VAX and the ICI-2.5 is directly to a serial port on the VAX then only the TRANSMIT DATA, RECEIVE DATA, AND SIGNAL GROUND are required.If the connection between the VAX and the ICI-2.5 is through a terminal server the communication cable must be configured to use either CTS or DSR flow control.


Terminal Server SetupIf the ICI-2.5 is to be connected to a terminal server, you must log into the server and enter several setup commands. Refer to Section 1.3.3 which contains the terminal server setup commands required when a Model 320 ICI is used. All commands should be entered exactly as shown when using an ICI-2.5 except for the definition of port parity. The port parity should be defined as follows:define port parity none

I/O Port ConfigurationA command procedure is provided in Moore's HLL ICI Communications Software Package to configure the interface port. The name of the command procedure is ICI25TT.Com. All required SET TERM commands are executed in this procedure. The logical assignment of the ICI number (ICn) to the port name is done in this procedure as well. The command to run this procedure is listed below and should be included in PISysExe:Moore#.Com.$@SYS$Manager:ICI25TT LTAX: 19200 Icn

where n is the number of the ICI on a node, and n can be from 1 - 99.LTAX: is the terminal server port name. If no terminal server is going to be used, the port name will be TXAX: or TTAX:.

February 1998 15


Software ConfigurationPI Software

In addition to the PI Point Definition, the Point Source, I/O Rate Counter, and Interface Files must be specified.

Point SourceThe point source may be any alpha character not currently used by another process or interface. The point source may be defined by running PointSrc display on the PI menu, choosing a blank field from the point source list, and entering the following location parameter limits:

Location1 Location2 Location3 Location4 Location5

1 1001 0 -1 0

99 * 3 1615141312 1

* = 41516256 for the HLL* = 64256 for the LIL

Rate CounterThe I/O Rate Counter measures the rate at which the interface sends values to the PI Snapshot; i.e. it serves as a measure of the input load. It does not take into account the output load. To use the IO Rate Counter, a rate tag should first be configured, such as SY:MOORE.xx, by copying the point definition from another rate tag such as SY:SNP001. The extension .xx should be equal to the interface number in which the rate tag is used; i.e. SY:MOORE.01 for interface #1. The interface rate tag should then be added to the IO Rate List, PISysDat:IORates.dat. For additional information on Data Rate Monitoring refer to the Interface Standard chapter of the PI Interface Manual (IN).

Interface FilesAll startup files for the interface will reside in the PISysExe: directory except for those supplied by Moore Products Company. Listed below are the files that are required for starting up the interface. The # sign refers to the interface number which can be from 1 to 99. Each interface is associated with a particular ICI which is designated by ICn, where n can be from 1 to 99. Therefore, Moore1.Com is associated with IC1, Moore2.Com is associated with IC2, etc. It is important to note that if there is to be communication to both the LIL and the HLL, the ICI numbers must still be unique; e.g. there should not be a Model 320 IC1 and an ICI-2.5 IC1.


Moore#.ComEach interface is started by executing the file Moore#.Com where # represents the number of the interface. Each interface will have its own startup file in which the ICI type (2.0, 2.5, or 320), the ICI number, the point source, the port name, the IO Rate Counter ID, the scan frequency, and the baud rate are specified. The scan frequency is actually a delay between the scanning of all devices on the link. The true scan rate is equal to the scan frequency plus the program execution time. Note that the command procedures for conditioning the terminal line (if an ICI-2.5 or a Model 320 ICI is used) must be executed from this file as well. The command procedure to use if an ICI-2.5 is used is SYS$Manager:ICI25TT.Com. The command procedure to use if a Model 320 ICI is used is SYS$Manager:LCITT.Com. The following is an example interface startup file:$! Moore1.Com$!$! 20-Aug-92 JFZ OSI, Added baud rate under customization section$! 05/15/91 JFZ OSI, Modified for MOORE ICI Interface$! 11/07/90 RAB OSI, Original Modbus1.com$!$! this command file initializes the port for communications,$! calls a Moore Products software routine to condition the$! application port if required, and starts the interface process.$! each interface should have its own command file with its own$! set of parameters as specified below.$!$! 1 - ICI Number$! 2 - ICI Type (2.0, 2.5, or 320)$! 3 - Point Source Code$! 4 - Port Device Name$! 5 - I/O Rate Counter Number$! 6 - Delay between scans, in Seconds,$! default = 10 seconds$! 7 - Baud rate$!$! customize these:$!$ ICInumber := 1$ ICIType := 320$ PointSource := M$ Portname := LTA9:$ Counter := 1$ ScanFrequency := 10.$ BaudRate := 19200$!$! condition the terminal line, if necessary$!$! if ICI is an ICI-2.0, don't condition the terminal line$! if ICI is an ICI-2.5, command file is ICI25TT.Com$! if ICI is a Model 320, command file is LCITT.Com$!$ if (ICIType .eqs. "2.0") then goto execution$ if (ICIType .eqs. "2.5") then goto condition25$ if (ICIType .eqs. "320") then goto condition320$!$! incorrect ICI type entered$ write sys$output "Incorrect ICI type entered. Enter either 2.0,"$ write sys$output " 2.5, or 320. Interface not started."$ goto end$!$condition25:

February 1998 17


$ @SYS$Manager:ICI25TT 'portname' 'BaudRate' IC'ICINumber'$ goto execution$!$condition320:$ @SYS$Manager:LCITT 'Portname' 'BaudRate' IC'ICINumber'$!$execution:$! execute interface$!$ Devnam := IC'ICINumber'$ ICI :== $PISysExe:MOORE.exe$ ICI'ICINumber','ICIType','pointsource','Devnam','counter',- 'scanfrequency'$!$end:$ exit$! end of MOORE1.COM

MooreDetach.ComEach interface startup file is started as a detached process using the following command file:$! MooreDetach.Com$!$! 08/19/91 JFZ OSI, revised for MOORE interface$! 07/20/90 RAB original$!$! mooredetach.com starts the MOORE interface as a detached process$! by detaching the command file moore#.com. moore#.com is expecting$! the interface number (#) to be passed to identify the process.$!$! the following parameter must be passed:$!$! 1 - interface number (1-99)$ if (P1 .eq. "") then goto BadParameter$!$ if (f$search("PISysExe:moore''P1'.com") .nes. "") then - goto NextStep$ goto BadFile$!$NextStep:$ if (f$search("PISysExe:moore''P1'.out") .nes. "") then - purge/keep=3 PISysExe:moore'P1'.out$!$run/detach/uic=[system]/process_name="PI-MOORE-''P1'"/priority=4 - /input=PISysExe:moore'P1'.com - /output=PISysExe:moore'P1'.out- /working_set=512/maximum_work=1024/extent=2048 - /pagefile=10000/buffer=20480 sys$system:loginout$ exit$!$BadParameter:$ write sys$output "The Interface Number Must Be Passed "$ write sys$output "as a Parameter"$ exit$!$BadFile:$ write sys$output "File Moore''P1'.Com does NOT Exist..."$ write sys$output "Interface NOT Started"$ exit$! End of File


MooreDetach.Com is passed the number of the interface to be started. In this file the priority and other process parameters are set. MooreDetach.com should be run under the system account to ensure that PI-Moore-1 has the necessary privileges for extracting and writing information to the ICI.

MooreLink.ComThe interface is linked as part of the PI Installation procedure if the Moore files are in their default directories. If this is a new installation of the interface and the Moore Software has not yet been loaded, or the Moore Software is not located in the default directories specified in the MooreLink.com procedure, the link will fail. The user should follow the instructions that are printed out if the link does fail.An example of this command file is shown below.If the interface has been linked against both HLL and LIL routines provided by Moore, it will not run when communicating to an HLL. This is not a problem when the interface will communicate to a LIL. For most sites this will not be a problem. However for those sites that will have multiple interfaces on one node communicating with both HLL's and LIL's, some modifications must be made. Two separate interface executables will be required, one to communicate to the HLL and the other to communicate to the LIL. They must be named differently; e.g. MooreLIL.obj and MooreHLL.obj, which are both copies of Moore.obj. Modifications must be made to Moore1.com and the reference to Moore must be replaced with the new name of the interface executable. Two separate MooreDetach.com and MooreLink.com files are also required. They will also need to be modified to refer to the proper executable and object files respectively.

$! MooreLink.com$!$ Set NoOn$ say := write sys$output$!$ If (f$search ("Sys$Library:LCILIB.olb") .nes. "" .and. - f$search ("Sys$Library:ICILIB.olb") .nes. "")$ then $ LinkExe MOORE,Sys$Library:LCILIB/LIB, - Sys$Library:ICILIB/LIB,PILink:PITKLib/option$ goto end$ endif$!$ If (f$search ("Sys$Library:LCILIB.olb") .nes. "")$ then $ LinkExe MOORE,SYS$Library:LCILIB/LIB, - PIBuild:ICIDummyRoutines,PILink:PITKLib/option$ goto end$ endif$!$ If (f$search ("Sys$Library:ICILIB.olb") .nes. "")$ then $ LinkExe MOORE,SYS$Library:ICILIB/LIB, - PIBuild:LCIDummyRoutines,PILink:PITKLib/option$ goto end$ endif$!$ say " "$ say " WARNING - Moore interface not linked. "$ say " Moore Library LCILIB.olb or ICILIB.olb not found in Sys$Library"

February 1998 19


$! 21-aug-97 jfz> **************************************************$ say " The Moore Libraries are now supplied by OSI Software, Inc."$ say " "$ say " Installation of the Moore HLL Library"$ say " Required for communication to ICI 2.5 or 2.0"$ say " 1. execute @pibuild:makepilinksymbols"$ say " 2. execute @pibuild:icilink"$ say " ************* or ******************** "$ say " Installation of the Moore LIL Library"$ say " Required for communication to ICI 320 "$ say " 1. execute @pibuild:makepilinksymbols"$ say " 2. execute @pibuild:lcilink"$! 21-aug-97 jfz>***************end*************************************$ say " The interface can then be linked by executing: "$ say " "$ say " $ @pibuild:moorelink"$ say " "$ say " "$ say " If the software supplied by Moore is installed, but resides in a "$ say " directory other than Sys$Library, edit the file "$ say " PIBuild:MooreLink.com"$ say " replacing the directory name with your directory name then link this"$ say " interface as: "$ say " "$ say " $ @pibuild:moorelink"$ say " "$ goto veryend$!$ end:$!$! copy startup command procedures if necessary$! don't overwrite site specific files$ if (f$search("pisysexe:moore1.com") .eqs. "" )$ then$ copy Moore1.com PISysExe:$ copy MooreDetach.com PISysExe:$ endif$ veryend:$!--------- returning from MooreLink.com --------------------------------$ exit$! end of MOORELINK.COM$! EDIT HISTORY:$! 11/12/91 JFZ OSI written$! 12/19/91 m3k OSI check for existence of site specific files before$! overwriting. Reformat error message re: Moore Libs$! 12Aug92 m3k Add MPKelly enhancements$! 18-aug-93 jfz> replaced all occurrences of Link/Execuatable=PISysExe:$! with LinkExe to conform to interface link standard.$! 21-aug-97 jfz> OSI now supplies MPCO libraries. if software is not$! already installed then customer will manually install it$! by executing specified link procedures $!$! This procedure links a copy of the Moore interface with routines in the$! PI Toolkit library, as well as to one or both of Moore Products Company's$! Software support libraries. If a site plans to have interfaces to both$! the HLL and LIL, then both of those libraries must be linked to. If a$! site will only interface to one of the links, then the interface must$! be linked against those routines for that link. The interface must also$! be linked against a dummy library containing the other links routine names.$!


If the interface is to be linked on its own, @PIBuild:MakePILinkSymbols should be run so that the symbol LnkExe is defined.

Moore Products Company Supplied SoftwareOSI Software, Inc. now supplies the Moore Products Company LIL and HLL ICI Communications Software Packages which are written in FORTRAN. Use of the files contained in the packages simplifies the communication programming that needs to be written into the interface. See Moore Products Company bulletins ASMD 3932S1 (pertains to the HLL) and ASMD 320S1 (pertains to the LIL) for further information on installation of these files onto a system and on the contents of the software support routines. If links to both the HLL and LIL are to be running concurrently, LIL software version 3.4 or higher, and HLL software version 4.1 or higher are required.If an ICI-2.0 is used, a Moore Products Company parallel I/O driver must be purchased. The part number for the software is ASM 3934S002-2.The following tables list the files and the default directories in which they will reside in upon installation. The user may specify alternate directories for the Moore software. However if this is done then the file MooreLink.Com must be edited and the directory SYS$Library: replaced with the directory which contains the support object library; ICILIB.OLB for the HLL and LCILIB.OLB for the LIL. Additionally, the file Moore1.Com must be edited and the directory SYS$Manager: replaced with the directory which contains the terminal line conditioning file; ICI25TT.Com for the ICI-2.5 and LCITT.Com for the Model 320 ICI.Since the interface is written to communicate to either the HLL or the LIL, calls are made to both Moore Software HLL and LIL routines. Therefore, when the interface is linked, it must be linked against both the HLL support object library and the LIL support object library. If only one of the links is present; i.e. only the LIL or HLL (which is the typical case), dummy routines are used for the link which is not present.

HLL Communication FilesFile Name Directory Description

ICI25TT.COM SYS$Manager Terminal line conditioning

ICIDEF.INC SYS$Library FORTRAN Include file

ICILIB.OLB SYS$Library Support object library

ICI_SAMPLE.FOR SYS$Library Sample Fortran program

ICUTIL.EXE SYS$System Utility executable image

ICUTIL.HLB SYS$Help Utility help library

February 1998 21


LIL Communication FilesFile Name Directory Description

LCITT.COM SYS$Manager Terminal line conditioning

LCIDEF.INC SYS$Library FORTRAN Include file

LCILIB.OLB SYS$Library Support object library

LCI_SAMPLE.FOR SYS$Library Sample Fortran Program

LIUTIL.EXE SYS$System Utility executable image

LIUTIL.HLB SYS$Help Utility help library

VAX SYSGEN ParametersThe type ahead buffer, SYSGEN parameter TTY_TYPAHDSZ, must be set greater than or equal to 550 Bytes since this is the largest transfer length of any routine that will be called from either of the ICI Support Libraries. If the alternate type ahead buffer is to be used, the command file ICI25TT.Com or LCITT.Com must be edited. Replace the parameter /TYPEAHEAD with /ALTYPEAHD.


Interface OperationAfter configuring the hardware and software, and after developing the PI points associated with the Moore ICI Interface, the interface may be started.

StartupEach Moore ICI Interface is started by running MooreDetach.Com from the DCL prompt:$@PISysExe:MooreDetach #

where # is the number of the interface being started. This presumes that the file PISysExe:Moore1.Com has been configured. Repeat this process for each interface.To automate the interface startup add the above line to the file PISysMgr:SiteStart.Com for each interface.

ShutdownEach interface may be stopped by executing the following command:$@PISysExe:Stop PI-Moore-#where # is the ICI number.Stopping an interface in this manner does not place shutdown events in the snapshot. To automate the shutdown, add the above line for each interface to PISysMgr:SiteStop.Com.When the PI system is shutdown, the points coming into the system should receive shutdown events. Modify the argument list for program ShutdownEvents, which is executed from files ShutdownEvents.Com and CheckForCrash.Com. These files are all located in PISysExe:. Include in the argument list the point source character plus the Location1 parameter for the tags which should receive shutdown events.

Information and Error MessagesEach interface creates a log file where all operational information, warnings, and errors are written. This file is in PISysExe:Moore#.Out, where # is the interface number. In addition, the interface sends all important announcements to the PI Message Log. Error messages which specify ICI_xxxx pertain to the High Level Link and those which specify LCI_xxxx pertain to the Local Instrument Link. An LCI_GDSCR error indicates that a specific station on the link is having problems. An ICI_GDBSCR error indicates that a specific satellite on the link is having problems. Refer to the section below if the interface gets an ICCSTS or ICISTS I/O Timeout.

February 1998 23


The error message:Moore-1>>AddPT>>Invalid params for Reverse Act Tag ABCD

indicates that one of the following requirements was not met for a tag that was configured as reverse acting: the square root field must be 0, the point must be Real, Zero must equal 0., and the Span must equal 100..

ICCSTS or ICISTS TimeoutsIf the interface suddenly stops collecting data, or can't start collecting data due to the ICI timing out, it is almost always due to a hardware failure or hardware change. This will be indicated by a LCI_ICISTS or ICI_ICCSTS message indicating that an ICI timeout has occurred. Conditions that cause the ICI to time out are hardware related. Typically timeouts will occur when the interface is first installed as well as when an ICI has been sent out for repairs and then returned to service.If this is the initial installation of the interface and it never has collected data, you need to start from the beginning verifying all settings as you go. If have tried every possibility of combinations and still no luck, call Moore Products for technical assistance. There is a possibility that your ICI might not be working properly.If the interface was collecting data and it suddenly gets an ICI timeout, if nothing in the communication loop was changed, the most probable cause is the ICI itself. Contact Moore Products for technical assistance. If the ICI times out after it has just been returned to service, verify ALL the current hardware settings with the initial hardware settings you recorded when you first installed the interface. More than likely something was changed while the ICI was out for repair. Don't forget to recheck the settings on the ICI. The easiest way to check that the communication from the VAX to the ICI is working is to use the interactive utility provided by Moore Products. It allows the user to send out the same calls to the ICI that the interface does but in an interactive mode. See the section below for information on how to run the Moore interactive utility.

Using the Moore Products Interactive UtilityThe interactive utility which comes with both the HLL and LIL software allows a user to issue commands interactively to the ICI. Due to the fact that the ICI is connected to an online system, we recommend that the only command used is either ICISTS or ICCSTS. These commands obtain the current status of the ICI. ICISTS is used for the ICI-320 and ICCSTS is used for the ICI-2.0 and ICI-2.5. Refer to the table in the section Moore Products Company Supplied Software for the default directories of the files. These directories are valid unless you specified alternate directories for those files when they were installed.The procedure to run the interactive utilities is given below. 1. Run the utility program by typing

$Run XXXX:LIUTILto communicate to an ICI-320, or$Run XXXX:ICUTILto communicate to an ICI-2.0 or 2.5. XXXX is the directory where the utility program resides.


2. Enter in the logical name for the device. The logical name will be LC# for the ICI-320 and IC# for the ICI-2.0 or 2.5, where # is the interface number.

3. You will then be prompted for a command. LIUTIL:for the ICI-320, you then enter ICISTS, orICUTIL:for the ICI-2.0 or ICI-2.5, you then enter ICCSTS

4. You are then prompted for the number of passes. Enter a 1 since if an I/O Timeout occurs for the first pass it will occur for subsequent passes.

5. There is a help routine associated with each utility that describes the available commands. To use it, you must have the logical MPCO_HELP defined. If it isn't defined, define it by:define/process MPCO_HELP XXXXwhere XXXX is where is the directory where the utility help library is. The default directory for the help library is SYS$Help.

February 1998 25


InstallationWhen installing a PI or PINet System, all of the necessary files are linked and placed in the PISysExe: or PINet: directory. The Moore Products Company Communications Software Package must be installed on the node where the interface will reside and the interface program must be linked with the with the ICI Support Libraries and/or dummy library.The following seven instructions should be followed if the interface comes on a separate tape from the PI or PINet system.The enclosed tape contains the backup save set MOORE.BCK which contains the files for the PI-Moore interface. 1. Unpack the saveset to a “safe” directory.

a. Go to the safe directoryb. Mount the tape by:

mount/over=id mua0:or whatever the name of your tape drive is

c. Copy mua0:*.* *.*d. Unpack the saveset by:

backup/verify/log moore.bck/sav *.*2. Copy the files contained in MOORE.BCK to PIBuild: and go to that directory.3. If the Moore Products Communication software has been installed, proceed to

step 6.4. Install the HLL Software by executing the following procedures:

@pibuild:makepilinksymbols@pibuild:icilink

5. Install the LIL Software by executing the following procedures:@pibuild:makepilinksymbols@pibuild:lcilink

2. Link the interface by executing @ moorelink. The executable moore.exe and will then get copied to pisysexe:.

3. Please verify that the interface version number in moore.out matches the version shown on the tape containing the interface.

Once the above has been completed the following steps should be taken:1. Choose a Point Source character for the MOORE points and define it using

PointSrc on the PI menu.2. Configure points for the Moore ICI Interface.3. Update the Digital State Table as discussed in Section 1.2 under the Location 4

parameter discussion.4. Create I/O Rate Tags for each interface that will be run.


5. Determine an interface number for each interface to be run. This will be dependent upon how many ICI's the computer will be connected to.

6. Modify a copy of Moore1.Com for each interface number.7. Modify MooreLink.com and Moore1.com if the Moore Communication Software

does not reside in the default directories.8. Add the startup command and shutdown commands to SiteStart.Com and

SiteStop.Com respectively for each interface.9. Start the interface(s) manually or by stopping and restarting the PI System.The following should be done after interface has been initally installed and is successfully collecting data - record all hardware settings involved in the communication path!!! This can save you much grief in the future if the independent communications module starts timing out.Hardware settings to record are: All switch settings and connections on the ICI Serial cable pinning Terminal server settings Modem settings

February 1998 27


InterfaceThis section provides further information on how the interface works but is not critical for installing the interface on a PI system. Additional information is also presented on the Local Instrument Link and the High Level Link.

Interface Point ListAt startup, the interface scans the PI point data base for all points with the source code from PISysEXE:Moore#.Com and the ICI number associated with the interface. It performs range checking on all point attribute data. During runtime the interface continues to check the PI Point Database for point updates and modifies its point list accordingly.

Output DataTwo separate PI tags are required to be configured for the same address if that address will be written to and read back by the interface. If the tag will just be written to, only one tag is required. The number of outputs is limited to one fourth the number of the system tags. The maximum integer value that can be output is 4095. The highest bit that can be output to is bit 12. If a digital tag is to be output to via a user written program, the value may be sent out as the PI value or the negative of the digital state code.Only the following controller status/modes can be output for control loops on a MMLC. They are: LOCAL/MAN, LOC/AUTO, CONS/MAN, CONS/AUTO, COMP/MAN, and COMP/AUTO. All devices residing on a LIL must be set to INTERNAL rather than EXTERNAL to be able to receive output commands from the interface. A LIL device will not be able to accept output commands from the interface when it is in LOCAL. This applies for commands sent through the HLL via an LES or through the LIL. When outputting to devices via an LES on the HLL, the devices must be in CONSOLE mode. The LES does not recognize COMPUTER mode.It is important to note there are some cases where a controller may overwrite a channel that was previously written to by the interface. Consult the Moore manual for the specific controller for the requirements on outputting data to various channels.

Input DataThe interface optimizes data transfer by collecting data on a slot by slot basis for each HLL Satellite and on a station by station basis for each LIL Station. The maximum number of input tags is 5000. If a digital tag is going to be read from PI with a user written program, the value returned will be the negative of the digital state code.


Scanning PrinciplesAll input data is scanned at a fixed scan rate. The time between scans (in seconds) is specified in the Moore#.Com file. Multiple interfaces can be used to collect data at varying scan rates. However, each interface requires its own ICI. All input data is brought over from the ICI as an integer value between 0 and 4095. Since only the integer value for a tag is obtained from either the LIL or the HLL, it is imperative that the high and low limits that are used in the configuration of the instrument are used to calculate the zero and span that are input into the PI database. For integer point types, the value is equal to the integer value obtained directly from the ICI. For real point types, the zero is equal to the low DCS limit and the span is equal to the DCS high limit minus the DCS low limit. The interface then converts the integer value to the real value from the zero and span of the tag in its engineering units. An integer value of 128 is 0% of scale and an integer value of 3968 is 100% of scale. Analog values less than 128 are considered to be under range and analog values greater than 3968 are considered to be over range. For digital point types, single discrete data will be equal to a value of 128 to indicate the zero(0) state and 3968 to indicate the one(1) state. Multiple discrete data, where one or more bits of the word indicate a particular status, is converted from an integer value to binary form. Multiple discrete data is typically used to indicate alarms and the status of various devices.If input data fails with an extended communication failure, the digital state I/O TIMEOUT is written to the PI Snapshot for the effected tags. The interface will continue to attempt to communicate with the ICI. Once communication has been reestablished, new values will be written to PI Snapshot.

Time StampThe Moore interface will write all values to the snapshot using the VAX System Time as the time stamp.

Local Instrument Link (LIL)Information which is located in the LIL global data base comes from the following Station types: Mycro 324's, Mycro 351's, Mycro 352's, Mycro 382's, and the Mycro 383's. When reading data from Stations on the LIL, the interface sends out a LIL global data base read command. The data is read on a station by station basis. When outputting data, the interface sends out a parameter send command which is done for a single parameter.

High Level Link (HLL)Information which is located in the HLL global data base comes from Satellites connected directly to the HLL such as a Moore Multi-loop Controller (MMLC), a Modular Data Acquisition Satellite (MDAS), or a Local Expansion Satellite (LES). The LES provides a means for data communication between Stations which reside on the Local Instrument Link (LIL) and the HLL global data base. The types of devices that reside on the LIL include the following: Mycro 324's, Mycro 351's, Mycro 352's, Mycro 382's, and the Mycro 383's.When reading data from Stations on the LIL, the interface sends out a HLL global data base read command. Up to 732 channels of LIL global data can be transferred into the HLL global data base. Only LIL global data (Parameter 1 data) can be transferred into the HLL global data base. The configuration information for the data

February 1998 29


to be transferred resides within the LES in a table called the High Level Link Data Transfer Table (HLL DTT). The LES can contain 1 to 16 slots with a maximum of 256 channels per slot. To maximize scanning efficiency, a slot in the LES should be configured to contain as much data as possible since scanning is done on a slot by slot bases. The HLL DTT is the table in which the user assigns HLL global data base addresses (Satellite # which is the number for the LES, Slot #, and Channel #) to the LIL global data to be transferred. It is imperative that all data that is to be transferred from the LIL to the HLL global data base must be configured in this table.The interface retrieves data from a Satellite (this includes LIL global data in the LES) on the HLL on a slot by slot basis. Data configured in a slot of a Satellite on the HLL is contiguous. The interface uses the fact that the data from a slot is contiguous to pair the retrieved channels of data with the appropriate PI point. A table resides within the interface that pairs each PI point with the data from its location in the HLL global data base. It is important to note that if a channel or loop is removed from a slot then the slot will automatically reconfigure itself and make itself contiguous once again. To prevent this from occurring, dummy information can be substituted in for the removed channels in a slot.The addition of a new point to a slot will not disrupt the relationship between PI points and their location in the HLL global data base. When a point is configured in the first empty channel of a slot, the data residing in that slot will be ignored until the point is configured in the PI database. Once the point has been configured into the PI data base, Sign up for Updates will automatically add the point to the point list be scanned by the interface.If points are rearranged and are configured into different channels, the data for those points will be incorrect until the new configurations have been entered into the PI database. Once the new channel assignments for the points have been configured into the PI data base, Sign up for Updates will detect these changes and the interface will be notified.


Figure 1. ICI 320 Serial Port Board

LIL Address Selection (Minus 1)

Switch Bit Value

2 2 32

2 1 16

1 8 8

1 4 4

1 2 2

1 1 1

Data Format Selection (Switch 2)

Bit 8 Bit 4 Start Bits Data Bits Parity Stop Bits

Closed Closed 1 Even 1

Closed Open 1 Odd 1

February 1998 31


Figure 2. Data Set/Data Terminal Connections

1 2 3 4 5

Figure 3. ICI 320 MPU Board Dip Switch

Switch5 Position

Transmission Method

Switch4 Position

Link ACK Delay

Switch3 Position

Null-Filled Data

Closed Binary Closed Disabled Closed Disabled

Open ASCII Open Enabled Open Enabled

Switch 1 Position

Switch 2 Position

Security Level

Closed Closed None

Closed Open Record

Open Closed Parameter

Open Open Local


Figure 4. Blowup of ICC Piggyback Board

Figure 5. Setting of Jumpers W8 and W9

February 1998 33

Data Set Position Data Terminal Position

DS DT


Figure 6. Front Panel, ICI 2.0 or 2.5

Switch Legend

SW 1 Hardware Reset

SW 2 Communications Setup

BIT 1 Command Response Delay 1 Enabled

BIT 2 Null Data Response 0 Disabled

BIT 3 Baud Rate

BIT 4 Baud Rate

SW 3 LED Test Button

SW 4 Security Access (Future)

SW 5 Data Transmission Mode Select

BAUD Rate Table, SW 2 Switch Settings

BIT 3 BIT 4 BAUD Rate == 0

0 0 38400

1 0 19200

0 1 9600

1 1 1200 == 1


February 1998 35

Moore ICI - OSIsoftcdn.osisoft.com › interfaces › 1369 › PI_MrICIVMS_VAX… · Web...

Documents

Transcript of Moore ICI - OSIsoftcdn.osisoft.com › interfaces › 1369 › PI_MrICIVMS_VAX… · Web...