+ All Categories
Home > Documents > E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to...

E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to...

Date post: 04-Mar-2020
Category:
Upload: others
View: 6 times
Download: 0 times
Share this document with a friend
65
® ® Process Control and Automation Solutions from Elsag Bailey Group E96-624 Plant Loop to Plant Loop Remote Interface (INPPR01)
Transcript
Page 1: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

®®

E96-624

Plant Loop to Plant Loop Remote Interface(INPPR01)

Process Control andAutomation Solutionsfrom Elsag Bailey Group

Page 2: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

WARNING notices as used in this instruction apply to hazards or unsafe practices that could result inpersonal injury or death.

CAUTION notices apply to hazards or unsafe practices that could result in property damage.

NOTES highlight procedures and contain information that assists the operator in understanding theinformation contained in this instruction.

WARNING

INSTRUCTION MANUALSDO NOT INSTALL, MAINTAIN, OR OPERATE THIS EQUIPMENT WITHOUT READING, UNDERSTANDING,AND FOLLOWING THE PROPER Elsag Bailey INSTRUCTIONS AND MANUALS; OTHERWISE, INJURY ORDAMAGE MAY RESULT.

RADIO FREQUENCY INTERFERENCEMOST ELECTRONIC EQUIPMENT IS INFLUENCED BY RADIO FREQUENCY INTERFERENCE (RFI). CAU-TION SHOULD BE EXERCISED WITH REGARD TO THE USE OF PORTABLE COMMUNICATIONS EQUIP-MENT IN THE AREA AROUND SUCH EQUIPMENT. PRUDENT PRACTICE DICTATES THAT SIGNSSHOULD BE POSTED IN THE VICINITY OF THE EQUIPMENT CAUTIONING AGAINST THE USE OF POR-TABLE COMMUNICATIONS EQUIPMENT.

POSSIBLE PROCESS UPSETSMAINTENANCE MUST BE PERFORMED ONLY BY QUALIFIED PERSONNEL AND ONLY AFTER SECURINGEQUIPMENT CONTROLLED BY THIS PRODUCT. ADJUSTING OR REMOVING THIS PRODUCT WHILE IT ISIN THE SYSTEM MAY UPSET THE PROCESS BEING CONTROLLED. SOME PROCESS UPSETS MAYCAUSE INJURY OR DAMAGE.

AVERTISSEMENT

MANUELS D’OPÉRATIONNE PAS METTRE EN PLACE, RÉPARER OU FAIRE FONCTIONNER L’ÉQUIPEMENT SANS AVOIR LU,COMPRIS ET SUIVI LES INSTRUCTIONS RÉGLEMENTAIRES DE Elsag Bailey . TOUTE NÉGLIGENCE ÀCET ÉGARD POURRAIT ÊTRE UNE CAUSE D’ACCIDENT OU DE DÉFAILLANCE DU MATÉRIEL.

PERTURBATIONS PAR FRÉQUENCE RADIOLA PLUPART DES ÉQUIPEMENTS ÉLECTRONIQUES SONT SENSIBLES AUX PERTURBATIONS PARFRÉQUENCE RADIO. DES PRÉCAUTIONS DEVRONT ÊTRE PRISES LORS DE L’UTILISATION DU MATÉ-RIEL DE COMMUNICATION PORTATIF. LA PRUDENCE EXIGE QUE LES PRÉCAUTIONS À PRENDREDANS CE CAS SOIENT SIGNALÉES AUX ENDROITS VOULUS DANS VOTRE USINE.

PERTURBATIONS DU PROCÉDÉL’ENTRETIEN DOIT ÊTRE ASSURÉ PAR UNE PERSONNE QUALIFIÉE EN CONSIDÉRANT L’ASPECTSÉCURITAIRE DES ÉQUIPEMENTS CONTRÔLÉS PAR CE PRODUIT. L’AJUSTEMENT ET/OU L’EXTRAC-TION DE CE PRODUIT PEUT OCCASIONNER DES À-COUPS AU PROCÉDÉ CONTRÔLE LORSQU’IL ESTINSÉRÉ DANS UNE SYSTÈME ACTIF. CES À-COUPS PEUVENT ÉGALEMENT OCCASIONNER DESBLESSURES OU DES DOMMAGES MATÉREILS.

NOTICE

The information contained in this document is subject to change without notice.

Elsag Bailey, its affiliates, employees, and agents, and the authors and contributors to this publication specif-ically disclaim all liabilities and warranties, express and implied (including warranties of merchantability andfitness for a particular purpose), for the accuracy, currency, completeness, and/or reliability of the informationcontained herein and/or for the fitness for any particular use and/or for the performance of any material and/or equipment selected in whole or part with the user of/or in reliance upon information contained herein.Selection of materials and/or equipment is at the sole risk of the user of this publication.

This document contains proprietary information of Elsag Bailey, Elsag Bailey Process Automation, andis issued in strict confidence. Its use, or reproduction for use, for the reverse engineering, developmentor manufacture of hardware or software described herein is prohibited. No part of this document may bephotocopied or reproduced without the prior written consent of Elsag Bailey.

Page 3: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

I-E96-624A

Preface

The Plant Loop to Plant Loop Remote Interface (INPPR01)enables communication between a local and remote PlantLoop. The interface consists of three modules, the Plant Loopto Plant Loop Transfer Module (INPPT01), the Bus TransferModule (INBTM01) and the Loop Interface Module (INLIM03).Plant Loop to Plant Loop Remote Interfaces connect throughcable, modem or microwave link.

This instruction explains PPR features, specifications, andoperation. It also includes installation and troubleshootingprocedures for the interface.

The system engineer or technician using the INPPR01 shouldread and understand this instruction before installing theinterface modules. In addition, a complete understanding ofthe INFI 90 system is beneficial to the user.

Page 4: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

®

List of Effective Pages

Total number of pages in this manual is 62, consisting of the following:

Page No. Change Date

Preface OriginalList of Effective Pages Original

iii through viii Original1-1 through 1-6 Original2-1 through 2-4 Original3-1 through 3-13 Original4-1 through 4-10 Original5-1 through 5-5 Original6-1 Original7-1 Original8-1 OriginalA-1 through A-5 Original B-1 through B-2 Original C-1 through C-4 Original D-1 through D-2 Original

When an update is received, insert the latest changed pages and dispose of the super-seded pages.

NOTE: On an update page, the changed text or table is indicated by a vertical bar in the outer mar-gin of the page adjacent to the changed area. A changed figure is indicated by a vertical bar in theouter margin next to the figure caption. The date the update was prepared will appear beside thepage number.

I-E96-624A

Page 5: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

I-E96-624A

Safety Summary

GENERAL WARNINGS

Equipment EnvironmentAll components, whether in transportation, operation or storagemust be in a noncorrosive environment.

Electrical Shock Hazard During MaintenanceDisconnect power or take precautions to ensure that contact withenergized parts is avoided when servicing.

Special HandlingThis unit uses Electrostatic Sensitive Devices (ESD).

SPECIFICWARNINGS

Disconnect power before installing dipshunts for slave modules onthe MMU backplane (slave expander bus). Failure to do so couldresult in severe or fatal shock. (p. 3-10)

SPECIFIC CAUTIONS

Ensure that the cable end marked J1 is connected to P1 on theNICL01, and J2 is connected to the LIM. Failure to do so couldresult in module damage (see Figure D-1). (p. D-1)

vii

Page 6: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

Sommaire de Sécurité

®

AVERTISSEMENTSD’ORDREGÉNÉRAL

Envirmonent de l'dquipementNe pas soumettre les composants a une atmosphere corrosive lorsdu transport, de l'entreposage ou de l'utilisation.

Rissques de chocs electriques lors de l'entretienS'assurer de debrancher l'alimentation ou de prendre les precau-tions necessaires a eviter tout contact avec des composants sourstension lors de l'enretien.

Precautions de manutentionCe module contient des composantes sensibles aux dechargeselectro-statiques.

AVERTISSEMENTSD’ORDRE

SPÉCIFIQUE

Couper l'alimentation avant d'installer les dipshunts sur la plaquearrlere du chassis de montage de modules (MMU). Toute negli-gence a cet egard constitue un risque de choc pouvant entrainerdes blessures graves, voire moretlles. (p. 3-10)

ATTENTIONSD’ORDRE

SPÉCIFIQUE

S'assuree que L'extremite identifiee par J1 est reliee a P1 du mod-ule NICL01 et que J2 est reliee au module LIM. Sinon, les modulespouiraient etre endommages (voir la figure D-1). (p. D-1)

viii I-E96-624A

Page 7: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

Table of Contents

I-E96-624A

Page

SECTION 1 - INTRODUCTION....................................................................................................1-1OVERVIEW ..................................................................................................................1-1INTENDED USER.........................................................................................................1-1HARDWARE DESCRIPTION..........................................................................................1-2

Plant Loop to Plant Loop Transfer Module (INPPT01) ..............................................1-2Bus Transfer Module (INBTM01) ............................................................................1-2Loop Interface Module (INLIM03) ............................................................................1-2Additional Hardware ..............................................................................................1-2

FEATURES...................................................................................................................1-2INSTRUCTION CONTENT .............................................................................................1-3HOW TO USE THIS MANUAL .......................................................................................1-3GLOSSARY OF TERMS AND ABBREVIATIONS .............................................................1-4REFERENCE DOCUMENTS..........................................................................................1-5NOMENCLATURE ........................................................................................................1-5SPECIFICATIONS.........................................................................................................1-6

SECTION 2 - DESCRIPTION AND OPERATION........................................................................2-1INTRODUCTION...........................................................................................................2-1LOCAL/REMOTE COMMUNICATIONS..........................................................................2-1DATA INTEGRITY .........................................................................................................2-2TIMING INTERVAL .......................................................................................................2-2

Transmit/Receive Timing .......................................................................................2-3

SECTION 3 - INSTALLATION .....................................................................................................3-1INTRODUCTION...........................................................................................................3-1SPECIAL HANDLING ....................................................................................................3-1UNPACKING AND INSPECTION ....................................................................................3-1INPPT01 SWITCH SETTINGS ........................................................................................3-1

Option Switch (U72) ...............................................................................................3-2Serial Port Communication Rate (U73) ...................................................................3-3Loop Address (U75) ................................................................................................3-4

INLIM03 SWITCH SETTINGS ........................................................................................3-5INBTM01 SWITCH SETTINGS.......................................................................................3-7TERMINATION UNIT (MODULE) CONFIGURATION .......................................................3-8

NTMF01/NIMF01/NIMF02 Configuration...............................................................3-8One-way Control..............................................................................................3-8Two-way Control............................................................................................3-10

NTCL01/NICL01 Configuration ............................................................................3-10INSTALLING THE INTERFACE MODULES ..................................................................3-10

Installing the INPPT01 .........................................................................................3-10Installing the INLIM03 and INBTM01 ...................................................................3-11

INSTALLING A REDUNDANT INTERFACE...................................................................3-12INTERFACE CONFIGURATION ...................................................................................3-12

SECTION 4 - OPERATING PROCEDURES................................................................................4-1INTRODUCTION...........................................................................................................4-1PLANT LOOP TO PLANT LOOP TRANSFER MODULE LEDs AND CONTROLS ................4-1

Status LED ............................................................................................................4-2CPU LEDs..............................................................................................................4-2Memory LEDs ........................................................................................................4-2

iii

Page 8: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

Table of Contents (continued)

®

Page

SECTION 4 - OPERATING PROCEDURES (continued)Stop Pushbutton ................................................................................................... 4-2Reset Pushbutton .................................................................................................. 4-2

LOOP INTERFACE MODULE LEDs .............................................................................. 4-3BUS TRANSFER MODULE LED ................................................................................... 4-3MODES OF OPERATION .............................................................................................. 4-3

Configure Mode ..................................................................................................... 4-4Execute Mode........................................................................................................ 4-4Error Mode ............................................................................................................ 4-5One-Way Control ................................................................................................... 4-5Two-Way Control ................................................................................................... 4-6

REDUNDANT INTERFACE OPERATION ....................................................................... 4-6INTERFACE POINT CAPACITY ..................................................................................... 4-7MEMORY USAGE EXAMPLE........................................................................................ 4-8

Memory Usage in the Local PPT ............................................................................. 4-8Memory Usage in the Remote PPT .......................................................................... 4-8

SECURITY FUNCTIONS ............................................................................................... 4-9Hardware Checks .................................................................................................. 4-9Software Checks.................................................................................................... 4-9Utilities ................................................................................................................. 4-9

SECTION 5 - TROUBLESHOOTING...........................................................................................5-1INTRODUCTION .......................................................................................................... 5-1

Status Bytes.......................................................................................................... 5-2

SECTION 6 - MAINTENANCE.....................................................................................................6-1INTRODUCTION .......................................................................................................... 6-1MAINTENANCE SCHEDULE ........................................................................................ 6-1

SECTION 7 - REPAIR/REPLACEMENT PROCEDURES ...........................................................7-1INTRODUCTION .......................................................................................................... 7-1MODULE REPAIR/REPLACEMENT.............................................................................. 7-1

SECTION 8 - SUPPORT SERVICES...........................................................................................8-1INTRODUCTION .......................................................................................................... 8-1REPLACEMENT PARTS AND ORDERING INFORMATION ............................................. 8-1TRAINING.................................................................................................................... 8-1TECHNICAL DOCUMENTATION................................................................................... 8-1

APPENDIX A - TERMINATION UNIT CONFIGURATION (NTMF01) ........................................ A-1INTRODUCTION ..........................................................................................................A-1

APPENDIX B - TERMINATION UNIT CONFIGURATION (NTCL01)......................................... B-1INTRODUCTION ..........................................................................................................B-1

APPENDIX C - TERMINATION MODULE CONFIGURATION (NIMF01/NIMF02) .................... C-1INTRODUCTION ..........................................................................................................C-1

iv I-E96-624A

Page 9: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

I-E96-624A

Table of Contents (continued)

Page

APPENDIX D - TERMINATION MODULE CONFIGURATION (NICL01)................................... D-1INTRODUCTION.......................................................................................................... D-1

List of Figures

No. Title Page

1-1. Diagram of Plant Loop to Plant Loop Remote Interfaces in Two-Way Control Mode ..1-12-1. Send/Receive Timing Diagram ...............................................................................2-43-1. Switch Locations on the PPT (CPU board) ...............................................................3-23-2. LIM Switch Locations .............................................................................................3-53-3. BTM Switch (SW1) Location ...................................................................................3-73-4. NTMF01 and NTCL01 in a Redundant Installation .................................................3-93-5. NIMF01/NIMF02 and NICL01 in a Redundant Installation .....................................3-93-6. Redundant Transceiver ........................................................................................3-134-1. PPT Faceplate LEDs ...............................................................................................4-14-2. LIM Faceplate LEDs ...............................................................................................4-34-3. BTM Faceplate LEDs..............................................................................................4-44-4. Local Plant Loop Using Bosth Serial Ports in One-Way Control ...............................4-54-5. Local and Remote Plant Loops in Two-Way Control ................................................4-64-6. PPT Utilities Menu ...............................................................................................4-10A-1. Dipshunt Configuration for PPT Acting as DTE (Requires Modem or Other DCE) ... A-1A-2. Dipshunt Configuration for Direct Connection with Local PPT Acting as DTE ........ A-2A-3. Dipshunt Configuration for Direct Connection with Remote PPT Acting as DCE ..... A-3A-4. Dispshunt Configuration for Diagnostic Terminal (Port 1 only) .............................. A-4A-5. DB-25 Pin Assignments and RS-232-C Signals ..................................................... A-5B-1. NTCL01 Termination Unit and Terminal Assignments ........................................... B-2C-1. Dipshunt Configuration for PPT Acting as DTE (requires Modem or Other DCE) .... C-1C-2. Dipshunt Configuration for Direct Connection of Local PPT Acting as DTE ............ C-2C-3. Dipshunt Configuration for Direct Connection of Remote PPT Acting as DCE ........ C-3C-4. Dispshunt Configuration for Diagnostic Terminal .................................................. C-4D-1. Typical Twinax Cable Connection for the NICL01 .................................................. D-2

v

Page 10: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

No. Title Page

List of Tables

®

3-1. Option Switch (U72) Settings ................................................................................ 3-23-2. Serial Port Communication Rate (U73) ................................................................... 3-33-3. Message Throughput ............................................................................................. 3-43-4. U75 Loop Addresses ............................................................................................. 3-43-5. LIM Event Counter Addresses (SW1) ...................................................................... 3-53-6. LIM Error Counter Addresses (SW1) ...................................................................... 3-63-7. LIM Node Address Setting (SW2) ............................................................................ 3-73-8. BTM Options (SW1) ............................................................................................... 3-83-9. INPPR01 Function Codes ..................................................................................... 3-134-1. PPT Status LED States .......................................................................................... 4-24-2. BTM Status LEDs States ....................................................................................... 4-44-3. Memory Usage in Receiving Communication .......................................................... 4-74-4. Memory Usage in Sending Communication ............................................................ 4-85-1. PPT Error Codes .................................................................................................... 5-15-2. Status Bytes.......................................................................................................... 5-25-3. Status Byte Definitions.......................................................................................... 5-35-4. LIM Edge Connector P3 Pin Assignments ............................................................... 5-35-5. BTM Edge Connector P1 Pin Assignments.............................................................. 5-45-6. PPT CPU Board Edge Connector P2 Pin Assignments ............................................. 5-45-7. PPT CPU Board Edge Connector P3 Pin Assignments ............................................. 5-46-1. Maintenance Schedule........................................................................................... 6-1B-1. NTCL01 Terminal Assignments..............................................................................B-1B-2. BNC Terminal Assignments ...................................................................................B-1B-3. Jumper Settings and Cable Types ..........................................................................B-2D-1. NICL01 Terminal Assignments...............................................................................D-1D-2. BNC Assignments..................................................................................................D-1D-3. Jumper Settings and Cable Types ..........................................................................D-2

vi I-E96-624A

Page 11: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 1 - INTRODUCTION

I-E96-624A

OVERVIEW

The Plant Loop to Plant Loop Remote Interface (INPPR01)enables communication between a local and remote PlantLoop. Two modes (user-selectable) of control are available. Alocal Plant Loop is able to issue control commands and receiveException Report (XR) data from up to 32 remote Plant Loopswhen it is in the one-way mode. Only the local Plant Loop caninitiate control commands and request exception reports in theone-way mode. The two-way mode connects only two PlantLoops. In the two-way mode, either Plant Loop is able to initiatecontrol commands and request exception reports. Plant Loopto Plant Loop Remote Interfaces can connect through cable,modem or microwave link. Figure 1-1 shows a block diagram ofPlant Loop to Plant Loop Remote Interfaces in two-way control.The INPPR01 is a direct replacement of the Network 90 PlantLoop to Plant Loop Gateway (NPPG02).

INTENDED USER

System engineers and technicians should read this manualbefore installing and operating the INPPR01 module. Refer tothe Table of Contents to find specific information after themodule is operating.

Figure 1-1. Diagram of Plant Loop to Plant Loop Remote Interfaces inTwo-Way Control Mode

PLANT LOOP PLANT LOOP

MODULE BUS MODULE BUSLIM PPT

ICL IMFIMF ICL

T00417A

DMACABLE

DMACABLE

BTM BTMPPT LIM

INPPR01 INPPR01

LEGEND:BTM = BUS TRANSFER MODULEIMF = MULTI-FUNCTION CONTROLLER TERMINATION MODULEICL = COMMUNICATION TERMINATION MODULELIM = LOOP INTERFACE MODULEPPT = PLANT LOOP TO PLANT LOOP TRANSFER MODULE

OVERVIEW

1 - 1

Page 12: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INTRODUCTION ®

HARDWARE DESCRIPTION

The Plant Loop to Plant Loop Remote Interface acts as anothernode on the Plant Loop. The interface consists of three moduleson a dedicated module bus.

Plant Loop to Plant Loop Transfer Module (INPPT01)

This module processes incoming and outgoing Plant Loop mes-sages, buffers data and communicates with other PPT modulesin remote Plant Loops. The PPT is a double circuit board mod-ule. It has a memory board and CPU board. The user selectsgeneral operating characteristics and point definitions throughsoftware configuration. Other characteristics such as type ofcontrol (one-way or two-way), Node ID and port options areuser-configured through dipswitches on the CPU board.

Bus Transfer Module (INBTM01)

The BTM is responsible for translating messages from the LIMand placing them on the module bus. It also receives messagesfrom the PPT. It translates those messages and sends them tothe LIM through a direct memory access (DMA) cable.

Loop Interface Module (INLIM03)

The LIM provides the communication link between the PlantLoop and the PPT. It receives messages from Plant Loop nodesand monitors loop status. The LIM forwards messages from theloop to the PPT (though the BTM) via a direct memory access(DMA) cable. Additionally, it receives messages from the PPT(through the BTM) and sends them to the proper node on theloop.

Additional Hardware

Some applications require additional hardware such as amodem network, radio link or microwave link. This hardware isnot part of the INPPR01 standard hardware. INFI 90 DigitalSlave Modules (IMDSO01 through IMDSO04, IMDSM05) sup-port control signals to these devices.

FEATURES

The Plant Loop to Plant Loop Remote Interface provides com-munication between a local loop and one or more remote loops.This interface has user selectable control modes. Selecting theone-way mode enables a local loop to receive exception reportsfrom up to 32 remote loops. In the one-way mode, only thelocal loop can initiate control commands. The two-way modeenables bidirectional control and exception reporting between

HARDWARE DESCRIPTION

1 - 2 I-E96-624A

Page 13: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INTRODUCTION

I-E96-624A

a local and one remote loop. This interface handles a maximumcapacity of 5,000 blocks of exception report data.

The INPPR01 can handle a mixture of point types. Point typesinclude analog and digital station, remote control memory,manual set constant and device driver. The user can select theinterface communication rate, up to 19.2 kbaud.

INSTRUCTION CONTENT

This document is divided into eight sections. Introductionprovides an overview of the individual modules of the PPR, alist of related documents, glossary of terms and abbreviationsand specifications. Description and Operation explains howPPR communication occurs. Installation covers preliminarymodule setup, physical installation and configuration. Operat-ing Procedures explains faceplate LEDs, controls and inter-face operating modes. Troubleshooting explains how totroubleshoot problems with the interface modules using errorcodes and status byte information and lists the correctiveaction. Maintenance contains a maintenance schedule for theslave module. Repair/Replacement Procedures explain howto replace the PPR modules. Support Services explains thecustomer training Bailey Controls Company provides andinformation about ordering replacement parts.

HOW TO USE THIS MANUAL

Read this manual in sequence. It is important to become famil-iar with the entire contents of this manual before using thePPR. The organization of this manual enables the user to findneeded information quickly.

1. Read and do the steps in Section 3.

2. Read Section 4 thoroughly before powering up the station.

3. Refer to Section 5 if a problem occurs.

4. Refer to Section 6 for scheduled maintenancerequirements.

5. Use the Section 8 for a list of replacement parts and war-ranty information.

INSTRUCTION CONTENT

1 - 3

Page 14: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INTRODUCTION ®

GLOSSARY OF TERMS AND ABBREVIATIONS

Term Definition

DCE Data Circuit-Terminating Equipment - The termination point of a communication cir-cuit such as a line driver or modem.

DTE Data Terminal Equipment - End-user machine of a communication circuit such as a terminal or computer.

Dipshunt A dual in-line package with shorting bars.

EWS Engineering Work Station - An integrated hardware and software personal computer system for configuring and monitoring INFI 90/Network 90 modules.

Module Bus The serial communication link between a process control module and other process control modules.

Node Device(s) on the INFI 90/Network 90 Plant Loop, Superloop or INFI-NET (maximum of 63 on Plant Loop, 250 on Superloop/INFI-NET). A node can be an Operator Inter-face Station (OIS), a Process Control Unit (PCU) or Engineering Work Station (EWS) in any combination.

OIS Operator Interface Station - Integrated operator console with data acquisition and reporting capabilities. It provides a window into the process for flexible control and monitoring.

PCI Plant Loop to Computer Interface (INPCI01/02) - A Plant Loop communication inter-face that provides configuration and control of the Plant Loop through a host computer.

PCU Process Control Unit - Rack type industrial cabinet that contains master, slave and communication modules and their communication paths.

Plant Loop INFI 90 data communication highway with 63 node capacity.

RS-232-C One in a series of standards developed by the Electronics Industry Association (EIA) that specifies what signals and voltages will be used to transmit data from DTE (com-puter) to DCE (modem).

Slave ExpanderBus

Parallel address/data bus between the master module and the slave.

XR Exception Report - A function block that reports a monitored point value when that value changes and is polled by a communication or master module.

GLOSSARY OF TERMS AND ABBREVIATIONS

1 - 4 I-E96-624A

Page 15: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INTRODUCTION

I-E96-624A

REFERENCE DOCUMENTS

The following documents provide additional information aboutINPPR01 support hardware and software. Please refer to themas needed.

NOMENCLATURE

Document Number Document

I-E96-309 Digital Slave Module (IMDSM05)

I-E96-310 Digital Slave Output Module (IMDSO01/02/03)

I-E96-313 Digital Slave Output Module (IMDSO04)

I-E93-905-2 Enhanced CIU Programmer's Reference Manual

I-E93-900-20 Function Code Application Manual

I-E96-611 Loop Interface/Bus Interface Module (INLIM03/INBIM02)

I-E96-110 Operator Interface Station

I-E96-620 Plant Loop to Computer Interface (INPCI01)

I-E96-621 Plant Loop to Computer Interface (INPCI02)

I-E93-900-5 Site, Planning and Equipment Installation

I-E93-911 Termination Unit Manual

Hardware Nomenclature

Field Termination Panel NFTP01

Module Mounting Unit IEMMU01/02

Multi-Function Controller Termination ModuleRedundant Termination ModuleCable

NIMF01NIMF02NKTM01

Multi-Function Controller Termination UnitCable

NTMF01NKTU01

Communication Termination ModuleCable

NICL01NKLS04

Communication Termination UnitCable

NTCL01NKLS03

Termination Mounting Unit NTMU01/02

REFERENCE DOCUMENTS

1 - 5

Page 16: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INTRODUCTION ®

SPECIFICATIONS

Memory

PPT

LIM

BTM

256 kbytes UVROM512 kbytes RAM80 kbytes NVM (non-volatile memory)

2 kbytes RAM4 kbytes ROM

32 kbytes RAM16 kbytes ROM

I/O Ports 2 RS-232C serial ports

Communication Rates 50 to 19,200 baud (user selectable)

Power Requirements

PPT

LIM

BTM

6 amps @ +5 VDC; 30 watts37 mA @ +15 VDC; 0.55 watts18 mA @ -15 VDC; 0.27 watts

+5 VDC @ 2.0 amps; 10 watts nominal±15 VDC @ 80 mA; 1.2 watts nominal

+5 VDC @ 1.0 amps; 5 watts nominal+15 VDC @ 150 mA; 2.25 watts nominal-15 VDC @ 120 mA; 1.80 watts nominal

Environmental

Electromagnetic/Radio Frequency Interference

Ambient Temperature

Relative Humidity

Altitude

Air Quality

Values are not available at this time.Keep cabinet doors closed. Do not use com-munication equipment any closer than two meters from the cabinet.

0o to 70oC (32o to 158oF)

0 to 95% up to 55oC (131oF) (non-condensing) 0 to 45% at 70oC (158oF) (non-condensing)

Sea level to 3 Km (1.86 miles)

Noncorrosive

Certification All INPPR01 modules have been individually CSA certified for use as process control equipment in an ordinary (nonhazardous) environment.

Specifications Subject To Change Without Notice

SPECIFICATIONS

1 - 6 I-E96-624A

Page 17: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 2 - DESCRIPTION AND OPERATION

I-E96-624A

INTRODUCTION

This section explains the operation of the Plant Loop to PlantLoop Remote Interface.

LOCAL/REMOTE COMMUNICATIONS

Local and remote PPTs communicate with each other througha series of commands and replies over the serial ports. In theone-way mode, the local PPT issues commands only; intwo-way, both the local and remote PPTs issue commands. Thecommand format is:

where:

1. Loop number is the loop that responds to the command (1byte field).

2. Message byte count is the total length of the message (2byte field).

3. Command code is the command code the PPT processes (1byte field).

4. Command data is the specific command (variable lengthfield).

5. Checksum is the sum of all the bytes in the command (1byte field) or CRC, the cyclic redundancy check word computedfor all of the bytes in the command using the CRC-16 algo-rithm (2 byte field).

All communications between interfaces use this format.INPPR01 commands are a modified form of Plant Loop to Com-puter Interface commands (refer to I-E93-905-9 for commanddetails). The PPT format eliminates the key field from the PCIcommand. In addition to PCI commands, the PPT processes acommand (code 29) that permits passage of a required PPTmessage.

1 2 3 4 5

LoopNumber

Message Byte Count

Command Code

Command Data

Checksum or CRC

INTRODUCTION

2 - 1

Page 18: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

DESCRIPTION AND OPERATION ®

DATA INTEGRITY

Verification of data integrity consists of even parity checkingand the checksum in each command and reply format. Theinterface retries a transaction whenever it detects a communi-cation error.

There are two levels of communication breakdown detection.The first level detects a complete failure of the communicationlink. Should this occur, Function Code 130 output block onewill be set (logic one) and the alarm status bit set if port 1 fails.If port 0 fails, the output of block two will be set (logic one) andthe alarm status bit set.

The second level of communication failure concerns the loss ofa single remote interface. If this occurs, all blocks coming fromthat remote interface are bad quality. The PPR makes use of auser-configurable watchdog timer or absolute retry count indetermining the sensitivity to these failures (refer toI-E93-200-20 for information about Function Code 130, S10and S12).

TIMING INTERVAL

The local interface attempts communication twice a secondwith all the remote interfaces. Each successful transactionresets the communication watchdog timer. Therefore, if thecommunication link is faulty, no transactions occur success-fully. After the watchdog time period expires, the link ismarked bad.

For all communication transactions, the watchdog timer isreset on the reception of each character. If the time intervalbetween characters in a transaction exceeds 1.25 seconds, thetransaction is flushed and the remote interface is marked asbeing suspect. This condition causes retry logic to begin. Retrylogic consists of retrying communication once per second for anumber of times equal to one-fourth the watchdog time periodif the absolute retry count is set to zero. A non-zero absoluteretry count causes a specific number of retries (the number ofthe retry count). If the failure persists after the retry periodexpires, the remote interface is internally marked off-line andthe quality of all the points it provides are marked bad.

Thereafter, a single retry of the failed remote interface occursat a period equal to one half the watchdog timer period until asuccessful transaction occurs. The local interface sets thequality of all the points to their original state (before the com-munication failure). It also does a one time poll of the currentvalue of each point.

A user-configurable time delay envelopes each command/replysequence. This time delay accommodates the keying up/down

DATA INTEGRITY

2 - 2 I-E96-624A

Page 19: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

DESCRIPTION AND OPERATION

I-E96-624A

of modems and transmission equipment. The interface coordi-nates this activity through the RTS (Request-To-Send) signal ofthe RS-232-C port for modems or through digital outputs whenusing Digital Slave Modules (IMDSM05, IMDSO01/02/03/04)to enable other transmission equipment.

Transmit/Receive Timing

The user can set up the RS-232-C ports to operate as Data Cir-cuit-Terminating Equipment (DCE) or Data Terminal Equip-ment (DTE). In the DCE mode, the Request-To-Send (RTS) lineis always asserted. In the DTE mode, the RTS line is assertedbefore data transmission and inhibited after data transmissionoccurs.

The following events occur (see Figure 2-1) on port 0 whentransmitting a command:

1. Assert RTS on the RS-232-C port (DTE mode) or set digitaloutputs 1 and 4 on the digital slave module.

2. A delay occurs between the time the port 0 asserts the RTS(or the digital outputs are set) and the command transmissionoccurs. Function Code 130 (S5) sets this delay (inmilliseconds).

3. Output 4 is reset.

4. A delay occurs between the time output 4 is reset and out-put 1 is reset. Function Code 130 (S6) sets the length of thisdelay.

5. Output 1 is reset and RS-232-C RTS signal is inhibited(DTE mode).

6. A delay set by S5 of Function Code 130 occur between theoutput 1 reset and the reception of the reply.

7. The remote target issues a reply.

The following events occur (see Figure 2-1) when Port 0receives a command:

1. The port receives the command.

2. A time delay set by S6 of Function Code 130 occurs.

3. The RS-232-C asserts the RTS signal (DTE mode) or setoutputs 1 and 4 on the digital slave modules.

4. A time delay set by S5 of Function Code 130 occurs.

TIMING INTERVAL

2 - 3

Page 20: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

DESCRIPTION AND OPERATION ®

5. The remote interface transmits a reply to the interfacesending the command.

6. Output 4 is reset.

7. A time delay set by S6 of Function Code 130 occurs.

8. Output 1 resets, RS-232-C RTS signal is inhibited (DTEmode).

NOTE: RTS assert and inhibit apply to DTE mode only. RTS isalways asserted for DCE mode.

Figure 2-1. Send/Receive Timing Diagram

S5DELAY

S5DELAY

S5DELAY

S6DELAY

S6DELAY

TRANSMITCOMMAND

TxTxTxTxTxTx

RTS ASSERTED (DTE MODE)SET OUT1 AND OUT4

RESET OUT4 RTS INHIBITED (DTE MODE)RESET OUT1

RECEIVEREPLY

RxRxRxRxRxRx0

SENDING A COMMAND, PORT 0 (P0)

TIME

S7DELAY

S7DELAY

S8DELAY

S8DELAY

TRANSMITCOMMAND

TxTxTxTxTxTx

RTS ASSERTED (DTE MODE)

SET OUT2 AND OUT5

RESET OUT5 RTS INHIBITED (DTE MODE)

RESET OUT2

RECEIVEREPLY

RxRxRxRxRxRx0

SENDING A COMMAND, PORT 1 (P1)

TIME

S6DELAY S5

DELAYS6

DELAYTRANSMIT

REPLYTxTxTxTxTxTx

RTS ASSERTED (DTE MODE)

SET OUT1 AND OUT4

RESET OUT4 RTS INHIBITED (DTE MODE)

RESET OUT1

RECEIVECOMMAND

RxRxRxRxRxRx0

RECEIVING A REPLY, PORT 0 (P0)

TIME

S8DELAY S7

DELAYS8

DELAYTRANSMIT

REPLYTxTxTxTxTxTx

RTS ASSERTED (DTE MODE)SET OUT2 AND OUT5

RESET OUT5 RTS INHIBITED (DTE MODE)RESET OUT2

RECEIVECOMMAND

RxRxRxRxRxRx0

RECEIVING A REPLY, PORT 1 (P1)

TIME

T00418A

TIMING INTERVAL

2 - 4 I-E96-624A

Page 21: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 3 - INSTALLATION

I-E96-624A

INTRODUCTION

This section explains special handling procedures, switch set-tings for each interface module, and how to install relatedhardware. Complete the preliminary procedures in this sectionbefore placing the INPPR01 into operation.

SPECIAL HANDLING

Plant Loop to Plant Loop Interface modules use ElectrostaticSensitive (ESD) devices. Follow these handling procedures:

NOTE: Always use the Bailey Field Static Kit (P/N 1948385A1)when working with interface modules. This kit connects the staticdissipative work surface and technician to the same ground point.

1. Keep the modules in their special anti-static bags until youare ready to install them in the system. Save the bags forfuture use.

2. Ground the anti-static bag before opening.

3. Verify that all devices connected to the modules are prop-erly grounded before using them.

4. Avoid touching the circuitry when handling the module.

UNPACKING AND INSPECTION

1. Examine the PPT, LIM and BTM immediately to verify thatthey have not been damaged in transit.

2. Notify the nearest Bailey Controls Sales Office of any suchdamage.

3. File a claim for any damage with the transportation com-pany that handled the shipment.

4. Use the original packing material and/or container to storethe modules.

5. Store the module in an environment of good air quality andfree from temperature and moisture extremes.

INPPT01 SWITCH SETTINGS

The INPPT01 consists of two circuit boards, a memory boardand a CPU board. The memory board has no user-configurable

INTRODUCTION

3 - 1

Page 22: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

operating options. The CPU board has three dipswitches thatset the module operating characteristics. These switches pro-vide the means of establishing the type of control, serial portcommunication rate, and loop address. Figure 3-1 shows thedipswitch locations on the CPU board.

Option Switch (U72)

U72 is an eight position dipswitch that determines the operat-ing options of the module. Table 3-1 lists the U72 option set-tings. Record the U72 settings in the space provided. Whensetting switches, 0 = Closed (on) and 1 = Open (off).

Figure 3-1. Switch Locations on the PPT (CPU board)

T00387A

P1

P2

P3

STOP SW2

OPTIONSWITCH

BAUD RATESWITCH

JUMPERSJ1, J2, J3

DIAGNOSTICSSWITCH

U72 U73 U75

RESET SW11 2 3 4

OPEN

5 6 7 8 1 2 3 4

OPEN

5 6 7 8 1 2 3 4

OPEN

5

J1 J2 J3

Table 3-1. Option Switch (U72) Settings

Position Setting FunctionUser

Setting

1 01

ROM checksumming enabledROM checksumming disabled

2 01

RS-232-C port in DCE mode (direct connections)RS-232-C port in DTE mode (modem connections)

3 01

Equipment select output de-energizedEquipment select output energized1

4 01

Port 1 option interface communicationPort 1 utility option2

5 01

Interface ID local3

Interface ID remote

6 01

Interface mode two-way control4

Interface mode one-way control

INPPT01 SWITCH SETTINGS

3 - 2 I-E96-624A

Page 23: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

Serial Port Communication Rate (U73)

U73 is an eight pole dipswitch that sets the serial port commu-nication rate. The communication rate directly affects datathroughput. Refer to Table 3-2 for communication rates. Table3-3 lists message throughput for different point types. Recordthe U73 setting in the space provided.

7 01

Don not initialize NVMInitialize NVM

8 01

Primary/Secondary (one module of redundant pair is set to 0, the other module is set to 1)

NOTES: 0 = Closed (on), 1 = Open (off)1. A unique equipment select output can exist between the primary and secondary PPT. The equipment select output is digital output threeof a digital slave (IMDSM05 or IMDSO01/02/03/04).2. Port 1 responds as DCE when it is configured as a utility port. Set switch position 4 = 1 if port 1 is not used as a communication interface.

3. Define only one interface as a local interface (position 5).4. The following conditions apply when using two-way control (position 6 = 0):

a. The port 1 option defaults to interface communication (position 4 = 0).

b. The local INPPR01 uses port 0 as its command port and port 1 as its reply port.c. The remote INPPR01 uses port 1 as its command port and port 0 as its reply port.d. Both the local and remote interface must have a loop address of 0 (U75).

Table 3-1. Option Switch (U72) Settings (continued)

Position Setting FunctionUser

Setting

Table 3-2. Serial Port Communication Rate (U73)

Switch PositionBaud Rate

User Setting

Port 01 2 3 4

Port 15 6 7 8

Port 01 2 3 4

Port 15 6 7 8

0 0 0 0 0 0 0 0 50

1 0 0 0 1 0 0 0 75

0 1 0 0 0 1 0 0 110

1 1 0 0 1 1 0 0 134.5

0 0 1 0 0 0 1 0 150

1 0 1 0 1 0 1 0 300

0 1 1 0 0 1 1 0 600

1 1 1 0 1 1 1 0 1200

0 0 0 1 0 0 0 1 1800

1 0 0 1 1 0 0 1 2000

0 1 0 1 0 1 0 1 2400

1 1 0 1 1 1 0 1 3600

0 0 1 1 0 0 1 1 4800

1 0 1 1 1 0 1 1 7200

0 1 1 1 0 1 1 1 9600

1 1 1 1 1 1 1 1 19200NOTE: 0 = Closed (on), 1 = Open (off)

INPPT01 SWITCH SETTINGS

3 - 3

Page 24: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

Loop Address (U75)

Dipswitch U75 sets the loop address. Valid addresses are 0through 31. Table 3-4 shows examples of switch settings forthe loop address. Record the loop address in the spaceprovided.

Table 3-3. Message Throughput

Point TypeNumber of

BytesTime per Point 1

Points perSecond

Station 19 10.4 msec 96

Analog 8 4.7 msec 214

Digital 5 3.1 msec 322

Remote Control Mem-ory (RCM)

7 4.1 msec 241

Remote Manual Set Constant (RMSC)

7 4.1 msec 241

Device Driver 7 4.1 msec 2411. These figures are based on the calculated throughput of the various Exception Report data types(at 19200 baud). Regardless of communication rate, the software overhead is approximately 0.5millisecond per point.

Table 3-4. U75 Loop Addresses

Example Settings

AddressExample

Switch Position 1 2 3 4 5

Binary Value 16 8 4 2 1

0 0 0 0 0 0

9 0 1 0 0 1

26 1 1 0 1 0

User Setting

UserAddress

Switch Position 1 2 3 4 5

Binary Value 16 8 4 2 1

NOTE: 0 = Closed (on), 1 = Open (off)

INPPT01 SWITCH SETTINGS

3 - 4 I-E96-624A

Page 25: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

INLIM03 SWITCH SETTINGS

The Loop Interface Module (INLIM03), shown in Figure 3-2, hastwo user-configurable dipswitches: Event/Error CounterAddress Switch SW1 and Address Switch SW2. Tables 3-5 and3-6 list the switch settings for the Event and Error Counters.The LIM faceplate LEDs display the contents of the event/errorcounters. Switch SW2 poles 1 and 2 are CLOSED for normaloperation. Refer to Table 3-7 for SW2 settings. The LIM canhave any address from 1 to 63.

Figure 3-2. LIM Switch Locations

Table 3-5. LIM Event Counter Addresses (SW1)

Counter Address

HexAddress

Switch Position1 2 3 4 5 6 7 8

DescriptionUser

Setting

48 30 0 0 1 1 0 0 0 0 Total messages transmitted, including forwarding.

49 31 0 0 1 1 0 0 0 1 Transmit retries.

50 32 0 0 1 1 0 0 1 0 Composite BTM Receive/Transmit, 4 bits each. Receive is viewed at the top LED.

51 33 0 0 1 1 0 0 1 1 Messages taken from the BTM transmit buffer.

52 34 0 0 1 1 0 1 0 0 Messages stored in BTM receive buffer.

53 35 0 0 1 1 0 1 0 1 Interrupt Requests (IRQs) sent by BTM.

54 36 0 0 1 1 0 1 1 0 High Priority (HP) messages transmitted.

55 37 0 0 1 1 0 1 1 1 High Priority messages received.

56 38 0 0 1 1 1 0 0 0 Commands issued by the BTM.

57 39 0 0 1 1 1 0 0 1 Missed BTM transmit requests.

T00403A

S2NODE ADDRESS

S1EVENT/ERROR

COUNTER ADDRESS

P4 CONNECTORRIBBON CABLE

ATTACHES HERE

EDGECONNECTORSP3

P2

P1

XU4

1 2 3 4

OPEN

5 6 7 8

1 2 3 4

OPEN

5 6 7 8

INLIM03 SWITCH SETTINGS

3 - 5

Page 26: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

58 3A 0 0 1 1 1 0 1 0 Spurious Non-Maskable Interrupts (NMI) caused by address present.

59 3B 0 0 1 1 1 0 1 1 HEY (request for an interrupt; generated by BTM) message sent.

60 3C 0 0 1 1 1 1 0 0 Messages discarded when the destination is off-line.

61 3D 0 0 1 1 1 1 0 1 HEY time expirations.

62 3E 0 0 1 1 1 1 1 0 Passes through the IDLE level(2 bytes wide).

NOTE: 0 = Closed (on), 1 = Open (off)

Table 3-6. LIM Error Counter Addresses (SW1)

CounterAddress

HexAddress

Switch Position1 2 3 4 5 6 7 8

DescriptionUser

Setting

64 40 0 1 0 0 0 0 0 0 Composite error count developed every handshake period - the summation of all other error counters.

65 41 0 1 0 0 0 0 0 1 Unresolved NMI interrupts.

66 42 0 1 0 0 0 0 1 0 Unresolved IRQ interrupts.

67 43 0 1 0 0 0 0 1 1 Unresolved timer interrupts.

68 44 0 1 0 0 0 1 0 0 Unused.

69 45 0 1 0 0 0 1 0 1 Queue overflows.

70 46 0 1 0 0 0 1 1 0 Unresolved BTM IRQs.

71 47 0 1 0 0 0 1 1 1 Sequence errors.

72 48 0 1 0 0 1 0 0 0 Header CRC/OVRN errors.

73 49 0 1 0 0 1 0 0 1 Data CRC/OVRN errors.

74 4A 0 1 0 0 1 0 1 0 Messages developing data CRC errors on route to destination.

75 4B 0 1 0 0 1 0 1 1 Transmission failures.

76 4C 0 1 0 0 1 1 0 0 Watchdog timer expirations.

77 4D 0 1 0 0 1 1 0 1 Data length errors.

78 4E 0 1 0 0 1 1 1 0 Loop - 1 Receive (RCV) failure.

79 4F 0 1 0 0 1 1 1 1 Loop - 2 Receive failures.

80 50 0 1 0 1 0 0 0 0 Loop - 1 Transmit (TX) failure.

81 51 0 1 0 1 0 0 0 1 Loop - 2 Transmit failures.NOTE: 0 = Closed (on), 1 = Open (off)

Table 3-5. LIM Event Counter Addresses (SW1) (continued)

Counter Address

HexAddress

Switch Position1 2 3 4 5 6 7 8

DescriptionUser

Setting

INLIM03 SWITCH SETTINGS

3 - 6 I-E96-624A

Page 27: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

INBTM01 SWITCH SETTINGS

The Bus Transfer Module (INBTM01), shown in Figure 3-3, hasone user-configured dipswitch (SW1). SW1 enables modulediagnostics. Refer to Table 3-8 and set SW1 for normaloperation.

Table 3-7. LIM Node Address Setting (SW2)

Example Settings

Address Example

Switch Position 1 2 3 4 5 6 7 8

Binary Value 128 64 32 16 8 4 2 1

1 0 0 0 0 0 0 0 1

9 0 0 0 0 1 0 0 1

63 0 0 1 1 1 1 1 1

User Setting

UserAddress

Switch Position 1 2 3 4 5 6 7 8

Binary Value 128 64 32 16 8 4 2 1

NOTE: 0 = Closed (on), 1 = Open (off)

Figure 3-3. BTM Switch (SW1) Location

T00401A

RESETSWITCH

SW1OPTION SWITCH

EDGECONNECTORSP3

P2

P1

51

OPEN

INBTM01 SWITCH SETTINGS

3 - 7

Page 28: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

TERMINATION UNIT (MODULE) CONFIGURATION

Two of the interface modules (INLIM03, INPPT01) require ter-mination. The INPPT01 terminates with the NTMF01 orNIMF01/NIMF02. The INLIM03 terminates with the NTCL01 orNICL01. Appendices A through D contain disphunt configura-tion information. Figure 3-4 shows a diagram of the NTMF01and NTCL01 in a redundant installation. Figure 3-5 shows adiagram of the NIMF01/NIMF02 and NICL01 in a redundantinstallation.

NTMF01/NIMF01/NIMF02 Configuration

The TMF and IMF provide the INPPT01 with two RS-232-Cports. Configure these ports to operate as DTE, DCE or diag-nostic terminal. Refer to Figures A-1, A-2, and A-3 for NTMF01dipshunt configurations. Refer to Figures C-1, C-2, and C-3 forNIMF01/NIMF02 dipshunt configurations.

NOTE: You must use the NIMF01 and NIMF02 when using termina-tion modules to terminate a redundant interface. Non-redundantinterfaces need only the NIMF01.

ONE-WAY CONTROL

Configure port 0 on the local and remote interfaces to act asDTE. One local INPPR01 can communicate with up to 32remote interfaces in the one-way control mode. Additionalcommunication equipment such as a modem network, radiolink or microwave link is required when interfacing multipleremotes. The user supplies any additional equipment that isneeded.

Table 3-8. BTM Options (SW1)

Switch Position1 2 3 4 5

Function User Setting

0 0 0 0 0 Normal operation.

0 0 0 1 0 Normal BTM operation without catastrophic error checking (for Test Pur-poses ONLY).

0 0 1 0 0 RAM test mode. If Status LED turns red, the module has failed the test.

0 0 1 1 0 ROM test mode. If Status LED turns red, the module has failed the test.

0 1 0 0 0 Execute Interrupt Request (IRQ) LIM handshake diagnostic. Used in combination with the LIM off-line diagnostics.

NOTE: 0 = Closed (on), 1 = Open (off)

TERMINATION UNIT (MODULE) CONFIGURATION

3 - 8 I-E96-624A

Page 29: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

Figure 3-4. NTMF01 and NTCL01 in a Redundant Installation

Figure 3-5. NIMF01/NIMF02 and NICL01 in a Redundant Installation

MODULE BUS

T00419A

DMACABLE

DMACABLE

INBTM01INLIM03 INLIM03INPPT01

MODULE BUS

INBTM01 INLIM03

NTCL01

TWINAXOR COAX

NKLS03

NKTU01NKTU01

TWINAXOR COAX

NKLS03

NTCL01

INPPT01

SLAVE EXPANDER BUS

COMMUNICATION HIGHWAY (PLANT LOOP)

P1 P1

P3

P3 P3

P3

TO OTHER PPR

PORT 0COMMUNICATIONS

PORT 1COMMUNICATIONSOR UTILITY

NTMF01TERMINATION UNIT

P1 P3

MODULE BUS

T00420A

DMACABLE

DMACABLE

INBTM01INLIM03 INLIM03INPPT01

NIMF01TERMINATION

MODULE

NIMF02TERMINATION

MODULE

MODULE BUS

INBTM01 INLIM03

NICL01

TWINAXOR COAX

NKLS04

NKTM01NKTM01

TWINAXOR COAX

NKLS04

NICL01

INPPT01

SLAVE EXPANDER BUS

COMMUNICATION HIGHWAY (PLANT LOOP)

P1

P1

J2 J3

P1

P1

P3

P3 P3

P3

TO OTHER PPR

PORT 0COMMUNICATIONS

PORT 1COMMUNICATIONSOR UTILITY

TERMINATION UNIT (MODULE) CONFIGURATION

3 - 9

Page 30: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

When directly connecting only one remote interface in one-waycontrol, set port 0 on the local interface to act as a DTE. Setport 0 on the remote interface to act as DCE.

NOTE: Always configure port 1 as a utility port if it is not used as aninterface communication port. The PPT option switch (U72) position4 must be set to 0 (utility option). Port 1 will always act as a DCE inthis configuration.

TWO-WAY CONTROL

The interface requires both serial communication ports in thetwo-way control mode. Connect port 0 of the local Plant Loop toport 0 of the remote Plant Loop. Connect port 1 of local PlantLoop to port 1 of the remote Plant Loop.

Configure the termination unit to act as DTE to enable thePlant Loop to Plant Loop Transfer Module to communicate withDCE (i.e, a modem). Configure the termination unit to act asDCE to enable the PPT to communicate with DTE (i.e., a termi-nal). Figure A-4 shows how the termination dipshunt configu-ration directs the RS-232-C signals.

NTCL01/NICL01 Configuration

The TCL and ICL provide the INLIM03 with Plant Loop termina-tion. The user has the option of using Twinax or Coax cable toconnect the interface to the Plant Loop. Tables B-3 (NTCL01)and D-3 (NICL01) show the jumper settings for twinax andcoax cables. Set the jumpers accordingly for your application.

NOTE: For complete cable and TU/TM installation information, referto the Termination Unit Manual l (I-E93-911).

INSTALLING THE INTERFACE MODULES

If the switch settings on the interface modules are complete,they are ready to be installed in the Module Mounting Unit(MMU).

Installing the INPPT01

WARNING Disconnect power before installing dipshunts for slave mod-ules on the MMU backplane (slave expander bus). Failure to doso could result in severe or fatal shock.

AVERTISSEMENT Couper l'alimentation avant d'installer les dipshunts sur laplaque arrlere du chassis de montage de modules (MMU).Toute negligence a cet egard constitue un risque de choc pou-vant entrainer des blessures graves, voire moretlles.

INSTALLING THE INTERFACE MODULES

3 - 10 I-E96-624A

Page 31: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

To install the PPT:

1. Verify the PPT slot assignment in the MMU.

a. If you are installing redundant PPTs, install a 24 pindisphunt in the Slave Expander Bus socket between theslot used by the primary PPT and the slot used by the sec-ondary PPT. Both PPTs must reside on the same SlaveExpander Bus.

b. Each PPT must reside on its own module bus.

2. Attach the hooded end of the cable (NTKU01 for theNTMF01; NKTM01 for the NIMF01 and NIMF02) to the MMUbackplane cable connector opening for the PPT. The other endof the cable attaches to the termination unit or backplane ofthe Termination Mounting Unit (NTMU01).

3. Guide the top and bottom edges of the circuit card alongthe top and bottom rails of MMU.

4. Slide the module into the slot; push the module until thefront panel is flush with the top and bottom of the MMU frame.

5. Turn the two captive latches a half turn to lock the modulein place.

Installing the INLIM03 and INBTM01

The LIM and BTM should be installed as a pair in adjacentslots. To install the LIM/BTM:

1. Verify the MMU slot assignments for the modules. If youare installing redundant LIM/BTM pairs, each BTM must beinstalled on the module bus that belongs to its related PPT.

2. Attach the hooded end of the cable (NKLS03 for NTCL01;NKLS04 for the NICL01) to the MMU backplane cable connec-tor opening for the LIM. The other end of the cable attaches tothe termination unit or TMU backplane.

3. Connect one end of the Bailey supplied ribbon cable (DMAcable) to the P4 connector on the LIM. Connect the other end ofthe DMA cable to the P4 connector on the BTM (see Figures 3-2and 3-3).

4. Guide the top and bottom edges of both circuit cards alongthe top and bottom rails of adjacent slots in the MMU.

5. Slide the modules into the slot; push the module until thefront panels are flush with the top and bottom of the MMUframe.

INSTALLING THE INTERFACE MODULES

3 - 11

Page 32: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION ®

6. Turn the two captive latches a half turn to lock the modulein place.

INSTALLING A REDUNDANT INTERFACE

Installing a redundant interface requires an additional set ofINPPT01, INLIM03 and INBTM01 modules. Both PPT modulesmust be on the same Slave Expander Bus, but reside on sepa-rate Module Bus. Each PPT has a pair of LIM/BTM modules ona dedicated Module Bus.

Observe the following conditions when installing a redundantinterface:

1. U72 position 8 must be set to 0 on the primary PPT.

2. U72 position 8 must be set to 1 on the secondary PPT.

3. SW1 all positions must be set to 0 on both BTMs.

4. The slave expander bus of two adjacent MMUs (one on topof the other) are connected with the expander bus extendercable (Bailey P/N 1958502A0340).

5. The module bus between these MMUs are not connected.

Applications that use redundant communication equipmentmay require additional hardware. Figure 3-6 shows a diagramof the interface using the IMDSM05 to enable redundant trans-ceivers. Function Code 130 provides the software the PPTneeds to enable the transceivers. Voltage levels and polaritiesof enable signals to transceivers and other communicationequipment may vary. Refer to the applicable user manual whenconnecting this equipment to the IMDSM05, IMDSO01/02/03/04 Digital Slave Module.

INTERFACE CONFIGURATION

The user must configure the PPT with the proper functioncodes before it can be placed into service. The PPT configura-tion determines interface operating characteristics such astime synchronization, serial communication rate, node defini-tion, point definitions and general execution characteristics.

Table 3-9 lists the function codes used by the INPPR01. Referto the Function Code Application Manual (I-E93-900-20) forinformation about the function codes in Table 3-9.

INSTALLING A REDUNDANT INTERFACE

3 - 12 I-E96-624A

Page 33: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

INSTALLATION

I-E96-624A

Figure 3-6. Redundant Transceiver

DSM05PPT

PRIMARY

PPT

SECONDARY

NTMF01NTDI01

P1

P1

P3

NKTU01 CABLES

RS232 (LINES 1-5, 8, 20)

A1

A2

A3

A4

+–

+

+

+

ANTENNASWITCH

MODEM

REDUNDANTTRANSCEIVER

PRIMARYTRANSCEIVERENABLE

ENABLE

T00421A

SELECT

Table 3-9. INPPR01 Function Codes

Function Code Title

FC 127 Plant Loop Gateway Node Map

FC 130 Plant Loop Gateway Executive

FC 131 Plant Loop Gateway Point Definition

INTERFACE CONFIGURATION

3 - 13

Page 34: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 4 - OPERATING PROCEDURES

I-E96-624A

INTRODUCTION

This section explains how to place the INPPR01 in operation Itcovers faceplate LEDs, modes of operation, and the two controltypes. Additionally, it provides information concerning redun-dant operation and interface memory utilization.

PLANT LOOP TO PLANT LOOP TRANSFER MODULE LEDs AND CONTROLS

The faceplate of the PPT has the following components (see Fig-ure 4-1):

1. Status LED2. 8 CPU LEDs3. 2 Memory Status LEDs4. Stop pushbutton5. Reset pushbutton

Figure 4-1. PPT Faceplate LEDs

STATUS LED

RESETPUSHBUTTON

T00422A

INPPT01

12345678

12

CPU

MEM

STOP

INTRODUCTION

4 - 1

Page 35: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES ®

Status LED

The Status LED is a red/green LED that displays the operatingstatus of the PPT. It has five possible states. Table 4-1 lists themeaning of the status LED states. Refer to Section 5 for correc-tive action if the status LED indicates that an operating errorexists.

CPU LEDs

During normal operation, the CPU LEDs keep a count of theinternal and external messages that pass through the PPT. If acommunication error occurs, these LEDs display an error codeand the Status LED turns RED. Refer to Table 5-1 for a list ofCPU LED error codes and corrective action.

Memory LEDs

There are two Memory LEDs. MEM LED 2 is on while the mod-ule is correcting single bit errors. Both LEDs are on when atwo-bit error or a complete memory failure occurs.

Stop Pushbutton

Push the stop pushbutton before removing a PPT from theModule Mounting Unit. The stop pushbutton causes the fol-lowing actions to occur:

1. Allows any NVM write in progress to complete.

2. Forces control from a primary to a secondary PPT in redun-dant configurations.

Reset Pushbutton

Pressing the reset pushbutton causes:

1. Restoration of PPT to power-up values after a halt.

Table 4-1. PPT Status LED States

LED State Meaning

Off No power to the PPT.

Solid Green The PPT is in the EXECUTE Mode.

Flashing Green (once per second) The PPT is in the EXECUTE Mode and detects a NVM checksum error.

Flashing Green (4 times per second) The PPT is in the CONFIGURE or ERROR Mode.

Solid Red The PPT diagnostics detect a hardware failure or configuration problem. CPU LEDs display an error code when the status LED is red.

PLANT LOOP TO PLANT LOOP TRANSFER MODULE LEDs AND CONTROLS

4 - 2 I-E96-624A

Page 36: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES

I-E96-624A

2. Recovery from an operator-initiated stop or a moduletimeout.

LOOP INTERFACE MODULE LEDs

There are eight LEDs on the LIM faceplate (see Figure 4-2).These LEDs display the contents of event and error counters,and pass/fail information when on-board diagnostics are run(refer to Tables 3-4 and 3-5 for a list of event and error countercodes).

BUS TRANSFER MODULE LED

The Bus Transfer Module has one red/green LED that displaysthe module's operating condition (see Figure 4-3). The BTMStatus LED has three possible states. Refer to Table 4-2 forBTM Status LED states and their meaning. Section 5 explainsthe corrective action to take if the Status LED displays a BTMhardware failure.

MODES OF OPERATION

The Plant Loop-to-Plant Loop Remote Interface has threemodes of operation: Configure, Execute and Error. Within theExecute mode the module has two methods of control: one-wayor two-way control.

Figure 4-2. LIM Faceplate LEDs

T00399A

INLIM03

12345678

LOOP INTERFACE MODULE LEDs

4 - 3

Page 37: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES ®

Configure Mode

This mode applies to the INPPT01 module. Module configura-tion requires an INFI 90 operator interface device (i.e., Opera-tor Interface Station, Management Command System,Engineering Work Station, etc.). Refer to Section 3 and to theinstruction for your operator interface device for informationabout interface configuration.

Execute Mode

This is the normal mode of operation for the PPR. In the exe-cute mode, the PPR issues requests for exception reports (XRs)twice a second, collects XRs, exercises control (local to remote),allows the operator to adjust tunable module specificationsand configure modules in remote loops. The interface entersone of the two control types that the user configures duringinstallation.

Figure 4-3. BTM Faceplate LEDs

Table 4-2. BTM Status LEDs States

LED States Meaning

Off No power to the BTM.

Solid Green Normal Operation.

Solid Red BTM hardware failure.

STATUS LED

T00413A

INBTM01

MODES OF OPERATION

4 - 4 I-E96-624A

Page 38: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES

I-E96-624A

Error Mode

The PPT enters this mode if the built-in system diagnosticsdetect a hardware or configuration error. If the PPT detects ahardware error, the module halts and displays an error code onthe CPU LEDs. If the CPU LEDs display a configuration error,the module remains in the error mode. Refer to Section 5 forcorrective action when the PPT enters the error mode.

One-Way Control

The PPT option switch setting (set during installation) deter-mines if the module is in one-way control. In one-way control,the local Plant Loop requests XRs from all remotes twice a sec-ond. The operator does module tuning and configuration, andissues control commands to the remote Plant Loops throughthe operator interface.

This type of control requires only one serial port (port 0). Port 1can also be used as an additional link through which the localloop issues commands. Using both ports increases the totalthroughput of the PPT (see Figure 4-4).

Figure 4-4. Local Plant Loop Using Both Serial Ports in One-Way Control

PCU4

PCU1

PPR10

PCU20

PPR10

SERIAL PORT 0SERIAL PORT 1

SERIAL PORT

OIS1

REMOTEPLANT LOOP

A

LOCAL PLANT LOOP

REMOTEPLANT LOOP

B

PPR10

OIS30

T00423A

PCU10

PCU1

PCU2

PCI33

PCU4

OIS20

LEGEND:OIS = OPERATOR INTERFACE STATIONPCI = PLANT LOOP TO COMPUTERINTERFACEPCU = PROCESS CONTROL UNITPPR = PLANT LOOP TO PLANT LOOPREMOTE INTERFACE

MODES OF OPERATION

4 - 5

Page 39: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES ®

Two-Way Control

In two-way control, bidirectional communication requires bothports on both Plant Loops (Port 0 to Port 0; Port 1 to Port 1).Both loop interfaces can issue requests, control commandsand do module tuning and configuration. The local interfaceuses one serial port to issue commands and receive replies (seeFigure 4-5). The remote interface uses the other port for thesame purpose. As in one-way control, the PPT requests XRstwice a second; control and configuration commands arethrough operator action.

REDUNDANT INTERFACE OPERATION

Redundant interface configurations require two sets of LIM/BTM and PPT modules. Each set of modules reside on a sepa-rate module bus. Redundant interfaces share a common slaveexpander bus. Upon start-up, one interface assumes the pri-mary role; the other waits in a backup role. The primary PPT

Figure 4-5. Local and Remote Plant Loops in Two-Way Control

PCU4

PCU4

PCU20

PCU1

PPR10

PPR10

OIS1

OIS2

REMOTEPLANT LOOP

LOCALPLANT LOOP

SERIAL PORTS

SERIAL PORTS

LOCAL XMIT/RCVREMOTE XMIT/RCV

T00424A

REDUNDANT INTERFACE OPERATION

4 - 6 I-E96-624A

Page 40: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES

I-E96-624A

downloads the interface configuration to the secondary (redun-dant modules are identically configured to their primary coun-terpart). If the primary interface fails, the redundant unit takesover and re-establishes the point data.

INTERFACE POINT CAPACITY

There are three factors that determine the maximum numberof points in a PPT configuration. Those factors are: point type(exception report data type), the number of devices that receiveinterface generated exception reports and the total memoryavailable (440,000 bytes). Table 4-3 lists the required memorybytes for all point types when memory usage is for:

1. The local PPT receiving points from the remote PPT.

2. The remote PPT (in two-way mode) receiving points fromthe local PPT.

Table 4-4 lists the required memory bytes for all point typeswhen the memory usage is for:

1. The remote PPT sending points to the local PPT.

2. The local PPT (in two-way mode) sending points to theremote PPT.

NOTE: The PPT has a capacity of 5,000 blocks.

Table 4-3. Memory Usage in Receiving Communication

Point TypeMemory Bytes

Required

Digital 16

Analog 30

Station 76

Remote Control Memory (RCM) 22

Remote Manual Set Constant (RMSC) 38

Device Driver 22NOTE: Add 6 bytes per point per destination being sent.

INTERFACE POINT CAPACITY

4 - 7

Page 41: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES ®

MEMORY USAGE EXAMPLE

In this example, a pair of interfaces in one-way mode has thefollowing mix of points in their configuration:

500 digital points (S3 of FC131 = 0)200 analog points (S3 of FC131 = 1)50 stations (S3 of FC131 = 2)

Distribution of 750 total points on the remote loop is among 20modules residing in 10 different PCUs. There are five OISs onthe local loop. Each OIS receives all of the points.

Memory Usage in the Local PPT

The points are coming to the local from the remote, therefore,Table 4-3 applies. The calculations are:

500 digital points x 16 bytes/point = 8,000 bytes200 analog points x 30 bytes/point = 6,000 bytes50 station points x 76 bytes/point = 3,800 bytes

Each OIS receives all 750 points:5 OIS x 750 points x 6 bytes/point = 22,500 bytesTotal memory used in the local PPT = 40,300 bytes

Memory Usage in the Remote PPT

These points are to be sent to the local, therefore, Table 4-4applies. The calculations are:

500 digital points x 18 bytes/point = 9,000 bytes200 analog points x 22 bytes/point = 4,400 bytes50 station points x 70 bytes/point = 3,500 bytes20 modules x 10 bytes/module = 200 bytes10 PCUs x 16 bytes/PCU = 160 bytesTotal memory used in the remote PPT = 17,260 bytes

Table 4-4. Memory Usage in Sending Communication

Point Type Memory Bytes Required

Digital 18

Analog 22

Station 70

Remote Control Memory(RCM) 22

Remote Manual Set Constant (RMSC) 26

Device Driver 22NOTE: Add 16 bytes for each PCU that sources Exception Reports. Add 10 bytes for each modulethat sources Exception Reports.

MEMORY USAGE EXAMPLE

4 - 8 I-E96-624A

Page 42: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES

I-E96-624A

SECURITY FUNCTIONS

The PPT performs both hardware and software security checksto insure module integrity.

Hardware Checks

The PPT does the following hardware checks:

1. Error Detection and Correction - Detects single bit anddouble bit errors in the dynamic RAM. Corrects single biterrors; halts PPT operation on double bit errors.

2. Illegal Address Detection - Detecting an illegal address gen-erates a bus error and the PPT halts operation.

3. Machine Fault Timer - The microprocessor updates thistimer. A machine fault timeout halts module operation.

Software Checks

The PPT does the following software checks:

1. Module Diagnostics - Module diagnostics execute automat-ically on system power up. PPT faceplate LEDs display errorconditions if the diagnostic tests fail.

2. Module Status Check - This test verifies checksums of theUVROM and NVM. Discrepancies cause the PPT Status LED toflash green and PPT operation halts.

Utilities

The utilities menu shown in Figure 4-6 is available to the userby attaching a diagnostic monitor to serial port 1. Items 1, 4and 5 are used for Bailey Engineering purposes. Items 2 and 3are available to the user.

When 2 is keyed in, the following appears:

2 - Which Loop?reply: not configured orcommunicating orcommunication failed, will retry in x seconds

When 3 is keyed in, the following appears:

3 - Enter Slave Address:enter new digital outputs:reply 0 or 1

SECURITY FUNCTIONS

4 - 9

Page 43: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

OPERATING PROCEDURES ®

Figure 4-6. PPT Utilities Menu

PPT UTILITIES MENU, REVISION X.XCOPYRIGHT (C) 1990 BAILEY CONTROLS COMPANY

1 DEBUG 2 LOOP COMM. REPORT3 DIGITAL OUTPUT TEST 4 CPU UTILIZATION5 READ MEMORY

T00425A

SECURITY FUNCTIONS

4 - 10 I-E96-624A

Page 44: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 5 - TROUBLESHOOTING

I-E96-624A

INTRODUCTION

If errors occur while the interface is operating, the CPU LEDson the PPT faceplate display error codes. Table 5-1 lists theerror codes and corrective action.

NOTE: Codes are displayed only when the PPT is halted and theStatus LED is red. A 0 represents a LED that is off and a 1 repre-sents a LED that is on.

Table 5-1. Table 5-1. PPT Error Codes

LED8 7 6 5 4 3 2 1

Meaning Corrective Action

0 0 0 0 0 0 0 1 An error affecting the NVM checksum has occurred.

None.

0 0 0 0 0 0 1 0 An error occurred while the PPT was writing to its non-volatile memory.

None.

0 0 0 0 0 0 1 1 External communication equipment failure detected.

Check the external communication equipment.

0 0 0 0 1 0 1 1 Contact 7 of Option Switch U72 has been set (NVM initialized).

None.

0 0 0 0 1 1 0 0 NVM write in progress when power lost. None.

0 0 0 0 1 1 0 1 An error occurred in communication between primary PPT and redundant PPT.

None.

0 0 0 0 1 1 1 0 PPT redundancy switches (Option Switch U72 contact 8) are the same.

Set U72 (position 8) on secondary PPT to 0 and U72 on the primary PPT to 1.

0 0 0 0 1 1 1 1 Primary PPT failed before its configuration was copied to the backup.

Reset the secondary PPT and enter the configuration.

0 0 0 1 0 0 0 0 Secondary PPT loop address (U75) does not match primary PPT.

Set secondary PPT loop address to match the primary PPT loop address.

0 0 0 1 0 0 0 1 Secondary PPT control mode or RS-232C mode (DCE or DTE) or ID (local or remote) does not match primary PPT.

Check the option switch settings (U72) on the secondary PPT.

0 0 0 1 0 0 1 0 BTM not responding. Replace the BTM.

0 0 0 1 0 0 1 1 ROM checksum error. Reset the PPT.

0 0 1 1 0 0 0 0 The system tried to force control to the redundant PPT while the primary PPT was still functioning.

None.

0 0 1 1 0 0 0 1 A fault in either the CPU or MEM boards exists.

Replace the PPT.

0 0 1 1 0 0 1 0 An addressing error occurred on internal microprocessor address bus.

Reset the PPT.

0 0 1 1 0 0 1 1 Attempt to execute an illegal processor instruction.

Reset the PPT.

INTRODUCTION

5 - 1

Page 45: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TROUBLESHOOTING ®

Status Bytes

Five status bytes provide information about Plant Loop to PlantLoop Transfer Module status. These bytes are availablethrough any operator interface such as the Operator InterfaceStation (OIS). Refer to the instruction for your operator inter-face for an explanation of how to access status bytes. Table 5-2lists the status bytes. Table 5-3 lists the status bytedefinitions.

0 0 1 1 0 1 0 1 Microprocessor received spurious excep-tion vector.

Reset the PPT.

0 0 1 1 0 1 1 0 A divide by 0 or CHK instruction was expected.

Reset the PPT.

0 0 1 1 0 1 1 1 TRAP instruction was executed. None.

0 0 1 1 1 1 1 1 The PPT has stopped because the user pressed the Stop pushbutton.

Reset the PPT.

0 0 0 0 0 0 0 01 The secondary PPT configuration is not copied from the primary PPT yet.

None.

1 0 0 0 0 0 0 01 The secondary PPT correctly copied the pri-mary configuration and is ready to take over.

None.

1. These codes apply to the secondary PPT in a redundant configuration.

Table 5-1. Table 5-1. PPT Error Codes (continued)

LED8 7 6 5 4 3 2 1

Meaning Corrective Action

Table 5-2. Status Bytes

ByteBit+

7 6 5 4 3 2 1 0

1 ES MODE TYPE

2 FTX BAC RIO LIO N/A NVI CFG N/A

3 PCU MEM NEF N/A N/A N/A N/A N/A

4 LIE LRE LRE LTE LTE N/A N/A N/A

5 N/A N/A N/A N/A N/A N/A N/A N/A

INTRODUCTION

5 - 2 I-E96-624A

Page 46: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TROUBLESHOOTING

I-E96-624A

Table 5-3. Status Byte Definitions

Field Value Description

Byte 1ESMODETYPE

80601F

Error Summary (0-OK, 1-Error)Module Mode (00-Config, 01-Error, 11-Exec)Module Type Code = Hex 11 (INPPT01)

Byte 2FTXBACRIOLION/ANVICFGN/A

80402010

0402

First Time in Execute (0-No, 1-Yes)Backup PPT Status (0-OK, 1-Bad)Summary Remote I/O Status (0-OK, 1-Bad)Summary Local I/O Status (0-OK, 1-Bad)Not ApplicableNVM Checksum Error (0-OK, 1-Bad)Default Configuration (0-No, 1-Yes)Not Applicable

Byte 3PCUMEMNEFBits 0-4

010203

One or more PCUs offline (0-No, 1-Yes)Memory Full (0-No, 1-Yes)Node Environment Failure (0-No, 1-Yes)Not Applicable

Byte 4LIELRELRELTELTEBits 0-3

8040204080

LIM Internal ErrorLoop Receive Error Channel 1Loop Receive Error Channel 2Loop Transmit Error Channel 1Loop Receive Error Channel 2Not Applicable

Byte 5Bits 0-7 Not Applicable

Table 5-4. LIM Edge Connector P3 Pin Assignments

Pin No. Signal Pin No. Signal

1 Loop 2 In (+) 13 Loop 2 Bypass Control

2 Loop 2 In (-) 14 Cable Shield

3 Cable Shield A Cable Shield

4 Loop 1 Out (+) D Loop 1 Out (-)

5 Loop 1 Out (+) E Loop 1 Out (-)

6 Loop 1 In (+) F Cable Shield

7 Loop 1 In (-) H Loop 2 Bypass Control

8 Cable Shield K Loop 2 Out (-)

9 Loop 2 Out (+) L Loop 2 Out (-)

10 Loop 2 Out (+) M Cable Shield

11 Cable Shield S Cable Shield

INTRODUCTION

5 - 3

Page 47: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TROUBLESHOOTING ®

Table 5-5. BTM Edge Connector P1 Pin Assignments

Pin No. Signal Pin No. Signal

1 +5 VDC 2 +5 VDC

3 N/C 4 N/C

5 Common 6 Common

7 +15 VDC 8 -15 VDC

9 Power Fail Interrupt 10 Power Fail Interrupt

11 Module Bus 12 Module Bus

Table 5-6. PPT CPU Board Edge Connector P2 Pin Assignments

Pin No. Signal Pin No. Signal

1 Data Bit D1 2 Data Bit D0

3 Data Bit D3 4 Data Bit D2

5 Data Bit D5 6 Data Bit D4

7 Data Bit D7 8 Data Bit D6

9 Clock 10 Sync

11 N/C 12 N/CNOTE: All data bits are low true.

Table 5-7. PPT CPU Board Edge Connector P3 Pin Assignments

Pin No. Signal Pin No. Signal

1 SAC Link (+) A SAC Link (-)

2 Redundancy LinkTransmit Data (+)

B Redundancy LinkTransmit Data (-)

3 Redundancy LinkReceive Data (-)

C Redundancy LinkReceive Data (+)

4 Terminal PortTransmit Data

D Terminal PortReceive Data

5 Terminal PortRequest to Send

E Terminal PortClear to Send

6 Terminal PortData Carrier Detect

F N/A

7 Printer PortTransmit Data

H Printer PortReceive Data

8 Printer PortRequest to Send

J Printer PortClear to Send

9 Printer PortData Carrier Detect

K N/A

INTRODUCTION

5 - 4 I-E96-624A

Page 48: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TROUBLESHOOTING

I-E96-624A

10 Digital Output 1 (+) L Digital Output 1 (-)

11 Digital Output 2 (+) M Digital Output 2 (-)

12 N/A N N/A

13 N/A P N/A

14 N/A R N/A

15 N/A S N/A

Table 5-7. PPT CPU Board Edge Connector P3 Pin Assignments (continued)

Pin No. Signal Pin No. Signal

INTRODUCTION

5 - 5

Page 49: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 6 - MAINTENANCE

I-E96-624A

INTRODUCTION

The Plant Loop to Plant Loop Remote Interface (INPPR01)requires minimal maintenance. The following maintenanceschedule will ensure trouble free service.

NOTE: Only qualified personnel should perform maintenance.

MAINTENANCE SCHEDULE

The PPR maintenance schedule is shown in Table 6-1. Performthese tasks at the specified intervals.

Table 6-1. Maintenance Schedule

Task Interval

Clean and check all cable connections to the INLIM03, INBTM01 and INPPT01.

Every 6 months or during plant shutdown, whichever occurs first.

Use a static vacuum cleaner to remove dust from:

ModulesModule Mounting UnitFan AssemblyPower Entry Panel

Every 6 months or during plant shutdown, whichever occurs first.

INTRODUCTION

6 - 1

Page 50: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 7 - REPAIR/REPLACEMENT PROCEDURES

I-E96-624A

INTRODUCTION

This section explains the replacement procedures for the PlantLoop to Plant Loop Remote Interface (INNPPR01). There are nospecial tools required to replace an interface module.

NOTE: Always use the Bailey Field Static Kit (P/N 1948385A1)when working with the interface modules. This kit connects the staticdissipative work surface and technician to the same ground point.

MODULE REPAIR/REPLACEMENT

If you determine an interface module is faulty, replace it with anew one. DO NOT try to repair the module; replacing compo-nents may affect the module performance. You can remove themodule while system power is supplied. To replace a module:

1. Press the stop pushbutton and wait for the status LED toturn red.

2. Push and turn the two front panel captive latches one halfturn to unlatch the module. It is unlatched when the slots onthe latches are vertical and the open end of the slots face awayfrom the module.

3. Gently slide the module out of the MMU.

4. Configure the replacement module switch and jumper set-tings. Ensure they are set the same as the original module.

5. In the same slot assignment as the original module, alignthe replacement module with the guide rails in the MMU; gen-tly slide it in until the front panel is flush with the top and bot-tom of the MMU frame.

6. Push and turn the two captive retaining latches on themodule faceplate one half turn to the latched position. It islatched when the slots on the latches are vertical and the openends face the center of the module.

7. Return to normal operation.

INTRODUCTION

7 - 1

Page 51: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

SECTION 8 - SUPPORT SERVICES

I-E96-624A

INTRODUCTION

Bailey Controls is ready to assist in the use of its products.Requests for sales, applications services, installation, repair,overhaul and maintenance contract services should be made tothe nearest sales office.

REPLACEMENT PARTS AND ORDERING INFORMATION

If you are making repairs at your own facility, replacementparts should be ordered through a Bailey sales office. Providethe following information for parts orders:

1. Part description, part number and quantity.

2. Model, serial number (if applicable) and ratings of theassembly containing the ordered part.

3. Bailey publication number and reference used in identify-ing the part.

When ordering standard parts from Bailey Controls, use thepart number and description from the Replacement Parts sec-tion of the manual. Parts not having a commercial descriptionin the Replacement Parts section must be ordered from aBailey Controls sales office.

TRAINING

Bailey Controls has a modern training facility equipped to pro-vide service and repair instructions. This facility is available forin-plant training of your personnel. Contact a Bailey Controlssales office for information on available classes and schedul-ing.

TECHNICAL DOCUMENTATION

You can obtain additional copies of this manual through thenearest Bailey sales office. Copies, over and above those pro-vided with the original purchase, are available at a minimumcharge to the customer. Contact a Bailey Controls sales officefor information.

INTRODUCTION

8 - 1

Page 52: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

APPENDIX A - TERMINATION UNIT CONFIGURATION(NTMF01)

I-E96-624A

INTRODUCTION

The INPPT01 uses the NTMF01 for termination. Figure A-1shows the dipshunt configuration required when connecting alocal and remote PPT (DTE) via a modem (DCE). Figure A-2 andA-3 show the dipshunt configuration required when directlyconnecting a local PPT (DTE) to a remote PPT (DCE) via a cable.Figure A-4 shows how to configure the dispshunts so that port1 can drive a diagnostics terminal. Figure A-5 shows theRS-232-C signals and the associated DB-25 pin assignments.

Figure A-1. Disphunt Configuration for PPT Acting as DTE (Requires Modem or Other DCE)

P1 CONNECTOR

STATIONCOMMUNICATION

P2 CONNECTOR

TERMINALPORT

PRINTERPORT

PORT1

PORT0

F1 FUSE

+24 V (E2)COM (E3)

T00426A

P3CONNECTOR

XU1

XU2

P5

P6

XU4

XU4

XU2

XU3

XU3

XU1

+24 VDC

+24 VDC

RXD

RXD

RXD

RXD

RTS

RTS

RTS

RTS

CTS

CTS

CTS

CTS

TXD

TXD

TXD

TXD

DCD

DCD

1

1

CABLESHIELDINGGROUND

CABLESHIELDINGGROUND

DB-25 PINASSIGNMENT

DB-25 PINASSIGNMENT

3

3

4

4

5

5

2

2

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

LOCAL AND REMOTE

INTRODUCTION

A - 1

Page 53: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION UNIT CONFIGURATION (NTMF01) ®

Figure A-2. Dipshunt Configuration for Direct Connection with Local PPT Acting as DTE

P1 CONNECTOR

STATIONCOMMUNICATION

P2 CONNECTOR

TERMINALPORT

PRINTERPORT

PORT1

PORT0

F1 FUSE

+24 V (E2)COM (E3)

T00427A

P3CONNECTOR

XU1

XU2

P5

P6

XU4

XU4

XU2

XU3

XU3

XU1

+24 VDC

+24 VDC

RXD

RXD

RXD

RXD

RTS

RTS

RTS

RTS

CTS

CTS

CTS

CTS

TXD

TXD

TXD

TXD

DCD

DCD

1

1

CABLESHIELDINGGROUND

CABLESHIELDINGGROUND

DB-25 PINASSIGNMENT

DB-25 PINASSIGNMENT

3

3

4

4

5

5

2

2

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

LOCAL

INTRODUCTION

A - 2 I-E96-624A

Page 54: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION UNIT CONFIGURATION (NTMF01)

I-E96-624A

Figure A-3. Dipshunt Configuration for Direct Connection with Remote PPT Acting as DCE

P1 CONNECTOR

STATIONCOMMUNICATION

P2 CONNECTOR

TERMINALPORT

PRINTERPORT

PORT0

PORT1

F1 FUSE

+24 V (E2)COM (E3)

T00428A

P3CONNECTOR

XU1

XU2

P5

P6

XU4

XU2

XU4

XU3

XU1

XU3

+24 VDC

+24 VDC

RTS

RTS

RXD

RXD

TXD

TXD

CTS

CTS

DCD

DCD

RXD

RXD

TXD

TXD

CTS

CTS

RTS

RTS

1

1

CABLESHIELDINGGROUND

CABLESHIELDINGGROUND

DB-25 PINASSIGNMENT

DB-25 PINASSIGNMENT

4

4

3

3

2

2

5

5

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

1

7

98

6

2

543

10

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

REMOTE

INTRODUCTION

A - 3

Page 55: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION UNIT CONFIGURATION (NTMF01) ®

Figure A-4. Dipshunt Configuration for Diagnostic Terminal (Port 1 only)

P1 CONNECTOR

STATIONCOMMUNICATION

P2 CONNECTOR

TERMINALPORT

LOCAL OR REMOTE

PRINTERPORT

PORT 1ONLY FOR

DIAGNOSTICTERMINAL

F1 FUSE

+24 V (E2)COM (E3)

T00429A

P3CONNECTOR

XU1

XU2

P5

P6

XU4

XU4

XU3

XU3

+24 VDC

DCD

RXDTXD

CTSDCD

RXDDCD

TXD

CTS

CTS 9

8

32

5

1

7

98

6

2

543

10

1

7

98

6

2

543

10

20

14

1213

15

19

161718

11

20

14

1213

15

19

161718

11

INTRODUCTION

A - 4 I-E96-624A

Page 56: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION UNIT CONFIGURATION (NTMF01)

I-E96-624A

Figure A-5. DB-25 Pin Assignments and RS-232-C Signals

1

2

3

4

5

6

7

8

20

19

18

17

16

15

14

13

129

10 11

1

2

3

4

5

6

7

8

20

19

18

17

16

15

14

13

129

10 11

TXD

RXD

RTS REQUEST TO SEND

CTS

DCD

CLEAR TO SEND

RECEIVED LINE SIGNAL DETECT

TRANSMIT DATA

RECEIVE DATA

DCD

RXD

TXD

CTS

RTS

CTS

CTS

CTS

RTS

CTS

DCD

CTS

RTS

RXD

TXD

XU2XU4

XU1XU3

DTE

+24V

TD

RD

RTS

CTS

DCD

SDCE

SRD

DTR

DSR

DCE

2 TRANSMIT DATA

3 RECEIVE DATA

4 REQUEST TO SEND

5 CLEAR TO SEND

8 RECEIVED LINE SIGNAL DETECT

9 + VOLTS

12 SECONDARY RECEIVE SIGNAL DETECT

16 SECONDARY RECEIVE SIGNAL

25 BUSY

1 PROTECTIVE GROUND

20 DATA TERMINAL READY

6 DATA SET READY

7 SIGNAL GROUND

22 RING DETECT

14 SECONDARY TRANSMITTED DATA

11 EQUALIZER MODE

STD

QM

T00375A

INTRODUCTION

A - 5

Page 57: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

APPENDIX B - TERMINATION UNIT CONFIGURATION(NTCL01)

I-E96-624A

INTRODUCTION

The INLIM03 uses the NTCL01 for termination. Table B-1 liststhe terminal assignments and Table B-2 lists the BNC terminalassignments for the loop input/output connections. Table B-3provides jumper settings associated with cable type. Figure B-1shows twinax cable connections for the NTCL01.

NOTE: Twinax cables connect to the terminals. Coax cables con-nect to the BNC connectors.

Table B-1. NTCL01 Terminal Assignments

Terminal Number

TB1Assignments

Terminal Number

TB3Assignments

12345678

Loop 1 In, +Loop 1 In, -Loop 1 In, Shieldno connectionLoop 1 Out, +Loop 1 Out, -Loop 1 Out, ShieldPower System Status 1

12345678

Loop 2 In, +Loop 2 In, -Loop 2 In, Shieldno connectionLoop 2 Out, +Loop 2 Out, -Loop 2 Out, ShieldPower System Status 2

Table B-2. BNC Terminal Assignments

BNC Number

AssignmentsBNC

NumberAssignments

J1J2

Loop 1 InLoop 1 Out

J8J9

Loop 2 InLoop 2 Out

INTRODUCTION

B - 1

Page 58: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION UNIT CONFIGURATION (NTCL01) ®

Table B-3. Jumper Settings and Cable Types

JUMPER NO.

J3, J10

J15-J18

J4-J7, J11-J14

TWINAX COAX

NLIM03

T00365A

1 2 3POST

NUMBERS

Figure B-1. NTCL01 Termination Unit and Terminal Assignments

NLIM03 - PLANT LOOP

T00366A

NKLS03 (NLIM03)

NTCL01

NTCL01

NKPL01

P1

P1

TB2

J9

J2

J2

J9

J8

J1

J1

J8

TB2

SH- IN+

TB1

TB1

E2

E2

COM

LOOP2

LOOP1

LOOP1

LOOP2

COM

E1

E1

+24V

+24V

P1

P3

P2

8 7 6 5 4 3 2 1

8 7 6 5 4 3 2 1

8 7 6 5 4 3 2 1

8 7 6 5 4 3 2 1

INTRODUCTION

B - 2 I-E96-624A

Page 59: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

APPENDIX C - TERMINATION MODULECONFIGURATION (NIMF01/NIMF02)

I-E96-624A

INTRODUCTION

The INPPT01 can use the NIMF01 for termination. The NIMF02is required when terminating redundant interfaces. The disp-shunt configurations shown in Figure C-1 through C-4 applyto the NIMF01 and NIMF02. Figure C-1 shows the dipshuntconfiguration required when connecting a local and remotePPT (DTE) via a modem (DCE). Figure C-2 and C-3 show thedipshunt configuration required when directly connecting alocal PPT (DTE) to a remote PPT (DCE) via a cable.

Figure C-1. Dipshunt Configuration for PPT Acting as DTE (requires Modem or Other DCE)

20

20

1

1

18

18

3

3

17

17

4

4

16

16

5

5

15

15

6

6

19

19

2

2

14

14

7

7

13

13

8

8

12

12

9

9

11

11

10

10

20

20

1

1

18

18

3

3

17

17

4

4

16

16

5

5

15

15

6

6

19

19

2

2

14

14

7

7

13

13

8

8

12

12

9

9

11

11

5

5

4

4

3

3

1

1

2

2

10

10

+24 VDC

+24 VDC

XU2

XU4

CTS

CTS

DCD

DCD

CTS

CTS

CABLE SHIELDING GROUND

CABLE SHIELDING GROUND

RTS

RTS

RTS

RTS

RXD

RXD

RXD

RXD

TXD

TXD

TXD

TXD

XU1

XU3

DB-25 PINASSIGNMENTS

DB-25 PINASSIGNMENTS

PORT 0

PORT 1

LOCAL AND REMOTE

TERMINAL PORT

PRINTER PORTT00430A

PORT 0

PORT 1

P1 EDGECONNECTOR

XU3

XU1

XU4

XU2

INTRODUCTION

C - 1

Page 60: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION MODULE CONFIGURATION (NIMF01/NIMF02) ®

Figure C-3 shows how to configure the dispshunts so that port1 can drive a diagnostics terminal.

Figure C-2. Dipshunt Configuration for Direct Connection of Local PPT Acting as DTE

20

20

1

1

18

18

3

3

17

17

4

4

16

16

5

5

15

15

6

6

19

19

2

2

14

14

7

7

13

13

8

8

12

12

9

9

11

11

10

10

20

20

1

1

18

18

3

3

17

17

4

4

16

16

5

5

15

15

6

6

19

19

2

2

14

14

7

7

13

13

8

8

12

12

9

9

11

11

5

5

4

4

3

3

1

1

2

2

10

10

+24 VDC

+24 VDC

XU2

XU4

CTS

CTS

DCD

DCD

CTS

CTS

CABLE SHIELDING GROUND

CABLE SHIELDING GROUND

RTS

RTS

RTS

RTS

RXD

RXD

RXD

RXD

TXD

TXD

TXD

TXD

XU1

XU3

DB-25 PINASSIGNMENTS

DB-25 PINASSIGNMENTS

PORT 0

PORT 1

LOCAL

TERMINAL PORT

PRINTER PORTT00431A

PORT 0

PORT 1

P1 EDGECONNECTOR

XU3

XU1

XU4

XU2

INTRODUCTION

C - 2 I-E96-624A

Page 61: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION MODULE CONFIGURATION (NIMF01/NIMF02)

I-E96-624A

Figure C-3. Dipshunt Configuration for Direct Connection of Remote PPT Acting as DCE

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

10

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

2

3

4

1

5

10

+24 VDC

XU4

DCD

TXD

CABLE SHIELDING GROUND

RXD

RXD

TXD

CTS

RTS

RTS

CTS

XU3

DB-25 PINASSIGNMENTS

PORT 1

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

10

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

2

3

4

1

5

10

+24 VDC

XU2

DCD

TXD

CABLE SHIELDING GROUND

RXD

RXD

TXD

CTS

RTS

RTS

CTS

XU1

DB-25 PINASSIGNMENTS

PORT 0

REMOTE

T00432A

TERMINAL PORT

PRINTER PORT

PORT 0

PORT 1

P1 EDGECONNECTOR

XU3

XU1

XU4

XU2

INTRODUCTION

C - 3

Page 62: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION MODULE CONFIGURATION (NIMF01/NIMF02) ®

Figure C-4. Dispshunt Configuration for Diagnostic Terminal

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

10

20

1

18

3

17

4

16

5

15

6

19

2

14

7

13

8

12

9

11

2

3

8

9

5

10

+24 VDC

XU4

TXD

RXD

RXD

CTSDCD

DCD

TXD

CTS

XU3

DB-25 PINASSIGNMENTS

PORT 1

DIAGNOSTIC TERMINAL(PORT 1 ONLY)

T00433A

TERMINAL PORT

PRINTER PORT

PORT 0

PORT 1

P1 EDGECONNECTOR

XU3 XU4

INTRODUCTION

C - 4 I-E96-624A

Page 63: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

APPENDIX D - TERMINATION MODULECONFIGURATION (NICL01)

I-E96-624A

INTRODUCTION

The INLIM03 can use the NICL01 for termination. Table D-1lists the terminal assignments for the loop input/output con-nections. Table D-2 provides jumper settings associated withcable type. Figure D-1 shows twinax cable connections forNICL01.

NOTE: Twinax cables connect to the terminals. Coax cables con-nect to the BNC connectors.

CAUTION Ensure that the end marked J1 is connected to P1 on theNICL01, and J2 is connected to the LIM. Failure to do so couldresult in module damage (see Figure D-1).

ATTENTION S'assuree que L'extremite identifiee par J1 est reliee a P1 dumodule NICL01 et que J2 est reliee au module LIM. Sinon, lesmodules pouiraient etre endommages (voir la figure D-1).

Table D-1. NICL01 Terminal Assignments

TB1Terminal

AssignmentsTB2

Terminal Assignments

TB3Terminal

Assignments

123

GroundCommon+24 VDC

4

5

6789

1011

Power System Status 1Power System Status 2Loop 2 In, +Loop 2 In, -Loop 2, ShieldLoop 2 Out, +Loop 2 Out, -Loop 2 Out, Shield

2526272829303132

Loop 1 Out, ShieldLoop 1 Out, -Loop 1 Out, +Loop 1 In, ShieldLoop 1 In, -Loop 1 In, +no connectionno connection

Table D-2. BNC Assignments

BNC Number Assignments

J1J2J8J9

Loop 1 InLoop 1 OutLoop 2 InLoop 2 Out

INTRODUCTION

D - 1

Page 64: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

TERMINATION MODULE CONFIGURATION (NICL01) ®

Table D-3. Jumper Settings and Cable Types

JUMPER NO.

J3, J10

J15-J18

J4-J7, J11-J14

TWINAX COAX

NLIM03

T00365A

1 2 3POST

NUMBERS

Figure D-1. Typical Twinax Cable Connection for the NICL01

T00396A

NLIM03 - PLANT LOOP

NICL01

NKLS04(NLIM03)J2 J1

P1

P2

P3 P1

J1

J2

J9

J8

30

11

29

10

123

28TB3

TB2

TB1

NICL01

J1

J2

J9

J8

27

11

26

10

123

25TB3

TB2

TB1

NKPL01

TERMINAL 25 TO 2826 TO 2927 TO 30

INTRODUCTION

D - 2 I-E96-624A

Page 65: E96-624 Plant Loop to Plant Loop Remote Interface Infi90 Documentation/INPPR01.pdfThe Plant Loop to Plant Loop Remote Interface (INPPR01) enables communication between a local and

Visit Elsag Bailey on the World Wide Web at http://www.bailey.com

Our worldwide staff of professionals is ready to meet your needs for process automation. For the location nearest you, please contact the appropriate regional office.

AMERICAS29801 Euclid AvenueWickliffe, Ohio USA 44092Telephone 1-216-585-8500Telefax 1-216-585-8756

ASIA/PACIFIC152 Beach RoadGateway East #20-04Singapore 189721Telephone 65-391-0800Telefax 65-292-9011

EUROPE, AFRICA, MIDDLE EASTVia Puccini 216154 Genoa, ItalyTelephone 39-10-6582-943Telefax 39-10-6582-941

GERMANYGraefstrasse 97D-60487 Frankfurt MainGermanyTelephone 49-69-799-0Telefax 49-69-799-2406

Form I-E96-624A Litho in U.S.A. 690Copyright © 1990 by Elsag Bailey Process Automation, As An Unpublished Work® Registered Trademark of Elsag Bailey Process Automation™ Trademark of Elsag Bailey Process Automation


Recommended