Professional Documents
Culture Documents
IOV18
IOV18
IOV18
I/O Block
Configuration
August 1994
U.S. Manual PN: 1984-2645-1801
A-4 Size Manual PN: 1984-2645-1811
1984-2645-5006
1984-2645-5016
E 1987--1999 Fisher-Rosemount Systems, Inc.
All rights reserved.
Printed in the U.S.A.
Components of the RS3 distributed process control system may be protected by U.S. patent Nos. 4,243,931; 4,370,257; 4,581,734. Other
Patents Pending.
RS3 is a mark of one of the Fisher-Rosemount group of companies. All other marks are property of their respective owners. The contents
of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are
not to be construed as warranties or guarantees, express or implied, regarding the products or services described herein or their use or
applicability. We reserve the right to modify or improve the designs or specifications of such products without notice.
2. Does this manual answer your questions? ______ ______ ______ ______ ______
Errors and Problems: Please note errors or problems in this manual, including chapter and page number,
if applicable; or send a marked-up copy of the affected page(s).
Name ______________________________________________
Company ______________________________________________
Phone ______________________________________________
Date ______________________________________________
Fisher-Rosemount FAX #: (512) 834--7200 Thank you!
Name
Place
Company stamp
here
Address
RS3t
I/O Block Configuration
This manual describes the input and output blocks used in the
Rosemount System 3ä control system.
References to other RS3 user manuals list the manual, chapter, and
sometimes the section as shown below.
Sample Entries:
For ..., see CC: 3. For ..., see CC: 1-1.
Reference Documents
Prerequisite Documents
Related Documents
You may find the following documents helpful when using this manual:
ABC Batch Software Manual 1984-2654-18x1
Alarm Messages Manual 1984-2657-18x1
ABC Batch Quick Reference Guide 1984-2814-11xx
Configuration Quick Reference Guide 1984-2812-08xx
Console Configuration Manual 1984-2643-18x1
ControlBlock Configuration Manual 1984-2646-18x1
I/O Block Configuration Manual 1984-2645-18x1
Operator’s Guide 1984-2647-18x1
PeerWay Interfaces Manual 1984-2650-18x1
Rosemount Basic Language Manual 1984-2653-18x1
RNI Programmer’s Reference Manual 1984-3356-01x1
RNI Release Notes and Installation Guide 1984-3357-01x1
Service Manual, Volume 1 1984-2648-18x1
Service Manual, Volume 2 1984-2648-18x2
Site Preparation and Installation Manual 1984-2642-xxx1
Software Defects for Version 18 1984-2818-03xx
System Resource Unit (SRU) Manual 1984-2651-18x1
User Manual Master Index 1984-2641-18x1
List of Figures
Figure 1.3.14. Analog Field Interface Card (FIC) I/O Point Addressing . . . . . . . IO:1-3-15
Figure 1.3.16. Pulse Field Interface Card (FIC) I/O Point Addressing . . . . . . . . IO:1-3-17
Figure 1.3.18. Multiplexer Front End Module (FEM) I/O Point Addressing . . . . IO:1-3-19
Figure 3.2.9. Configuring Voltage Pulse Input PIOB to Measure Pulse Duration IO:3-2-11
Figure 3.2.12. Effect of Target Count on PIOB Output—Target Count from ControlBlock . .
IO:3-2-14
Figure 3.2.13. Configuring Voltage Input PIOB to Count Pulses—Target Count from
ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-15
Figure 3.2.14. Configuring PIOB to Count Pulse Inputs—Target Count from Configuror . . .
IO:3-2-17
Figure 3.2.15. Effect of Target Count on PIOB Output—Target Count from Configuror . . . .
IO:3-2-17
Figure 3.2.16. Sample of a Voltage Input PIOB to Count Pulses—Target Count Provided
by Configuror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-18
Figure 3.2.20. Configuring a PIOB to Output a Pulse with a Specified Duration IO:3-2-24
Figure 3.2.22. Configuring a Pulse Output PIOB with a Specified Duration . . . . IO:3-2-25
Figure 3.2.24. Outputting Fixed Frequency for Specified Number of Pulses . . . IO:3-2-26
Figure 3.2.25. Configuring Pulse Output PIOB with Specified Number of Pulses IO:3-2-27
Figure 3.2.26. Analog Output PIOB Configured to Output 4--20 mA Signal . . . . IO:3-2-29
Figure 3.2.27. Analog Output PIOB Configured to Output a 23 V Power Supply IO:3-2-29
Figure 3.2.29. Configuring PIOBs for a Loader Application with a Binary Output IO:3-2-33
Figure 3.2.30. Interaction of PIOBs for a Loader Application with a Binary Output . . . . . . .
IO:3-2-33
Figure 3.2.31. Configuring a Pulse Output PIOB for a Loader Application with a Binary
Output—Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-34
Figure 3.2.32. Configuring a Pulse Input PIOB for a Loader Application with a Binary
Output—Loader Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-34
Figure 3.2.33. Configuring an Analog Output PIOB for a Loader Application with an
Analog Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-36
Figure 3.2.34. Interaction of PIOBs for a Loader Application with an Analog Output . . . . . .
IO:3-2-37
Figure 3.2.35. Effect of the Target Count on the PIOB Outputs . . . . . . . . . . . . . . IO:3-2-37
Figure 3.2.36. Configuring a Pulse Input PIOB for a Loader Application with an Analog
Output—Loader Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-38
Figure 3.2.37. Configuring an Analog Output PIOB for a Loader Application with an
Analog Output—Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-38
Figure 4.2.6. Scaling a TIB with the Default Eng Zero and Eng Max Values . . . IO:4-2-15
Figure 4.2.7. Scaling a TIB with Eng Zero and Eng Max Values Other than the Default
Values . IO:4-2-16
Figure 4.2.8. TIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:4-2-17
Figure 8.1.6. Smart Transmitter Input Block and Value Input Block in Manual Modes . . . . .
IO:8-1-6
Figure 8.1.7. SIB Configuration Screen—Filter Configuration . . . . . . . . . . . . . . . IO:8-1-7
Figure 8.1.8. SIB Configuration Screen—PV Type Configuration . . . . . . . . . . . .
IO:8-1-10
Figure 8.1.9. SIB Configuration Screen—Alarm Configuration . . . . . . . . . . . . . . .
IO:8-1-12
Figure 8.1.10. SIB Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-13
Figure 8.1.11. VIB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-17
Figure 8.1.12. VIB Block Configuration Screen—Linking a VIB Block to an SIB
IO:8-1-20
Figure 8.1.13. SIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-21
Figure 8.1.14. VIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-22
Figure 8.1.15. Transmitter Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-23
Figure 8.1.16. Configuration Screen Entry for Transmitter Configuration Screen
IO:8-1-29
Figure 8.1.17. Transmitter Configuration I/O Screen—Performing Transmitter Commands
IO:8-1-31
Figure 8.1.18. Transmitter Configuration I/O Screen—Performing Transmitter Address
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IO:8-1-32
Figure 8.1.19. Transmitter Configuration I/O Screen—Assigning a Descriptor .
IO:8-1-33
Figure 8.1.20. Transmitter Configuration I/O Screen—Range Configuration . . .
IO:8-1-34
Figure 8.1.21. Transmitter Configuration I/O Screen—Assigning Units . . . . . . .
IO:8-1-35
Figure 8.1.22. Transmitter Configuration I/O Screen—Damping Configuration . IO:8-1-40
Figure 9.3.3. PLCB I/O Block Configuration Screen (Read Only) . . . . . . . . . . . . IO:9-3-11
Figure 9.3.6. Configuration Window Linking PLC Bit Input to a Graphic . . . . . . . IO:9-3-16
Figure 9.3.10. PLCB I/O Block Configuration Screen (Write Only) . . . . . . . . . . . IO:9-3-22
Figure 9.3.12. PLCB I/O Block Configuration Screen (Data Type Other Than Flags) . . . . .
IO:9-3-23
Figure 9.3.13. Using the Write Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:9-3-25
Figure 9.3.14. Reading and Writing Through a Single I/O Block . . . . . . . . . . . . . IO:9-3-26
Figure 10.2.7. DOB Block Configuration Screen—FIM Switch Volt Configuration IO:10-2-9
List of Tables
Table 2.2.1. Analog Output Block (AOB) Configuration Screen Fields ....... IO:2-2-7
Table 3.2.1. Common Fields for the PIOB I/O Block Configuration Screen . . . . IO:3-2-3
Table 3.2.2. Contact Pulse Input PIOB Common Fields . . . . . . . . . . . . . . . . . . . . IO:3-2-6
Table 3.2.3. Voltage Pulse Input PIOB Common Fields . . . . . . . . . . . . . . . . . . . . IO:3-2-8
Table 3.2.4. Pulse Input PIOB Fields to Measure Pulse Frequency . . . . . . . . . . IO:3-2-10
Table 3.2.5. Pulse Input PIOB Fields to Measure Pulse Duration . . . . . . . . . . . . IO:3-2-12
Table 3.2.6. Pulse Input PIOB Fields to Count Pulses--Target Count Provided by
ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-15
Table 3.2.7. Pulse Input PIOB Fields to Count Pulses--Target Count Provided
by Configuror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IO:3-2-19
Table 3.2.9. Pulse Output Fields to Output a Pulse at a Specified Frequency . IO:3-2-23
Table 3.2.13. PIOB Fields for a Loader Application with a Binary Output . . . . . . IO:3-2-35
Table 3.2.14. PIOB Fields for a Loader Application with an Analog Output . . . . IO:3-2-39
Table 4.2.1. Common Fields for the TIB Configuration Screen . . . . . . . . . . . . . . IO:4-2-4
Table 4.2.2. Centigrade Temperature Ranges for RTD inputs . . . . . . . . . . . . . . . IO:4-2-7
Table 4.2.3. Centigrade Temperature Ranges for Thermocouple Inputs . . . . . . . IO:4-2-7
Table 5.2.1. Redundant I/O Block (RIOB) Configuration Screen Fields . . . . . . . IO:5-2-2
Table 6.1.1. Contact Input Block (CIB) Filter Options . . . . . . . . . . . . . . . . . . . . . . IO:6-1-3
Table 6.1.2. Contact Input Block (CIB) Configuration Screen Fields . . . . . . . . . IO:6-1-11
Table 8.1.2. VIB I/O Block Configuration Screen Fields ................... IO:8-1-18
Table 8.1.7. Transmitter Status Error Messages Generated by the Transmitter IO:8-1-27
Table 8.2.1. HART Output Block (HOB) Configuration Screen Fields . . . . . . . . IO:8-2-10
Table 8.2.4. FIC Communication Error Messages Generated by the FIC . . . . . IO:8-2-17
Table 8.2.6. Slot Variables for Fisher Transducer Output Device . . . . . . . . . . . . . IO:8-2-28
Table 8.2.7. Slot Variables for Fisher valve, no pressure sensor . . . . . . . . . . . . . IO:8-2-28
Table 8.2.8. Slot Variables for Fisher valve with pressure sensor . . . . . . . . . . . . IO:8-2-28
Table 9.3.1. Discrete Bit Maps for RS3 and Modicon Interface . . . . . . . . . . . . . . IO:9-3-3
Table 9.3.2. Discrete Bit Map for RS3 and Modicon Interface (GE Series 6) . . IO:9-3-4
Table 9.3.3. Discrete Bit Map for RS3 and Allen--Bradley PLC 2 . . . . . . . . . . . . . IO:9-3-5
Table 9.3.4. Discrete Bit Map for RS3 and Allen--Bradley PLC 5 . . . . . . . . . . . . . IO:9-3-7
Table 9.3.5. Register Map for RS3 and GE Series 6 PLC . . . . . . . . . . . . . . . . . . . IO:9-3-8
Table 9.3.6. Register Map for RS3 and Modicon PLC . . . . . . . . . . . . . . . . . . . . . . IO:9-3-8
Table 9.3.7. Register Map for RS3 and MItsubishi PLC . . . . . . . . . . . . . . . . . . . . IO:9-3-9
Table 9.3.8. 16-bit Binary-to-Hexadecimal Conversion Chart . . . . . . . . . . . . . . . . IO:9-3-12
RS3t
I/O Block Configuration
Chapter 1:
Introduction to Input/Output Blocks
List of Figures
Figure Page
1.1.1 Role of I/O Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-4
1.1.2 Flow of Values through a Typical Control Loop . . . . . . . . . . . . . . . . . . . . 1-1-7
1.2.1 I/O Point Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1
1.2.2 Unconfigured I/O Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . 1-2-2
1.2.3 Example of Access Arrows on an I/O Block Configuration
Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-4
1.3.1 PeerWay Node Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-2
1.3.2 Addressing PeerWay Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-3
1.3.3 Controller Processor Card Slot Address . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-4
1.3.4 Controller Processor Card Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-5
1.3.5 Card Cage/Discrete Termination Panel Address . . . . . . . . . . . . . . . . . . . 1-3-6
1.3.6 Card Cage Card Slot/Communication Line Address . . . . . . . . . . . . . . . 1-3-7
1.3.7 Card Cage and Communication Line Addressing . . . . . . . . . . . . . . . . . . 1-3-8
1.3.8 Card Cage Card Slot Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-9
1.3.9 Analog Card Cage Card Slot Addressing . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-10
1.3.10 Contact Card Cage Card Slot Addressing . . . . . . . . . . . . . . . . . . . . . . . . 1-3-11
1.3.11 Communication Connect Card III Line Addressing . . . . . . . . . . . . . . . . . 1-3-12
1.3.12 Communication Termination Panel II Line Addressing . . . . . . . . . . . . . . 1-3-13
1.3.13 I/O Point Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-14
1.3.14 Analog Field Interface Card (FIC) I/O Point Addressing . . . . . . . . . . . . 1-3-15
1.3.15 Multipoint Analog I/O Point Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-16
1.3.16 Pulse Field Interface Card (FIC)/IO Point Addressing . . . . . . . . . . . . . . 1-3-17
1.3.17 Contact FIC I/O Point Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-18
1.3.18 Multiplexer Front End Module (FEM) I/O Point Addressing . . . . . . . . . 1-3-19
1.3.19 Isolated Discrete I/O Point Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-20
1.3.20 Direct Discrete I/O Point Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3-21
1.4.1 Block Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-2
1.4.2 Block Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-4
List of Tables
Table Page
1.1.1 Types of Input/Output Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2
1.2.1 Display Screen Access Arrows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3
1.4.1 Block Status Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-3
1.4.2 Block Status Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4-5
Section 1:
What are Input/Output Blocks?
This section describes the input and output block types, the role of input
and output blocks in a control loop, and how values are scaled in a
control loop.
Table 1.1.1 briefly describes the I/O block types that are covered in
more detail in the following chapters of this manual.
Analog Input Block (AIB) Accepts an analog field input through an analog input Field Interface Card
(FIC) and prepares the data for use by the rest of the system. Performs
analog input signal addressing, signal conditioning, trending, and
alarming.
Analog Output Block (AOB) Prepares a specific analog value for output to the field. Performs analog
output signal storage and addressing and provides for selection of direct
or reverse action.
Pulse Input/Output Block Accepts pulse field input through a pulse input/output FIC and generates
(PIOB) output pulses of specified width, frequency, or total count for output to the
field. The PIOB performs pulse input signal addressing and signal
conditioning as well as pulse output signal storage and addressing.
Temperature Input Block (TIB) Receives a temperature measurement from a resistance temperature
device (RTD) or a thermocouple. It does not require the use of a special
RTD or thermocouple transmitter.
Redundant Input/Output Tracks the health and backup status of the FICs. Performs a backup of an
Block (RIOB) FIC. Configured when redundant FICs or FIMs are being used.
Contact Input Block (CIB) Accepts a contact field input through an optical isolator and contact FIC
and prepares the data for use by the rest of the system. Performs contact
input signal addressing, signal conditioning, event recording, trending, and
alarming.
Contact Output Block (COB) Prepares a specific contact state for output to the field. Performs contact
output signal storage and addressing and provides for inverting output
relative to input.
Multiplex Input Block (MIB) Accepts an analog field input through a Front End Module (FEM) and
prepares the data for use by the rest of the system. Performs analog input
signal addressing, signal conditioning, including selection of thermocouple
or RTD type, trending, and alarming.
Smart Transmitter Input Block Receives signals from the Smart transmitter for use by other blocks.
(SIB) Allows modification of the Smart transmitter configuration parameters.
Configured when the field I/O device is a Rosemount Smart transmitter.
Value Input Block (VIB) Receives digital signals from the Smart transmitter for use by other blocks.
Allows more than one process variable to be measured. Configured when
the field I/O device is a multivariable Rosemount Smart transmitter with
more than one measured process variable.
Receives digital signals from the ControlBlock and prepares either analog
HART Output Block (HOB) or digital signals for output to Smart field devices. Shares characteristics
of both Analog Output Blocks (AOBs) and Smart Input Blocks (SIBs).
Programmable Logic Reads or writes the contents of a PLC register or reads from or writes to a
Controller Block (PLCB) PLC register.
Discrete Input Block (DIB) Accepts a discrete field input through a Discrete Termination Panel and
prepares the data for use by the rest of the system. Performs discrete
input signal addressing, signal conditioning, event recording, trending, and
alarming.
Discrete Output Block (DOB) Prepares a specific discrete state for output to the field. Performs discrete
output signal storage and addressing and provides for inverting output
relative to input.
The shaded blocks in Figure 1.1.1 show an input block and an output
block in a typical control loop.
FIELD FIELD
DEVICE DEVICE
CONTROLLER
PROCESSOR
OPERATOR ENTRY
Input/output (I/O) blocks are used to bring in signals from Field Interface
Cards (FIC), Field Interface Modules (FIM), or Front End Modules
(FEM) to the system and to send system--generated signals back to
FICs or FIMs. The input/output block stores the address of the
corresponding pair of terminals for each signal. I/O blocks can perform
filtering and other signal conditioning functions as well as alarm
checking and event message generating.
An input block and an output block are configured for each signal.
Input/output blocks can be viewed and accessed from numerous
operator console screens.
Figure 1.1.2 shows how values are transmitted through a control loop,
beginning with a 4--20 mA signal that is converted to a 0--1 value for
internal use by the RS3 control system.
Internal Scaling
The RS3 control system uses a 0--1 value to perform all I/O block and
ControlBlock functions and calculations. This 0--1 value, which is called
an internal scaling value, is for internal control system use only. This
internal scaling value can be displayed on faceplates and console
screens as a display scaling value that you define.
Display Scaling
You can define the display scaling value as desired, using the “Eng
Zero” and “Eng Max” fields on the I/O Block Configuration screen. You
can define the “Eng Units” field to describe the block values. A
definition of the I/O block scaling fields follows:
D Eng Zero Assigned value that is to be displayed when
the I/O block output is zero percent
D Eng Max Assigned value that is to be displayed when
the I/O block output is 100 percent
D Eng Units Assigned units for the block value
FIELD FIELD
DEVICE DEVICE
Section 2:
Using an I/O Block Configuration Screen
=16 A B 1 05
Card Cage
Analog Card Cages: A -- D
Contact Card Cages: A -- B
CONFIG 1
Figure 1.2.3 shows a sample screen with the various access arrows.
The lower right corner of the screen displays the user whose access key
is inserted in the console.
Fields that are lacking an arrow are for display only and cannot be
manipulated by a user. Many fields, however, allow user access only
when an I/O block is in a particular mode, such as Manual.
Þ Configuror Config
Section 3:
Input/Output Block Addressing
Addressing is the convention used to insure that data is routed from the
field to the system, from one software block to another within the
system, from the system to the field, and between the system and the
consoles.
=16
Console Addressing
Command
Console
=12
=3
=28
ControlFile
FlexTerms
MicroVAX Computer
Modem Modem
=14
or
Supervisory
Computer
Interface (SCI)
Supervisory
=6 Computer
Diogenes
Interface
Diogenes
Control
System
=10
System
Resource
Unit (SRU)
=16 A
ControlFile = 16
B
U
F A B C D E F G H
F
E C C C C C C C C C C
R O O O O O O O O O O
P P O O N N N N N N N N N
O O R R O T T T T T T T T
A W W N
D D R R R R R R R R
E E I I V O O O O O O O O
R R N N O L L L L L L L L
A A L L L L L L L L L
R R T T A E E E E E E E E
B E E O O T R R ControlFile
R R Card
R Slots
R R R
U G G R R I
F U U L P P P P P P P P
F L L P P E R R R R R R R R
E A A R R O O O O O O O O
R T T O O M C C C C C C C C
O O C C E E E E E E E E E
B R R E E M S S S S S S S S
S S O S S S S S S S S
S S R O O O O O O O O
O O Y R R R R R R R R
R R
=16A
=16B
Controller =16C
Processor Card =16D
Addresses
=16E
=16F
=16G
=16H
=16 A B
Figure 1.3.6 shows the components of a card cage card slot address.
=16 A B 1
ControlFile
=16A
Contact
Card Cage A
=16AA
Analog
Card Cage B
=16AB
Communication
Connect Card III
Line 1
Line 2 Line 8
ADDRESS /
COMM RATE
A B C D E F
Discrete
Termination
Panels HD1
=16ADxxx =16ADxxx . . . =16ADxxx
Equivalent of
Card Cage D
=16AD
Figure 1.3.8 shows the components of a card cage card slot address.
=16 A B 1
PeerWay Node Number Card Cage Card Slot
(Must begin with = sign) Analog, Pulse, or Contact (FIC):
(Leading zeros can be omitted) 1 -- 8
1--992
Each of the individual card cage card slots (1 through 8) has a unique
hardware address. Figure 1.3.9 shows the analog card cage FIC
addressing.
=16AA1
=16AA2
Analog =16AA3
Card Cage =16AA4
Card Slots
=16AA5
=16AA6
=16AA7
=16AA8
Each of the individual card cage card slots (1 through 8) has a unique
hardware address. Figure 1.3.10 shows the contact card cage FIC
addressing.
Contact =16AB4
Card Cage =16AB3
Card Slots =16AB2
=16AB1
Contact =16AB5
Card Cage =16AB6
Card Slots
=16AB7
=16AB8
Communication Lines 1 -- 8
Line 1
Line 2
Line 8
ADDRESS /
COMM RATE
A B C D E F
Discrete
Termination
Panels HD1
=16AD1xx =16AD2xx . . . =16AD8xx
Equivalent of
Card Cage D
=16AD
CP Card Slot A
=16A
Communication Termination Panel
II
Communication
Lines 1 -- 8
Line 1
Line 2
Line 8
ADDRESS /
COMM RATE
A B C D E F
Discrete
Termination
Panels HD1
=16AD1xx =16AD2xx . . . =16AD8xx
Equivalent of
Card Cage D
=16AD
The Field Interface Cards (FICs), Front End Modules (FEMs), and
discrete termination panels communicate with input/output (I/O) devices
in the field. The number of points on an FIC varies for each type of
card. Each of the I/O points residing on an FIC, FEM, or discrete
termination panel has a unique hardware address. Figure 1.3.13 shows
the components of an I/O point address.
=16 A B 1 05
Card Cage
Analog Card Cages: A -- D
Contact Card Cages: A -- B
Discrete Termination Panel: A -- D
NOTE: Analog I/O points can also include other block types with the
following addressing limitations.
D SIB (Smart Transmitter Input Blocks): 01 -- 03
D VIB (Value Input Blocks): 04 -- 32
D TIB (Temperature Input Blocks): 01 -- 02
D HOB (HART Output Blocks): 03
=16AA101
=16AA102
=16AA103
=16AA201
=16AA202
=16AA203
=16AA701
=16AA702
=16AA703
Figure 1.3.14. Analog Field Interface Card (FIC) I/O Point Addressing
=16AA101
=16AA102
=16AA103
=16AA104
=16AA105
=16AA106
=16AA107
=16AA108
=16AA109
=16AA110
=16AA111
=16AA112
=16AA113
=16AA114
=16AA115
=16AA116
Figure 1.3.16. Pulse Field Interface Card (FIC) I/O Point Addressing
A contact Field Interface Card (FIC) supports 6 points. The contact I/O
points have an address of 1 through 6. Figure 1.3.17 shows contact
FIC point addressing.
=16AB101
=16AB102
=16AB103
=16AB104
=16AB105
=16AB106
=16AB601
=16AB602
=16AB603
=16AB604
=16AB605
=16AB606
Multiplexer
input points
=16A1
=16A2
=16A3
=16A4 FlexTerm Card Cage
=16A5 =16A
=16A6
=16A7
=16A8
=16A9
=16A10
=16A11 =16A41
=16A12 =16A42
=16A13 =16A43
=16A14 =16A44
=16A15 =16A45
=16A16 =16A46
=16A17 =16A47
=16A18 =16A48
=16A19 =16A49
=16A20 =16A50
=16A51
=16A52
=16A53
=16A54
=16A55
=16A56
=16A57
=16A58
=16A59
=16A60
Figure 1.3.18. Multiplexer Front End Module (FEM) I/O Point Addressing
=16AC101
=16AC102 Inputs or outputs:
=16AC103 01 -- 16 Isolated
=16AC104 Discrete
=16AC105 Termination
=16AC106 Panel A
=16AC107
=16AC108
=16AC109
=16AC110
=16AC111
=16AC112
=16AC113
=16AC117
=16AC114
=16AC118
=16AC115
=16AC119
=16AC116
=16AC120
Inputs only:
=16AC121 Isolated
17 -- 32
=16AC122 Discrete
=16AC123 Termination
=16AC124 Panel B
=16AC125
=16AC126
=16AC127
=16AC128
=16AC129
=16AC130
=16AC131
=16AC132
=16AC101
=16AC102 Inputs or outputs:
=16AC103 01 -- 16
=16AC104
=16AC105
=16AC106 =16AC117
=16AC107 =16AC118 Inputs only:
=16AC108 =16AC119 17 -- 32
=16AC109 =16AC120
=16AC110 =16AC121
=16AC111 =16AC122
=16AC112 =16AC123
=16AC113 =16AC124 Direct
=16AC114 =16AC125 Discrete
=16AC115 =16AC126 Termination
=16AC116 =16AC127 Panel
=16AC128
=16AC129
=16AC130
=16AC131
=16AC132
Section 4:
Block Directory and Block Status Screens
This section describes the Block Directory screen and the Block Status
screen, which provide information about the configured I/O blocks and
ControlBlocks.
RS3: Introduction to Input/Output Blocks Block Directory and Block Status Screens
IO: 1-4-2
*MORE*
RS3: Introduction to Input/Output Blocks Block Directory and Block Status Screens
IO: 1-4-3
Field Description
Indicates whether the block is currently in alarm. Not all block alarms trigger an
Alarm
indication.
For ControlBlocks only, this field displays any steps that are currently in manual
Steps in Manual
mode.
Amount of static and dynamic space (bytes) used by the block and the total amount
Size
of space (bytes) the block uses. This information is displayed for a configuror only.
RS3: Introduction to Input/Output Blocks Block Directory and Block Status Screens
IO: 1-4-4
The Block Status screen displays the configured I/O blocks and
ControlBlocks that are in modes other than Auto or that are in alarm.
This screen is for display only; you cannot make entries from it.
- To call up the Block Status screens, type:
CBS [ENTER]
The Block Status screen for the first available Controller Processor is
displayed first. I/O blocks are listed first, followed by ControlBlocks.
Press [PAGE AHEAD] to view all other blocks in that Controller
Processor, and then press [PAGE AHEAD] to see the blocks for the next
Controller Processor. Press [EXCH] to call up the Block Directory
screen for the Controller Processor.
RS3: Introduction to Input/Output Blocks Block Directory and Block Status Screens
IO: 1-4-5
Field Description
Indicates whether the block is currently in alarm. Not all block alarms trigger an
Alarm
indication.
Steps in Manual For ControlBlocks only, displays any steps that are currently in manual mode.
Amount of static and dynamic space (bytes) used by the block and the total amount
Size
of space (bytes) the block uses. This information is displayed for a configuror only.
RS3: Introduction to Input/Output Blocks Block Directory and Block Status Screens
IO: 1-5-1
Section 5:
Hints for Configuring I/O Blocks
This section discusses some of the problems that you may encounter
when configuring I/O blocks and some possible ways to deal with them.
This section also provides tips that are helpful when configuring I/O
blocks.
Configuration Problems
Listed below are typical problems that occur when configuring I/O blocks
and possible ways to handle them.
- When reconfiguring an I/O block, I cannot access some of the
screen fields to reconfigure an entry.
Try changing the I/O block mode. Many fields are accessible only
when the I/O block is in a particular mode, such as Manual.
- When I try to configure some of the I/O block types, I get a
“Controller Got Bad Message” error.
Some I/O blocks require special hardware in order to configure the
I/O Block Configuration screen. Check that the proper hardware is
installed for the block that you are trying to configure.
Configuration Tips
Listed below are hints to help you when configuring I/O blocks.
- Accessing screen fields
Remember that you can only access the I/O Block Configuration
screen fields for which you have the proper access, such as
configuror, supervisor, or operator access.
- Unconfiguring an I/O block
When unconfiguring an I/O block, be sure to configure the “Block
Type” as “None”.
Chapter 2:
Configuring Analog Blocks
List of Figures
Figure Page
2.1.1 AIB Block Configuration Screen—Filter Configuration . . . . . . . . . . . . . . 2-1-2
2.1.2 AIB Block Configuration Screen—Signal Characterization
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-6
2.1.3 AIB Block Configuration Screen----Instrument Bias
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-7
2.1.4 AIB Block Configuration Screen----Alarm Configuration . . . . . . . . . . . . . 2-1-10
2.1.5 AIB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-11
2.1.6 AIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-15
2.2.1 AOB Block Configuration Screen—Reverse Action
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-3
2.2.2 Configuration Screen—Alarm Configuration . . . . . . . . . . . . . . . . . . . . . . 2-2-4
2.2.3 AOB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-5
2.2.4 AOB Block Configuration Screen—MAIO Hardware Installed . . . . . . . 2-2-6
2.2.5 AOB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2-9
List of Tables
Table Page
2.1.1 Thermocouple Configuration Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-5
2.1.2 RTD Configuration Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-5
2.1.3 Analog Input Block (AIB) Configuration Screen Fields ............ 2-1-12
2.2.1 Analog Output Block (AOB) Configuration Screen Fields . . . . . . . . . . 2-2-7
Section 1:
Configuring an Analog Input Block (AIB)
An AIB filter is used to provide a first order lag response to the AIB
input. The shaded area of Figure 2.1.1 shows the section of the AIB
Block Configuration screen used for configuring an AIB filter. The AIB
block in Figure 2.1.1 is configured with a filter time of 10 seconds.
A filter time constant is applied to the field value to smooth the effect of
any changes. The longer the filter time, the smoother the curve. You
can configure the filter time constant between 0 and 3276 seconds.
A filter time constant is normally used for indicators. If you use a filter
time constant in a control loop, configure a filter time that is less than
10% of the integral time.
- To set the filter time:
D Cursor to the “Filt Time” field and enter the desired delay time
constant in seconds. Press [ENTER].
Depending on the type of field device being used, you can configure one
of the following signal characterizations: square root, thermocouple, or
resistance temperature device.
You can select thermocouple or RTD signal characterization for use with
transmitters that are linear in millivolts or ohms.
* The ranges provided in this table are for rated accuracy. Using limits other than
these will reduce accuracy.
* The ranges provided in this table are for rated accuracy. Using limits other than
these will reduce accuracy.
The two shaded areas of Figure 2.1.2 show the sections of the AIB
Block Configuration screen for configuring AIB signal characterization.
The AIB block in Figure 2.1.2 is configured for type J thermocouple
signal characterization with the configuration temperature range in
degrees Fahrenheit.
NOTE: Before configuring thermocouple or RTD signal
characterization, be sure to calibrate the transmitter for the ohms or
millivolts corresponding to the range.
- To configure AIB signal characterization:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Sig Char” field and press [NEXT OPTION] to select
the desired signal characterization to be used. Press [ENTER].
3. An F or C appears to select the type of temperature units. Press
[NEXT OPTION] to select the desired temperature units (F for
Fahrenheit, C for Centigrade). Press [ENTER].
4. Cursor to the “Eng Max” field and enter the desired maximum
temperature value and press [ENTER]. Then cursor to the “Eng
Zero” field; enter the desired minimum temperature value; and
press [ENTER].
5. If desired, cursor to the “Eng Units” field and enter the desired
temperature units; then press [ENTER].
6. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
The shaded area of Figure 2.1.3 shows the section of the AIB Block
Configuration screen for configuring instrument bias.
- To configure AIB instrument bias:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Inst Bias” field and enter the bias value (in percent)
of the field instrument; then press [ENTER].
3. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
The shaded areas of Figure 2.1.4 show the sections of the AIB Block
Configuration screen for configuring AIB alarms. In most cases, you will
configure instrument alarms (also called hardware alarms) for AIB
blocks. You can configure critical or advisory process alarms, but we do
not recommend it. The best practice for easiest traceability is to set
process alarms on ControlBlocks, rather than on I/O blocks. This
section provides a brief description of the AIB alarms.
Access
Field Description Allowable Entries
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
NONE, AIB,CIB, DIB,
AOB,COB, DOB, ADS,
Block Type Conf Type of input/output block.
MIB, PLCB, SIB, RIOB,
VIB, PIOB, TIB
Current block mode.
If “Auto”, the block function drives the block output.
Mode Supr AUTO, MANUAL
If “Manual”, the operator can directly manipulate the
block output from the console.
Indicates whether or not the block is locked into Auto
mode.
Auto Lock Conf If “yes”, the block is locked in Auto mode. The block yes, no
cannot be changed to Manual mode.
If “no”, the block can be switched to Manual mode.
Current transmitter input value in engineering units
Field Value NA Display only
and percent.
Max = 999999
Block output value in engineering units.
Block Out Oper Min = --999999
Must be in Manual mode to enter.
Default=.00
Eng Units Conf Engineering units assigned with the block output. Maximum of 8 characters
Value to be displayed when the block output is 0%. Max = 999999.
Eng Zero Conf Must match the transmitter calibration for Min = --999999.
thermocouple and RTD signal characterization. Default=.00
Calibration field. For information about calibrating an
Calibrate Supr AIB block, see SV: 7. None, Cal Low, Cal High
Must be in Manual mode to calibrate.
Max = 999999. %
Nom Out Oper Not used at this time. Min = --999999. %
Default=None
Value to be displayed when the block output is 100%. Max = 999999.
Eng Max Conf Must match the transmitter calibration for Min = --999999.
thermocouple and RTD signal characterization. Default=100.00
(continued on next page)
Table 2.1.3. Analog Input Block (AIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Max = 999999. %
Bias signal used to modify the field value.
Inst Bias Supr Min = --999999. %
Must be in Manual mode to configure.
Default=.00
Descriptor Conf User configured descriptor. Any characters up to 24
User assigned filter time constant applied to the field Max = 3276.79 S
Filt Time Conf
value. Min = None
Table 2.1.3. Analog Input Block (AIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Hardware
Indicates an FIC hardware fault. For information on
Alarm NA Display only
alarm messages, see the Alarm Messages Manual.
Code
Assigns alarm priority to hardware alarms and critical
Priority Conf and advisory process alarms. 0 indicates highest 0--3
priority. 3 indicates lowest priority.
Indicates a user defined group to which the block is
assigned. Access to I/O blocks from a console may
Plant Unit Conf be restricted if the console has not been assigned to 0--255
the I/O block plant unit.
For more information on plant units, see CC: 1.
Max = 999999.%
Deadband value (in percent of engineering units
Al DdBand Conf Min = .00%
scale) that is applied to all block alarm points.
Default=1.00
NOTE: Bold text indicates default selection.
Figure 2.1.6 shows the Analog Input Block functional diagram. All items
within the dotted line reside in the AIB software.
Console Keyboard
None
Field Value Block Out
Cal Low
50.00 50.00
Cal High
MAN
A/D Instrument Signal Low To
Filter
Bias Character Cutoff CB
AUTO
From
Instrument Advisory Critical
FIC
Alarm Alarms Alarms
Section 2:
Configuring an Analog Output Block (AOB)
Analog Output Blocks (AOBs) prepare a specific analog value for output
to the field. The AOB performs analog output signal storage and
addressing and provides for selection of direct or reverse action.
This section provides the following information for configuring an
AOB block:
D Configuring output action
D Configuring AOB alarms
D AOB reference material
— AOB Block Configuration screen and table of screen fields
— AOB functional block diagram
AOBs can be configured for standard I/O or the new Multipoint Analog
I/O (MAIO) hardware family. For information on changes to the AOB
screen with MAIO hardware installed, see IO: 2-2-6.
Calibrate ® None
0% Value 4. ma
100% Value 20. ma
Alarm Priority Þ0 Plant Unit Þ0
Hardware Alarm Code 8 Fail Safe Jumper Hold Output Card Rev 2.1
CONFIG 1
The shaded area of Figure 2.2.2 shows the section of the AOB Block
Configuration screen used for configuring the alarm priority for hardware
alarms. If the RS3 control system generates more than one
unacknowledged hardware alarm at one time, the corresponding alarm
banner for each alarm appears at the bottom of the console screen in
the order of priority. You can configure the priority of an AOB block
hardware alarm in the “Alarm Priority” field on the AOB Block
Configuration screen.
You configure the default value for the “Alarm Priority” field on the Alarm
Configuration screen.
Calibrate ® None
0% Value 4. ma
100% Value 20. ma
Alarm Priority Þ0 Plant Unit Þ0
Hardware Alarm Code 8 Fail Safe Jumper Hold Output Card Rev 2.1
CONFIG 1
Calibrate ® None
0% Value 4. ma
100% Value 20. ma
Alarm Priority Þ0 Plant Unit Þ0
Hardware Alarm Code 8 Fail Safe Jumper Hold Output Card Rev 2.1
CONFIG 1
Calibrate ® None
Fail Safe >Hold 0% Value 4. ma
100% Value 20. ma
Alarm Priority Þ0 Plant Unit Þ0
Hardware Alarm Code 8 Output Card Rev 2.1
CONFIG 1
The Fail Safe field allows the configuration of a failure option upon loss
of communication with the Field Interface Module (FIM). The Fail Safe
field can be configured as either Hold or Zero. Hold indicates that the
last valid PV is the fail safe signal. Zero sets the the signal to 3.5 mA if
communication with the FIM is lost. See Table 2.2.1 for a description of
the new field.
Access
Field Description Allowable Entries
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
NONE, AIB,CIB, DIB,
Block AOB,COB, DOB, ADS,
Conf Type of input/output block.
Type MIB, PLCB, SIB, RIOB,
VIB, PIOB, TIB, HOB
Current block mode.
If “Auto”, the block function drives the block output.
Mode Supr If “Manual”, the operator can directly manipulate the AUTO, MANUAL
block output from the console.
If “Override”, the output bypass card drives the block
output.
Indicates whether or not the block is locked into Auto
mode.
Auto Lock Conf If “Yes”, the block is locked in Auto mode. The block yes, no
cannot be changed to Manual mode.
If “No”, the block can be switched to Manual mode.
The tag of the block from which the input originated.
Up to 16 alphanumeric
The source tag may be entered as a block tag, block
characters; at least one
Source Conf link (tag/x), or the address of the source block. After
must be an alphabetical
entering the source tag, the address of the block
character
appears below the tag.
The output feedback value.
Actual
NA NOTE: This field does not appear when Multipoint Display only
Value
Analog I/O (MAIO) hardware is installed.
Value NA The signal value at the input of the block. Display only
Max = 112.5% of
The signal value at the output of the block. engineering scale
Output
Oper Must be in Manual mode to configure the output value Min = --12.5% of
Value
in engineering units. Also displays the percent value. engineering scale
Default=.00
Eng Units Conf Engineering units of the source block. Display only
Reverse
Conf User defined block input to output relationship. yes, no
Acting
Calibration field. For information about calibrating an
AOB block, see SV: 7. None, Cal Low, Cal High,
Calibrate Supr
Calibrate
Must be in Manual mode to enter.
NOTE: Bold text indicates the default selection.
Table 2.2.1. Analog Output Block (AOB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Low calibration correction value. Max = 5.0 mA
0% Value NA
Must be in Manual mode to appear. Min = 3.0 mA
Figure 2.2.5 shows the Analog Output Block functional diagram. All
items within the dotted lines reside in the AOB software.
Console keyboard
50.00 50.00
MANUAL
From REVERSE
Inverter Correction D/A
CB AUTO
DIRECT
CAL
0% Value
4. ma A/D
Calibrate
100% Value
50.00
20. ma
Actual Value
Console Keyboard
Section 3:
Hints for Configuring Analog Blocks
This section discusses some of the problems that you may encounter
when configuring analog blocks and some possible ways to deal with
them. This section also provides tips that are helpful when configuring
analog blocks.
Configuration Problems
Listed below are typical problems that occur when configuring analog
blocks and possible ways to handle them.
- I cannot manipulate some of the block fields.
Try changing the I/O block mode. Many fields are accessible
only in Manual mode.
- I think the flowmeter readings are inaccurate.
You might want to configure a low cutoff value or an instrument
bias.
Configuration Tips
Listed below are hints to help you when configuring analog blocks.
- Configuring AIB alarms
You will probably want to configure instrument alarms and alarm
priority for each AIB.
- Evaluation of alarms when using a filter
Remember that if you are using a filter, process alarms are
evaluated in the AIB input after the input is filtered.
- Configuring the filter time
If you use a filter time constant in a control loop, you probably want
to configure a filter time that is less than 10% of the integral time.
- Configuring low cutoff
Remember that when a low cutoff is configured and the Controller
Processor setpoint is zero, integration stops.
- Using Rosemount transmitter model 444R
Remember that the Rosemount transmitter model 444R series of
TRD transmitters are linear in temperature over the range of --50° C
to 750° C and do not require characterization in an AIB.
- Using a Thermocouple or an RTD with an AIB
D For rated accuracy when using a thermocouple or an RTD with
an AIB, be sure to use the signal characterization provided in
Section 1: “Configuring Analog Input Blocks.”
D Be sure to calibrate the transmitter for the ohms or millivolts
corresponding to the range before configuring thermocouple or
RTD signal characterization.
Chapter 3:
Configuring Pulse Input/Output Blocks
List of Figures
Figure Page
3.1.1 PIOB Block Configured to Measure the Frequency of a Pulse Input . . 3-1-2
3.1.2 PIOB Block Configured to Measure the Duration of a Pulse Input . . . 3-1-3
3.1.3 PIOB Block Configured to Count Pulse Inputs . . . . . . . . . . . . . . . . . . . . 3-1-3
3.1.4 PIOB Block Configured to Output Pulse with Specified Frequency . . . 3-1-4
3.1.5 PIOB Block Configured to Output a Pulse with a Specified Duration . 3-1-5
3.1.6 PIOB Block Configured to Output a Specified Number of Pulses . . . . 3-1-5
3.1.7 PIOB Block Configured to Output a 4--20 mA Signal . . . . . . . . . . . . . . . 3-1-6
3.1.8 PIOB Block Configured to Output a 23 V Power Supply . . . . . . . . . . . . 3-1-6
3.1.9 Loader Application with Binary Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-8
3.1.10 Loader Application with Analog Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-8
3.2.1 PIOB Configuration Screen—Configuring a PIOB . . . . . . . . . . . . . . . . . 3-2-2
3.2.2 Hysteresis for Contact Pulse Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-4
3.2.3 Hysteresis for Voltage Pulse Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-5
3.2.4 Configuring a Contact Pulse Input PIOB . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-6
3.2.5 Configuring a Voltage Pulse Input PIOB . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-7
3.2.6 Configuring a PIOB to Measure the Frequency of a Pulse Input . . . . . 3-2-9
3.2.7 Configuring Contact Pulse Input PIOB to Measure Pulse Frequency . 3-2-10
3.2.8 Configuring PIOB to Measure Duration of Pulse Input . . . . . . . . . . . . . 3-2-11
3.2.9 Configuring Voltage Pulse Input PIOB to Measure Pulse Duration . . . 3-2-11
3.2.10 Duration Input States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-12
3.2.11 Configuring a PIOB to Count Pulse Inputs—Target Count
Supplied by a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-13
3.2.12 Effect of Target Count on PIOB Output—Target Count from
ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-14
3.2.13 Configuring Voltage Input PIOB to Count Pulses—Target Count
from ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-15
3.2.14 Configuring PIOB to Count Pulse Inputs—Target Count from
Configuror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-17
3.2.15 Effect of Target Count on PIOB Output—Target Count from Configuror 3-2-17
3.2.16 Sample of a Voltage Input PIOB to Count Pulses—Target Count
Provided by Configuror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-18
3.2.17 Configuring a Pulse Output PIOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-20
3.2.18 Configuring a PIOB to Output a Pulse with a Specified Frequency . . . 3-2-22
3.2.19 Configuring a Pulse Output PIOB with a Specified Frequency . . . . . . . 3-2-22
List of Tables
Table Page
3.2.1 Common Fields for the PIOB I/O Block Configuration Screen . . . . . . . 3-2-3
3.2.2 Contact Pulse Input PIOB Common Fields . . . . . . . . . . . . . . . . . . . . . . . 3-2-6
3.2.3 Voltage Pulse Input PIOB Common Fields . . . . . . . . . . . . . . . . . . . . . . . 3-2-8
3.2.4 Pulse Input PIOB Fields to Measure Pulse Frequency . . . . . . . . . . . . . 3-2-10
3.2.5 Pulse Input PIOB Fields to Measure Pulse Duration . . . . . . . . . . . . . . . 3-2-12
3.2.6 Pulse Input PIOB Fields to Count Pulses--Target Count Provided
by ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-15
3.2.7 Pulse Input PIOB Fields to Count Pulses--Target Count Provided
by Configuror . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-19
3.2.8 Pulse Output PIOB Common Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-21
3.2.9 Pulse Output Fields to Output a Pulse at a Specified Frequency . . . . 3-2-23
3.2.10 Pulse Output Fields for Pulse Duration . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-25
3.2.11 Pulse Output Fields for a Pulse Count . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-27
3.2.12 Analog Output PIOB Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-31
3.2.13 PIOB Fields for a Loader Application with a Binary Output . . . . . . . . . . 3-2-35
3.2.14 PIOB Fields for a Loader Application with an Analog Output . . . . . . . . 3-2-39
Section 1:
Applications for the Pulse Input/Output Block
You can use the Pulse Input/Output Block (PIOB) for a variety of
applications. You can configure the PIOB block as a pulse input, pulse
output, or analog output, depending on the desired application. To
perform a particular application, configure selections in the “Point Type,”
“Type,” “Function Type,” and “Output Type” fields on the PIOB Block
Configuration screen for the PIOB block.
This section describes and illustrates the PIOB block applications and
the corresponding field selections for each application:
D Pulse input PIOB applications
D Pulse output PIOB applications
D Analog output PIOB applications
D Combinations of input PIOB blocks and output PIOB blocks for
loader applications
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-2
You can configure a pulse input PIOB block to perform the following
applications:
D Measure the frequency of a pulse input (Figure 3.1.1); for more
information, see “Configuring a PIOB to Measure the Frequency
of a Pulse Input” in Section 2 on page IO:3-2-9.
D Measure the duration of a pulse input (Figure 3.1.2); for more
information, see “Configuring a PIOB to Measure the Duration of
a Pulse Input” in Section 2 on page IO:3-2-11.
D Count the total number of pulse inputs (Figure 3.1.3); for more
information, see “Configuring a PIOB to Count Pulse Inputs” in
Section 2 on page IO:3-2-13.
Figure 3.1.1. PIOB Block Configured to Measure the Frequency of a Pulse Input
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-3
Figure 3.1.2. PIOB Block Configured to Measure the Duration of a Pulse Input
Manual Entry
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-4
You can configure a pulse output PIOB block to perform the following
applications:
D Output a pulse with a specified frequency (Figure 3.1.4); for more
information, see “Configuring a PIOB to Output a Pulse with a
Specified Frequency” in Section 2 on page IO:3-2-22.
D Output a pulse with a specified duration (Figure 3.1.5); for more
information, see “Configuring a PIOB to Output a Pulse with a
Specified Duration” in Section 2 on page IO:3-2-24.
D Output a specified number of pulses (Figure 3.1.6); for more
information, see “Configuring a PIOB to Output a Specified
Number of Pulses” in Section 2 on page IO:3-2-26.
Figure 3.1.4. PIOB Block Configured to Output Pulse with Specified Frequency
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-5
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-6
PIOB BLOCK
=xxxx03 23 V Power
Supply at 60 mA
Field
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-7
You can configure an input PIOB with an output PIOB for a loader
application that provides a quick output response when a counter input
reaches a target value. The input PIOB acts as a loader counter to
count the pulse inputs. A ControlBlock is linked to the loader counter to
provide the target count. The output PIOB acts as a loader output that
is controlled by the loader counter. The loader can be a binary output
PIOB as shown in Figure 3.1.9 or an analog output PIOB as shown in
Figure 3.1.10.
A binary output loader outputs a 1.0 value while the loader counter is
counting, and a 0.0 value when the counter reaches the target value.
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-1-8
Begins
ControlBlock PIOB BLOCK counting PIOB BLOCK
Target Loader Loader 1.0 value
Field
Count Counter
=xxxx02
=xxxx01
0.0 value
Reaches Field
Target
ControlBlock
RS3: Configuring Pulse Input/Output Blocks Applications for the Pulse Input/Output Block
IO: 3-2-1
Section 2:
Configuring a Pulse Input/Output Block (PIOB)
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-2
You configure a PIOB on the I/O Block Configuration screen. The fields
that appear on the I/O Block Configuration screen depend on the entries
that you configure in some of these fields. Figure 3.2.1 shows the I/O
Block Configuration screen fields that are common to all PIOB
applications. Table 3.2.1 describes these fields.
The “Point Type” field determines the basic function of the PIOB—pulse
input, pulse output, or analog output.
D Pulse input PIOBs can be configured in addresses =xxxx01 and
=xxxx02.
D Pulse output PIOBs can be configured in addresses =xxxx01 and
=xxxx02.
D Analog output PIOBs can be configured in address =xxxx03.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-3
Table 3.2.1. Common Fields for the PIOB I/O Block Configuration Screen
Access
Field Description Allowable Entries
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag Conf User defined block tag. characters, one of which
must be alphabetic
NONE, AIB, CIB, AOB,
COB, ADS, MIB, PLCB,
Block Type Conf Type of input/output block.
SIB, RIOB, VIB, PIOB,
TIB, DIB, DOB, HOB
Current block mode.
If “Auto,” the block function drives the block output.
Mode Supr AUTO, MANUAL
If “Manual,” the operator can directly manipulate
the block output from the console.
Type of PIOB:
Pulse Input = pulse input Pulse Input, Pulse
Point Type Conf
Pulse Output = pulse output Output, mA Output
mA Output = analog output
Output value of the block in engineering units. Max=999999
Block Output Oper
Must be in Manual mode to configure. Min=--999999
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-4
On (>8 mA)
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-5
Hysteresis exists for varying pulse input signals and uses 20% of the
nominal range with ±10% about the threshold. Signals above the
hysteresis area are considered to be a 20 mA signal. Signals below the
hysteresis area are considered to be a 0 mA signal. Within the
hysteresis area, signal variation has no effect on the signal.
Figure 3.2.3 shows the hysteresis areas for unipolar and bipolar signals.
Unipolar
Signals
100%
60%
50% Threshold
40%
0%
+5 0%
+1 0%
0% Threshold
--10%
--50%
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-6
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-7
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-8
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-9
NOTE: Configure the Range Max to include the highest possible real
input frequency in order to prevent the generation of hardware alarms
and the loss of input values.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-10
Figure 3.2.7. Configuring Contact Pulse Input PIOB to Measure Pulse Frequency
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-11
Output state when the measured Block output is the last measured
duration is greater than 1 second length of the duration
Figure 3.2.9. Configuring Voltage Pulse Input PIOB to Measure Pulse Duration
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-12
Table 3.2.5 describes the fields for configuring a PIOB to measure the
duration of a pulse input. Figure 3.2.10 shows an example of the
duration input states for contact and voltage signals.
Threshold
Fall--to--rise
Fall--to--fall
Voltage Rise--to--rise
Signals Rise--to--fall
Threshold
Fall--to--rise
Fall--to--fall
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-13
You can configure a PIOB to count pulse inputs. When the count
reaches a target value, the count resets to zero. The target value can
be supplied by a ControlBlock or by the configuror.
Figure 3.2.11. Configuring a PIOB to Count Pulse Inputs—Target Count Supplied by a ControlBlock
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-14
Figure 3.2.12 shows an example of the effect of the source link value
and flags on the PIOB output.
ControlBlock
Target count 3
Target count 1
Target count 2
Source Link
0 Value
1
0 user flag m
1
0 user flag n
0 PIOB
Output
1
0 user flag k
For the ControlBlock, configured logic conditions in the ControlBlock set the source link
value as the target count and flag m rises.
For the PIOB counter, assuming a constant input frequency through this example, the
PIOB output begins counting and counts to the target count. When the target count is
reached, the PIOB output resets to 0 and flag k toggles to 1. In the ControlBlock, source
link flags m and n return to 0 due to configured logic conditions.
The PIOB continually checks for a new target value from the source link. The example
shows the interaction of a PIOB with a source link during three different target--count
values.
Figure 3.2.12. Effect of Target Count on PIOB Output—Target Count from ControlBlock
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-15
Actual value of the ControlBlock output Block output is the current value in the counter
Figure 3.2.13. Configuring Voltage Input PIOB to Count Pulses—Target Count from ControlBlock
Table 3.2.6. Pulse Input PIOB Fields to Count Pulses--Target Count Provided by ControlBlock
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-16
For processing, you can internally slow down an input frequency that is
greater than 500 Hz by prescaling the input frequency. You can also
slow down an input frequency to extend the range of the counter.
Use the “Prescale” field to configure the prescale value. If the prescale
value is n, the counter is incremented by 1 for each n input pulses. To
prevent hardware alarms from being generated or counts from being
lost, properly configure the “Prescale” field.
- To configure the prescale value:
1. Use the following formula to determine the prescale value:
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-17
Target
count
0 PIOB
Output
1
0 user flag k
For processing, you can internally slow down an input frequency that is
greater than 500 Hz by prescaling the input frequency. You can also
slow down an input frequency to extend the range of the counter.
Use the “Prescale” field to configure the prescale value. If the prescale
value is n, the counter is incremented by 1 for each n input pulses. To
prevent hardware alarms from being generated or counts from being
lost, properly configure the “Prescale” field.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-18
Actual value of the ControlBlock output Block output is the current value in the counter
Figure 3.2.16. Sample of a Voltage Input PIOB to Count Pulses—Target Count Provided by Configuror
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-19
Table 3.2.7. Pulse Input PIOB Fields to Count Pulses--Target Count Provided by Configuror
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-20
Function Type Þ
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-21
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-22
Determines the frequency at which the pulse is to be generated Current frequency value
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-23
* If both =xxxx01 and =xxxx02 are configured, the maximum frequency output of each point is 750 Hz.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-24
The duty cycle is equal to the period of the output waveform. The
Minimum ON Time sets the pulse width as a percentage of the duty
cycle that is output when the source value is 0. The Maximum ON Time
sets the pulse width as a percentage of the duty cycle that is output
when the source value is 1. As the Source Value changes from 0 to 1,
the duty cycle varies linearly from the Minimum ON Time to the
Maximum ON Time.
ControlBlock PIOB
Continuous
Duty cycle =xxxx01 Fixed frequency
Q
or Field
0--1 value =xxxx02 Variable ON time
Discrete
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-25
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-26
1 sec
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-27
Figure 3.2.25. Configuring Pulse Output PIOB with Specified Number of Pulses
* If both =xxxx01 and =xxxx02 are configured, the maximum frequency output of each point is 750 Hz.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-28
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-29
ControlBlock PIOB
4--20 mA
=xxxx03 signal
0--1 value
Field
PIOB
23 V Power Supply
=xxxx03 up to 60 mA
Field
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-30
Figure 3.2.28 shows the I/O Block Configuration screen for an analog
output. Table 3.2.12 describes the fields on the screen.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-31
Allowable
Field Description
Entries
Analog, Supply,
Output Type Selects the type of output to be provided by the block.
Loader
Displays the block output value or state, depending on the output type
configured.
Block Output For Analog output types, displays the block output value. Display only
For Supply output types, displays the block output state. The block
output state is always on.
Current (mA) Displays the output current for Analog output types only. Display only
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-32
You can configure an input PIOB with an output PIOB for a loader
application that provides a quick output response when a counter input
reaches a target value. The input PIOB acts as a loader counter to
count the pulse inputs. A ControlBlock is linked to the loader counter to
provide the target count. The output PIOB acts as a loader output that
is controlled by the loader counter. The loader can be a binary output
PIOB or an analog output PIOB.
A binary output loader outputs a 1.0 value while the loader counter is
counting and a 0.0 value when the counter reaches the target value.
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-33
When logic step m rises, the ControlBlock Point Type ÞPulse Output
outputs a new target value, and flag k is set Function Type ÞLoader
to 0.
When logic step n rises, the loader counter When the loader counter reaches the
PIOB count is set to 0, and flag k of the target value, flag k is set to 1.
loader counter PIOB is set to 0.
Figure 3.2.29. Configuring PIOBs for a Loader Application with a Binary Output
Point 1
100%
On
0% Point 2 output
Off
Figure 3.2.30. Interaction of PIOBs for a Loader Application with a Binary Output
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-34
Figure 3.2.31. Configuring a Pulse Output PIOB for a Loader Application with a Binary
Output—Loader
Figure 3.2.32. Configuring a Pulse Input PIOB for a Loader Application with a Binary Output—Loader
Counter
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-35
Table 3.2.13 describes the fields used to configure a pulse input PIOB
to act as a loader counter.
Table 3.2.13. PIOB Fields for a Loader Application with a Binary Output
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-36
Loader
Source Link
ControlBlock
Continuous
Q
Discrete
Figure 3.2.33. Configuring an Analog Output PIOB for a Loader Application with an Analog Output
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-37
Point 1
100%
Target count=Actual
count
Valve shuts
0% Point 3 output
User flag n
User flag m
User flag k
Figure 3.2.34. Interaction of PIOBs for a Loader Application with an Analog Output
1
0 user flag m
1
0
0 PIOB Output
1
0 user flag k
Point 2 ON
OFF user flag k
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-38
Figure 3.2.36. Configuring a Pulse Input PIOB for a Loader Application with an Analog
Output—Loader Counter
Figure 3.2.37. Configuring an Analog Output PIOB for a Loader Application with an Analog
Output—Loader
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-2-39
Table 3.2.14. PIOB Fields for a Loader Application with an Analog Output
RS3: Configuring Pulse Input/Output Blocks Configuring a Pulse Input/Output Block (PIOB)
IO: 3-3-1
Section 3:
Hints for Configuring PIOBs
This section discusses some of the problems that you may encounter
when configuring PIOBs and some possible ways to deal with them.
This section also provides tips that are helpful when configuring PIOBs.
Configuration Problems
Listed below are typical problems that occur when configuring PIOBs
and possible ways to handle them.
- I am trying to enter a value in the “Prescale” field but the value that
I need is not an option.
If the exact prescale value is not listed, select the next greater value.
Configuration Tips
Chapter 4:
Configuring Temperature Input Blocks
List of Figures
Figure Page
4.1.1 Configuring an RTD Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2
4.1.2 Configuring a Thermocouple Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4
4.2.1 TIB Configuration Screen—Configuring a TIB . . . . . . . . . . . . . . . . . . . . 4-2-3
4.2.2 TIB Configuration Screen—Configuring an RTD Sensor TIB . . . . . . . . 4-2-8
4.2.3 TIB Configuration Screen—Configuring a Thermocouple
Sensor TIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-11
4.2.4 TIB Configuration Screen—Configuring a CJC Sensor TIB . . . . . . . . . 4-2-12
4.2.5 Display Scaling of Continuous Faceplates . . . . . . . . . . . . . . . . . . . . . . . . 4-2-14
4.2.6 Scaling a TIB with the Default Eng Zero and Eng Max Values . . . . . . . 4-2-15
4.2.7 Scaling a TIB with Eng Zero and Eng Max Values Other than
the Default Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-16
4.2.8 TIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-17
List of Tables
Table Page
4.2.1 Common Fields for the TIB Configuration Screen . . . . . . . . . . . . . . . . . 4-2-4
4.2.2 Centigrade Temperature Ranges for RTD inputs . . . . . . . . . . . . . . . . . . 4-2-7
4.2.3 Centigrade Temperature Ranges for Thermocouple Inputs . . . . . . . . . 4-2-7
4.2.4 Centigrade Temperature Ranges for CJC Inputs . . . . . . . . . . . . . . . . . . 4-2-7
4.2.5 Ranges for Millivolt and Ohm Scale Inputs . . . . . . . . . . . . . . . . . . . . . . . 4-2-7
4.2.6 Common Fields for an RTD Sensor TIB . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-9
4.2.7 Common Fields for a Thermocouple Sensor TIB . . . . . . . . . . . . . . . . . . 4-2-11
Section 1:
Applications for the Temperature Input Block
RS3: Configuring Temperature Input Blocks Applications for the Temperature Input Block
IO: 4-1-2
Sensor TypeÞRTD
Ext. ResÞ0--327
RS3: Configuring Temperature Input Blocks Applications for the Temperature Input Block
IO: 4-1-3
RS3: Configuring Temperature Input Blocks Applications for the Temperature Input Block
IO: 4-1-4
Sensor
TypeÞCJC
Measures the Temp (in mV)
and scales the value for the
thermocouple sensor
Thermocouple
Measures the temp
(in °C)
RS3: Configuring Temperature Input Blocks Applications for the Temperature Input Block
IO: 4-2-1
Section 2:
Configuring a Temperature Input Block (TIB)
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-2
You use the I/O Block Configuration screen to configure a TIB. The
“Sensor Type” field determines the function of the TIB-RTD application,
thermocouple application, or cold junction compensator RTD
application. Some of the fields that appear on the I/O Block
Configuration screen depend on the type of sensor being configured.
Figure 4.2.1 shows the I/O Block Configuration screen fields that are
common to all TIB applications. Table 4.2.1 describes these fields. The
fields that appear only for particular applications are described later.
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-3
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-4
Access
Field Description Allowable Entries
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag Conf User defined block tag. characters; at least one
must be alphabetic.
NONE, AIB, CIB, AOB,
COB, ADS, MIB, PLCB,
Block Type Conf Type of input/output block.
SIB, RIOB, VIB, PIOB,
TIB, DIB, DOB, HOB
Current block mode.
If “Auto,” the block function drives the block
Mode Supr output. AUTO, MANUAL
If “Manual,” the operator can directly manipulate
the block output from the console.
Indicates whether or not the block is locked into
Auto mode.
If “Yes,” the block is locked in Auto mode. The
Auto Lock Conf yes, no
block cannot be changed to Manual mode.
If “No,” the block can be switched to Manual
mode.
Current input value and the corresponding
Temperature scale.
The upper value is the linearized input value. If a
temperature scale other than centigrade is
Field Value NA Display only
configured, this value has been converted from
centigrade to the configured temperature scale.
The lower value is the actual value of the current
field input (in millivolts or ohms).
Block output value in engineering units or percent
of span, depending on the display scaling. For
Max.=999999
more information, refer to page 4-2-13, “Scaling
(Eng Max)
Block Out Oper an RTD Sensor TIB or a Thermocouple Sensor
TIB” later in this section. Min.=--999999
(Eng Zero)
Must be in Manual mode to enter a value for test
purposes.
User selectable signal characterization curve.
Depending on the type of sensor selected,
additional fields may appear. All thermocouples RTD, J, K, T, E, R, S, B,
Sensor Type Conf
use NBS standards. --E, --T, CJC, OHM, MV
Must be in Manual mode to configure.
NOTE: Bold text indicates default selections.
(continued on next page)
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-5
Table 4.2.1. Common Fields for the TIB Configuration Screen (continued)
Access
Field Level Description Allowable Entries
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-6
Table 4.2.1. Common Fields for the TIB Configuration Screen (continued)
Access
Field Level Description Allowable Entries
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-7
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-8
Figure 4.2.2 shows a TIB Configuration screen for an RTD sensor TIB.
Table 4.2.6 describes the fields that are common to RTD sensor TIBs.
(Refer to Table 4.2.1 for a description of the fields common to all TIBs.)
Use the “Ext. Res” field to configure external resistance. The external
resistance can be any value from 0.00 to 600.00 Ohms.
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-9
Access
Field Description Allowable Entries
Level
C (Celsius),
Selects the Temperature units for the RTD sensor. F (Fahrenheit),
Temp Conf
Must be in Manual mode to configure. K (Kelvin),
R (Rankine)
Selects the value of the external resistance for the
RTD sensor, allowing Range 1 to be biased to any
temperature range up to 850 °C, 100 Ohm span .00--600.00
Ext. Res Conf
only. Default = .00
Must be in Manual mode to configure.
Used for lead resistance calibration
Offset Cal Oper This field appears when the block is in Manual No, Yes
mode.
Used for lead resistance calibration.
Off. Value Oper Display Only
This field appears when the block is in Auto mode.
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-10
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-11
Access
Field Description Allowable Entries
Level
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-12
You can link a CJC sensor TIB to more than one thermocouple sensor;
however, until you configure the CJC link to a thermocouple application,
an “Input Configuration Error” is generated. If, after you configure the
link, a hold forward flag is asserted, the last known good value for the
CJC is sent to the FIC. To ensure that the hold forward flag is asserted,
you should configure the Inst High and Inst Low fields.
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-13
The “Sensor Type” and “Range” fields determine the temperature inputs
for the TIB. The default display scaling is an Eng Zero value of .00 and
an Eng Max value of 1.00. This default value (.00--1.00) differs from
other I/O blocks, which default to a range of .00 to 100.00%. This
difference allows scale values for batch input.
You can configure a display scaling other than .00 to 1.00 to view
fluctuations in the temperature range that otherwise may not appear on
the faceplate. To alter the display scaling to display slight temperature
variations, configure the “Eng Zero” and “Eng Max” fields to reflect the
desired scale.
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-14
85--
-- 551--
50--
.5-- 140.5--
-- 15--
}
0-- --240-- --20
55.47 Normal temperature
55.47 range in which 55.47
OUT OUT viewing is
OUT
desired—
GPM --20 to 120
GPM GPM
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-15
If you use the default display scaling (Eng Zero of 0.0, Eng Max of 1.0),
the field value input to the TIB is not altered in any way for the block
output. Figure 4.2.6 shows a TIB that is configured as an RTD using
temperature range 2, --245 to 850 degrees Celsius (Table 4.2.2). The
TIB uses the default display scaling of Eng Zero of .00 and an Eng Max
of 1.0. Figure 4.2.6 shows that the block output value is the same as
the block input value. All configured alarms use the engineering value
over the full range of the sensor.
Figure 4.2.6. Scaling a TIB with the Default Eng Zero and Eng Max Values
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-16
If you configure a display scaling other than the default display scaling
for the TIB, the block output is a percentage of span of the Eng Zero
and Eng Max. This percentage of span has an upper limit of +15% of
the span and a lower limit of --15% of the span. The TIB output value
must be between the limits. If the TIB output value exceeds one of
these limits, the output value is limited to a value ±15% of the Eng Zero
and Eng Max range.
Figure 4.2.6 also shows that when you configure a display scaling other
than the default scaling, the instrument high and instrument low alarms
are entered as a percentage of scale.
TIB input value is 600.00 degrees. However, the upper limit of the displayed
scaling limit is 141.0. The block output cannot exceed this limit.
Figure 4.2.7. Scaling a TIB with Eng Zero and Eng Max Values Other than the Default Values
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-17
FIC Software
None
Field
Cal Low Value
50.00
Cal High Voltage/ °C
A/D Resistance to
TEMP
Filter Conversion
TC/ Software
RTD
3 Lead
Compensation
Range 1
Console Keyboard
TIB CJC
Software Link
Block Out
Ext Res 50.00
Value
MAN
To
AUTO CB
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-18
TIB Summary
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-19
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-2-20
RS3: Configuring Temperature Input Blocks Configuring a Temperature Input Block (TIB)
IO: 4-3-1
Section 3:
Hints for Configuring TIBs
This section provides tips that are helpful when configuring TIBs.
Configuration Tips
Chapter 5:
Configuring Redundant Input/Output Blocks
List of Figures
Figure Page
5.1.1 Configuring an RIOB for an Analog Card Cage . . . . . . . . . . . . . . . . . . . 5-1-3
5.1.2 Configuring an RIOB for a FIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-4
5.1.3 RIOB Configuration Screen—Backing Up FICs . . . . . . . . . . . . . . . . . . . 5-1-6
5.1.4 RIOB Configuration Screen—Determining FIC Backup Status . . . . . . 5-1-8
5.1.5 RIOB Configuration Screen for a Second Redundant FIC . . . . . . . . . . 5-1-8
5.1.6 RIOB Configuration Screen—Determining FIM Backup Status . . . . . . 5-1-9
5.2.1 Redundant I/O Block (RIOB) Configuration Screen . . . . . . . . . . . . . . . . 5-2-1
List of Tables
Table Page
5.2.1 Redundant I/O Block (RIOB) Configuration Screen Fields ......... 5-2-2
Section 1:
Configuring a Redundant Input/Output Block
Configuration Guidelines
D You must consider the RIOB as the first block on the first
redundant card slot:
NOTE: The Discrete Termination Panel does not have 7/1 and 3/1
capabilities. It only has 1:1 redundancy capabilities.
— with 7/1 redundancy, the RIOB is at address =xxx801
— with 3/1 redundancy, the RIOB is at address =xxx401 or
xxx801
— with 1/1 redundancy, the RIOB is at address =xxx201,
xxx401, xxx601, or xxx801
D The 1/1 redundancy scheme is available only when using a
Multipurpose Controller Processor running the MPCA or MPC+
software image.
D No additional blocks can be configured on the FIC or FIM if an
RIOB has been configured.
D The RIOB must be in Auto mode for redundancy to be in effect.
D The FICs in the card cage and the Discrete Termination Panel
and Isolated Termination Panels must have the redundancy
scheme jumpers set for the proper redundancy scheme. For
information about redundancy scheme jumper positions, see
SV: 5.
D If the primary FIM fails and you replace it, as soon as the new
FIM powers up it will assume cooperative redundancy along with
the FIM that is currently running.
Figure 5.1.3 shows that the FICs in slots A1 and A2 are to be backed up
by the redundant FIC in slot A4.
- To change from Backup Mode to Nonbackup Mode:
1. Cursor to the “Backup” field and press [NEXT OPTION] to select
No; then press [ENTER]. The “Backup Status” field displays the
following message:
FREE
Figure 5.1.3 shows that the FIC in slot A3 is not being backed up by a
redundant FIC.
The “Backup Status” field on the RIOB Configuration screen displays the backup
status of the FIM. The status types that may occur are described below and are
shown in Figure 5.1.6.
BACKUP The FIM has failed and the backup FIM is now functioning for the FIM.
Figure 5.1.6 shows that the FIM in slot A1 is backed up by the FIM in
slot A2. If the FIM in slot A fails, the green LEDs on the FIM card in slot
A1 flash while the card is being backed up.
READY The FIM is functional and the FIM is backed up by a redundant FIM. If
the FIM were ready to receive signals, the backup status would show
ready.
FREE The FIM is functional and is not being backed up by a redundant FIM.
The “Backup Status” field shows free if the “Backup” field is set to no.
R-x The FIM is functional as the redundant backup FIM. The x refers to the
slot number of the redundant card. Figure 5.1.6 shows that the FIM in
slot A2 is the redundant card for the FIM in slot A1.
CO--OP Redundancy is enabled and both FIMs are healthy and running. The
FIMs are running cooperatively, with both cards reading inputs and
driving outputs together. Figure 5.1.6 shows that both FIMs are running.
Section 2:
RIOB Block Configuration Screen
Access
Field Description Allowable Entries
Level
NONE, AIB, CIB,
AOB, COB, ADS,
MIB, PLCB, SIB,
Block Type Conf Type of input/output block.
RIOB, VIB, PIOB,
TIB, DIB, DOB,
HOB
Determines the operating mode of FICs or FIMs.
NOTE: Auto is the normal operating mode of the block.
In the case of a failure, Auto mode allows the redundant
Mode Supr card to back up the failed FIC or FIM. Auto, Manual
In the case of a failure, Manual mode does not allow
FIC or FIM redundancy. Manual mode allows the user
to select “Reset Backup” or “Force Backup on Number.”
Indicates whether or not the block is locked into Auto
mode.
Auto Lock Conf If “Yes”, the block is locked in Auto mode. The block no, yes
cannot be changed to Manual mode.
If “No”, the block can be switched to Manual mode.
none, 1/1, 3/1, 7/1
Type of redundancy scheme to be used.
Redundancy The
NOTE:
Conf NOTE: The 1/1 option is functional only when using a
Scheme Discrete Termination
Multipurpose Controller Processor running the MPCA or
Panel allows only
MPC+ software image.
1/1 redundancy.
Displays the FIC or FIM slot positions in order from left
to right.
Cage Line NA To call up an RIOB Configuration screen for an FIC or Display only
FIM in a particular slot, cursor to the desired slot
number in the “Cage Line” field and press [SELECT].
Backup (for Determines whether or not this RIOB provides
Cage Line A1 Conf redundancy for the FIC or FIM designated in the “Cage YES, NO
through A7) Line” field.
Identifies the health of the FIC or FIM.
Health NA GOOD = Functional. Display only
BAD = Not functional.
Identifies the health of the Transfer card.
GOOD = Functional.
BAD = Not functional.
Xfer Health NA Display only
NOTE: This field applies only to the Analog, TC/RTD,
and Pulse RIOB screens. It does not appear on the
Discrete Termination Panel RIOB screen.
NOTE: Bold text indicates the default condition.
(continued on next page)
Table 5.2.1. Redundant I/O Block (RIOB) Configuration Screen Fields (continued)
Access
Field Level Description Allowable Entries
Table 5.2.1. Redundant I/O Block (RIOB) Configuration Screen Fields (continued)
Access
Field Level Description Allowable Entries
Section 3:
Hints for Configuring RIOBs
This section discusses some of the problems that you may encounter
when configuring RIOBs and some possible ways to deal with them.
This section also provides tips that are helpful when configuring RIOBs.
Configuration Problems
Listed below are typical problems that occur when configuring RIOBs
and possible ways to handle them.
- I can not force a backup or reset a backup on a specified FIC or
FIM.
The RIOB must be in Manual mode in order to force a backup on an
FIC or FIM. Be sure that the “Mode” field is in Manual.
Configuration Tips
Chapter 6:
Configuring Contact Blocks
List of Figures
Figure Page
6.1.1 CIB Configuration Screen—Filter Configuration . . . . . . . . . . . . . . . . . . . 6-1-2
6.1.2 CIB Configuration Screen—Field Contact Configuration . . . . . . . . . . . . 6-1-4
6.1.3 CIB Configuration Screen—Message Pair Configuration . . . . . . . . . . . 6-1-5
6.1.4 CIB Configuration Screen—Descriptor Configuration . . . . . . . . . . . . . . 6-1-6
6.1.5 CIB Configuration Screen—Fail Safe Configuration . . . . . . . . . . . . . . . . 6-1-7
6.1.6 CIB Configuration Screen—Event Configuration . . . . . . . . . . . . . . . . . . 6-1-8
6.1.7 CIB Configuration Screen—Alarm Configuration . . . . . . . . . . . . . . . . . . 6-1-9
6.1.8 CIB Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-10
6.1.9 Delay Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-14
6.1.10 Delay--on Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-15
6.1.11 Delay--off Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-16
6.1.12 Glitch Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-17
6.1.13 Settle Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-19
6.1.14 Extend Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-21
6.1.15 CIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-23
6.2.1 COB Configuration Screen—Contact Type Configuration . . . . . . . . . . . 6-2-2
6.2.2 COB Configuration Screen—Output Hold Configuration . . . . . . . . . . . . 6-2-3
6.2.3 Output Hold Off (Delay On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-4
6.2.4 Output Hold On (Delay Off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-5
6.2.5 Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-6
6.2.6 COB Configuration Screen—Message Pair Configuration . . . . . . . . . . 6-2-7
6.2.7 COB Configuration Screen—Alarm Configuration . . . . . . . . . . . . . . . . . 6-2-8
6.2.8 COB Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-9
6.2.9 COB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-12
List of Tables
Table Page
6.1.1 Contact Input Block (CIB) Filter Options . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-3
6.1.2 Contact Input Block (CIB) Configuration Screen Fields . . . . . . . . . . . . 6-1-11
6.1.3 Delay Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-14
6.1.4 Delay--on Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-15
6.1.5 Delay--off Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-16
6.1.6 Glitch Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-18
6.1.7 Settle Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-20
6.1.8 Extend Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-22
6.2.1 Output Hold Off (Delay On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-4
6.2.2 Output Hold On (Delay Off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-5
6.2.3 Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-6
6.2.4 Contact Output Block (COB) Configuration Screen Fields . . . . . . . . . . 6-2-10
Section 1:
Configuring a Contact Input Block (CIB)
You can use a CIB filter to eliminate contact bounce by filtering the CIB
Raw State when it is received in order to determine the Output State.
The shaded area of Figure 6.1.1 shows the section of the CIB
Configuration screen used for configuring a CIB filter. To configure a
filter, the block must be in Manual mode.
Table 6.1.1 lists and briefly describes the CIB filter options available.
The effect on the Output State by the FIC is explained in detail in “CIB
Filter Options” later in this section.
- To select a filter type:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual, then press [ENTER].
2. Cursor to the “Filt Type” field and press [NEXT OPTION] to select
the desired filter type. Press [ENTER].
3. For options other than “None”, cursor to the “Filt Time” field to
assign the desired filter time. Enter the time in seconds using a
minimum of 0.00 seconds and a maximum of 1023.75 seconds.
Press [ENTER].
4. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
You can configure a CIB to allow inversion of the field contact position.
The shaded area of Figure 6.1.2 shows the section of the CIB
Configuration screen used for configuring the CIB field contact position.
To configure the field contact, status of the the block must be in Manual
mode.
Configuring a Descriptor
You can configure a descriptor for a CIB. The descriptor appears on the
Alarm Message and Alarm Lists. The shaded area of Figure 6.1.4
shows the section of the CIB Configuration screen that is used for
assigning descriptors to a CIB.
The “Fail Safe” field allows you to configure the type of failure option for
loss of communication with the FIC.
D “No” indicates that the FIC holds the last valid Output State if
communication is lost. “No” is the default selection.
D “Yes” indicates that you can set the block output to on or off if
communication with the FIC fails. When “yes” is selected, the
“Safe State” field appears below the “Fail Safe” field. The “Safe
State” field allows you to select whether the Output State is to be
on or off in the case of a communication failure.
The shaded area of Figure 6.1.5 shows the section of the CIB
Configuration screen that is used for setting the CIB fail safe.
Configuring an Event
The shaded areas of Figure 6.1.7 show the sections of the CIB Configuration
screen used for configuring CIB alarms. An alarm may be generated
depending on the on or off state of the Output State. If no alarm is desired,
select “None”. “None” is the default alarm condition. Figure 6.1.7 shows a
sample CIB that generates a critical alarm when the Output State is off.
- To configure a CIB input alarm:
If you have configured a CIB alarm, we recommend that you also configure
alarm priority. Configure alarm priority using a numeral from 0 to 3. An entry
of 0 indicates the highest alarm priority; 3 the lowest.
If the RS3 generates more than one unacknowledged critical or advisory
process alarm or hardware alarm at one time, the corresponding alarm
banner for each alarm appears at the bottom of the console screen in the
order of priority. Configure priority of a CIB critical or advisory process alarm
or hardware alarm in the “Priority” field on the CIB Configuration screen.
Configure the default value for the “Alarm Priority” field on the Alarm
Configuration screen.
I/O BLOCK CONFIGURATION 25-Jan-92 10:42:34
Address =10AB203 Device Type CIB or COB
Block Tag Þ Block Type ÞCIB Mode ®AUTO
Auto Lock Þno
Filtered State OFF Output State> OFF
Raw State OFF
Field Contact ÞNO
Message Pair Þ*1 Filt Type ÞNone
true ON Fail Safe Þno
false OFF
Descriptor Þ
EVENTS ALARMS
Rising Edge ®no Event Type ®0 Alarm Cond ®OFF
Falling Edge ®no Alarm Type ®Crit
Hardware Alarm Code 9 Priority Þ0 Plant UnitÞ0 Contact I/O Card Rev 0.0
CONFIG 1
Access
Field Description Allowable Entries
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
NONE,
AIB,CIB,AOB,COB,
Block Type Conf Type of input/output block. DIB, DOB, ADS, MIB,
PLCB, SIB, RIOB,
VIB, PIOB, TIB
Current block mode.
If “Auto”, the block function drives the block
Mode Supr output. AUTO, MANUAL
If “Manual”, the operator can directly manipulate
the block output from the console.
Indicates whether or not the block is locked into
Auto mode.
If “Yes”, the block is locked in Auto mode. The
Auto Lock Conf yes, no
block cannot be changed to Manual mode.
If “No”, the block can be switched to Manual
mode.
The signal value of the block after block
Filtered State NA Display only
conditioning.
The signal value at the output of the block. Toggle, Clear (OFF),
Output State Oper
Must be in Manual mode to manipulate. Set (ON)
Raw State NA Displays the raw (unfiltered) input state. Display only
User defined block input to output relationship.
Field Contact Conf NO, NC
Must be in Manual mode to configure.
Message Pair Conf Assigns a message pair to the output state field. *1--*100, 1--155
Table 6.1.2. Contact Input Block (CIB) Configuration Screen Fields (continued)
Access
Field Level Description Allowable Entries
Use one of the filter options available in the CIB to manipulate the Raw
State. The effect on the Output State relative to the Raw State supplied
by the FIC is explained in this section along with a brief description and
timing diagram for each of the following filter types:
D None filter option
D Delay filter option
D Delay On filter option
D Delay Off filter option
D Glitch filter option
D Settle filter option
D Extend filter option
Using a delay filter on a CIB block delays the CIB by the interval
assigned in the “Filt Time” field. The delay has an effect on the CIB
block when the Raw State changes to on (0 to 1) and changes to off (1
to 0) (0 = off, 1= on). If the “Raw State” changes but does not maintain
that state for greater than or equal to the “Filt Time”, the Output State
does not change.
Figure 6.1.9 shows the effect of a delay filter used on a CIB block.
Table 6.1.3 describes the “Raw State” effect on the Output State at
different times
T0 T1 T2 T3 T4 T5 T6
1
Raw
State
0
Output 1
State
0
Filt Time duration
duration
duration > < duration
TIME Filt Time Filt Time >
<
Filt Time
Filt Time
T0 Initial condition. Off condition from the field Initial condition. Output State off.
(Raw State).
T4 Raw State changes to on condition. Output State remains on because the duration
of the Raw State off condition was less than
the Filt Time.
T5 Raw State changes to off condition. Output State remains on because there has
been no uninterrupted off Raw State condition
greater than or equal to the Filt Time.
T6 Raw State remains off. Output State changes to off when the Raw
State off exceeds the Filt Time.
NOTE: The Output State is equal to the Filtered State when the block is in Auto mode.
The D--on filter delays the CIB output by the interval assigned in the “Filt
Time” field. The delay has an effect only when the Raw State changes
to on (0 to 1). The Output State responds immediately when the Raw
State changes to off (1 to 0).
Figure 6.1.10 shows the effect of a D--on filter used on a CIB block.
Table 6.1.4 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5
1
Raw
State
0
1
Output
State
0
duration
= Filt Time duration
TIME < Filt Time
T0 Initial condition. Off condition from the field Initial condition. Output State off.
(Raw State).
T3 Raw State changes to off. Output State changes to off. Output State
always changes immediately to off in response
to Raw State changing to off.
T4 Raw State changes to on. Output State remains off and begins delay
interval.
T5 Raw State changes to off. Output State remains off. Delay is canceled
when the Raw State is changed to off.
NOTE: The Output State is equal to the Filtered State when the block is in Auto mode.
Using a delay off filter delays the CIB Output State by the interval
assigned in the “Filt Time” field. The delay has an effect only when the
Raw State is changing to off (1 to 0). The Output State responds
immediately when the input changes to on (0 to 1).
Figure 6.1.11 shows the effect of a delay off filter used on a CIB block.
Table 6.1.5 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5 T6
1
Raw
State
0
1
Output
State
0
duration duration
TIME
= Filt Time < Filt Time
T1 Raw State changes to on. Output State changes to on. Output State always changes
immediately to on in response to the Raw State changing to on.
T2 Raw State changes to off. Output State remains on and begins delay interval.
T3 Raw State remains off. Output State changes to off in response to the Raw State
changing to off at T2 plus the interval assigned in the “Filt Time”
field of CIB.
T4 Raw State changes to on. Output State changes to on. Output State always changes
immediately to on in response to the Raw State changing to on.
T5 Raw State changes to off. Output State remains on and begins delay interval.
T6 Raw State changes to on. Output State remains on. Delay is canceled when the Raw State
is changed to on.
* The Output State is equal to the Filtered State when the block is in Auto mode.
A glitch filter holds the CIB Output State each time that the Output State
changes for a minimum time as specified in the “Filt Time” field. If the
Raw State changes state during the hold time, the Output State
responds to that change after the hold expires and again holds for the
time defined by “Filt Time”. In the event of multiple Raw State changes
during the hold time, the Output State responds to the first and last Raw
State changes only.
Figure 6.1.12 shows the effect of a glitch filter used on a CIB block.
Table 6.1.6 describes the Raw State effect on the Output State at
different times.
T2 T4 T6 T10 T11
T0 T1 T3 T5 T7 T8 T9 T12 T13
1
Raw
State
0
1
Output
State
0
TIME duration
= Filt Time
T1 Raw State rises to on. Output State changes to on. Duration defined
by Filt Time begins.
T3 Raw State remains off. Output State changes to off in response to Raw
State falling to off at T2.
T4 Raw State rises to on. Output State remains off in response to T2 for
the duration of the Filt Time.
T8 Raw State remains on. Output State changes to off in response to the
Raw State falling to off at T6.
T10 Raw State falls to off. Output State remains on in response to T7 for
the duration of the Filt Time.
T11 Raw State rises to on. Output State remains on in response to T7 for
the duration of the Filt Time.
T12 Raw State remains on. Output State changes to off in response to the
Raw State falling to off at T10.
T13 Raw State remains on. Output State changes to on in response to the
Raw State rising to on at T11.
* The Output State is equal to the Filtered State when the block is in Auto mode.
A settle filter holds the CIB output in the changed state until the same Raw State is
maintained for a minimum time equal to “Filt Time”. At that time a change in the Raw
State causes an immediate change in the Output State. Figure 6.1.13 shows the
effect of a settle filter used on a CIB block. Table 6.1.7 shows the “Raw State” effect
on the Output State at various times.
T0 T1 T2 T3 T4 T5 T6 T7 T8
1
Raw
State
0
1
Output
State
0
1
Raw
State
0
1
Output
State
0
duration
> Filt Time
duration
TIME < Filt Time
T2 Raw State changes to off. Output State changes to off immediately because
the interval between T1 and T2 was equal to Filt
Time.
T3 Raw State changes to on. Output State remains off because the interval
between T2 and T3 was less than the Filt Time.
T6 Raw State changes to off. Output State remains on because the interval
between T5 and T6 was less than the Filt Time.
T8 Raw State changes to off. Output State changes to off immediately because
the interval between T7 and T8 was greater than the
Filt Time.
T10 Raw State changes to off. Output State remains on because the Output State
was not equal to the Raw State for the filter time.
The Output State will remain different from the Raw
State forever until the Raw State changes.
* The Output State is equal to the Filtered State when the block is in Auto mode.
An extend filter holds the CIB Output State for the time assigned in the
“Filt Time” field. Subsequent Raw State changes that occur within the
output hold time are ignored, with the exception of the most recent Raw
State at the end of the hold to which the Output State responds.
Figure 6.1.14 shows the effect of an extend filter used on a CIB block.
Table 6.1.8 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5 T6
1
Raw
State
0
1
Output
State
0
duration duration=
TIME = Filt Time Filt Time
* The Output State is equal to the Filtered State when the block is in Auto mode.
Figure 6.1.15 shows the Contact Input Block functional diagram. All
items within the dotted line reside in the CIB software.
Console Keyboard
Output
Raw State Filtered State State
Off Off
Off
MAN
NC To
FIC Inverter Debounce
Filter CB
NO AUTO
Events Alarms
Section 2:
Configuring a Contact Output Block (COB)
You can configure a COB to allow inversion of the field contact position.
The shaded area of Figure 6.2.1 shows the section of the COB
Configuration screen that is used for configuring the COB field contact
position. To configure the field contact, the status of the block must be
in Manual mode.
You can delay the COB output state for a designated hold time
depending on the output hold configuration. The block output state can
be held on (Off), held off (On), set to pulse (Pulse), or not held at all
(none). “None” is the default selection. If you choose On, Off, or Pulse
options, a “Hold Time” field appears. In the “Hold Time” field, configure
the number of seconds, from 0 to 511, that the output state is to hold in
this field. To configure output hold, the block must be in Manual mode.
The shaded area of Figure 6.2.2 shows the section of the COB
Configuration screen used for configuring output hold for a COB. The
block in Figure 6.2.2 has an on output hold configured for 5 seconds.
- To set the output hold:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual, then press [ENTER].
2. Cursor to the “Output Hold” field and press [NEXT OPTION] to
select the desired hold condition. Press [ENTER]. If an output
hold is selected, the “Hold Time” field appears.
3. Cursor to the “Hold Time” field and enter the number of seconds
for which the output state is to be held. Press [ENTER].
4. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto, then press [ENTER].
Figure 6.2.3 shows the effect of configuring the “Output Hold” field to
stay on. Table 6.2.1 describes the field input effect on the block output
at different times.
T0 T1 T2 T3 T4 T5 T6
1
Block Input
0
1
Block Output
0
Figure 6.2.4. shows the effect of configuring the “Output Hold” field to
stay off. Table 6.2.2 describes the field input effect on the block output
at different times.
T0 T1 T2 T3
1
Block Input
0
1
Block Output
0
TIME
Hold
Time
Figure 6.2.5 shows the effect of configuring the “Output Hold” field for
the pulse option. Table 6.2.3 describes the field input effect on the
block output at different times.
T0 T1 T2 T3 T4 T5 T6
1
Block Input
0
1
Block Output
0
The shaded area of Figure 6.2.7 shows the section of the COB
Configuration screen used for configuring the alarm priority for COB
hardware alarms. If the RS3 generates more than one
unacknowledged hardware alarm at one time, the corresponding alarm
banner for each alarm appears at the bottom of the console screen in
the order of priority. Configure the priority of a COB hardware alarm in
the “Alarm Priority” field on the COB Configuration screen.
Access
Field Description Allowable Entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
NONE,
AIB,CIB,AOB,COB,
Block Type Conf Type of input/output block. DIB, DOB, ADS, MIB,
PLCB, SIB, RIOB, VIB,
PIOB, TIB
Input State NA The field signal value at the input of the block. Display only
The signal value at the output of the block. Toggle, Clear (OFF),
Output State Oper
Must be in Manual mode to configure. Set (ON)
Message Pair Conf Assigns a message pair to the output state field. *1--*100, 1--155
Table 6.2.4. Contact Output Block (COB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Figure 6.2.9 shows the COB functional block diagram. All items within
the dotted line reside in the COB software.
Console Keyboard
Off Off
MAN
Section 3:
Hints for Configuring Contact Blocks
This section discusses some of the problems that you may encounter
when configuring contact blocks and some possible ways to deal with
them. This section also provides tips that are helpful when configuring
contact blocks.
Configuration Problems
Listed below are typical problems that occur when configuring contact
blocks and possible ways to handle them.
- I cannot access some of the contact Block Configuration
screen fields.
In order to configure many screen fields, the block must be in
Manual mode. Be sure that the block is in Manual mode.
Configuration Tips
Listed below are hints to help you when configuring contact blocks.
- Configuring a contact block alarm
D Remember that if you configure a contact block alarm, you
should also configure the alarm priority.
D Be sure that the failure option jumpers on the FIC correspond
with the selection in the “Output Hold” field.
Chapter 7:
Configuring Multiplex Input Blocks
List of Figures
Figure Page
7.1.1 MIB Block Configuration Screen—Signal Characterization . . . . . . . . . . 7-1-2
7.1.2 MIB Block Configuration Screen—Filter Configuration . . . . . . . . . . . . . 7-1-6
7.1.3 MIB Block Configuration Screen—Skip Function . . . . . . . . . . . . . . . . . . 7-1-7
7.1.4 MIB Block Configuration Screen—Scaling Configuration . . . . . . . . . . . 7-1-9
7.1.5 MIB Block Configuration Screen—Alarm Configuration . . . . . . . . . . . . . 7-1-13
7.1.6 MIB Block Configuration Screen—Block Output Configuration . . . . . . 7-1-14
7.2.1 MIB Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-2
7.2.2 MIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-7
List of Tables
Table Page
7.1.1 MIB Ranges for Thermocouple Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-3
7.1.2 MIB Ranges for RTD Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-4
7.1.3 MIB Ranges for Miscellaneous Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-5
7.2.1 Multiplex Input Block (MIB) Configuration Screen Fields . . . . . . . . . . . 7-2-3
Section 1:
Configuring a Multiplex Input Block (MIB)
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-2
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-3
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-4
Table 7.1.2 provides the RTD types and the corresponding temperature
ranges and resolution for each type of device.
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-5
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-6
Use an MIB filter to provide a first order response to the MIB input. A
filter provides a delay between the time when the input is received and
the time when the output is sent.
The shaded area of Figure 7.1.2 shows the section of the MIB Block
Configuration screen that is used for configuring an MIB filter. The MIB
block in Figure 7.1.2 is configured for a filter time of 15 seconds.
A filter time constant is applied to the field value to delay and smooth
the effect of any changes. The longer the filter time, the smoother the
curve. Configure the filter time constant as desired.
- To set the filter time:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Filt Time” field and enter the desired time constant
in seconds. Press [ENTER].
3. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
NOTE: When configuring the filter time, remember that the update rate
of each point can be up to 7 seconds for a 100 point Multiplexer.
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-7
The shaded area of Figure 7.1.3 shows the section of the MIB Block
Configuration screen used for configuring the MIB skip function.
- To set the skip function:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Skip” field and select “yes” or “no.” Press
[ENTER].
3. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-8
Scaling an MIB
You can configure the display scaling of the block input for display on a
continuous faceplate. You can also scale the temperature range for the
MIB input signal. The block must be in Manual mode to change either
type of scaling.
Use the “Zero” and “Max” fields to configure the display scaling.
Use the “Input Scale” fields to scale the MIB block input as desired to
correspond with the display scaling. These fields must be defined
within the ranges corresponding to the input device type. The top input
scale number corresponds to the desired engineering zero. The bottom
input scale number corresponds to the engineering units maximum
value.
CAUTION
Be careful if you change the input scaling since this could
result in inaccurate values. The “Zero” and “Max”
engineering units should be the same as the Input scale
values for all “Sig Char” types except
“4--20 mA” and “4-- 20 sqrt”; otherwise, the “Block Out” will
not be the same as the “Field Value.” The 4-- 20 mA, unlike
temperature, has no determined value; therefore, you use
the MIB to show the real engineering unit range of the
transmitter.
The shaded areas of Figure 7.1.4 show the sections of the MIB Block
Configuration screen that are used to configure scaling.
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-9
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-10
You will usually want to configure instrument alarms for MIB blocks.
Depending on how you are using the MIB, you may also want to
configure critical or advisory process alarms.
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-11
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-12
Rate of change alarms inform the operator that the block output is
changing at a particular rate.
D Critical rate of change alarms represent conditions that require
immediate action.
D Advisory rate of change alarms represent conditions that may
require attention in the future.
Deviation Alarms
Deviation alarms inform the operator of a block output that is lower than
the nominal output minus the deviation value or higher than the
deviation value plus the nominal output.
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-13
- To configure alarms:
1. Cursor to the “Home” position or to any field, and press [EXCH].
2. Cursor to a field in the alarm section, and enter the desired
value. Press [ENTER].
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-1-14
The MIB “Block Output” field shows the current block output in
engineering units. Modify the value by putting the block in Manual
mode and entering a value in the “Block Output” field. The block must
be in Manual mode to change the block output manually.
D If an MIB block is out of range, the following block input and block
output is displayed:
99999
D If no device is connected to an MIB block, the following block
output is displayed:
77777
The shaded area of Figure 7.1.6 shows the section of the MIB Block
Configuration screen that is used for changing the block output.
- To change the block output:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual, then press [ENTER].
2. Cursor to the “Block Out” field and enter the desired block output.
Press [ENTER].
3. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto, then press [ENTER].
RS3: Configuring Multiplex Input Blocks Configuring a Multiplex Input Block (MIB)
IO: 7-2-1
Section 2:
MIB Reference Material
Access
Field Description Allowable Entries
Level
Up to 16
alphanumeric
Block Tag Conf User defined block tag. characters; at least
one must be
alphabetic.
Field Value NA Current transmitter input value in engineering units. Display only
Max = 112.5% of
eng. scale
Block output value in engineering units.
Block Out Oper Min.= --12.5% of
Must be in Manual mode to configure.
eng. scale
Default=.00
Table 7.2.1. Multiplex Input Block (MIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
User--assigned filter time constant applied to the field Max = 3276 sec.
Filt Time Conf
value. Min = None
Max = 112.5%
Nom Out Oper Value used in conjunction with deviation alarms. Min = --12.5 %
Default=None
Table 7.2.1. Multiplex Input Block (MIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Max = 999999.
Deadband value (in engineering units) applied to all block
Al DdBand Conf Min = .00
alarms.
Default=1.00
Hardware
Alarm Indicates an FIC hardware fault. For information about
NA Display only
alarm messages, see the Alarm Messages Manual.
Code
Max = 999999.%
High hardware alarm point (in percent) applied to the field
Inst High Supr Min = --999999.%
value.
Default=None
Max = 999999.%
Low hardware alarm point (in percent) applied to the field
Inst Low Supr Min = --999999.%
value.
Default=None
Max = 999999.
High critical process alarm point (in engineering units)
Crit High Conf Min = --999999.
applied to the block output value.
Default=None
Max = 999999.
Low critical process alarm point (in engineering units)
Crit Low Conf Min = --999999.
applied to the block output value.
Default=None
Max = 999999.
Crit Critical rate of change process alarm point (in
Conf Min = --999999.
Rate--Chg engineering units) applied to the block output value.
Default=None
Max = 999999.
Critical process alarm point (in engineering units) based Min = --999999.
Crit Dev Conf
on difference between block output value and Nom Out. (Nom Out ¹ None)
Default=None
Max = 999999.
High advisory process alarm point (in engineering units)
Adv High Conf Min = --999999.
applied to the block output value.
Default=None
Max = 999999.
Low advisory process alarm point (in engineering units)
Adv Low Conf Min = --999999.
applied to the block output value.
Default=None
Table 7.2.1. Multiplex Input Block (MIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Max = 999999.
Adv Advisory rate of change process alarm point (in
Conf Min = --999999.
Rate--Chg engineering units) applied to the block output value.
Default=None
Max = 999999.
Advisory process alarm point (in engineering units) based
Min = --999999.
Adv Dev Conf on difference between the block output value and Nom
Out. (Nom Out ¹ None)
Default=None
Figure 7.2.2 shows the MIB functional block diagram. All items within
the dotted line reside in the MIB software.
Console Keyboard
None
Field Value Block Out
Cal High
50.00 50.00
Send Const
Man
To
Signal Filter Scaling
Char CB
Auto
FEM
Section 3:
Hints for Configuring MIBs
This section discusses some of the problems that you may encounter
when configuring MIBs and some possible ways to deal with them. This
section also provides tips that are helpful when configuring MIBs.
Configuration Problems
Listed below are typical problems that occur when configuring MIBs and
possible ways to handle them.
- I can not access some of the MIB Block Configuration screen
fields.
D In order to configure many screen fields, the block must be in
Manual mode. Be sure that the block is in Manual mode.
D If you are trying to access the “Descriptor” field or one of the
alarm fields, press [EXCH].
- The MIB block input and block output are displayed as 99999.
This indicates that the MIB block is out of range.
- The MIB block output is displayed as 77777.
This indicates that there is no device connected to the MIB block.
- There is no field for selecting the temperature units when you
are using a thermocouple or RTD device with an MIB.
The temperature field is displayed when you select the desired
signal characterization, if that signal characterization is a
thermocouple or RTD device.
- The MIB input value seems inaccurate
Be sure that the “Input Scale” field is properly configured.
Configuration Tips
Chapter 8:
Configuring Smart Blocks
List of Figures
Figure Page
8.1.1 Smart Transmitter Input Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-2
8.1.2 Value Input Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-2
8.1.3 Accessing the SIB I/O Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-3
8.1.4 Smart Transmitter Input Block and Value Input Block in
Auto Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-4
8.1.5 Smart Transmitter Input Block and Value Input Block in
Simulate Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-5
8.1.6 Smart Transmitter Input Block and Value Input Block in
Manual Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-6
8.1.7 SIB Configuration Screen—Filter Configuration . . . . . . . . . . . . . . . . . . . 8-1-7
8.1.8 SIB Configuration Screen—PV Type Configuration . . . . . . . . . . . . . . . . 8-1-10
8.1.9 SIB Configuration Screen—Alarm Configuration . . . . . . . . . . . . . . . . . . 8-1-12
8.1.10 SIB Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-13
8.1.11 VIB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-17
8.1.12 VIB Block Configuration Screen—Linking a VIB Block to
an SIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-20
8.1.13 SIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-21
8.1.14 VIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-22
8.1.15 Transmitter Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-23
8.1.16 Configuration Screen Entry for Transmitter Configuration
Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-29
8.1.17 Transmitter Configuration I/O Screen—Performing
Transmitter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-31
8.1.18 Transmitter Configuration I/O Screen—Performing
Transmitter Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-32
8.1.19 Transmitter Configuration I/O Screen—Assigning a
Descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-33
8.1.20 Transmitter Configuration I/O Screen—Range Configuration . . . . . . . . 8-1-34
8.1.21 Transmitter Configuration I/O Screen—Assigning Units . . . . . . . . . . . . 8-1-35
8.1.22 Transmitter Configuration I/O Screen—Damping
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-40
8.1.23 Transmitter Configuration I/O Screen—Output Configuration . . . . . . . 8-1-41
8.1.24 Transmitter Configuration I/O Screen—Block Limit
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-42
8.1.25 Transmitter Configuration I/O Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-43
8.1.26 Log Files Directory Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-47
List of Tables
Table Page
8.1.1 SIB I/O Block Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . 8-1-14
8.1.2 VIB I/O Block Configuration Screen Fields ...................... 8-1-18
8.1.3 Transmitter Status Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-24
8.1.4 Controller Communication Error Messages Generated
by the Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-26
8.1.5 FIC Communication Error Messages Generated by the FIC . . . . . . . . 8-1-26
8.1.6 Transmitter Communication Error Generated by the
Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-27
8.1.7 Transmitter Status Error Messages Generated by the
Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-27
8.1.8 Transmitter Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-30
8.1.9 “Units” Field Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-36
8.1.10 Alphabetic List of “Units” Field Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-38
8.1.11 Transmitter Configuration Screen Fields . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-44
8.1.12 Transmitter Maintenance Log Screen Fields . . . . . . . . . . . . . . . . . . . . . . 8-1-49
8.2.1 HART Output Block (HOB) Configuration Screen Fields . . . . . . . . . . . 8-2-10
8.2.2 HART Output Device Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-15
8.2.3 Output Device Status Message Descriptions . . . . . . . . . . . . . . . . . . . . . 8-2-16
8.2.4 FIC Communication Error Messages Generated by the FIC . . . . . . . . 8-2-17
8.2.5 HART Output Device Configuration Screen Fields . . . . . . . . . . . . . . . . . 8-2-20
8.2.6 Slot Variables for Fisher Transducer Output Device . . . . . . . . . . . . . . . 8-2-28
8.2.7 Slot Variables for Fisher valve, no pressure sensor . . . . . . . . . . . . . . . . 8-2-28
8.2.8 Slot Variables for Fisher valve with pressure sensor . . . . . . . . . . . . . . . 8-2-28
Section 1:
Configuring SIBs and VIBs
You can use both Smart transmitter Input Blocks (SIBs) and Value Input
Blocks (VIBs) RS3 communication with Smart transmitters.
Use a Value Input Block (VIB) with an SIB for multi--variable transmitters
that have more than one process variable. Configure an SIB to
measure the primary output and configure a VIB block for each
additional variable that needs to be measured to calculate the primary
output of the SIB. You can configure up to three VIBs for one SIB,
which allows up to four variables to be read from one transmitter.
Figure 8.1.2 shows how a VIB block receives input from an SIB and
sends its output to a ControlBlock.
Value Input
Block (VIB)
More
Transmitter
Configuration
Screen
Transmitter Transmitter
Status Configuration
Screen Screen
KEY
[EXCHANGE] key
NOTE: Serial I/O limits: The maximum number of SIBs and VIBs that
can be configured per FIC is 3 SIBs and 13 VIBs. The limit of SIBs per
MPCI or MPCII controller is 32. Ideally, 2 SIBs per FIC is suggested.
NOTE: Multipoint I/O (MAIO) limits: 16 SIBs and 16 VIBs per FIM.
SIB and VIB blocks can be in one of three modes: Auto, Simulate, or
Manual.
Auto Mode
Auto mode is the normal operating mode of the SIB and VIB blocks. In
Auto mode, the transmitter provides input to the SIB. The SIB provides
the transmitter input to a VIB block, if necessary. Both the SIB and VIB
outputs are sent to a ControlBlock. Figure 8.1.4 shows the SIB and VIB
blocks in Auto mode.
Value Input
Block (VIB)
Output
Figure 8.1.4. Smart Transmitter Input Block and Value Input Block in Auto Mode
Simulate Mode
An SIB in Simulate mode uses the input from another block instead of
the transmitter. The SIB provides output to a ControlBlock. With a VIB
block in Simulate mode, the VIB block uses the input from another block
instead of the SIB. The VIB provides output to a ControlBlock.
Figure 8.1.5 shows the SIB and VIB blocks in Simulate mode.
Smart
Transmitter
SIB in
Simulate mode Smart ControlBlock
Simulate
Block Transmitter
Input Block Output
Input (SIB)
Figure 8.1.5. Smart Transmitter Input Block and Value Input Block in Simulate Mode
Manual Mode
In Manual mode, the transmitter provides the input to the SIB or VIB
block, but the SIB or VIB block output is held constant. The operator
can issue commands through the SIB to change the configuration of the
Smart transmitter. In addition, other SIB or VIB fields can be modified.
Figure 8.1.6 shows the SIB and VIB blocks in Manual mode.
SIB or
Transmitter Transmitter Operator
Change Smart Change
SIB in Smart Transmitter
Manual mode Transmitter Input Block
(SIB) Output ControlBlock
Smart Smart
Transmitter Transmitter
Input Block
VIB Block in (SIB)
Manual mode
VIB Operator
Value Input Change
Block (VIB)
Output ControlBlock
Figure 8.1.6. Smart Transmitter Input Block and Value Input Block in Manual Modes
Use an SIB filter to provide a delay between the time when the input is
received and the time when the output is sent. The shaded area of
Figure 8.1.7 shows the section of the SIB Configuration screen that is
used for configuring an SIB filter. The SIB in Figure 8.1.7 is configured
for a filter time of 15 seconds.
- To set the filter time:
1. Cursor to the “Filt Time” field and enter the desired time constant
in seconds. Press [ENTER].
You can use the SIB PV value in analog or digital, depending on your
needs.
Select the PV option on the SIB Configuration screen. The shaded area
of Figure 8.1.8 shows the section of the SIB Configuration screen used
for configuring the PV type and the values that are displayed.
Using Analog PV
The analog PV displays the 4 to 20 mA signal coming into the FIC. The
analog PV is sampled 16 times each second.
Using Digital PV
Using Combined PV
If you need to use both the analog and digital values, you can use the
analog value in the SIB and the digital value by configuring a VIB. If you
configure a VIB block to display a PV value, the VIB block must be
scaled the same as the corresponding SIB.
- To set the PV type:
1. Cursor to the “Use” field and press [NEXT OPTION] to select the
desired type of PV, then press [ENTER].
SIB Value
Analog PV Digital PV
The shaded area of Figure 8.1.9 shows the section of the SIB
Configuration screen used for configuring SIB alarms. Instrument
alarms are usually configured for SIBs.
You can configure the default value for the “Alarm Priority” field on the
Alarm Configuration screen.
You can configure a low cutoff value that is the block output value below
which the block output is set to zero. Values below the assigned cutoff
value do not generate instrument alarms. The SIB must be in Manual
mode to configure a low cutoff. Figure 8.1.9 shows the Low Cutoff field.
Access
Field Description Allowable Entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
Up to 8 alphanumeric
Eng Units Conf Engineering units displayed for the block.
characters
Xmtr Units NA Engineering units configured for the transmitter. Display only
Max = 999999
Zero Conf Value displayed when the block output is 0Þ.
Min = --999999
Access
Field Description Allowable Entries
Level
Tag of the block used for the input when the I/O Any existing block tag.
Sim Tag Conf
block is in Simulate mode. Address is display only.
Access
Field Description Allowable Entries
Level
Max = 999999
Low hardware (sensor failure) alarm point (in Min = --999999
Inst Low Conf
engineering units) applied to field value.
Default=None
Max = 999999
High hardware (sensor failure) alarm point (in Min = --999999
Inst High Conf
engineering units) applied to field value.
Default=None
Max = 999999
Deadband value (in engineering units) applied Min = --999999
Deadband Conf
to all block alarm points.
Default=1.00
Use the Value Input Block (VIB) with an SIB for multi--variable
transmitters that have more than one measured output. Up to three
VIBs can be configured for one SIB.
The VIB I/O Block Configuration screen, once configured, displays the
SIB tag and address of the corresponding SIB and the SIB input. When
configuring a VIB block, the block must be linked to an SIB residing on
the same FIC. Figure 8.1.11 shows the VIB block configuration screen.
Table 8.1.2 provides a description of the VIB block configuration screen
fields.
Access
Field Description Allowable Entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
Up to 8 alphanumeric
Eng Units Conf Engineering units displayed for the block.
characters
Max = 999999
Zero Conf Value displayed when the block output is 0%. Min = --999999
Default=.00
Max = 999999
Value displayed when the block output is Min = --999999
Max Conf
100%.
Default=100.00
Access
Field Description Allowable Entries
Level
Up to four VIB blocks can serve as inputs from an SIB. The SIB input
number identifies which SIB input is being linked to a particular VIB
block.
The shaded area of Figure 8.1.12 shows the section of the VIB Block
Configuration screen used for linking a VIB block to an SIB. The
example in Figure 8.1.12 shows the VIB block at =129AB204 is linked to
an SIB at =129AB203.
- To link a VIB block to an SIB:
1. Cursor to the “SIB/HOB Tag” field and enter the tag or address of
the SIB to which the VIB block is to be linked.
2. Cursor to the “SIB/HOB Input” field and enter the number of the
SIB input to which the VIB block is to be linked, then press
[ENTER].
Figure 8.1.13 shows the SIB functional block diagram. All items within
the dotted line reside in the SIB software.
None
Field Value Block Out
Cal Low
50.00 50.00
Cal High
MAN
Use Analog or
From Combined
FIC Filter To
A/D CB
Use Digital AUTO
SIM
From
FIC Filter
Xmtr Simulate
Comm Use Analog or Tag
Combined Instrument
Alarm
Use Digital
Figure 8.1.14 shows the VIB functional block diagram. All items within
the dotted line reside in the VIB software.
Eng Simulate
Units Tag
XXXXXXXXXXXXXXXXXXXXX
Command ®Done Stat 39.0 000 Num 15.0 000
CONFIG 1
Field Description
Shows the identification code for the manufacturer of the transmitter being used. The
Mfr ID manufacturer identification code is entered automatically by the RS3.
See Table 8.1.8.
Date Date as entered by the user (transmitter date) in the format dd/mm/yy.
Units The units of the Range, “Analog Val” and “Digital Val” fields.
Damping value for the transmitter. Damping is used to increase the response time of
Damping
the transmitter to smooth the output when there are rapid input variations.
Analog Val Current analog input value in engineering units and mA.
Xmtr Status Bit mapped representation code of the transmitter status messages. See Table 8.1.7.
Field Description
Digital Val Current digital input value in engineering units and mA.
Indicates the type of command in progress: Upload Xmtr Config, Send Config to
Xmtr, Xmtr Self Test, Save Xmtr Config, End Fixed Current, (Trim Xmtr DAC, 4mA)
Command (Trim Xmtr DAC, 20mA) Set Output Current, Re--Zero Xmtr, Set Xmtr Address.
Must be in Manual mode to configure a transmitter configuration command.
Configurable by a supervisor or configuror.
Failed command and transmitter response code status. Only the first failure or
response code in a group of commands is retained.
There are two types of definitions for command--specific response codes: those with
the word warning in them and those without.
D The error definitions with WARNING indicate that the command was accepted
Stat and successfully executed, but some condition existed within the device that
affected the result. The response data bytes are returned with the data as
modified by the device.
D Error definitions that do not begin with warning indicate that an error was
found while attempting to execute the command and the execution of the
command could not be completed. The response data bytes are not returned
when errors are being reported.
Num Indicates status of the current command being sent to the transmitter.
Table 8.1.4 lists the Controller Processor error messages that might
appear on the Transmitter Status screen or the SIB Configuration
screen when using the transmitter commands.
Table 8.1.4. Controller Communication Error Messages Generated by the
Controller
Message Description
Table 8.1.5 lists the FIC error messages that might appear on the
Transmitter Status screen or the SIB Configuration screen when you are
using the transmitter commands. It shows error messages that may
occur in communication between the FIC and transmitter.
Table 8.1.5. FIC Communication Error Messages Generated by the FIC
Code Description
FIC Comm Err 1000 0001 The transmitter modem signal was lost.
FIC Comm Err 1000 0010 Buffer overrun error. Too many characters were received.
Smart transmitter parity byte error. The calculated checksum did not
FIC Comm Err 1000 0100
match the checksum at the end of the message.
Framing error. The Stop Bit of one or more bytes received was not
FIC Comm Err 1001 0000
detected.
Overrun error. At least one byte of data in the receive buffer was
FIC Comm Err 1010 0000
overwritten before it was read.
Character parity error. The parity of one or more of the bytes received
FIC Comm Err 1100 0000
was incorrect.
Table 8.1.6 and Table 8.1.7 list the transmitter error messages that
might appear on the Transmitter Status screen, the SIB Configuration
screen, or the Transmitter Configuration screen when using the
transmitter commands.
Message Description
Buffer overflow. The message was too long for the receive buffer of
Xmtr Comm Err 1000 0010
the device.
Xmtr Comm Err 1000 0x00 Bit 2 is reserved. It is set to zero by the transmitter.
Framing Error. The stop bit of one or more bytes received by the
Xmtr Comm Err 100 10000
device was not detected by the UART.
Overrun Error. At least one byte of data in the receive buffer of the
Xmtr Comm Err 10 100000
UART was overwritten before it was read.
Byte Parity Error. The parity of one or more of the bytes received by
Xmtr Comm Err 1100 0000
the device was incorrect.
Xmtr Status
Message Description
field
PV Out of Xmtr Limits 00000001 Primary variable is out of the transmitter operating limits.
Non PV out of Limits 00000010 A Non--primary variable value is out of the transmitter limits.
Output Current Saturated 00000100 Primary variable is reading above 20 mA or below 4 mA.
Power has been turned off and then on, which reinstalls the
Cold Start 00100000
setup information.
Xmtr Config Changed 01000000 A write or set command has been executed.
The configuror can use the SIB commands described later in this
section to upload the field transmitter configuration to the SIB and to
download the SIB transmitter configuration to the field device.
Command Description
Indicates that there is no active command. This is not a user option, but is
Done
displayed to indicate that a command has been completed.
Copies the transmitter configuration from the transmitter in the field to the dynamic
Upload Xmtr Config portion of the SIB. This happens automatically when a new transmitter is configured
or when any transmitter configuration is changed.
Sends the transmitter configuration from the static portion of the SIB to the
Send Config to Xmtr transmitter in the field. Also causes an automatic upload of the transmitter
configuration.
Causes the transmitter to begin a self test and indicates the result in the “Diagnostic
Xmtr Self Test
Status” field on the Transmitter Status screen.
Copies the field transmitter configuration (SIB dynamic portion) to the SIB (static)
Save Xmtr Config
configuration.
Exits the transmitter fixed current output mode. The “End Fixed Current” must be
End Fixed Current performed following any of the “Trim Xmtr DAC” command functions or the “Set
Output Current”.
Sets the transmitter to 4 mA. When selected, the “Enter the Trim Value” field
Trim Xmtr DAC, appears. This field allows the user to calibrate the transmitter D/A zero. The trim
4 mA
value is entered in mA.
Sets the transmitter to 20 mA. When selected, the “Enter the Trim Value” field
Trim Xmtr DAC, appears. This field allows the user to calibrate the transmitter D/A gain. Must be
20 mA followed by an “End Fixed Current” command function. The trim value is entered in
mA.
(continued on next page)
Command Description
Sets the transmitter current to the user value. When selected, the “Enter the Output
Current” field appears. This field allows the user to select a particular output for the
Set Output Current
transmitter to check that the transmitter is working properly. Must be followed by an
“End Fixed Current” command function.
Re--Zero Xmtr Adjusts the zero at the transmitter.
Changes the address of the transmitter. Puts the transmitter into Fixed Current
Set Xmtr Address Mode. Fixes the digital and analog currents at 4.0 mA. The digital PV provides the
transmitter reading.
Command ®Send Config to Xmtr Stat 39.0 000 Num 15.0 000
CONFIG 1
Command ®Send Config to Xmtr Stat 39.0 000 Num 15.0 000
CONFIG 1
The shaded area of Figure 8.1.21 shows the section of the Transmitter
Configuration screen used for assigning the Units. To assign the units,
the block must be in Manual mode.
- To assign the units:
1. Cursor to the “Mode” field and press the [OPERATOR] key or
press [NEXT OPTION] to select Manual mode; then press
[ENTER].
2. Cursor to the “Units” field; press [NEXT OPTION] to select the
desired units; then press [ENTER].
3. Cursor to the “Command” field; press [NEXT OPTION] to select
“Send Config to Xmtr”; then press [ENTER].
4. Cursor to the “Mode” field and press the [AUTO] key or press
[NEXT OPTION] to select Auto mode.
Table 8.1.9 and Table 8.1.10 show the codes that provide the RS3 with
the appropriate unit. Table 8.1.9 is listed by code number. Table 8.1.10
is listed by alphabetical order.
If a question mark is shown for the Transmitter Type field, the device is
not fully supported. Enter the appropriate code, shown in the tables
below, in the “Units” field.
Table 8.1.9. “Units” Field Codes Table 8.1.9. “Units” Field Codes (continued)
14 atmospheres 39 milliamperes
16 gallons/minute 41 liters
20 feet/second 45 meters
21 meters/second 46 barrels
22 gallons/second 47 inches
24 liters/second 49 millimeters
Table 8.1.9. “Units” Field Codes (continued) Table 8.1.9. “Units” Field Codes (continued)
Table 8.1.10. Alphabetic List of “Units” Field Table 8.1.10. Alphabetic List of “Units” Field
Codes Codes (continued)
barrels 46 feet/second 20
bars 7 gallons 40
centimeters 48 gallons/second 22
feet 44 kilograms 61
Table 8.1.10. Alphabetic List of “Units” Field Table 8.1.10. Alphabetic List of “Units” Field
Codes (continued) Codes (continued)
millivolts 36
kilograms/liter 96
minutes 50
kilograms/minute 74
ohms 37
kilograms/second 73
pascals 11
kilograms/square centimeter 10
percent solids/volume 106
kilopascals 12
percent solids/weight 105
liters 41
pounds 63
liters/minute 17
pounds/cubic foot 94
liters/second 24
pounds/cubic inch 98
long tons (2240 pounds) 65
pounds/day 83
meters 45 pounds/gallon 93
meters/hour 120 pounds/hour 82
meters/second 21 pounds/minute 81
When there are rapid input variations, you can use transmitter damping
to smooth the transmitter output. However, for more reliability with
redundant configurations, we recommend that you use the SIB filter
time instead of the transmitter damping.
The shaded area of Figure 8.1.22 shows the section of the Transmitter
Configuration screen used for setting the transmitter damping. To set
the transmitter damping, the block must be in Manual mode.
Command ®Send Config to Xmtr Stat 39.0 000 Num 15.0 000
CONFIG 1
You may configure the SIB output to be a linear or square root function,
depending on the type of transmitter to which the block is configured.
The shaded area of Figure 8.1.23 shows the section of the Transmitter
Configuration screen used for assigning the block output. To assign the
block output, the status of the block must be in Manual mode.
The shaded area of Figure 8.1.24 shows the section of the Transmitter
Configuration screen used for viewing the high and low transmitter limits
and the type of units corresponding to the limits.
or
D From the Transmitter Status screen, press [PAGE AHEAD]
Access
Field Description Allowable Entries
Level
Type of transmitter.
NOTE: A list of the codes and the corresponding
transmitters follows. This field might display a code
preceded by a question mark to refer to the transmitter
that is connected to it rather than displaying the name of
the transmitter type.
0 =ASCII
Manufacturer Identification Code 38 (Rosemount)
3051 Pressure Transmitter
3044 Temperature Transmitter
1151S Pressure Transmitter
Xmtr Type Conf 8712 Mag Flow Meter Display only
8712H Mag Flow Meter
2001 Pressure Transmitter
3051C Pressure Transmitter
3001L Pressure Transmitter
3044C Temperature Transmitter
3001C Pressure Transmitter
8800 Vortex Flow Transmitter
1152S Pressure Transmitter
Options ?7, ?8, ?9, ?10 in the Xmtr Type field are
reserved transmitter type code numbers for future use.
Access
Field Description Allowable Entries
Level
Up to 16
Tag Conf Transmitter identification tag. alphanumeric
characters
Up to 16
Desc Conf Description of the transmitter. alphanumeric
characters
Access
Field Description Allowable Entries
Level
Up to 32
Mesg Conf Any user message or note. alphanumeric
characters
Range 20 Engineering units value associated with the 20 mA signal. Max = 999999
Conf
mA These units are transmitter dependent. Min = --999999
Log entries are made in chronological order from top to bottom of the
display. Unless specified otherwise, all event entries for a transmitter
are recorded on both the transmitter address maintenance log and the
transmitter serial number maintenance log.
*END*
CONFIG 1
The Transmitter Maint Log screen provides a log of entries from the
operation of a transmitter. Each transmitter has a transmitter address
maintenance log screen and a transmitter serial number maintenance
log screen. All event entries for a transmitter are recorded on both the
transmitter address maintenance log and the transmitter serial number
maintenance log. You can configure information entered in the “Log
Entry” field to be recorded on the selected log only, or on both the
selected and related logs.
You can call up either the address or serial number Transmitter Maint
Log screen. The specific log called up is called the selected log. The
corresponding log is called the related log. Figure 8.1.27 shows the
Transmitter Maint Log screen for the transmitter with serial number
S004009936; The figure also identifies its related log by the address
=87FA201.
Figure 8.1.27 shows the Transmitter Maint Log screen. Table 8.1.12
describes the Transmitter Maint Log screen fields.
- To call up the Transmitter Maintenance Log screen:
D From the command line, type T L , (address or serial number)
[ENTER]. Move between the selected log and the related log by
cursoring to the “Related Log” field and pressing [SELECT].
or
D From the Log File Directory, cursor to the desired transmitter
address or serial number and press [SELECT]. Move between
the selected log and the related log by cursoring to the “Related
Log” field and pressing [SELECT].
or
D From another node, type T L (volume name, address or serial
number) [ENTER].
Field Description
Displays the serial number of the transmitter for the serial number
File Name maintenance log or the address of the transmitter for the address maintenance
log.
Determines whether or not the user entry is to be listed on both the address
and serial number log files.
“No” = The entry configured in the “Log Entry” field is listed only on the log
Send to both?
file of the selected maintenance log. “No” is the default.
“Yes” = The entry configured in the “Log Entry” field is listed on both the log
file of the selected maintenance log and the related log.
Maximum number of entries that can be entered in a log file. If the number of
Max entries entries exceeds the maximum, the oldest entries are deleted from the file.
The default is 1000.
Orig Plant Unit Plant unit at which the message was generated.
Allows the user to make a manual entry into the transmitter maintenance log.
To add an entry, type a line of text and press the [ENTER] key.
Also allows display of the following information about the entries by cursoring
to the “Log Entry” field (or the command line) and repeatedly pressing [EXCH]:
D Date the entries were generated
Log Entry D Time the entries were generated
D Tag from which the entry was generated
D Address from which the entry was generated
D Serial number from which the entry was generated
D Key number
Displays the first display entry. To display the most current log entry, cursor to
the field and press [ENTER].
Top Entry To display a particular log entry, cursor to the field, type in the number of the
entry, and press [ENTER]. If the line number of the entry is unknown, use the
trackball to scroll down the screen to locate the desired entry.
Section 2:
HARTä Output Block
This section describes the functions of the HART Output Block (HOB).
The HOB allows users to communicate with SMARTä field actuator
devices such as valve positioners. By allowing communication between
the ControlBlock and a HART field device, the HART Output Block can
determine actual valve position. The HOB also allows the operator to
distinguish between transmitter and valve problems.
In this section, you will find the following information relating to the HOB:
For information about new Multipoint I/O hardware used with the HOB,
see SV:6.
The HART Output Block receives data from the ControlBlock and
transmits that data to a field device either through a Digital/Analog
converter, or as a digital HART--protocol message.
MPCII
SIB XMTR PROCESS
Smart
Input SMART
Control Block Field Interface
Block Card (FIC)
PV A
PID Q HOB
SP B
MTCC Digital
Console VIB Valve
Graphics Controller
Value Input
Blocks
VIB
MAI
MPCII FIM
SIB XMTR PROCESS
Smart
Input
Control Block
Block
PV A
PID Q HOB
SP B MAO
FIM
MTCC Digital
Console VIB Valve
Graphics Controller
Value Input
VIB Blocks
Figure 8.2.2. How an HOB Functions with a Smart FIC or Multipoint Hardware in a Control Loop
Each HOB will have three associated screens.Figure 8.2.3 shows how
to access each screen:
[EXCHANGE] [EXCHANGE]
Like most other I/O blocks, The HART Output Block can be in either
Manual or Auto mode.
D If the block is in “Auto” mode, the block function drives the block
output.
D If the block is in “Manual” mode, the operator can directly
manipulate the block output from the console.
The Digital option will set the valve’s position with a HART command,
rather than by analog current. This is not recommended for closed--loop
control operations. Figure 8.2.5 shows the Output Option Field.
- To set the Output Option field:
1. Cursor to the “Output Option” field and press [NEXT OPTION] to
select Analog or Digital, then press [ENTER].
The shaded area of Figure 8.2.7 shows the section of the HOB
Configuration screen used for configuring HOB alarm priority.
You can configure the priority of an HOB instrument alarm in the “Alarm
Priority” field on the HOB Configuration screen using a numeral from 0
to 3. An entry of 0 indicates the highest alarm priority. An entry of 3
indicates the lowest priority. The default value is 0.
You can configure the default value for the “Alarm Priority” field on the
Alarm Configuration screen.
Access
Field Description Allowable entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag
characters
Table 8.2.1. HART Output Block (HOB) Configuration Screen Fields (continued)
Access
Field Description Allowable entries
Level
Field Device NA Displays the name of the field device. Display only
Table 8.2.1. HART Output Block (HOB) Configuration Screen Fields (continued)
Access
Field Description Allowable entries
Level
The HART Output Device Status Screen displays the status of the
HART field device. Figure 8.2.8 displays the screen.
I/O Block
Configuration
Screen
[EXCHANGE] [EXCHANGE]
Command ®Done Stat 44.0 064 cmd not implemented Num 38.0 000
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ALARM LINE~~~~~~~~~~~~~~~~~~~~~~~~~~~ CONFIG 1
Only the Mode and Command fields can be changed on the HART
Output Device Status Screen; the rest are for display only.
Only two fields are enterable on the HART Output Device Status
Screen: the Mode field and the Command field, which are listed below.
Table 8.2.2 lists all the fields and their descriptions.
Field Description
Mode The current operating mode of the HOB. Supervisor--level access only.
Field Device Type Name of the field device type (e.g. valve positioner)
Dev Alarm Val Deviation alarm trip value of the HART field device
Output Device Status Status of the HART field device. See Table 8.2.3 for list of field values
Diagnostic status of the HART field device, in hexadecimal notation. See field
Diagnostic Status
device documentation for device--specific codes.
Communication status between the controller and the Field Interface Card.
Cont Comm Err
If 0, nothing displayed.
Control Mode Control mode of the field device: Manual, automatic, or remote
Communication status between the Field Interface Card and the HART field
FIC/Device Comm Err device.
If 0, nothing displayed.
The Output Device Status field returns binary information to the HOB on
both the I/O Block Configuration screen and the HART Output Device
Status screen. Table 8.2.3 provides a description of the possible field
displays. Table 8.2.4 provides a list of the FIC communication error
messages from the FIC/Device Comm Err field.
Code Description
Code Description
FIC/Device Comm Err 1000 0010 Buffer overrun error. Too many characters were received.
Smart transmitter parity byte error. The calculated checksum did not
FIC/Device Comm Err 1000 0100
match the checksum at the end of the message.
Framing error. The Stop Bit of one or more bytes received was not
FIC/Device Comm Err 1001 0000
detected.
Overrun error. At least one byte of data in the receive buffer was
FIC/Device Comm Err 1010 0000
overwritten before it was read.
Character parity error. The parity of one or more of the bytes received
FIC/Device Comm Err 1100 0000
was incorrect.
I/O Block
Configuration
Screen
[EXCHANGE] [EXCHANGE]
Dead TimeÞ0. Sec Dev. Alarm Val. Þ0.% Inst. Mode ÞNorm
0. Sec 0.% Norm
# of Variables Þ4
4
Slot 0 Var ID Code Prim. Analog In Slot 1 Var ID Code Pressure
(HOB Input 1) Prim. Analog In (HOB Input 2) Pressure
Slot 2 Var ID Code Þ1 Slot 3 Var ID Code Þ211
(HOB Input 3) Aux Analog In(1) (HOB Input 4) Temperature(211)
Command >Done Stat 44.0 064 cmd not implemented Num 38.0 000
FULL CONFIG 1
Each configurable entry has two values, as shown in Table 8.2.5 The
top number is the device configuration value and can be changed by the
configuror. The bottom number is the field device configuration value
and cannot be edited at the console.
The configuror can use the HOB commands described later in this
section to upload the field device configuration to the HOB and to
download the HOB field device configuration.
Access
Field Description Allowable entries
Level
Address NA Address of the block Display only
Current block mode. See “Determining
Mode Supr the Block Mode to Use” onpage 8-2-5 Auto, Manual
for more information.
Block Out NA Displays the Output value from the HOB. Display only
Up to 16 alphanumeric
Block Tag NA User defined block tag.
characters
There are two displays on the screen:
D The top indicates the
manufacturer I.D., which is
Mfr ID NA Display only
located in the HOB static data
D The bottom indicates the actual
I.D. of the field device
There are two displays on the screen:
D The top indicates the device type
located in the HOB static data.
Field Device Type Conf Display only
D The bottom indicates the actual
device type of the connected field
device
There are two displays on the screen:
D The top indicates the date of the
Conf field device stored in the HOB
Date dd/mm/yy
static data
D The bottom indicates the actual
date of the field device
There are two displays on the screen:
D Enter the tag of the field device in
Conf the top field. Up to 8 alphanumeric
Tag
characters
D The bottom field indicates the
actual tag of the field device.
There are two displays on the screen:
D Enter the descriptor of the field
Conf device in the top field. Up to 16 alphanumeric
Desc
D The bottom field indicates the characters
actual descriptor of the field
device.
* This field is only operable when the Mode is in manual.
NOTE: Bold text indicates default selections.
Access
Field Level Description Allowable entries
Access
Field Level Description Allowable entries
Access
Field Level Description Allowable entries
The shaded area of Figure 8.2.10 shows the section of the HART
Output Device Configuration screen used for assigning a tag,
descriptor, message, or date to a SMART field device. To assign any of
these, the block must be in Manual mode.
- To assign a tag, descriptor, message, or date:
1. Be sure that the HOB is in Manual mode.
2. Cursor to the “Tag”, “Desc”, “Mesg”, or “Date” field and enter the
desired tag, descriptor, message, or date. Press [ENTER].
3. Cursor to the “Command” field and press [NEXT OPTION] to
select “Send Config to Xmtr”; then press [ENTER].
4. Cursor to the “Command” field and press [NEXT OPTION] to
select “Save Xmtr Config”; then press [ENTER].
This field displays the time, in seconds, that a deviation alarm will be
allowed to persist before being reported by the field device. Use this
field to prevent consistent alarm conditions from variables that fluctuate
around the setpoint. The upper field is enterable; the lower field returns
the currently stored value. The allowed range is 0.015 to 60 seconds.
Figure 8.2.11 highlights the Dead Time field.
The Deviation Alarm Value field displays the range, in percent, that the
requested setpoint will be allowed to fluctuate around the actual
setpoint. For example, if the Deviation Alarm Value is 10% and the
requested setpoint is 50%, then the actual setpoint must be between
40% and 60%, or a deviation alarm will be generated.
Configure this field in coordination with the Dead Time field to allow for
greater consistency in reporting alarm conditions. Figure 8.2.12 shows
the Dev. Alarm Val. field. The upper field is enterable; the lower field
represents the currently stored value.
Dead TimeÞ 0. Sec Dev. Alarm Val. Þ 0.% Inst. ModeÞ Norm
0. Sec 0.% Norm
# of Variables Þ 4
4
Slot 0 Var ID Code Prim. Analog In Slot 1 Var ID Code Pressure
(HOB Input 1) Prim. Analog In (HOB Input 2) Pressure
Slot 2 Var ID Code Þ1 Slot 3 Var ID Code Þ211
(HOB Input 3) Aux Analog In(1) (HOB Input 4) Temperature(211)
Command ®Done Stat 44.0 064 cmd not implemented Num 38.0 000
FULL CONFIG 1
The HOB is similar to an SIB because it can receive inputs from SMART
field devices. The Slot fields on the HART Output Device Configuration
Screen provide this functionality. The four slots are labeled 0 through 3,
and allow the following inputs from the field:
Dead TimeÞ 0. Sec Dev. Alarm Val. Þ 0.% Inst. Mode Þ Norm
0. Sec 0.% Norm
# of VariablesÞ 4
4
Slot 0 Var ID Code Prim. Analog In Slot 1 Var ID Code Pressure
(HOB Input 1) Prim. Analog In (HOB Input 2) Pressure
Slot 2 Var ID Code Þ1 Slot 3 Var ID Code Þ211
(HOB Input 3) Aux Analog In(1) (HOB Input 4) Temperature(211)
Command ®Done Stat 44.0 064 cmd not implemented Num 38.0 000
FULL CONFIG 1
Figure 8.2.13. The Slot Fields on the HART Output Device Configuration Screen
0 Primary Analog In
1 Aux Analog In
2 Pressure
3 Position
4 Servo Drive
211 Temperature
0 Primary Analog In
1 Aux Analog In
3 Servo Drive
211 Temperature
Table 8.2.8. Slot Variables for Fisher valve with pressure sensor
0 Primary Analog In
1 Aux Analog In
2 Pressure
4 Servo Drive
211 Temperature
Up to four VIB blocks can serve as inputs from an HOB. The HOB input
number identifies which HOB input is being linked to a particular VIB
block. For more information on configuring a VIB block, see page
8-1-17.
The shaded area of Figure 8.2.14 shows the section of the VIB Block
Configuration screen that is used for linking a VIB block to an HOB.
The example in Figure 8.2.14 shows the VIB block at =129AB204 is
linked to an HOB at =129AB203.
- To link a VIB block to an HOB:
1. Cursor to the “SIB/HOB Tag” field and enter the tag or address of
the HOB to which the VIB block is to be linked.
2. Cursor to the “SIB/HOB Input” field and enter the number of the
HOB input to which the VIB block is to be linked, then press
[ENTER].
Configuration Problems
Listed below are typical problems that occur when configuring HART
Output Blocks and possible ways to handle them.
- When I plug in a redundant FIM, I lose all HART communication.
You should configure an RIOB before plugging in a redundant FIM.
Similarly, when removing redundancy, you should pull the FIM first,
then deconfigure the RIOB.
- When I execute a ‘Kill Controller’ command, with a redundant
FIM configuration, HART communication locks up.
If you have redundant controllers, you must switch to the backup
controller to maintain HART communication.
Without redundant controllers, you must disable and re--enable the
controller to re--establish HART communication.
Section 3:
Hints for Configuring SIBs and VIBs
This section discusses some of the problems that you may encounter
when configuring smart transmitter input blocks and some possible
ways to deal with them. This section also provides tips that are helpful
when configuring SIBs and VIBs.
RS3: Configuring Smart Blocks Hints for Configuring SIBs and VIBs
IO: 8-3-2
Configuration Problems
Listed below are typical problems that occur when configuring smart
transmitter input blocks and possible ways to handle them.
- I cannot access some of the SIB and VIB Block Configuration
screen fields.
In order to configure many screen fields, the block must be in
Manual mode. Be sure that the block is in Manual mode.
- The Transmitter Status screen shows FIC Comm Error 10001000
and Controller Comm Error 132.
The transmitter is probably not communicating with the FIC. Check
the following conditions:
D The Analog FIC PWR jumpers are correctly set.
D The redundant Analog FIC PWR jumpers are correctly set.
D The polarity of the transmitter wiring to the marshalling panel is
correct.
D The address of the transmitter is set to zero.
D The transmitter type is supported by the RS3.
RS3: Configuring Smart Blocks Hints for Configuring SIBs and VIBs
IO: 8-3-3
Configuration Tips
Listed below are hints to help you when configuring SIBs and VIBs.
- Assigning a descriptor
Remember that when assigning a descriptor to a transmitter on the
SIB Block Configuration screen, you must enter the descriptor in the
“Desc” field, even if the exact descriptor already appears.
- Using both the analog and digital PV values
If you would like to use both analog and digital PV values, configure
an SIB for the analog value and a VIB for the digital value.
- Configuring SIB alarms
D Remember that you will probably want to configure instrument
alarms and the alarm priority for each SIB.
D Remember that if you configure an SIB alarm, you should also
configure the alarm priority.
- Configuring a VIB
When configuring a VIB, be sure to link the VIB to an SIB residing on
the same FIC. The VIB must have a block address in the range of
4--16. (Addresses 1--3 are reserved for SIBs.)
- Difference between the field transmitter configuration and the
SIB transmitter configuration
The field transmitter configuration is the configuration that exists in
the transmitter. It appears as the bottom line of text on the
Transmitter Status screen and Configuration screens. It cannot be
edited from the console.
The SIB transmitter configuration is the configuration that is saved to
the SIB and can be changed by the configuror. The SIB
configuration can then be loaded into the transmitter in order to
change the field transmitter configuration.
- Trending the SIB information
When trending SIB information, it is helpful to have a descriptor to
label the data on the trend display.
To have a descriptor appear on a trend display for an SIB, assign a
descriptor on the Transmitter Configuration screen. The descriptor
is actually assigned to the transmitter, but can be used for an SIB as
well.
RS3: Configuring Smart Blocks Hints for Configuring SIBs and VIBs
IO: 8-3-4
RS3: Configuring Smart Blocks Hints for Configuring SIBs and VIBs
RS3t
I/O Block Configuration
Chapter 9:
Configuring PLC Blocks
List of Figures
Figure Page
9.1.1 PLC Interface Hardware Functional Overview . . . . . . . . . . . . . . . . . . . . 9-1-3
9.1.2 PLC Interface Software Functional Diagram . . . . . . . . . . . . . . . . . . . . . . 9-1-5
9.1.3 Sample Configuration—One Port I/O Card and One Data Highway . . 9-1-8
9.1.4 Sample Configuration—Two Port I/O Cards and One Data
Highway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-9
9.1.5 Sample Configuration—Two Port I/O Cards and Two Data
Highways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-10
9.1.6 Sample Configuration—Modbus PLC and Data Highway . . . . . . . . . . . 9-1-11
9.1.7 Sample Configuration—Mitsubishi PLC RS422 Network
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-13
9.1.8 Sample Configuration—Mitsubishi PLC Melsec Network
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-15
9.2.1 PLC Addressing Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-4
9.2.2 Sample Simulation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-7
9.2.3 PLC Configuration Screen for Modbus-Compatible Devices . . . . . . . . 9-2-11
9.2.4 PLC Configuration Screen for Allen-Bradley-Compatible Devices . . . . 9-2-11
9.2.5 PLC Configuration Screen for Mitsubishi Devices . . . . . . . . . . . . . . . . . 9-2-12
9.3.1 PLCB I/O Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-2
9.3.2 Typical PLC Register Contents and Logic . . . . . . . . . . . . . . . . . . . . . . . . 9-3-10
9.3.3 PLCB I/O Block Configuration Screen (Read Only) . . . . . . . . . . . . . . . . 9-3-11
9.3.4 Bit Designators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-12
9.3.5 Using PLC Data in a ControlBlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-15
9.3.6 Configuration Window Linking PLC Bit Input to a Graphic . . . . . . . . . . 9-3-16
9.3.7 Bit Descriptor Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-17
9.3.8 Alarm Descriptor Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-19
9.3.9 Writing to a PLC Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-20
9.3.10 PLCB I/O Block Configuration Screen (Write Only) . . . . . . . . . . . . . . . . 9-3-22
9.3.11 Designating a Source for the I/O Block . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-22
9.3.12 PLCB I/O Block Configuration Screen (Data Type Other Than
Flags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-23
9.3.13 Using the Write Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-25
9.3.14 Reading and Writing Through a Single I/O Block . . . . . . . . . . . . . . . . . . 9-3-26
9.4.1 PLC Configuration Screen with Redundancy Fields . . . . . . . . . . . . . . . . 9-4-3
9.4.2 Typical PLC Interface FIC Redundancy for Allen-Bradley PLCs . . . . . 9-4-5
9.4.3 Typical PLC Interface FIC Redundancy for Modicon PLCs . . . . . . . . . 9-4-6
9.4.4 Typical Configuration for Mitsubishi PLC Redundancy . . . . . . . . . . . . . 9-4-7
9.5.1 PLC Configuration Screen with Loopback Test Selected . . . . . . . . . . . 9-5-3
9.5.2 RS422/RS232 Port I/O Card Block Diagram . . . . . . . . . . . . . . . . . . . . . . 9-5-5
9.5.3 RS422/RS422 Port I/O Card Block Diagram . . . . . . . . . . . . . . . . . . . . . . 9-5-6
9.5.4 PLC Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-11
9.5.5 Configuring a PLC--2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-12
9.5.6 PLC--2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-13
9.5.7 PLC--3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-15
9.5.8 PLC--5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-17
List of Tables
Table Page
9.2.1 Function Codes for Specific Modbus Devices . . . . . . . . . . . . . . . . . . . . . 9-2-2
9.2.2 Modbus Function Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-2
9.2.3 Mitsubishi PLC Device Ranges and Addresses . . . . . . . . . . . . . . . . . . . 9-2-6
9.2.4 Station Numbers Octal-Decimal Conversion Chart . . . . . . . . . . . . . . . . 9-2-9
9.2.5 PLC Configuration Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-13
9.3.1 Discrete Bit Maps for RS3 and Modicon Interface . . . . . . . . . . . . . . . . . 9-3-3
9.3.2 Discrete Bit Map for RS3
and Modicon Interface (GE Series 6) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-4
9.3.3 Discrete Bit Map for RS3 and Allen--Bradley PLC 2 . . . . . . . . . . . . . . . . 9-3-5
9.3.4 Discrete Bit Map for RS3 and Allen--Bradley PLC 5 . . . . . . . . . . . . . . . . 9-3-7
9.3.5 Register Map for RS3 and GE Series 6 PLC . . . . . . . . . . . . . . . . . . . . . . 9-3-8
9.3.6 Register Map for RS3 and Modicon PLC . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-8
9.3.7 Register Map for RS3 and MItsubishi PLC . . . . . . . . . . . . . . . . . . . . . . . 9-3-9
9.3.8 16-bit Binary-to-Hexadecimal Conversion Chart . . . . . . . . . . . . . . . . . . . 9-3-12
9.3.9 PLCB I/O Block Configuration Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-13
9.3.10 Bit Descriptor and Alarm Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-18
9.3.11 Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-23
9.4.1 PLC Configuration Redundancy Fields . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-3
9.5.1 General PLC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-18
9.5.2 PLC Communication Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-19
9.5.3 Mitsubishi Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-20
Section 1:
What is a PLC Interface?
This section describes the hardware and software used to interface with
programmable logic controllers (PLCs). This section also describes the
protocols and network configurations that this PLC interface supports.
You can attach PLCs to the RS3 PLC interface with either an RS232C
or an RS422 connection. Allen-Bradley Data Highways One, Two, and
Plus are supported.
You can incorporate data that is received from or sent to a PLC into the
RS3 operating displays in the same way as any other process data
stored in a controller. This interface does not, however, allow you to
configure a PLC through an RS3 console.
Figure 9.1.1 shows that, like other members of the RS3 controller
family, the PLC interface consists of a Controller Processor card and a
Communication FlexTerm. The Controller Processor can be a PLC
Processor card (1984-1494-000x) or a MultiPurpose Controller card
(1984-2500-000x or 1984-4068-0006). One FlexTerm can be shared by
two Controller Processor cards. Communication between a Controller
Processor card and a FlexTerm is carried by an RS422 cable.
Communication between the PLCs and the FlexTerm is carried by either
an RS232C cable or an RS422 cable.
A FlexTerm has two ports (A and B) for each Controller Processor card.
Each port consists of a Port I/O card. This card provides electrical
isolation of the system and connection of the PLCs to the system. The
attributes of each port, such as the baud rate and the communication
format, are configured separately on a PLC Configuration screen.
There are eight port slots on the FlexTerm, but only four are used by the
PLC software. Slots 1 and 2 in the Flexterm contain ports A and B for
Processor card 1; slots 5 and 6 contain ports A and B for Processor
card 2.
Controller Processor
Card
RS422 Port A
CB CB IO IO Field
PLCs or Discrete/
Port B other Analog
CB CB IO IO
Compatible Inputs and
CB CB IO IO Devices Outputs
Port A
The PLC register contains one of the following items (data types):
D Signed integer (S INT)
D 3-bit BCD value (BCD3)
D 16 bits, each representing an individual point (Flags)
D Unsigned integer (U INT)
D 4-bit BCD value (BCD4)
D 32-bit floating point number read only (Float for Daniels Gas
Chromatograph only)
Controller Processor
Card Port A
PLC 1 PLC 32
CB CB IO IO Port B
Register 1 Register 1
CB CB IO IO Port A Register 2 Register 2
Register 3 Register 3
CB CB IO IO Port B Register 4 Register 4
etc. etc.
Controller Processor
Card FlexTerm M5
CB CB IO IO Motor
Control M6
CB CB IO IO Center
No. 5
CB CB IO IO M7
M8
Modbus Protocols
D Modbus/RTU A mode of transmission that uses 8-bit
binary format
D Modbus/ASCII A hexadecimal-oriented mode of
transmission that uses 7-bit ASCII
characters
D Square D A variation of Modbus/RTU
D Modbus/5-6 A variation of Modbus/RTU that uses
function codes 5 and 6 only
D Daniels/RTU Gas Chromatograph that communicates via
a specialized Modbus link.
D Daniels/ASCII Gas Chromatograph that communicates via
a specialized Modbus link.
Allen-Bradley Protocol
D Allen-Bradley only
Mitsubishi Protocol
D Mitsubishi/FMT1
Sample Configuration with One I/O Card and One Data Highway
For a list of the modules that are used to connect the PLCs and the RS3
control system to the data highways, see the Allen-Bradley
documentation. These modules can be rack- or wall-mounted.
Rack-mounted modules are installed in the PLC. Wall-mounted
modules are installed in the RS3 cabinet.
Communication FlexTerm
Controller
Processor 1 2 3 4 5 6 7 8
KE Module
KA Module KA Module
Figure 9.1.3. Sample Configuration—One Port I/O Card and One Data Highway
Figure 9.1.4 shows two Port I/O cards connected to the same data
highway. Using a second KE communication module increases the
throughput.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
KE Module KE Module
Allen-Bradley Data Highway
Figure 9.1.4. Sample Configuration—Two Port I/O Cards and One Data Highway
Sample Configuration with Two I/O Cards and Two Data Highways
Figure 9.1.5 shows two Port I/O cards, each connected to a different
data highway.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
KE Module KE Module
Figure 9.1.5. Sample Configuration—Two Port I/O Cards and Two Data Highways
Communication FlexTerm
Controller
Processor 1 2 3 4 5 6 7 8
KE Module
Allen-Bradley Data Highway
A Mitsubishi PLC base unit consists of a power supply, the CPU unit, I/O
cards, and up to two AJ71C24 computer link modules. An RS3
distributed control system or any other external computer can
communicate with the PLC through the AJ71C24 module, which
handles the communication between the CPU and external computer.
Figure 9.1.7 shows a sample configuration that uses the RS422 port on
the AJ71C24 unit. In this type of configuration, each base unit must
have an AJ71C24 card.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
NOTE: maximum 32
stations: #0 -- #31
RS232
C C C
P P P
......
U U U
RS422 RS422
AJ71C24
Figure 9.1.7. Sample Configuration—Mitsubishi PLC RS422 Network Configuration
NOTE: In this type of configuration, the PLC number that you specify
on the PLCB configuration screen is between 1 and 63; these are the
numbers of the PLC base units on the Melsec network, and they must
be consecutive. To access the Master PLC (see Figure 9.1.8), enter
255 as the PLC number on the PLCB configuration screen.
Master PLC
C
P PLC # 0
Station # 0 Coaxial or Fiber--Optic Cable RS232
U
AJ71C24
C C C
P P P
U U U
......
NOTE: maximum 64
PLC bases: #0 -- #63
Controller
Processor 1 2 3 4 5 6 7 8
Communication FlexTerm
Section 2:
Communicating with the PLC
Table 9.2.2 gives the standard Modbus function codes that are
supported by the RS3. These function codes are part of the Modbus
protocol. They set the function to be executed by the
Modbus-compatible PLC. For a complete description of the Modbus
Function Codes, see the Standard Modbus Protocol Specification.
Table 9.2.1 shows the Modbus Function Codes that are required for
communication to be established with specific devices. Square D and
Modbus/5-6 devices use the RTU format of the Modbus protocol.
Function Code
Device Type
1 2 3 4 5 6 15 16
Modbus/ASCII X X X X X X
Modbus/RTU X X X X X X
Square D X X X X X X
Modbus/5-6 X X X X X X
Daniels RTU X X X X X X
Daniels ASCII X X X X X X
1 Read/Write Coils Read coil status. This code obtains the current status (on/off) of a group
(0xxxx) of logic coils.
2 Input Coils (1xxxx) Read input coil status. This code obtains the current status (on/off) of a
group of discrete inputs.
3 Read/Write Registers Read holding registers. This code obtains the binary value in one or
(4xxxx) more holding registers.
4 Input Registers Read input registers. This code obtains the binary value in one or more
(3xxxx) input registers.
5 Read/Write Coils Force single coil. This code forces a coil to a state of on or off.
(0xxxx)
6 Read/Write Registers Preset single register. This code changes the binary value in a single
(4xxxx) register.
15 Read/Write Coils Force multiple coils. This code changes the status of one or more coils.
(0xxxx)
16 Read/Write Registers Force multiple registers. This code changes the binary value in one or
(4xxxx) more registers.
To use the PLC interface most efficiently, the PLC reads and writes
should be done from consecutive PLC addresses as often as possible.
For example, if the confirmation signals from a number of motors must
be read at one time, put these signals in registers with consecutive
addresses. In this way, the registers can be read with a single
message. Do the same thing with the registers to which the PLC is
writing: write the values to consecutive registers.
For the function codes for consecutive reads and writes, see the
Standard Modbus Protocol Specification. All devices listed in
Table 9.2.1 support consecutive reads. However, Square D and
Modbus/5-6 devices do not support consecutive writes.
=16 A 45
Mitsubishi Devices
The RS3 control system uses two commands to read and write PLC
data. Both of the following commands always manipulate 16 bits of
data:
D Batch Word Read (WR)
D Batch Word Write (WW)
* Special Relays M9000 to M9255 and Special Registers D9000 to D9255 are read only; no Batch Word
Write is allowed to these registers.
I/O Block
Group Display Addr 1A1 normal
“Logic” mode
ControlBlock
Sim
Tag Þ cb PLC
Faceplate Faceplate Addr 1A-3
simulate
“Simulation” mode
ControlBlock Plant
Addr 1A-3 a
b
c
.
Simulation Inputs .
(a-p)
.
p
The modules provide an interface between the data highway and the
RS3. The switch settings on the modules must meet the following
requirements:
D Half duplex, even parity, BCC (Block Check Character)
error-check field
D Ignore RS232 handshaking when not using a modem
D Detect and ignore duplicate messages
D Data highway rate of 57.6 Kbits per second
D Recommended baud rate of 9600
The station number selected for the Allen-Bradley module that connects
RS3 to the Allen-Bradley data highway is the same number that should
be entered on the PLC Configuration screen. This number is in octal in
the PLC.
The screen appears only if a Controller Processor jumpered for the PLC
additional image is installed in the specified ControlFile slot. Unless you
specify an address, the screen for the lowest-numbered Controller
Processor appears.
Controller ControlFile node number and card slot in which the Processor =1 to =992
Address resides. Slots A to H
Modbus/ASCII,
Modbus/RTU,
Square D,
Allen-Bradley,
Device Type Specifies the type of PLC device to which the port is connected. Modbus/5-6,
Loopback Test,
Daniels/RTU,
Daniels/ASCII,
Mitsubishi/FMT1
Communication rate between the port and the PLCs to which it 1200, 2400, 4800,
Baud Rate
is connected. 9600
Time the PLC Interface waits for a reply from a PLC before
sending the request again. Enter a higher value for slower
Msg Timeout in PLCs. 0 to 1000
1/100 Seconds
For Allen-Bradley PLCs, the timeout should remain at the
default value of 10 seconds.
Number of The total number of PLCs with which this port is attempting to
Display only
PLCs communicate.
Number of Bad
Number of PLCs not communicating properly with the port. Display only
PLCs
Blocks/Eval Number of times PLCBs are being evaluated through this port
Display only
Time during each processing cycle.
Section 3:
Configuring a PLCB
The RS3 can read and write to PLC registers and coils. You need to
map the communications between the RS3 and PLC. The tables on the
following pages have two columns: one column tells you what to enter
into the RS3 and the other tells you the corresponding register or coil in
the PLC.
NOTE: Not all PLC coils available can be accessed by the RS3. The
upper 16 coils in a PLC can not be accessed.
Table 9.3.1 and Table 9.3.2 represent the mapping between the RS3 I/O
block bits and the discrete bits in the PLC. Mapping with discrete bits
(coils) is only applicable when the “Data Type” field on the I/O Block
Configuration screen is set to Flags.
Entering a value of 1 in the “PLC Word Address” field on the PLC I/O
Block Configuration screen reads 16 bits from the PLC, starting with coil
1. Coil 1 corresponds to bit “a” in the PLC I/O block; coil 2 corresponds
to bit “b”; etc.
Table 9.3.1. Discrete Bit Maps for RS3 and Modicon Interface
RS3* Modicon
1/a 00001
1/b 00002
... ...
1/p 00016
17/a 00017
17/b 00018
... ...
17/p 00032
33/a 00033
33/b 00034
... ...
33/p 00048
* Entering a value of 1 in the “PLC
Word Address” field on the PLC I/O
Block Configuration screen reads 16
bits from the PLC starting with coil 1.
Coil 1 corresponds to bit “a” in the
PLC I/O block, coil 2 corresponds to
bit “b” and so on.
Entering a value of 1 in the “PLC Word Address” field on the PLC I/O
Block Configuration screen reads 16 bits from the PLC, starting with coil
1. Coil 1 corresponds to bit “a” in the PLC I/O block; coil 2 corresponds
to bit “b”; etc.
GE Series 6
RS3* (Modicon
Interface)
1/a 00001
1/b 00002
... ...
1/p 00016
17/a 00017
17/b 00018
... ...
17/p 00032
33/a 00033
... ...
33p 00048
* Entering a value of 1 in the “PLC
Word Address” field on the PLC I/O
Block Configuration screen reads 16
bits from the PLC starting with coil 1.
Coil 1 corresponds to bit “a” in the
PLC I/O block, coil 2 corresponds to
bit “b” and so on.
Entering an octal value of 010 in the “PLC Word Address” field on the
PLC I/O Block Configuration screen reads 16 bits from the PLC, starting
with address 010/00. Address 010/00 corresponds to bit “a” in the PLC
I/O block, address 010/01 corresponds to bit “b”, etc.
Table 9.3.3. Discrete Bit Map for RS3 and Allen--Bradley PLC 2
The address switches on the PLC 5 designate the PLC number on the
highway and correspond to the “PLC Word Address” field on the PLCB
I/O Block screen. It is an octal address.
Table 9.3.4. Discrete Bit Map for RS3 and Allen--Bradley PLC 5
Allen--Bradley Allen--Bradley
RS3 (Octal)* RS3*
(Octal) (Octal)
00 0 /a /0
01 1 /b /1
02 2 /c /2
03 3 /d /3
... ... /e /4
07 7 /f /5
010 8 /g /6
011 9 /h /7
012 10 /i /8
013 11 /j /9
017 15 /l /11
030 24 /n /13
031 25 /o /14
032 26 /p /15
Table 9.3.5 and Table 9.3.6 represent the logical mapping between RS3
and the PLC when using register access.
This table shows the relationship between RS3 (using the Modbus
Device Configuration) and a GE Series 6 PLC. Entering 40001 in the
“PLC Word Address” field on the PLC I/O Block Configuration screen
accesses register 1 in the PLC. Entering 40002 accesses register 2,
etc.
GE Series 6
RS3 (Modicon
Interface)
40001 R0001
40002 R0002
40003 R0003
Table 9.3.6 shows the relationship between the RS3 (using the Modbus
Device Configuration) and a Modicon PLC. Entering 40001 in the “PLC
Word Address” field on the I/O Block Configuration screen accesses
register 40001 in the Modicon PLC. Entering 40002 accesses register
40002, etc.
RS3 Modicon
40001 40001
40002 40002
40003 40003
... ...
Table 9.3.7 shows the relationship between the RS3 and a Mitsubishi
PLC. Entering R0001 in the “PLC Word Address” field on the I/O Block
Configuration screen accesses register R0001 in the MItsubishi PLC.
Entering R0002 accesses register R0002, etc.
RS3 Mitsubishi
R0001 R0001
R0002 R0002
R0003 R0003
... ...
The example shown in Figure 9.3.2 assumes that the bits a, o, and p of
PLC register 1000 are directly related to the states of three contacts in
the field.
PLC 7
Field
1000o Contact
Open
1000p FIeld
Contact
Closed
The shaded areas in Figure 9.3.3 show the fields for specifying the PLC
register that is to be read.
NOTE: To determine what entry to make for the “PLC Word Address”
field, see “Preparing to Read and Write to a PLC Register or Coil” on
page 9-3-2. Table 9.3.9 describes all fields on the I/O Block
Configuration screen.
Hexadecimal F F F F
16 bit binary 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Letter Designator p o n m l k j i h g f e d c b a
Binary
Hexadecimal
p o n m l k j i h g f e d c b a
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 2
0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 3
0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 4
0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 5
0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 6
0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 7
0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 8
0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 9
0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 A
0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 0 0 B
0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 C
0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 0 0 0 D
0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 E
0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 0 F
Access
Field Description Allowable Entries(1)
Level
Address NA Address of the block. Display only
Up to 16 alphanumeric
Block Tag CONF User defined block tag.
characters
PLCB indicates that the controller contains the
appropriate image (PLC or PLC2).
Device Type NA NONE indicates that even though the block is Display only
configured, it will not function because the
controller does not contain the appropriate image.
Up to 16 alphanumeric
Tag or address of the ControlBlock from which characters for tag
Sim Tag/Addr CONF
data is obtained when in simulation mode. Up to 10 alphanumeric
characters for Address
Access
Field Description Allowable Entries(1)
Level
Identifies the communication port that is being
Port CONF A, B
used by the PLC.
Allen-Bradley and
Address of the PLC with which this block Modbus PLCs: 1 - 250;
PLC Number CONF
communicates. Mitsubishi PLC: 0 to 63
and 255.
Hex or decimal value;
depends on PLC
PLC Word Word address within the PLC with which this address structure.
CONF
Address block communicates.
(Table 9.3.1 through
Table 9.3.7.)
Indicates an FIC hardware fault. For information
Hardware Alarm on alarm messages, see the Alarm Messages
NA Display only
Code
Manual.
Assigns priority to hardware alarms. 0 indicates
Alarm Priority CONF 0-3
highest priority, and 3 indicates lowest priority.
Indicates the user defined group to which the
block is assigned. Access to I/O blocks from a
Plant Unit CONF console may be restricted if the console has not 0-255
been assigned to the I/O block plant unit.
For more information on plant units, see CC: 1.
Value from PLC NA Value received from the PLC. Display only
Each letter represents one bit of the “Value from
ponmlkjihgfedcba NA Display only
PLC.”
(1) Bold type indicates default value.
(2) “Float” data type is a special function that is available only for the Daniels Chromatograph.
One or more of the 16 bits from a PLC register can be used as inputs to
a ControlBlock. Just as with any other discrete input, you can use an
individual bit in a ControlBlock discrete faceplate display or in
ControlBlock logic steps, as shown in Figure 9.3.5.
ControlBlock
ETC
You can link an individual bit input directly from a PLC register to a
graphic display. The bit input can only be displayed and cannot be
controlled. Figure 9.3.6 shows a process graphic configuration window
that links a graphic object with a PLC bit input. The bit input is specified
as =2B008/p.
A PLC I/O Block allows you to attach a bit descriptor to specific bits and
to generate custom alarm messages (bit alarm descriptors) for
individual bits. You should use this feature with care because naming
and alarming I/O block bits rapidly depletes the Controller Processor
memory.
Each bit read by the I/O Block has an associated configuration screen.
Table 9.3.10 describes the fields in the shaded area of Figure 9.3.8,
which shows the I/O Block Configuration screen for bit “a”.
- To call up the I/O Block Configuration screen for a specific bit:
D Cursor to the desired bit, and press [SELECT].
You can configure each bit read by the I/O Block to generate one of the
following alarm types: None, Evt, Adv, Crit, Hard, or Batch. Additional
fields appear on the screen when the alarm type is changed from its
default type (None). These fields function the same as the fields in the
“Report” section of a Logic Step in a ControlBlock. For information
about configuring alarms on a logic step of a ControlBlock, see CB: 6.
The “Color” field allows you to specify a color for the bit descriptor. The
“Backlight State” entries of High or Low allow the configuror to
determine when the bit descriptor is backlighted. The “Alarm
Descriptor” field allows configuration of custom alarm messages that
can be up to 32 characters. These alarms are displayed, listed, and
traced in the same manner as all other RS3 alarms. For more
information about alarms, see CC: 6.
Access
Field Description Allowable Entries
Level
Up to 16 standard keyboard
a (through p) Conf Bit descriptor.
characters
Color selection for the flag name. Press [NEXT
OPTION] to select and then press [ENTER].
Color Conf Configured console colors
For more information about color configuration,
see CC: 1.
State in which the bit descriptor is displayed in
Backlight State Conf Low, High
reverse video.
Type of alarm to generate (same as logic steps None, Event, Adv, Crit, Hard,
Alarm Type Conf
alarms). Batch
State in which alarm is to be generated (same
When Conf Rise, On, Fall, Off, Chng
as logic steps alarms).
Event number (same as logic steps alarms).
Event Type Conf This field is shown only when Event is selected 1 to 255
as the Alarm Type.
a:MCC-101 e: i: m :
b: f: j: n :
[SELECT] c: g: k: o :
d: h: l: p :
You can configure an I/O Block to write to a specific PLC register. The
I/O Block receives inputs from a ControlBlock. The I/O Block can write
to the PLC register using a mask to specify the PLC register bits to
which the I/O Block writes. The PLC then controls a field device
through its control logic.
NOTE: To determine what entry to make for the “PLC Word Address”
field, see “Preparing to Read and Write to a PLC Register or Coil” on
page 9-3-2.
PLC 7
a through p Port
Flexterm
PLC Control Logic
CB I/O Port
1000j Start
Start
Command
to Field
1000k Stop
Stop
Command
to Field
1000a Start
Logic step p of the source link The source link (Q) determines
determines when a write occurs when a write occurs.
=2B--10 MOT--6
All Fields Not Shown
0
@d l
ETC ETC
Figure 9.3.12. PLCB I/O Block Configuration Screen (Data Type Other Than Flags)
For information on masking within the PLC itself, see the PLC
manufacturer’s instruction manual.
The “PLC Write Mask” field allows you to write to selected bits of the
PLC register. The “PLC Write Mask” field defaults to the value FFFF,
specifying that this I /O Block writes all 16 bits of the “Value From
Source” field to all 16 bits of the PLC register and overwrites the current
contents of that PLC register.
You can change the mask value to allow the I /O Block to write only to
specific bits in the register as shown in Figure 9.3.13. A Write Mask
value of 000F would allow the I/O Block to write to bits a through d only.
In the following example, the I/O Block will be allowed to write to only
the j bit (Start) and the k bit (Stop) of the PLC register; therefore the
value 0600 will be used in the Write Mask. Table 9.3.8 provides a
binary--to--hexadecimal conversion chart.
PLC 7
Register 1000
Port A ponml k j ihgfedcba
0 0000 10000000 000
Port B
Register 1001
Port ponmlkjihgfedcba
0 2 0 0 0 2 0 0 0 4 0 0
Source Value
0000-- 0010 --0000-- 0000 0000-- 0010 --0000-- 0000 0000-- 0100 --0000-- 0000
F F F F 0 6 0 0 0 6 0 0
Write Mask(1)
yyyy-- yyyy --yyyy-- yyyy nnnn-- nyyn --nnnn-- nnnn nnnn-- nyyn --nnnn-- nnnn
Resulting
Register Contents 0000-- 0010 --0000-- 0000 1111-- 0010 --1111-- 0000 1111-- 0100 --1111-- 0000
You can configure a PLC I/O Block to read from and write to a single
PLC register. A block configured to read always reads all 16 bits in the
register even though some bits may never be used as inputs. The
“Write Mask” field, discussed in the previous section, is used to write to
specific bits in the register.
In the example shown in Figure 9.3.14, the I/O Block is linked to the
discrete section of a ControlBlock. Only two of the 16 step outputs, a
Start command (Step h) and a Stop command (Step g), are to be
passed on to PLC register 1000 as bits h and g, as determined by the
Write Mask value 00C0. The PLC uses these commands as inputs to a
motor control logic configuration. Bits o and p in the PLC register
represent the Run Confirm and Off Confirm states of the motor.
FlexTerm
PLC 7
Controller Processor
Register 1000
Card Port A
po n m l kj i hg f e dc b a
Port B 0 1 0 0 00 0 0 1 0 0 0 0 0 0 0
Port
CB I/O
Port
1000h Start
Start Command
to Field
1000g Stop
Stop Command
to Field
Start Confirm
1000o Closed
Stop Confirm
1000p Open
Section 4:
PLC Interface Redundancy
The PLC interface supports FIC redundancy for some types of PLCs.
This section is divided into the following subjects:
D FIC redundancy information for all supported PLCs
D FIC redundancy for Allen-Bradley PLCs
D FIC redundancy for Modicon PLCs
D FIC redundancy for Mitsubishi PLCs
D Hints for using the redundant PLC interface
Allows the user to cause an FIC switch manually. When the new
value is entered, the switch occurs.
None = Removes and forced FIC redundancy.
Reset = Resets the FIC redundancy. FIC 1 (port A) becomes
Force Comm the primary FIC and FIC 2 (port B) becomes the
CONF
on FIC backup FIC.
1 = Disables redundancy and forces communication with
FIC 1.
2 = Disables redundancy and forces communication with
FIC 2.
Octal
Address of the Allen-Bradley highway interface module that is
AB Highway Number
CONF connected to the RS3 Field Interface Card on Port A; appears
Station # (See
only for Allen Bradley PLCs.
Table 9.2.4.)
or
Mitsubishi Address of the primary station communicating through port A; 0 to 32
CONF
Station # appears only for Mitsubishi PLCs. (Decimal)
Figure 9.4.2 shows a typical PLC Interface FIC redundancy scheme for
Allen-Bradley PLCs. When configuring the PLC Configuration screen:
D The “AB Highway Station” and “Health Addr” fields must be
specified in octal.
D The “PLC Health Num” field must be specified in decimal.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
Allen-Bradley Allen-Bradley
RS232/Data Highway RS232/Data Highway
Interface Interface
Allen-Bradley PLC
Interface Module
Allen-Bradley PLC
Figure 9.4.2. Typical PLC Interface FIC Redundancy for Allen-Bradley PLCs
Figure 9.4.3 shows a typical PLC Interface FIC redundancy scheme for
Modicon PLCs.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
Modicon PLC
Figure 9.4.3. Typical PLC Interface FIC Redundancy for Modicon PLCs
If the health of Station #23 (in the example in Figure 9.4.4) is detected
as bad, then all communications will occur through port B to Station
#25, the backup station.
Communication FlexTerm
Controller 1 2 3 4 5 6 7 8
Processor
Port A Port B
RS232 RS232
C C
P P
...... ......
U U
Listed below are some hints on using the redundant PLC interface:
- FIC switches from primary to secondary
D An FIC might switch when communications are interrupted, a
cable is pulled out, there is no reply, there is a bad FIC, etc.
When a fault occurs on the primary FIC, it switches to the
secondary FIC. You must switch communications from the
secondary FIC (port B) to the primary FIC (port A) manually.
Force the switch using the PLC Configuration screen “FIC reset”
field.
- Assigning an address to a redundant PLC
D Remember that, depending on the type of PLC you have, you
can define any address that you need. For more information
about PLC address ranges, see Section 3 of this chapter.
- Setting up ports A and B
D To ensure that the primary PLC can communicate with the
secondary PLC, be sure to set up ports A and B the same.
- Redundancy on PLC end
D Remember to check with your PLC vendor to find out what is
required on the PLC end to have PLC redundancy.
Section 5:
PLC Guidelines and Reference Material
PLC Guidelines
Following are items to verify if there are problems with the PLC
interface:
D The Allen-Bradley PLC must be in Run mode during PLC setup,
not Program mode.
D Make sure that the baud rate jumpers on the PLC controller are
set to the industry standard. For more information on the baud
rate jumper positions, see SV: 3.
D If you get the following error message: “Bad PLC FIC Card,”
communications have been interrupted.
Check the following things:
— Are the communication parameters set correctly—baud rate,
data bits, addresses, device type? Communication
parameters have a high probability of being the problem.
— Is the cable disconnected on either end?
— Is the card pulled out?
— Is the card bad? Hardware has a low probability of being the
problem?
Reference Material
NOTE: The Loopback Test works on only one port at a time and does
not function at 1200 baud. FIC redundancy must be disabled to use this
test.
Figure 9.5.2 and Figure 9.5.3 show functional diagrams for the
RS422/RS232 port I/O card and the RS422/RS422 port I/O card.
Figure 9.5.2 shows a block diagram of the RS422/RS232 Port I/O card.
Power is supplied to the Port I/O card through a 2-A board power fuse
(F1). The fuse supplies 30 V DC to the power regulator on the card. The
power regulator generates and regulates the DC voltages. The isolated
voltages are used to power all components on the PLC side of the
optical isolation. The non-isolated +5 V DC is used on the Controller
Processor side of the optical isolation. Optical isolation isolates the PLC
data from the Controller Processor.
Receive and transmit data between the Port I/O card and the Controller
Processor are in RS422 format. The data must pass through four
jumpers (HD1A through HD1D), which determine if communication port
A or B is being used. In normal operation, communication port A is
used. Figure 9.5.3 shows the jumper settings for port A.
The data passing between the Port I/O card and the PLC is in RS232
format. A set of jumpers (HD2A and HD2B) enable the Port I/O card to
be designated as the modem or terminal side of the RS232 interface.
Set the jumpers as a pair with both jumpers in the same position.
If the Port I/O card is talking to one PLC, set jumper HD3 to the S
(single point) position. This pulls RTS and CTS high all of the time. If
the card is talking to more than one PLC, set the jumper to the M
(multi-drop) position. In the M position, the card uses the CTS and RTS
from the PLCs.
Figure 9.5.3 shows a block diagram of the RS422/RS422 Port I/O card.
Cable Requirements
NOTE: For the cables above, jumper the PLC FICs in the TERMINAL
position; for a straight-through RS-232 cable, jumper the PLC FIC in the
MODEM position. A normal serial cable is not recommended but may
work in some situations.
The Allen-Bradley Data Highway One and Data Highway Plus are
similar to the RS3 PeerWay:
D The Allen-Bradley Data Highways use a twinax cable with
termination at both ends.
D Because only one cable is used, there is no redundancy.
D Each device on the Data Highway has a unique station address,
just like the node numbers on the PeerWay. Allen-Bradley
station addresses, however, use the octal numbering system
(0..7,10..17,20..27, etc.).
D The minimum configuration for the RS3 to talk to an
Allen-Bradley PLC is one PLC and one AB communications
module, each with their own unique station address.
The jumpers on the controller board should be set as follows for the
PLC and Multi-Purpose Controller Processor boards:
D Jumpers HD21 through HD24 select 9600 baud.
D Jumpers HD6 through HD8 select which additional image to load.
This should be the same as the additional image number on the
ControlFile Status screen which contains the PLC image. This is
not the setup for the Controller Processor II. See SV:4-2 for
details.
Jumpers on FICs
PLC-2 Setup
The PLC-2 has one data storage area. The RS3 can read or write to
any word/register in that storage area. Two fields on the I/O Block
Configuration screen (Figure 9.5.5) allow you to define this interface to
a PLC-2:
D The “PLC Number” indicates which PLC-2 on the Data Highway
to access. The number that you enter in this field is the decimal
equivalent of the octal Data Highway station address of the
PLC-2.
For example, to read data from a PLC-2 at octal station address
36, enter 30 in the “PLC Number” field.
D The “PLC Word Address” field indicates a word/register in the
PLC-2. This field accepts only an octal number. The memory on
the PLC-2 is also addressed in octal.
For example, to read word/register number 42 from the PLC-2,
enter 42 in the “PLC Word Address” field.
PLC-2 Example
NOTE: The number entered in the “AB Highway Station #” field on the
PLC Configuration screen has no effect on which word/register or which
PLC-2 is accessed.
PLC--3 Setup
The PLC-3 has multiple data input/output areas called input files, unlike
the PLC-2 which only has one data storage area. The input files are
used for bidirectional transfer of data into and out of the PLC-3.
Two fields on the I/O Block Configuration screen (Figure 9.5.5) allow
you to define this interface to a PLC-3.
D The “PLC Number” indicates which PLC-3 on the Data Highway
to access. The number that you enter in this field is the decimal
equivalent of the octal Data Highway station address of the
PLC-2.
For example, to read data from a PLC-2 at octal station address
36, enter 30 in the PLC Number field.
D The “PLC Word Address” field indicates a word/register within an
input file in the PLC-3. This field accepts only an octal number.
The memory on the PLC-3 is also addressed in octal.
For example, to read word/register number 42 from the PLC-3,
enter 42 in the “PLC Word Address” field.
PLC--3 Example
PLC-5 Setup
The PLC-5 has multiple data input/output areas called files, unlike the
PLC-2, which only has one data storage area.
NOTE: The RS3 can access any file type in the PLC-5 except floating
point. The integer or N file type is preferred.
Two fields on the I/O Block Configuration screen (Figure 9.5.5) allow
you to define this interface to a PLC-5.
D The “PLC Number” indicates which PLC-5 on the Data Highway
to access. The number that you enter in this field is the decimal
equivalent of the octal Data Highway station address of the
PLC-5.
For example, to read data from a PLC-2 at octal station address
36, enter 30 in the PLC Number field.
D The “PLC Word Address“ field indicates a word/register within the
file in the PLC-5. This field accepts only an octal number
although the PLC-5 uses decimal addresses within the file. The
actual word/register accessed on the PLC-5 is the decimal
equivalent of the octal number that you enter in the “PLC Word
Address” field.
For example, to read word/register number 38 in the file on the
PLC-5, enter 46 in the “PLC Word Address” field.
PLC--5 Example
Alarm Messages
Alarm messages can occur when you use or communicate with a PLC
interface.
Table 9.5.1 provides some of the alarm messages that can occur when
you use the PLC interface.
PLC Address Out of Range An attempt has been made to read from or write to an address which is out
of range for the PLC.
PLC Read Exception ## An error code returned to the control system from the PLC device. The
PLC Write Exception ## error code can be referenced in the PLC manuals.
Too Many PLCs Configured An attempt has been made to communicate with more than 32 PLC
devices from one controller.
Writing to a Read Only An attempt has been made to write to a read-only address. Generally
Address limited to Modbus configurations.
Table 9.5.2 provides some of the alarm messages that can occur as a
result of communicating with a PLC device.
No PLC Communication An unsuccessful attempt has been made to communicate with the PLC
device. This alarm is generated after the number of retries specified on the
PLC Configuration screen has been attempted and the message timeout
has expired. An attempt to reestablish communications will occur in five
seconds.
Out of Comm Bandwidth There is not enough communication time to meet all read/write requests.
A Break Was Caught An illegal break character was received from the slave.
Bad CRC/Checksum on The calculated CRC or checksum for a message from a slave was wrong.
Message
Premature End of Message End of Message (EOM) was detected before it was expected.
An Overrun Error Occurred After an EOM was detected, extra characters were received.
Bad Message Received A message which did not fit any of the expected formats was received.
Table 9.5.3 lists the error codes that can be returned from a Mitsubishi
PLC. If several errors occur simultaneously, the error with the lower
number takes precedence. For additional information, and corrective
action, see the Mitsubishi user’s manual for the AJ71C24 computer
interface module.
Error Code
Description
(Hexadecimal)
00H Disable during run: invalid access has been made during the run.
01H Parity error: parity check result does not match the odd/even parity setting.
Sum check error: sum check result of received data does not match sum check of data
02H
transmitted.
04H Framing error: data does not comply with stop bit setting.
Overrun error: new data has been sent before AJ71C24 could complete reception of
05H
preceding data.
06H Character area error: characters in data areas doe not match the mode set.
Character error: characters other than A to Z, 0 to 9, space, and control codes have
07H
been received.
08H PLC access error; buffer memory is unable to communicate with the PLC.
PLC number error: defined PLC number does not exist; number specified in control
10H
protocol must be FFH.
Mode error: invalid processing request mode has been sent; processing request
11H
command has been corrupted.
Special function unit specification error: addressed I/O location does not contain a
12H
special function unit.
Error in designation of program step number; step number is outside range designated
13H by PLC CPU parameters; or a subsequence program that does not exist was
designated.
Data link error: system attempted to access a station with which communications have
20H
been disconnected.
Special function unit bus error: memory access to special function unit cannot be made
21H
(for command TR, TW).
Chapter 10:
Configuring Discrete Blocks
List of Figures
Figure Page
10.1.1 DIB Block Configuration Screen—Filter Configuration . . . . . . . . . . . . . . 10-1-2
10.1.2 DIB Block Configuration Screen—Field Contact
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-4
10.1.3 DIB Block Configuration Screen—Message Pair
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-5
10.1.4 DIB Block Configuration Screen—Descriptor Configuration . . . . . . . . . 10-1-6
10.1.5 DIB Block Configuration Screen—Fail Safe Configuration . . . . . . . . . . 10-1-7
10.1.6 DIB Block Configuration Screen—FIM Switch Voltage
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-9
10.1.7 DIB Block Configuration Screen—Event Configuration . . . . . . . . . . . . . 10-1-10
10.1.8 DIB Block Configuration Screen—Alarm Configuration . . . . . . . . . . . . . 10-1-11
10.1.9 DIB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-13
10.1.10 Delay Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-18
10.1.11 Delay--on Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-19
10.1.12 Delay--off Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-21
10.1.13 Glitch Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-23
10.1.14 Settle Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-25
10.1.15 Extend Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-27
10.1.16 DIB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-29
10.2.1 DOB Block Configuration Screen—Contact Type
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-2
10.2.2 DOB Block Configuration Screen—Output Hold
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-3
10.2.3 Output Hold Off (Delay On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-4
10.2.4 Output Hold On (Delay Off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-5
10.2.5 Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-6
10.2.6 DOB Block Configuration Screen—Message Pair
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-7
10.2.7 DOB Block Configuration Screen—FIM Switch Volt
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-9
10.2.8 DOB Block Configuration Screen—Fail Safe Configuration . . . . . . . . . 10-2-10
10.2.9 DOB Block Configuration Screen—Alarm Configuration . . . . . . . . . . . . 10-2-11
10.2.10 DOB Block Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-12
10.2.11 DOB Functional Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-15
List of Tables
Table Page
10.1.1 Discrete Input Block (DIB) Filter Options . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-3
10.1.2 Discrete Input Block (DIB) Configuration Screen Fields . . . . . . . . . . . . 10-1-14
10.1.3 Delay Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-18
10.1.4 Delay--on Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-20
10.1.5 Delay--off Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-22
10.1.6 Glitch Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-24
10.1.7 Settle Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-26
10.1.8 Extend Filter Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1-28
10.2.1 Output Hold Off (Delay On) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-4
10.2.2 Output Hold On (Delay Off) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-5
10.2.3 Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2-6
10.2.4 Discrete Output Block (DOB) Configuration Screen Fields . . . . . . . . . 10-2-13
Section 1:
Configuring a Discrete Input Block (DIB)
The Discrete Input Block (DIB) is used with discrete hardware while the
Contact Input Block is used with contact hardware.
You can use a DIB filter to eliminate contact bounce by filtering the DIB
Raw State when it is received to determine the Output State. The
shaded area of Figure 10.1.1 shows the section of the DIB Block
Configuration screen used for configuring a DIB filter. To configure a
filter, the block must be in Manual mode.
Table 10.1.1 lists and briefly describes the DIB filter options available.
The effect on the Output State by the FIM is explained in detail in “DIB
Filter Options” later in this section.
- To select a filter type:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Filt Type” field and press [NEXT OPTION] to select
the desired filter type. Press [ENTER].
3. For options other than “None”, cursor to the “Filt Time” field to
assign the desired filter time. Enter the time in seconds using a
minimum of 0.00 seconds and a maximum of 1023.75 seconds.
Press [ENTER].
4. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
None No effect on the block. The Output State always equals the Raw State.
The Output State turns on (or off) after the Raw State has been on (or off) for at
Delay
least the duration of the time configured in the “Filt Time” field.
The Output State turns on after the Raw State has been on for at least the duration
Delay On (D--On)
of the time configured in the “Filt Time” field.
The Output State turns off after the Raw State has been off for at least the duration
Delay Off (D--Off)
of the time configured in the “Filt Time” field.
An Output State change is held for at least the interval assigned in the “Filt Time”
field. A change in the Raw State during the hold time causes the Output State to
Glitch
respond to the change after the hold expires and again hold for the time assigned
in the “Filt Time” field.
An Output State change is held until a matching Raw State is maintained for the
Settle interval assigned in the “Filt Time” field. A change in the Raw State causes a
change in the Output State.
The Output State is held for the interval assigned in the “Filt Time” field. The
Extend
Output State responds only to the most recent Raw State at the end of the hold.
You can configure a DIB to allow inversion of the field contact position.
The shaded area of Figure 10.1.2 shows the section of the DIB Block
Configuration screen used for configuring the DIB field contact position.
To configure the field contact, the block must be in Manual mode.
Configuring a Descriptor
You can configure a descriptor for a DIB block. The descriptor appears
on the Alarm Message and Alarm Lists. The shaded area of
Figure 10.1.4 shows the section of the DIB Block Detail Configuration
screen used to assign descriptors to a DIB.
The “Fail Safe” field allows you to configure the type of failure option for
loss of communication of the FIM with the controller.
D “Hold” indicates that the controller block holds the last valid
Output State if communication is lost. “Hold” is the default
selection.
D “On” indicates that the “Output State” is set to on.
D “Off” indicates that the “Output State” is set to off.
The shaded area of Figure 10.1.5 shows the section of the DIB Block
Configuration screen used for setting the DIB fail safe.
FIM Switch Voltage specifies the voltage level for the transition point
between low (off) and high (on) for FIM inputs. There is a 12.5%
hysteresis above and below the configured voltage level. For example,
if the switch voltage is set to 10 volts, it switches on at 11.25 volts (10
volts plus 12.5%) and won’t switch off until it reaches 8.75 volts. The
FIM A/D convertor also has a 5% tolerance.
When the FIM is initially configured, the FIM switch voltage will come up
in its default setting of 2.447 volts. This setting will have to be updated
for most applications. The FIM Switch Voltage is configured on the first
point of the FIM. Because this voltage is applied to all points on the
FIM, the block at address 1 must remain configured. The nominal
Switch Voltage should be set at 50% of the supply voltage for the
discrete I/O points. For instance, if output voltage switched at the field
is +24 volts, the FIM voltage should be set at +12.0 volts. For DIO
marshalling panels that use optically isolated modules, including the
High Density Isolated Discrete TP, Isolated Discrete TPA, and Isolated
Discrete TPB, the switch voltage should be set at 2.3 volts (which
actually appears as 2.294). The shaded area of Figure 10.1.6 shows
the section of the DIB used to specify the FIM Switch Voltage.
WARNING
You must not delete the DIB at address 1 on any FIM.
Deleting this block establishes a condition that can cause
all other points on a FIM to lose their switch voltage after
that FIM reboots. If the DIB at address 1 is deleted, all
other points continue to operate correctly until the FIM is
rebooted. (Rebooting can be caused by events such as a
power loss or online replacement.) Following a FIM reboot,
all points lose the switch voltage that was configured in a
block that no longer exists. As a result, the switch voltage
defaults to .3 volts; and incorrect or random switching of
the inputs can occur.
FIMs used on termination panels without optical isolation
modules, including direct connect and multi-FIM TPs, must
not have the switch voltage set to less than 2.447 if any of
the input signal voltages is equal to or greater than 10
volts. Doing so could cause thermal problems and reduce
the life of the product.
Configuring an Event
The shaded areas of Figure 10.1.8 show the sections of the DIB Block
Configuration screen used for configuring DIB alarms. An alarm may be
generated depending on the on or off state of the Output State. If no
alarm is desired, select “None”. “None” is the default alarm condition.
Figure 10.1.8 shows a sample DIB block that generates a critical alarm
when the Output State is off.
- To configure a DIB input alarm:
1. Cursor to the “When” field and press [NEXT OPTION] to select
the condition that is to trigger the alarm. Press [ENTER].
2. Cursor to the “Alarm Type” field and press [NEXT OPTION] to
select the desired type of alarm to be generated. Press
[ENTER].
Access
Field Description Allowable Entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
NONE, AIB,CIB,
DIB,AOB,COB,DOB
Block Type Conf Type of input/output block.
ADS, MIB, PLCB, SIB,
RIOB, VIB, PIOB, TIB
Raw State NA Displays the raw (unfiltered) input state. Display only
The signal value at the output of the block. Toggle (OFF, ON),
Output State Oper
Must be in Manual mode to manipulate. Clear (OFF), Set (ON)
Message Pair Conf Assigns a message pair to the output state field. *1--*100, 1--155
0 -- 999 seconds
Displayed only when an option other than none is Time resolution is to
Filt Time Conf
chosen for “Filt Type”. the smallest 0.25
seconds for inputs.
Table 10.1.2. Discrete Input Block (DIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Any characters up to
Descriptor Conf User configured descriptor.
24
Table 10.1.2. Discrete Input Block (DIB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Use one of the filter options available in the DIB to manipulate the Raw
State. This section explains the effect on the Output State relative to
the Raw State supplied by the FIM. It also provides a brief description
and timing diagram for each of the following filter types:
D None filter option
D Delay filter option
D Delay On filter option
D Delay Off filter option
D Glitch filter option
D Settle filter option
D Extend filter option
Using a delay filter on a DIB block delays the DIB by the interval
assigned in the “Filt Time” field. The delay has an effect on the DIB
block when the Raw State changes to on (0 to 1) and changes to off (1
to 0) (0 = off, 1= on). If the Raw State changes but does not maintain
that state for greater than or equal to the “Filt Time”, the Output State
does not change.
Figure 10.1.10 shows the effect of a delay filter used on a DIB block.
Table 10.1.3 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5 T6
1
Raw
State
0
1
Output
State
0
T4 Raw State changes to on condition. Output State remains on because the duration
of the Raw State off condition was less than the
Filt Time.
T5 Raw State changes to off condition. Output State remains on because there has
been no uninterrupted off Raw State condition
greater than or equal to the Filt Time.
T6 Raw State remains off. Output State changes to off when the Raw
State off exceeds the Filt Time.
* The Output State is equal to the Filtered State when the block is in Auto Mode.
The D--On filter delays the DIB output by the interval assigned in the
“Filt Time” field. The delay has an effect only when the Raw State
changes to on (0 to 1). The Output State responds immediately when
the Raw State changes to off (1 to 0).
Figure 10.1.11 shows the effect of a D--On filter used on a DIB block.
Table 10.1.4 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5
1
Raw
State
0
Output 1
State
duration
TIME = Filt Time duration
< Filt Time
T3 Raw State changes to off. Output State changes to off. Output State
always changes immediately to off in response
to Raw State changing to off.
T4 Raw State changes to on. Output State remains off and begins delay
interval.
T5 Raw State changes to off. Output State remains off. Delay is canceled
when the Raw State is changed to off.
* The Output State is equal to the Filtered State when the block is in Auto Mode.
The delay off filter delays the DIB Output State by the interval assigned
in the “Filt Time” field. The delay has an effect only when the Raw State
is changing to off (1 to 0). The Output State responds immediately
when the Raw State changes to on (0 to 1).
Figure 10.1.12 shows the effect of a delay off filter used on a DIB block.
Table 10.1.5 describes the Raw State effect on the Output State at
different times.
T0 T1 T2 T3 T4 T5 T6
1
Raw
State 0
1
Output
State 0
duration
TIME = Filt duration
Time < Filt Time
T1 Raw State changes to on. Output State changes to on. Output State
always changes immediately to on in response
to the Raw State changing to on.
T2 Raw State changes to off. Output State remains on and begins delay
interval.
T3 Raw State remains off. Output State changes to off in response to the
Raw State changing to off at T2 plus interval
assigned in “Filt Time” field of DIB.
T4 Raw State changes to on. Output State changes to on. Output State
always changes immediately to on in response
to the Raw State changing to on.
T5 Raw State changes to off. Output State remains on and begins delay
interval.
T6 Raw State changes to on. Output State remains on. Delay is canceled
when the Raw State is changed to on.
* The Output State is equal to the Filtered State when the block is in Auto Mode.
A glitch filter holds the DIB Output State each time that the Output State
changes for a minimum time as specified in the “Filt Time” field. If the
Raw State changes state during the hold time, the Output State
responds to that change after the hold expires and again holds for the
time defined by “Filt Time”. In the event of multiple Raw State changes
during the hold time, the Output State responds to the first and last Raw
State changes only.
Figure 10.1.13 shows the effect of a glitch filter used on a DIB block.
Table 10.1.6 describes the Raw State effect on the Output State at
different times.
T2 T4 T6 T10 T11
T0 T1 T3 T5 T7 T8 T9 T12 T13
1
Raw
State
0
1
Output
State
0
duration
TIME = Filt Time
T1 Raw State rises to on. Output State changes to on. Duration defined by
Filt Time begins.
T2 Raw State falls to off. Output State remains on in response to T1 for the
duration of the Filt Time.
T3 Raw State remains off. Output State changes to off in response to Raw
State falling to off at T2.
T4 Raw State rises to on. Output State remains off in response to T2 for the
duration of the Filt Time.
T5 Raw State remains on. Output State changes to on in response to the Raw
State rising to on at T4.
T6 Raw State falls to off. Output State remains on in response to T4 for the
duration of the Filt Time.
T7 Raw State rises to on. Output State remains on in response to T4 for the
duration of the Filt Time.
T8 Raw State remains on. Output State changes to off in response to the Raw
State falling to off at T6.
T9 Raw State remains on. Output State changes to on in response to the Raw
State rising to on at T7.
T10 Raw State falls to off. Output State remains on in response to T7 for the
duration of the Filt Time.
T11 Raw State rises to on. Output State remains on in response to T7 for the
duration of the Filt Time.
T12 Raw State remains on. Output State changes to off in response to the Raw
State falling to off at T10.
T13 Raw State remains on. Output State changes to on in response to the Raw
State rising to on at T11.
* The Output State is equal to the Filtered State when the block is in Auto Mode.
A settle filter holds the DIB output change until a Raw State of the same
state is maintained for a minimum time equal to “Filt Time”. At that time
a change in the Raw State causes an immediate change in the Output
State. Figure 10.1.14 shows the effect of a settle filter used on a DIB
block. Table 10.1.7 describes the Raw State effect on the Output State
at different times.
This filter type creates a state where the Output State refuses to change
until the Raw State stays equal to the Output State for the filter time.
Once the Raw State stays equal to the Output State for the filter time,
the Output State will change immediately when the Raw State changes.
Note that when the Raw State remains 0 at T10, the output will remain 1
forever (until another Raw State change). Glitches less than the filter
time will have this effect, which may or may not be desirable.
T0 T1 T2 T3 T4 T5 T6 T7 T8 T9 T10
1
Raw
State
0
1
Output
State
0
T2 Raw State changes to off. Output State changes to off immediately because
the interval between T1 and T2 was equal to Filt
Time.
T3 Raw State changes to on. Output State remains off because the interval
between T2 and T3 was less than the Filt Time.
T6 Raw State changes to off. Output State remains on because the interval
between T5 and T6 was less than the Filt Time.
T8 Raw State changes to off. Output State changes to off immediately because
the interval between T7 and T8 was greater than
the Filt Time.
T10 Raw State changes to off. Output State remains on because the Output State
was not equal to the Raw State for the filter time.
The Output State will remain different from the Raw
State forever until the Raw State changes.
* The Output State is equal to the Filtered State when the block is in Auto mode.
An extend filter holds the DIB Output State for the time assigned in the
“Filt Time” field. Subsequent Raw State changes which occur within the
output hold time are ignored, with the exception of the most recent Raw
State at the end of the hold to which the Output State responds.
Figure 10.1.15 shows the effect of an extend filter used on a DIB block.
Table 10.1.8 describes the Raw State effect on the Output State at
different times.
T2
T0 T1 T3 T4 T5 T6
Raw
State
0
1
Output
State
0
duration duration
TIME = Filt Time = Filt Time
T4 thru T5 Raw State changes of various durations. Output State remains off in response to Raw
State at T2 for the duration of Filt Time.
Figure 10.1.16 shows the Discrete Input Block functional diagram. All
items within the dotted line reside in the DIB software.
FIM MAN To
NC
Inverter Debounce CB
Filter
AUTO
NO
Alarms
Events
Section 2:
Configuring a Discrete Output Block (DOB)
You can configure a DOB to allow inversion of the field contact position.
The shaded area of Figure 10.2.1 shows the section of the DOB Block
Configuration screen that is used for configuring the DOB field contact
position. To configure the field contact, the block must be in Manual
mode.
Message Pair Þ*1 FIM Switch volt. 5.506 V Fail Safe ÞHold
true ON
false OFF
You can delay the DOB output state for a designated hold time
depending on the output hold configuration. The block output state can
be held on (Off), held off (On), set to pulse (Pulse), or not held at all
(None). “None” is the default selection. If you choose On, Off, or Pulse
options, a “Hold Time” field appears. In the “Hold Time” field, configure
the number of seconds, from 0 to 511, that the output state is to hold.
To configure output hold, the block must be in Manual mode.
The shaded area of Figure 10.2.2 shows the section of the DOB Block
Configuration screen used for configuring output hold for a DOB. The
block in Figure 10.2.2 has an On output hold configured for 5 seconds.
- To set the output hold:
1. Cursor to the “Mode” field and press [NEXT OPTION] to select
Manual; then press [ENTER].
2. Cursor to the “Output Hold” field and press [NEXT OPTION] to
select the desired hold condition. Press [ENTER]. If an output
hold is selected, the “Hold Time” field appears.
3. Cursor to the “Hold Time” field and enter the number of seconds
for which the output state is to be held. Press [ENTER].
4. Cursor to the “Mode” field and press [NEXT OPTION] to select
Auto; then press [ENTER].
Figure 10.2.3 shows the effect of configuring the “Output Hold” field to
stay on. Table 10.2.1 describes the field input effect on the block output
at different times.
T0 T1 T2 T3 T4 T5 T6
1
Block Input
0
1
Block Output
0
Hold
TIME Time Hold
Time
T0 Initial condition. Block input off. Initial condition. Block output off.
T1 Block input changes to on condition. Output remains off because the hold time
interval has not elapsed.
T2 Block input remains on. Hold time interval is Output changes to on condition in response to
complete. the block input change to on at T1 and the
interval assigned in “Hold Time” field of DOB
has expired.
T4 Block input changes to on condition. Output remains off because the hold time
interval has not elapsed.
T5 Block input changes to off condition. Output remains off because the input was not
in the on state for the duration of the hold
time.
Figure 10.2.4 shows the effect of configuring the “Output Hold” field to
stay off. Table 10.2.2 describes the field input effect on the block output
at different times.
T0 T1 T2 T3
1
Block Input
0
1
Block Output
0
TIME Hold
Time
T0 Initial condition. Block input off. Initial condition. Block output off.
T2 Block input changes to off condition. Output remains on for the duration of the hold
time.
T3 Block input remains off. Output changes to off condition because the
hold time interval is complete.
Figure 10.2.5 shows the effect of configuring the “Output Hold” field for
the pulse option. Table 10.2.3 describes the field input effect on the
block output at different times.
T0 T1 T2 T3 T4 T5 T6
1
Block Input
0
1
Block Output
0
T0 Initial condition. Block input off. Initial condition. Block output off.
T2 Block input remains on. Output changes to off condition when the hold time
interval is complete.
T3 Block input changes to off condition. Output remains off. This resets the hold time.
T5 Block input changes to off condition. Output changes to off condition. Because the hold
time interval was not complete the output follows the
input.
Message Pair Þ*1 FIM Switch volt. 5.506 V Fail Safe ÞHold
true ON
false OFF
FIM Switch Voltage specifies the voltage level for the transition point
between low (off) and high (on) for FIM inputs. There is a 12.5%
hysteresis above and below the configured voltage level. For example,
if the switch voltage is set to 10 volts, it switches on at 11.25 volts (10
volts plus 12.5%) and won’t switch off until it reaches 8.75 volts. The
FIM A/D convertor also has a 5% tolerance.
When the FIM is initially configured, the FIM switch voltage will come up
in its default setting of 2.447 volts. This setting will have to be updated
for most applications. The FIM Switch Voltage is configured on the first
point of the FIM. Because this voltage is applied to all points on the
FIM, the block at address 1 must remain configured. The nominal
Switch Voltage should be set at 50% of the supply voltage for the
discrete I/O points. For instance, if output voltage switched at the field
is +24 volts, the FIM voltage should be set at +12.0 volts. For DIO
marshalling panels that use optically isolated modules, including the
High Density Isolated Discrete TP, Isolated Discrete TPA, and Isolated
Discrete TPB, the switch voltage should be set at 2.3 volts (which
actually appears as 2.294). The shaded area of Figure 10.2.7 shows
the section of the DOB used to specify the FIM Switch Voltage.
WARNING
You must not delete the DIB at address 1 on any FIM.
Deleting this block establishes a condition that can cause
all other points on a FIM to lose their switch voltage after
that FIM reboots. If the DIB at address 1 is deleted, all
other points continue to operate correctly until the FIM is
rebooted. (Rebooting can be caused by events such as a
power loss or online replacement.) Following a FIM reboot,
all points lose the switch voltage that was configured in a
block that no longer exists. As a result, the switch voltage
defaults to .3 volts; and incorrect or random switching of
the inputs can occur.
FIMs used on termination panels without optical isolation
modules, including direct connect and multi-FIM TPs, must
not have the switch voltage set to less than 2.447 if any of
the input signal voltages is equal to or greater than 10
volts. Doing so could cause thermal problems and reduce
the life of the product.
Message Pair Þ*1 FIM Switch volt. Þ5.506 V Fail Safe ÞHold
true ON
false OFF
The “Fail Safe” field allows you to configure the type of failure option for
loss of communication with the FIM.
D “Hold” indicates that the FIM holds the last valid output value if
communication is lost. “Hold” is the default selection.
D “Off” indicates the FIM turns the output off if communication is
lost.
The shaded area of Figure 10.2.8 shows the section of the DOB Block
Configuration screen used for setting the DOB fail safe.
Message Pair Þ*1 FIM Switch volt. 5.506 V Fail Safe ÞHold
true ON
false OFF
The shaded area of Figure 10.2.9 shows the section of the DOB Block
Configuration screen used for configuring the alarm priority for DOB
hardware alarms. If the RS3 generates more than one
unacknowledged hardware alarm at one time, the corresponding alarm
banner for each alarm appears at the bottom of the console screen in
the order of priority. Configure the priority of a DOB block hardware
alarm in the “Priority” field on the DOB Block Configuration screen.
Message Pair Þ*1 FIM Switch volt. 5.506 V Fail Safe ÞHold
true ON
false OFF
Message Pair Þ*1 FIM Switch volt. 5.506 V Fail Safe ÞHold
true ON
false OFF
Access
Field Description Allowable Entries
Level
Up to 16 alphanumeric
Block Tag Conf User defined block tag.
characters
Source State NA The value being received from the block. Display only
The signal value at the output of the block. TOGGLE (OFF, ON),
Output State Oper CLEAR (OFF), SET
Must be in Manual mode to configure. (ON)
Message Pair Conf Assigns a message pair to the output state field. *1--*100, 1--155
Table 10.2.4. Discrete Output Block (DOB) Configuration Screen Fields (continued)
Access
Field Description Allowable Entries
Level
Figure 10.2.11 shows the DOB functional block diagram. All items
within the dotted line reside in the DOB software.
Console Keyboard
Off Off
MAN
RS3t
I/O Block Configuration
Index
Health Num field, PLC Configuration scree, 9-4-4 relationship to ControlBlocks, 1-1-5
hexadecimal--to--binary conversion char, 9-3-12 relationship to hardware, 1-1-5
HIA (Highway Interface Adapter), 1-3-2 role in control loop, 1-1-4
High Cutoff field, pulse input PIOB, 3-2-12 types, 1-1-2
hints Input Scale field, MIB, 7-1-8, 7-2-3
configuring analog blocks, 2-3-1– 2-3-2 input signal hysteresis, 3-2-5
configuring HOB, 8-2-30 Input State field, COB, 6-2-10
configuring I/O blocks, 1-5-1 input/output blocks, general description, 1-1-1–
configuring MIB, 7-3-1– 7-3-2 1-1-2, 1-1-4– 1-1-6
configuring PIOB, 3-3-1– 3-3-2 Inst Bias field, AIB, 2-1-7, 2-1-13
configuring RIOBs, 5-3-1 Inst High field
configuring SIB, 8-3-3 AIB, 2-1-13
configuring TIB, 4-2-2 MIB, 7-2-5
configuring VIB, 8-3-3 SIB, 8-1-16
contact blocks, 6-3-1 TIB, 4-2-6
TIB configuration, 4-3-1 Inst Low field
HOB, 1-1-3, 8-2-1 AIB, 2-1-13
accessing screens, 8-2-4 MIB, 7-2-5
communicating with SMART field devices, 8-2-1 SIB, 8-1-16
HART Output Device Configuration screen, TIB, 4-2-6
8-2-18– 8-2-24 Inst. Mode field, HOB, 8-2-15, 8-2-21
HART Output Device Status screen, 8-2-13– instrument alarms, AIB, 2-1-8
8-2-16 instrument bias, AIB, 2-1-7
I/O Block Configuration screen, 8-2-5 internal scaling, 1-1-6
linking, 8-2-29
transmitting data, 8-2-2
using in a control loop, 8-2-3 J
using with Value Input Blocks, 8-2-2
HOB Slot configuration, 8-2-27
Hold Time field jumper positions
COB, 6-2-3, 6-2-10 PLCs and CP, 9-5-9
DOB, 10-2-13 PLCs and FIC, 9-5-9
HW Alarm Code field RS422/RS232 Port I/O card, 9-5-5
PIOB, 3-2-3 jumpers
SIB, 8-1-16 addressing of card cages, 1-3-6
VIB, 8-1-19 hardware address, 1-3-2
hysteresis
contact pulse input PIOB, 3-2-4
in input signal, 3-2-5 K
voltage pulse input PIOB, 3-2-5
KE/KF/KFL module, 9-2-8
I
L
I/O Block Configuration screen, 1-2-1– 1-2-2
bit descriptor and alarm fields, 9-3-17– 9-3-19 Limits field
calling up, 1-2-1 Transmitter Configuration screen, 8-1-42
initial configuration, 1-2-1– 1-2-2 Transmitter Status screen, 8-1-24
simulation configuration, 9-2-7 Limits High field, Transmitter Configuration screen,
write only, 9-3-20 8-1-46
I/O point addressing, discrete, 1-3-21– 1-3-22 Limits Low field, Transmitter Configuration screen,
I/O points addressing, 1-3-14– 1-3-18 8-1-46
analog, 1-3-15 Lo Cutoff field
contact, 1-3-18 AIB, 2-1-13
Multiplexer, 1-3-19 SIB, 8-1-14
MultiPurpose, 1-3-2 loader address options, 3-2-32
pulse, 1-3-17 loader counter function type PIOB
input block analog output, 3-1-7
configuration hints, 1-5-1 binary output, 3-2-32– 3-2-34
definition, 1-1-1– 1-1-2, 1-1-4– 1-1-6 loader function type PIOB
analog output, 3-1-7, 3-2-32, 3-2-35– 3-2-39 miscellaneous devices, MIB, 7-1-5
binary output, 3-1-7, 3-2-32– 3-2-34 Mitsubishi
Log Entry field, Transmitter Maintenance Log error codes, 9-5-20
Screen, 8-1-49 Melsec network, 9-1-14, 9-1-15
Log Files Directory screen, 8-1-47 protocol, 9-1-6
loopback test, PLC, 9-5-3 Mitsubishi PLC, configuration, 9-1-12, 9-1-13
Low Cutoff field Mitsubishi redundancy, 9-4-7
AIB, 2-1-10, 2-1-13 Mitsubishi Station # field, 9-2-13
pulse input PIOB, 3-2-10 PLC Configuration screen, 9-4-4
Modbus
function codes, 9-2-1
M function codes for specific devices, 9-2-2
protocol, 9-1-6, 9-1-11
Mode field
MAIO addressing, 1-3-16 AIB, 2-1-12
Manufacturer ID field. See Mfr ID field AOB, 2-2-7
mapping, 9-3-3– 9-3-9 Block Directory screen, 1-4-3
mask value, 9-3-24 CIB, 6-1-11
masking, within the PLC, 9-3-24 COB, 6-2-10
Max Entries field, Transmitter Maintenance Log DIB, 10-1-14
Screen, 8-1-49 DOB, 10-2-13
Max field HOB, 8-2-5, 8-2-10, 8-2-15, 8-2-20
SIB, 8-1-15 MIB, 7-2-3
VIB, 8-1-18 PIOB, 3-2-3
Max On Time field, pulse output PIOB, 3-2-23, PLCB, 9-3-13
3-2-25 SIB, 8-1-14
Measure From field, pulse input PIOB, 3-2-12 TIB, 4-2-4
Mesg field Transmitter Configuration screen, 8-1-44–
HOB, 8-2-15, 8-2-21 8-1-45
Transmitter Configuration screen, 8-1-46 Transmitter Status screen, 8-1-24
Transmitter Status screen, 8-1-24 VIB, 8-1-18
message pair Mode Type field, RIOB, 5-2-2
DIB, 10-1-5 Modicon interface, 9-3-4
DOB, 10-2-7 Modicon PLC redundancy, 9-4-6
Message Pair field More Transmitter Configuration screen, 8-1-3
CIB, 6-1-5, 6-1-11 Msg Timeout field, PLC Configuration screen,
COB, 6-2-7, 6-2-10 9-2-14
DIB, 10-1-14 Multiplex Input Block. See MIB
DOB, 10-2-13 Multipoint Analog I/O Point addressing. See MAIO
messages, assigning, 8-2-24 addressing
Messages/Seconds field, PLC Configuration screen, MultiPurpose Controller card, 9-1-2
9-2-14 MultiPurpose I/O address, 1-3-1
Mfr ID field MUX (Multiplexer) FlexTerm, 1-3-19
HOB, 8-2-15, 8-2-20 MUX (Multiplexer) inputs addressing, 1-3-19
Transmitter Configuration screen, 8-1-44–
8-1-45
Transmitter Status screen, 8-1-24
MIB, 1-1-2, 7-1-10– 7-1-11, 7-1-14, 7-2-1– 7-2-5
N
alarm configuration, 7-1-11– 7-1-12
block output configuration, 7-1-14 node addressing, 1-3-2
configuration hints, 7-3-1– 7-3-2 Nom Out field
configuration troubleshooting, 7-3-1 AIB, 2-1-12
filter configuration, 7-1-6 MIB, 7-1-10, 7-2-4
functional diagram, 7-2-7 None field, CIB, 6-1-3
I/O Block Configuration screen, 7-2-2 none filter
ranges, 7-1-3– 7-1-5 CIB, 6-1-13
reference material, 7-2-1– 7-2-5 DIB, 10-1-17
scaling configuration, 7-1-8 Num field
signal characterization configuration, 7-1-2 HOB, 8-2-15, 8-2-23
skip function configuration, 7-1-7 Transmitter Configuration screen, 8-1-46
Minimum On Time field, pulse output PIOB, 3-2-25 Transmitter Status screen, 8-1-25
Number of Bad PLCs field, PLC Configuration analog output PIOB configuration, 3-2-28–
screen, 9-2-14 3-2-31
Number of PLCs field, PLC Configuration screen, binary output loader application, 3-2-32
9-2-14 configuration, 3-2-1– 3-2-6, 3-2-7– 3-2-14
Number of Retries field, PLC Configuration screen, configuration hints, 3-3-1– 3-3-2
9-2-14 I/O Block Configuration screen, 3-2-2– 3-2-3
pulse input, 3-1-2– 3-1-3, 3-1-7– 3-1-8
pulse input PIOB, 3-2-4– 3-2-6, 3-2-7– 3-2-8
O pulse input PIOB contact, 3-2-4, 3-2-6
pulse input PIOB voltage, 3-2-5, 3-2-7– 3-2-8
pulse output, 3-1-4– 3-1-5, 3-1-7– 3-1-8
operator arrow, 1-2-3– 1-2-4 troubleshooting, 3-3-1
Orig Node field, Transmitter Maintenance Log PIOB applications, 3-1-1– 3-1-9
Screen, 8-1-49 analog output, 3-1-6
Orig Plant Unit field, Transmitter Maintenance Log pulse input, 3-1-2– 3-1-3
Screen, 8-1-49 pulse output, 3-1-4– 3-1-5
output action PIOB blocks, combining, 3-1-7– 3-1-8
AOB, 2-2-2 Plant Unit field
HOB, 8-2-7 AIB, 2-1-14
output block AOB, 2-2-8
configuration hints, 1-5-1 Block Directory screen, 1-4-3
definition, 1-1-1– 1-1-2, 1-1-4– 1-1-6 Block Status screen, 1-4-5
relationship to ControlBlocks, 1-1-5 CIB, 6-1-12
relationship to hardware, 1-1-5 COB, 6-2-11
role in control loop, 1-1-4 DIB, 10-1-16
types, 1-1-2 DOB, 10-2-14
Output Card Rev field HOB, 8-2-12
AOB, 2-2-8 MIB, 7-2-4
HOB, 8-2-12 PIOB, 3-2-3
Output Device Status field, 8-2-16 RIOB, 5-2-4
Output field SIB, 8-1-15
Transmitter Configuration screen, 8-1-35, TIB, 4-2-6
8-1-41, 8-1-46 VIB, 8-1-19
Transmitter Status screen, 8-1-24 PLC
output hold, DOB, 10-2-3, 10-2-4, 10-2-5, 10-2-6 alarm messages, 9-5-18– 9-5-19
output hold configuration, COB, 6-2-3 reference material, 9-5-2– 9-5-6
Output Hold field PLC coil, 9-3-2– 9-3-8
COB, 6-2-3, 6-2-10 PLC communication
DOB, 10-2-13 alarms, 9-5-19
Output Option field, HOB, 8-2-6, 8-2-10 checking logic steps, 9-2-7
Output State field communicating with an Allen--Bradley PL, 9-2-8,
CIB, 6-1-11 9-2-9
COB, 6-2-10 consecutive addresses for PLC optimization,
DIB, 10-1-14 9-2-3
DOB, 10-2-13 define port--PLC communications, 9-2-10–
Output Type field, analog output PIOB, 3-2-31 9-2-15
Output Value field factors affecting, 9-2-15
AOB, 2-2-7 Modbus function codes, 9-2-1
HOB, 8-2-11 module switch requirements, 9-2-8
PLC configuration
Modbus PLC and data highway, 9-1-11
P one Port I/O Card and one data highway, 9-1-8
two Port I/O Cards and one data highway, 9-1-9
two Port I/O Cards and two data highways,
Parity Bit field, PLC Configuration screen, 9-2-13 9-1-10
PeerWay node addressing, 1-3-2 PLC Configuration Screen, Allen--Bradley PLC,
PIOB, 1-1-2, 3-1-1– 3-1-9, 3-2-1– 3-2-6, 3-2-7– 9-5-10
3-2-14, 3-3-1– 3-3-2 PLC general alarms, 9-5-18
analog output, 3-1-6, 3-2-2, 3-2-28– 3-2-31, PLC interface
3-2-35– 3-2-39 hardware, 9-1-2, 9-1-3
analog output loader application, 3-1-7– 3-1-8 network configurations supported, 9-1-7