ÎÎ GE Fanuc Automation Programmable Control Products t Genius Modular Redundancy Flexible Triple Modular Redundant (TMR) System User’s Manual GFK-0787B March 1995
GFL–002 Warnings, Cautions, and Notes as Used in this Publication Warning Warning notices are used in this publication to emphasize that hazardous voltages, currents, temperatures, or other conditions that could cause personal injury exist in this equipment or may be associated with its use. In situations where inattention could cause either personal injury or damage to equipment, a Warning notice is used. Caution Caution notices are used where equipment might be damaged if care is not taken.
Preface t This manual is a reference to planning, configuring and programming a Series 90 -70 PLC system that utilizes Genius Modular Redundancy (GMR). The information in this manual is intended to supplement the basic system installation, programming, and configuration instructions located in the manuals listed on the next page. Content of this Manual Chapter 1. Introduction: describes the concept of GMR, and gives an overview of system components, configuration, and programming. Chapter 2.
Preface H The GMR configuration software now allows selection of memory addresses for external write access. Serial and network communication ports are restricted; the Genius bus is not. A GMR Genius bus must not be used for communications. H H Input autotest is enhanced. External isolation diodes are required. H H New diagnostics including parity checks and checksums are provided. The method used for input voting adaptation can now be configured to suit the application.
Contents Chapter 1 Chapter 2 Chapter 3 Chapter 4 Chapter 5 GFK-0787B Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Components of a GMR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Series 90-70 PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Busses and Bus Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Chapter 6 Chapter 7 GFK-0787B Diagnostics in a GMR System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Setting Up Blocks to Report Genius Faults . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 GMR Autotesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 GMR Discrepancy Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Chapter 8 Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Genius Bus Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Termination Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Input Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
restart lowapp ARestart oddapp: ARestarts for autonumbers that do not restart in each chapter. figure bi level 1, reset restart table_big level ARestart 1, reset chap_big 1, reset1 lowapp oddapp: level ARestarts for autonumbers that do not restart in Lowapp Alwbox restart evenap:A1app_big level 1, resetA level 1, reset level 1, reset chap_big level 1, reset1 each chapter. figure bi figure_ap level 1, reset table_big table_ap level 1, reset figure level 1, Lowapp reset Figure 1. table level 1, reset Table 1.
1 Components of a GMR System GMR Software GMR software version 2.06 (catalog number IC641SWP714B) provided on diskette consists of: H H H Easy-to-use GMR configuration software. GMR system software, which automatically processes, monitors, and tests redundant I/O. A download utility for updating programs in systems with SNP multidrop communications. Series 90-70 PLCs Two models of the Series 90-70 PLC CPU support GMR, CPU 788 and CPU 789.
1 Series 90-70 PLCs A GMR system normally consists of one to three identical CPUs running identical application software. Each CPU is connected to the same input and output subsystems. Each CPU receives all inputs and performs voting for discrete inputs and mid-value selection for analog inputs. Each CPU computes the required outputs as a function of the inputs and the application program logic. Inter-processor Communications The PLCs exchange initialization data at startup, then operate asynchronously.
1 Busses and Bus Controllers In a GMR system, there can be one to three bus controllers per bus, per PLC. Larger systems may require more than one I/O subsystem. For example, the GMR system represented below has two I/O subsystems for a total of six independent Genius busses and 18 bus controllers.
1 Operation Overview Genius Modular Redundancy has been developed for use in systems that have static or nearly static I/O under normal operating conditions. The system may have: H H Normally-on inputs with normally-energized outputs, as in emergency shutdown systems. Normally-off inputs with normally-deenergized outputs, as in fire and gas detection systems. Genius Modular Redundancy provides: H H H H high degree of self-test and monitoring with diagnostics fault tolerance.
1 Input Subsystem In a GMR system, the basic elements of an input subsystem are single or triple sensors connected to triple Genius blocks. Each block is on a different communications bus (shown below as A, B, and C). For this example, there are triple input sensors which are normally-on. However, one of these input sensors is off: A B C Open (0) Closed (1) Each PLC in the example system votes on the input data received from these three sensors as summarized below.
1 PLC Subsystem: Providing Output Data Running the same application program, each PLC (referred to here by Genius Bus Controller (GBC) serial bus addresses: 31, 30, and 29) processes the voted input data and produces appropriate outputs. Because each of the three PLCs is running the same program, they produce three copies of the same output data. Each PLC then sends this triplicated output data on the bus.
1 Genius I/O Blocks Inputs and outputs in a GMR system are provided by Genius I/O blocks. Some types of Genius blocks are now enhanced for GMR operation. In addition, these and other types of blocks can be included in a GMR system as “non-voted” blocks. Non-voted blocks are individual blocks that are present on GMR busses in the system; they are not part of any GMR input group or output group. They are included in the GMR configuration and they may be autotested.
1 Number of I/O Points in a GMR System The I/O capacity of the system depends on whether the CPU is a model 788 or model 789. For most applications, these limits will not be reached. If you need help estimating I/O sizes for a large application, contact GE Fanuc at 1-800-828-5747.
1 Configuration and Programming The GMR Software The GMR software consists of: H The GMR configuration software file, CONFIG.EXE. This file, which runs under DOS, is used to enter the system parameters that will be used by the GMR system software. When the GMR configuration is completed, it produces a Program Block named G_M_R10. H A directory named GMRxxyy containing the GMR system software files, to which the application program will be added.
1 The Basic Steps of Configuration and Programming 1. Use the GMR configuration software to complete the GMR configuration. There is only one GMR configuration needed for the system. GMR configuration sets up the parameters that will be used by the system, including reference addresses. The GMR configuration software produces: H H 2. A printout of the GMR Configuration. A program block named G_M_R10. This is later added to the application program.
Chapter 2 Input Subsystem 2 section level 1 1 figure bi level 1 table_big level 1 This chapter provides information about the inputs to a GMR system.
2 Overview The input subsystem is the part of a GMR system that gathers input data. It may consist of: H H GMR Input groups of 1 to 3 discrete or analog blocks Individual non-voted discrete and analog blocks ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ É É É É The following illustration represents basic elements of an input subsystem. Triple Genius Busses É É É A Triple PLCs Input Block Group Non-voted (non-redundant) Input Block B C Triple Input Sensors GMR blocks are arranged in “groups” of 1, 2, or 3 blocks.
2 GMR Input Groups The configuration can include as many as 128 16-circuit voted discrete and 256 four-input analog input groups. (The actual I/O capacity of the system depends on the CPU type. See page 1-9). In an system that has normally-energized discrete inputs, the following combinations of sensors and Genius inputs can be used with Genius Modular Redundancy.
2 Non-Voted I/O in the Input Subsystem The input subsystem can also include three types of non-voted inputs: H Inputs from single-block (simplex) GMR input groups Individual blocks can be included in the GMR configuration as “simplex groups”, and can utilize the GMR features such as autotesting. Inputs from simplex blocks are placed into the area of the Input Table used for GMR inputs.
2 Discrete Inputs Types of Blocks in the Input Subsystem The following discrete block versions can be configured for GMR version 2.06 operation and used as GMR input blocks: 24/48 VDC 16-Circuit Source block: IC660BBD020M or later 24/48 VDC 16-Circuit Sink block: IC660BBD021M or later 12/24 VDC 32-Circuit Source block: IC660BBD024N or later 5/12/24VDC32-Circuit Sink block: IC660BBD025N or later All types of Genius blocks can be used as non-GMR blocks in a GMR system.
2 Input Autotest for GMR Inputs During GMR configuration, input autotesting can be individually turned on or off for each input in an input group. The GMR software will automatically test the selected inputs for the ability to reach the alarm state. The ability to diagnose short circuits on inputs depends on whether the circuit is set up as a bistate or tristate input, and on whether the block itself is configured for GMR mode (using the Hand-held Monitor).
2 Line Monitoring for Discrete Inputs Normally-closed inputs on GMR-configured blocks can be monitored for short circuit faults. Normally-open inputs on blocks which are not configured in GMR mode can be monitored for open circuit faults. Normally-closed Inputs For applications such as Emergency Shutdown (ESD), normally-closed inputs are generally monitored for short circuits across the lines, since that represents a fail to danger condition (that is: trip is not detected).
2 Manual Input Controls Safety systems often use controls for manual trip and manual inhibit. The GMR autotest and fault processing operations are unaffected by such controls. H A manual trip causes the input to assume the alarm condition. For example, for a normally-energized input, the input is open circuit. H A manual inhibit causes the input to remain in the normal condition. For example, for a normally-energized input, the input is held high even if the device is in the Off state.
2 Analog Inputs Like discrete blocks, analog blocks can be used in the input subsystem as members of GMR input groups of 1 to 3 blocks, or as non-voted blocks. Also like discrete blocks, individual circuits of analog blocks in multiple-block GMR input groups can be used as non-voted analog inputs. Analog blocks in GMR input groups are not autotested by the GMR software. All of the available types of analog blocks can be used, including the Thermocouple and RTD blocks.
2 Analog Discrepancy Reporting When the GMR software compares analog input data, it checks each channel against discrepancy limits provided as a part of the configuration for that input group. Any channel that varies by more than a configurable percentage from the intermediate value is reported. Discrepancy signals are filtered for a configurable time period, to eliminate transient discrepancies caused by timing differences.
Chapter 3 Output Subsystem 3 section level 1 1 figure bi level 1 table_big level 1 This chapter describes GMR output subsystem.
3 Overview The output subsystem is the part of a GMR system that provides output data. It may consist of: H H GMR Output groups of 4 discrete blocks Individual non-GMR discrete and analog blocks The following illustration represents basic elements of an output subsystem.
3 GMR Output Handling Unlike GMR input voting, which is done by the GMR software in the PLCs, output voting is performed at the output block groups. To perform output voting, the blocks must be one of the listed types, and they must be configured (with a Hand-held Monitor) to be in GMR mode. Output Voting A GMR output block group compares corresponding output data for each point as received from each of the three PLCs. If all three PLCs are online, the data from at least two must match.
3 The following three tables compare voting results for a block group receiving outputs from all three PLCs with results when one of the three PLCs is offline. Results of Block Group Voting with Three PLCs Online For comparison, this table shows how a block group votes on outputs received from three PLCs when all three are online. The block group doesn’t use the Duplex Default, so it is shown as an X (don’t care).
3 Results of Block Group Voting with One PLC Online If two PLCs are offline, the “voted” outputs are the same as the outputs from the PLC which is still online (x = don’t care).
3 4-Block Output Groups All four blocks in a group must be either 16-circuit or 32-circuit blocks. In a group, two source-type Genius blocks are connected in parallel on one side of each load, and two sink-type Genius blocks are connected in parallel on the other side. Bus A Bus C Bus B ÉÉ ÉÉ ÉÉ ÉÉ ÉÉ Source Blocks (IC660BBD020 or IC660BBD024) A B Load C D Sink Blocks (IC660BBD022 or IC660BBD025) There are three busses.
3 Operation of a 4-Block Output Group Each GMR output state is sent to four blocks set up in an H-pattern as shown on the opposite page. This type of grouping creates a fault-tolerant system where any single point of failure does not cause the system to lose control of a critical load. This is achieved by: H H H output voting (which is explained on page 3-3), and the electrical characteristics of sink and source blocks, and redundant busses.
3 Manual Output Controls and Diagnostics Safety systems are often provided with controls for manual trip and manual override. H A manual trip causes the output to assume the alarm condition. For example, a normally-energized output would be de-energized. H A manual override causes the output to remain in the normal condition. For example, a normally-energized output is held energized. These manual controls can be implemented either in hardware, as represented below, or in software.
3 Redundancy Modes for Output Blocks There are three separate configuration processes for a GMR system: H H GMR configuration, which supplies parameters used by the GMR system software. H Genius block configuration, which sets up the operating characteristics of the blocks themselves. PLC configuration, which is performed as usual for a Series 90-70 PLC system using the Logicmaster 90 software. It is during Genius block configuration that the redundancy mode of blocks is selected.
3 Hot Standby Mode Individual blocks can be included in the output subsystem as GMR blocks, Hot Standby blocks, or non-GMR blocks. There are significant differences in block operation between these three operating modes. Operation of GMR output blocks and non-GMR blocks is explained elsewhere in this chapter. Hot Standby mode is a type of Genius redundancy that can be used with or without GMR.
Chapter 4 PLC Subsystem 4 section level 1 1 figure bi level 1 table_big level 1 This chapter describes operation of the PLC subsystem in a GMR system.
4 System Startup The following actions occur during orderly startup of the GMR system: 1. Each PLC disables its outputs to Genius blocks. If the Outputs Disable function does not complete successfully, the GMR software sets the flag “GMR System Initialization Fault” and the GMR software puts the PLC in Halt mode. 2. Each PLC determines its PLC identity: PLC A, PLC B, or PLC C.
4 output states of the blocks, the block does not use those outputs in its output voting. The block(s) continue to ignore outputs from the PLC until they match those of the block’s voted outputs or until commanded to do so by setting the FORCLOG command bit (%M12263). This is covered on more detail on page 7-17. Startup requires multiple PLC sweeps to complete. Execution of the application program should not be started until initialization and synchronization have been completed successfully.
4 Data Initialization During startup, a PLC either sets a flag to notify the application program to initialize %R and %M memory, or synchronizes the data with corresponding data in the other PLC(s). The %M data is typically latch logic states, while the %R data is typically timer/counter data. The beginning addresses and lengths of both areas are set up during configuration.
4 CPU Sweep in a GMR System The special functions required for Genius Modular Redundancy include autotest, input voting, and alarming. These GMR functions are provided by a set of Program Blocks that are placed into the Program Folder using the LM90 librarian feature. After this is done, the GMR logic is executed automatically by the CPU as shown below.
4 Estimating CPU Sweep Time The GMR system software runs on Series 90-70 CPU788 or CPU789 PLCs. It produces a “base” CPU sweep time that becomes a part of the overall sweep time of the CPU with a ladder logic application program in it. This base sweep time should be taken into consideration during the application program design and development. Base sweep time depends on GMR configuration parameters such as Input and Output table sizes. Typical base sweep times for 788 and 789 CPUs are shown below.
4 Input Processing During the Input Scan portion of the CPU sweep, the PLC receives inputs from the discrete and analog input blocks. It stores the input data in different areas of memory as described below. After the Input Scan, the GMR logic performs voting on the inputs configured for GMR redundancy, and places the results into the discrete and analog input tables where they are available to the application program.
4 Discrete Input Voting Immediately after the input scan, before the application program execution begins, the GMR software performs input voting. It automatically reads and votes on the three (or two) sets of data in areas A, B, and C of the discrete Input Table. If a failure (discrepancy fault, Autotest fault, or Genius fault) occurs, the GMR software adapts to reject the faulty data.
4 Voting with Three Discrete Inputs For a triplex input group with three inputs present, the GMR software performs 2 out of 3 voting. Field Input Data Input A 0 Input B 1 Input C 1 Duplex State 1 Default State 0 Single Input Provided to Application Logic 1 GMR Software Performs 2 out of 3 Voting The Duplex State and Default State are not used when three field inputs are available.
4 Voting with Two Discrete Inputs Two inputs may be present in either a Duplex input group, or in a Triplex input group where one of the three inputs has failed. For its 2 out of 3 voting, the GMR software uses the group’s configured Duplex State in place of a third actual input.
4 Voting for One Discrete Input One input may be present in a non-voted input group, in a Simplex input group, in a Duplex input group where one input has failed, or in a Triplex input group where two inputs have failed. In a non-voted input group, the actual input is always provided to the application logic. In a voted input group, if only one input is available the result of the voting depends on the Voting Adaptation mode that has been configured for the input group.
4 Analog Inputs The method of analog input processing is similar to the method used for discrete inputs. During the Input Scan, data from analog input blocks is placed in the Analog Input Table as shown below. Inputs from blocks that have been included in the GMR configuration are placed in the areas labelled A, B, and C. Data from any additional analog input blocks (non-voted blocks or blocks on other busses) is placed in a separate area as shown.
4 Analog Input Voting Immediately after the input scan, before the application program execution begins, the GMR software performs input voting. It automatically reads and votes on the three sets of data in areas A, B, and C of the analog Input Table. How it does the voting is described below. It places the resulting voted input value into the voted inputs area of the Input Table. If a failure (discrepancy fault, or Genius fault) occurs, the GMR software rejects the faulty data.
4 Voting for Three Analog Inputs For a triplex input group with three inputs present, the GMR software compares three corresponding analog input values. It selects the intermediate value and places it into the voted inputs portion of the Analog Input Table. Field Input Data Field Input Data Input 1 152 Input 2 150 Input 3 110 Duplex State (low, high, or average value) Default State (hold last, minimum, or maximum) Single Input Provided to Application Logic 150 average max.
4 Voting for Two Analog Inputs Two inputs may be present in either a Duplex input group, or in a Triplex input group where one of the three inputs has failed. Three vote options in duplex mode are determined by the duplex state: highest, lowest, or average. h If lowest has been configured, the GMR software selects the intermediate value with the unused (third) channel being assigned its minimum configured value.
4 Voting for One Analog Input One input may be present in a non-voted input group, in a Simplex input group, in a Duplex input group where one input has failed, or in a Triplex input group where two inputs have failed. In a non-voted input group, the actual input is always provided to the application logic. In a voted input group, if only one input is available the result of the voting depends on the Voting Adaptation mode that has been configured for the input group.
4 Output Processing For outputs, the PLC does not perform “redundancy” voting. Instead, voting is done by the specified types of discrete output block groups. Analog blocks do not provide redundancy voting or autotest features. Both discrete and analog Genius blocks can be used in the output subsystem as non-GMR blocks, however.
4 I/O Shutdown When the GMR system diagnoses a discrete I/O fault, it logs the appropriate faults in its fault tables and set the appropriate fault contacts. For certain types of discrete I/O faults, the system optionally allows a predefined amount of time for the problem that caused the fault to be repaired. If the problem is not rectified within this period of time, an I/O Shutdown of the I/O corresponding to the affected block(s) occurs.
4 Output Faults that Cause I/O Shutdown For discrete output groups there are also two types of faults which may prevent the output autotest from continuing to execute for that output group and thus cause an I/O shut down for the outputs in the group. 1.) Loss of a block within the group. (I.E. any failure which causes the block to no longer communicate on the Genius bus such as loss of power.) 2.
4 D). PLCC executes the autotest and detects the fault, then starts its 8-hour shutdown timer. The message “Shut down in 8 hours” is logged in the fault table. The autotest master function passes to PLCA. E.) The message “Shut down in 1 hour” is logged at PLCA. F.) The shutdown timer expires in PLCA. The message “I/O Shut Down” is logged in fault table of PLCA. PLCA shuts down the I/O of the affected I/O group.
4 I/O Shut Down Prevention If an I/O fault causes an I/O shutdown to initiate, there is up to 16 hours of time to repair the fault and put the block(s) back into operation before the shutdown occurs. When the next autotest occurs on the PLC(s) that started its shutdown timer, that PLC automatically cancels its I/O shutdown (If the autotest is executed without faults on the affected block(s) before the actual shut down occurs).
4 Communications Between PLCs Data is transferred between the PLCs in the system using Genius global data. Two busses are used to transfer duplicate data. While the system is operating, they transfer global data automatically. This global data includes two types of information: H Application program global data from %G memory. The GMR software automatically copies this data into %R memory before sending it. H Additional %R data used by the GMR software.
Chapter 5 Diagnostics 5 section level 1 1 figure bi level 1 table_big level 1 This chapter describes: H H H H H H H Diagnostics in a GMR System GMR Autotesting GMR Discrepancy Reporting Input Line Fault Detection in a GMR Application The PLC and I/O Fault Tables in a GMR System Monitoring Manual Output Controls Fault and Alarm Contacts Programming for Diagnostics The Programming chapter of this book explains some programming considerations for a GMR application.
5 Diagnostics in a GMR System In a GMR system, extensive diagnostic capabilities are provided by standard Genius I/O diagnostics and by the special autotesting and discrepancy reporting features of the GMR software. Standard Genius diagnostics, which are covered in other books, are not described in detail here. Each PLC provides a full range of fault table and program access to fault information. Input Diagnostics H GeniusDiagnostics: h Line fault. a feature of the 16-circuit DC blocks.
5 Setting Up Blocks to Report Genius Faults By default, most Genius blocks, including the types of blocks normally used in GMR systems, send only one copy of a Fault Report. For a GMR system, blocks can be set up to send additional Fault Reports. The setup needed for a block depends on two things: what type of block it is, and how many PLCs should receive its Fault Reports..
5 GMR Autotesting The GMR software automatically performs autotesting on discrete inputs and outputs that have been configured to be autotested. Analog inputs and outputs are not autotested by the GMR software. GMR autotesting can be used in a system with one, two, or three PLCs. Autotest Sequence GMR autotesting goes on at the configured interval (0 to 65535 minutes) during system operation. Each PLC in turn controls the sequence. PLC A PLC B ' PLC C ' 1. Autotest GMR inputs 1.
5 Discrete Input Autotest Discrete Input Autotest exercises the system inputs to assure their ability to detect and respond to actual inputs. It can be used on both 16-point and 32-point blocks. Input autotest will: H accommodate normally-closed and normally-open devices with the device in either state. H detect any input failure associated with an input that would result in a failure to respond. H not cause spurious outputs. Input autotest is internal to each Genius block.
5 Single Input Sensor to Triplex Block Group Field Switch Zener Diode Power feed outputs require isolation diode when single input device is wired to more than one block. Operation of the Input Autotest The following actions are performed during the Input Autotest: H H the power feed outputs * are pulsed Off. Selected input channels are pulsed On.
5 Discrete Output Autotest Discrete output autotest checks the ability of outputs to respond to the commanded output state. Bus A Bus C ÉÉ ÉÉ ÉÉ ÉÉ Bus B A B Load C D The discrete output autotest will: H work on outputs that are either on or off, with or without load monitoring.
5 Operation of the Discrete Output Autotest The PLC that is presently the autotest master informs the other PLCs (if any) which autotest group it is about to test. All PLCs read the diagnostic status of all blocks in the group to be tested, and will ignore any subsequent faults that may occur in that group. The autotest master PLC reads the current output state and force state for each circuit in the output group.
5 4. The autotest master pulse tests Block A. Any faults on block A are noted. A B Failed Switch outputs still overridden OFF. Load Block A Pulse-tested. Block C outputs still overridden ON D C 5. The master resets all four blocks in the output group. 6. Overrides on block C are cancelled. B Failed Switch outputs still overridden OFF. Load A Block C output overrides cancelled. 7. D C The master cancels overrides on block B except for any outputs that have tripped erroneously.
5 Pulse Test Operation The Output Autotest uses the standard Genius block Pulse Test feature. During this test, the system is on-line and available. For the test to be performed: H H H All blocks in the group must be on-line. There may be no I/O override applied to any block in the group. In addition, for each block output that is associated with a given system output within the group: h h h there may be no I/O force applied. there may be no hardware fault (such as a failed switch).
5 GMR Discrepancy Reporting The GMR software performs discrepancy reporting for: H H H Voted discrete inputs Discrete outputs Analog inputs There is no discrepancy reporting for analog outputs.
5 Discrete Output Discrepancy Reporting Output discrepancy monitoring is the process of monitoring the block output voting function to detect both processor discrepancies and lost communication between the block and the other processors. All PLCs periodically monitor all blocks’ discrepancy status. On interrogation by any PLC, the block responds with a discrepancy message indicating the discrepant output and disagreeing PLC.
5 Analog Input Discrepancy Reporting If there is a discrepancy in the data from a set of inputs, so that a channel deviates by more than a configurable percentage from the voted value, the PLC automatically places a message in the I/O Fault Table where it is available to the Logicmaster 90 software and the application program logic. Discrepancy is calculated for engineering units values inputs. Two distinct discrepancy bands are provided: threshold and limit.
5 Input Line Fault Detection in a GMR Application The 16-circuit Genius blocks are capable of continually monitoring field circuits for input short circuit or open circuit faults. The blocks detect On, Off, Short Circuit, or Open Wire conditions on circuits set up as tristate inputs. If a block is in a “non-GMR” mode, a resistor must be installed in the circuit to provide Open Wire fault detection. However, if the block is in GMR mode, a zener diode is used instead to detect short circuits.
5 The PLC and I/O Fault Tables in a GMR System Faults and alarms from I/O devices, Bus Controller faults, and bus faults are automatically logged into the Series 90–70 PLC’s I/O Fault Table. Faults can be displayed with the programmer in either On–Line or Monitor mode.
5 I/O Fault Table Messages for GMR I/OFault Table format is detailed in the Series 90-70 PLC Reference Manual (GFK-0265).
5 Displaying Additional Fault Information About I/O Faults (with CTRL/F) Pressing the programmer CTRL/F keys provides more information about a fault. Entries that apply to the GMR system are described below.
5 PLC Fault Table Messages for GMR The following tables lists PLC Fault Table messages for GMR.. If you need additional help, call GE Fanuc Technical Service at 1–800–828–5747.
5 Code Message 10146 10147 10148 2 10201 10202 10203 10204 10211 10212 10213 10221 10222 10223 10241 10242 10243 10244 10245 10246 10251 10301 10302 10303 10305 10306 10307 10308 10310 10311 10312 10313 10322 10323 10324 10328 10330 10601 10602 10603 10604 10607 10801 10802 10802 10803 10804 10805 10806 10810 10811 10812 ConfigmismatchA/B/C Config changed A Config changed B Config changed C Unauthorized GMR Access Incorrect GMR Version GMR Software Exception Invalid GMR Pointer Comms Fail PLC A bus a Com
5 Code Message 10814 10815 10817 10818 10819 GMR cfg err no of PLCs GMR cfg errW/dogtimer GMR Cfg Err %R usage GMR cfg err %AI Usage GMR cfg err comreq %R 10820 GMR cfg err Tx global 10821 GMR cfg err Rx global 10822 GMR cfg err I/O > max 10823 GMR cfg err voted DIN 10824 GMR cfg err voted AIN 10825 GMR cfg err redund O/P 10826 10827 10828 10829 10830 10831 10832 GMR cfg err alpha rack GMR cfg err alpha slot GMR cfg err beta rack GMR cfg err beta slot GMR cfg err %M sync GMR cfg err %R sync
5 Code Message 10903 User_IF–Invalid Table 10903 Bad Table c (h) 10905 10906 10907 10908 User_IF–Invalid Range User_IF–Table Space No fault contacts Bad blk loc r.s.b.d. 10909 Bad GBC Loc r.s. 11001 11101 11102 11201 11202 11401 11402 11403 11404 11410 11411 Null GMR Configuration Unauthorized GMR Access GMR S/W Except.
5 Code Message 11453 11455 GMR12–tmplt too small GMR15–IS x at y 11456 GMR15–ST x at y 11457 11458 11501 11502 11503 11504 11505 11506 11507 11508 11509 11510 11511 GMR15–IW x GMR15–tmplt too small Unauthorized GMR Access Incorrect GMR Version GMR Software Exception Invalid GMR Pointer More than 1 Master Invalid Switch Case Discrep NAK PLC A Discrep NAK PLC B Discrep NAK PLC C Disc results read fault DQ x.y.1.z –> d/f/s 11511 CQ x.y.1.z –> d/f/s 11513 11521 Xtalk results read flt CR fail x.y.l.
5 Manual Output Controls and Diagnostics Safety systems are often provided with controls for manual trip and manual override. H A manual trip causes the output to assume the alarm condition. For example, a normally-energized output would be de-energized. H A manual override causes the output to remain in the normal condition. For example, a normally-energized output is held energized. These manual controls can be implemented either in hardware, as represented below, or in software.
5 Monitoring Manual Output Controls The operation of manual trip and output override devices can be monitored and reported by connecting them as inputs to Genius blocks. These inputs should be configured to use references at the end of the Discrete Input Table shown as “reserved inputs” below.
5 Fault, No Fault, and Alarm Contacts Fault and No Fault contacts can optionally be used to detect fault or lack of fault conditions on a discrete (%I or %Q) or analog (%AI or %AQ) reference. They can also be programmed with the Series 90-70’s built-in fault-locating references. In a GMR system, there are fault contacts associated with voted inputs, with the original block inputs, and with logical outputs.
5 Discrete Output Fault Contacts for GMR For discrete outputs, the fault contact is associated with the logical outputs (outputs from the application program). Contact References Associated with an Output Logical reference Physical reference Fault contact These logical references are copied to the physical output references. If a fault is detected on a physical output, the fault contact associated with that output’s logical reference is set.
5 Short circuit fault Overtemperaturefault Overloadfault h Discrepancy The blocks each report the discrepancy status for the data from each PLC, together with the PLC online/offline status. All PLCs periodically monitor all blocks’ discrepancy status. Three discrepancy bits are maintained for each output; one for each of the PLCs. One of the bits is set if a block reports a discrepancy for any of its outputs. H For non-redundant outputs, the single fault contact is associated with the physical output.
5 Analog Fault and Alarm Contacts for GMR The fault, high alarm and low alarm contacts of non-voted analog inputs and outputs are not affected by GMR analog I/O processing. Fault Contacts for Analog Inputs As with discrete inputs, voted analog inputs have fault contacts associated with both the raw data inputs and the corresponding voted inputs. Non-voted analog inputs also have associated fault contacts. (For more information about fault contacts, see page 7-21.
Chapter 6 Configuration 6 section level 1 1 figure bi level 1 table_big level 1 This chapter describes configuration for a GMR system: H Configuration Overview h H Using the GMR Configuration Software h h h h h h h h h h h H Creating/Selecting a File System Configuration Screen Autotest Interval CPU Configuration I/O Limits Initialization Data Fault Actions Genius Bus Controller Group Configuration Configuring the Input Subsystem for a Bus Controller Group Configuring the Output Subsystem for a Bu
6 Configuration Overview In a GMR system, there are three basic configuration steps: H H H Completing the GMR configuration using the GMR configuration software. Configuring the Series 90-70 PLCs. Configuring the Genius blocks in the system (not shown below). GMR CONFIGURATION LM90 CONFIGURATION GMR Configuration Printout G_M_R10 Program Block GMR Diskette CONFIG.
6 (2) In the Program Folder functions menu, select F1 ... Select/Create a Program Folder. On the Select/Create screen, select the folder for the second PLC (for example CONFIGB) as the current folder. (3) In the Program Folder functions menu, select F10, Copy Contents of Program Folder to Current Program Folder. On the Copy Folder screen: (a) For Source Folder, enter the name of the folder containing the configuration of PLC A (for example, CONFIGA).
6 Using the GMR Configuration Software The GMR Configuration Software is used to enter data needed by the GMR program software. H H H H H H Autotest interval CPU type for the system I/O limits for the system initialization data for the system fault actions for the system all GBC (bus controller) groups, with all Genius I/O blocks that will use GMR features The GMR Configuration Software is not part of the Logicmaster 90 software package.
6 Getting Started To complete the configuration, you will need to provide the following information: H H H H H H the CPU type (788 or 789) the register memory table size. the Analog Input table size. the CPU Watchdog timer value. I/O block serial bus addresses. H Bus controller rack and slot locations. I/O block “logical” (%Q) and “voted” (%I and %AI) addresses to be used in the application program. The GMR Configuration Software will supply default values for these selections.
6 Mouse and Keyboard Guide for the Configuration Software Either a mouse or keyboard can be used with the GMR Configuration Software. It is easiest to use a mouse. Using a Mouse When using a mouse, simply move to the item you want to select, and click on it. Some windows can be closed, zoomed, or resized using a mouse.
6 There are two basic ways to select a menu item from the keyboard: A. pressing the letter key that corresponds to the highlighted letter on the display (for example, the letter “c” in CPU, below. B. moving the cursor to that item (using the cursor keys) and pressing Return (enter).
6 GMR Configuration Summary GMR configuration is described in detail on the following pages. The basic steps are: 1. Select File to create a New System configuration 2. In the System menu, create the CPU configuration H H H H H H CPU Type (788 / 789) Number of CPUs (1 – 3) Watchdog timer (must match PLC configuration) Enable or disable online programming. Simplex shutdown (enable/disable) Timeout (0 – 65535 seconds) Select [O]K or [C]ancel to quit the CPU Configuration window 3.
6 9. [Insert] the first GBC (bus controller) group A. Select each bus controller in the group (GBC_A, GBC_B, GBC_C). (1) Specify a rack and slot location (2) Select [OK] or [C]ancel to quit the Rack/Slot window B. Configure all the input and output block groups for the GBC group. (1) [Insert] each Input block group.
6 Creating/Selecting a File To create a new configuration, or begin editing an existing file, select File. (If you are using a mouse, click on “File” in the upper left corner of the screen. If you are making keyboard entries, type Alt/F.) You can now start a new configuration or open an existing configuration.
6 Saving a Configuration File Select Save (F2) to save the configuration file presently in RAM memory (the one displayed on your computer screen). This function saves the file with the selected name, overwriting the previous version. If you want to specify another filename (for example, to create a new version of a configuration file without writing over the old one, select Save As instead. The software gives each saved file the filename extension .SAV.
6 Changing to Another Directory Use the Change Directory function if you want to access another directory. (Additional directories must be created in DOS.) ' Select Chdir to change the directory. Select Revert to return to the previous directory. If you are using a mouse, you can click on the “elevator” bar at the right of the Directory Tree to scroll through the directory structure.
6 Starting a New Configuration When you select New System from the File menu using the mouse, or using the Enter (Return) key, the System screen appears: From this screen, you can: H H H return to the file-handling functions (click on File or press ALT/F) H print out a copy of the configuration (click on Output or press ALT/O. When the Output menu appears, click on Print Out or press [P].). H create the configuration output file (click on Output or press ALT/O.
6 GMR Configuration Selections When you select System, the following menu appears CPU configuration Select autotesting interval Input Discrepancy Filter Set configuration limits Select Initialize data areas Select fault actions Configure memory write access Create the configuration by selecting items from the menu, then completing entries on the screens that appear. Instructions for completing these screens begin on the next page.
6 CPU Configuration Complete the entries on the CPU Configuration menu. The defaults are indicated with dots in the parentheses, as shown below. If a default selection is correct for your system, you don’t need to edit that item. ' CPU Type Specify whether the CPU is model IC697CPU788 or 798. On Line Prog Specify whether Online programming will be permitted. If this item is set to Yes, online run mode stores, single word online changes, or block edits can be made without shutting down the PLCs.
6 Test Interval First, configure the interval for autotesting, and a register where this interval should be stored. ' On this screen, enter: Period Specify an autotest interval of 1 to 65535 minutes. This becomes the time interval the system will wait between autotests of the I/O subsystem. Register Specify a %R register. When the system is started and goes through initialization, this register is initialized to the period configured (above).
6 Input Discrepancy Filter ' On this screen, enter the input discrepancy filter time in seconds. This is the amount of time, in seconds, that a particular input may be discrepant before the CPU places a message in the I/O Fault Table, and sets the appropriate fault contact for that voted input. This input discrepancy filter time applies to both discrete and analog inputs. This time defaults to one second. The range is 1 to 65535 seconds.
6 I/O Limits Select System again. From the configuration menu, select Config Limits (click the mouse on that line or cursor down and press Enter). ' Entries made on this screen determine how the GMR software allocates memory. The maximum number of groups that can be configured is 128. Additional parameter limits for this screen are summarized below. Parameters Item Comment Total number of voted digital inputs and redundant outputs 1...112 (788 CPU) 1...
6 The voted analog references start at %AI0001. The size of the voted analog input area is determined by the number of voted analog inputs including spares. Physical input data from analog block groups is located at the end of the Analog Input Table, in the areas labelled A, B, and C in the preceding illustration. Each of these areas is equal in length to the number of voted inputs at the beginning of the table. Unused portions of the Analog Input Table may be used for simplex inputs.
6 Initialize Data Next, select System to configure the Initialization Data. ' Initialization data, as explained in the PLC Subsystem chapter of this book, is exchanged between PLCs during startup. It consists of data such as timers and counters and latched logic states. It is important to be sure that the memory assignments you make here do not directly conflict with %R and %M memory used in the application program or required elsewhere by the GMR software.
6 %R Temp Ref If, when the PLC is starting up, the other two PLCs are already online, %M data from the second online PLC (the one with the lower serial bus address) is also received by the initializing PLC. In the %R Temp Ref field, enter a starting reference in %R memory to receive %M data from the second online PLC. (In this field, the %M refers to the type of data being received.
6 Fault Actions Next, select System to configure Initialization Fault Actions: ' These entries determine how the GMR software will respond to either of the following faults during CPU initialization: H an initialization data error (data fault) H a hardware fault (system fault) For each type, select whether the GMR software will: ( ) Halt the PLC (fatal) ( ) Allow the PLC to continue operating (diagnostic) and set the appropriate %M status flag.
6 Write Access Next, select System to configure Write Access: ' On this screen, you can configure starting addresses and lengths for any memory areas to which data can be written to through a CMM, PCM, or Ethernet Communications Module. These configuration parameters do not prevent write access through Genius Bus Controllers, the CPU’s built-in port or with serial or parallel Logicmaster 90-70.
6 Adding Bus Controllers and I/O Modules When you select Insert from the System screen, the following menu appears Configure Bus Controller groups Configure Input Group Configure Output Group Configure non-voted discrete I/O Configure non-voted analog I/O Create the configuration by selecting items from the menu, then completing entries on the screens that appear. Instructions for completing these screens begin on the next page.
6 Genius Bus Controller Group Configuration Note: It is possible that an application may include bus controllers in the PLC racks that are not part of the GMR system. Do not include non-GMR bus controllers in the GMR configuration. The only exception to this is a bus controller pair that is used for global data communications between PLCs. (Other, non-GMR bus controllers are included in the Logicmaster configuration only).
6 Exiting the Window Normally, the GBC (Genius Bus Controller) group window remains on the screen, so you can insert the I/O groups for that bus controller group. (It must be the “active” window (identified by the double line border) to insert an I/O group into it). However, if you want to exit the window, and delete the window from your configuration, click on the Close button in the upper left corner of the window.
6 Configuring the Input Subsystem for a Bus Controller Group With the rack and slot locations for a bus controller group configured, the next step is to configure the input subsystem for that bus controller group. Click on Insert or press ALT–I to display the Insert menu. Select Input Group from the menu by clicking on that item or by pressing [I].
6 Configuring a Triplex, Duplex, or Simplex Discrete Input Group To configure a discrete group, click on that line, or move the cursor there and press the Return key, or press the highlighted letter key. Then select whether the blocks in the group are 16-point or 32-point blocks. For example: ' A configuration screen like the one shown above right appears. To item on this screen, use the Tab key or mouse. ID Enter a name or a description of up to 12 characters, such as “in group 3”.
6 Auto Test Highlight this item then press the space bar key to display a screen for setting up Input Autotest and Test Type for individual circuits (screen for 16-circuit blocks shown here). If input circuits on the blocks in the group should be autotested, circuit 16 (the powerfeed output) must have autotest enabled.
6 1.) Loss of a block within the group. (I.E. any failure which causes the block to no longer communicate on the Genius Bus such as loss of power.) 2.) Autotest failure of the power feed output (point Q16) of any of the blocks in a group. For discrete output groups there are also two types of faults which may prevent the output autotest from continuing to execute for that output group and thus cause an I/O shut down for the outputs in the group. 1.) Loss of a block within the group. (I.E.
6 Vote Adaptation Similarly, select which Voting Adaptation method will be used for each circuit. Vote Adapt Mode: Specify the manner in which the PLCs should perform voting adaptation. During operation, if a failure (discrepancy fault, Autotest fault, or Genius fault) occurs, the GMR software will reject the faulty data and perform voting adaptation as configured here. For a triplex group, if input voting should go from three inputs to two inputs to one input, select 3–2–1–0.
6 Default State: Choose a default state: OFF (0), ON (1), or hold last state. For a triplex group, this state will be provided to the application program if communications from all three blocks in the group are lost (if Voting Adaptation is 3–2–1–0). Alternatively, if Voting Adaptation is set to 3–2–0, this state is provided to the application program if communications from two blocks in the group are lost.
6 Analog I/O Group Configuration Select Analog to configure any analog group. Select a triplex, duplex, or simplex analog input group, then select the block type (6 inputs or 4 inputs/2 outputs). For example: ' Note: A “simplex” input group has just one I/O block, installed on one bus, but configured as a GMR block. It is not the same a “non-voted” block. To configure a GMR group with just one analog block, select Simplex Analog from the menu of analog group types as described above.
6 Vote Adaptation Specify how each circuit in a triplex or duplex group should utilize vote adaptation For a simplex group, this option does not apply. If a failure (discrepancy fault, or Genius fault) occurs, the GMR software rejects the faulty data. Depending on the configuration entered here, input voting may go from three inputs to two inputs to one input, or from three inputs to two inputs to the configured default value. For a 4 input/2 output block group, the window shows only four inputs.
6 Default State: For a triplex group, if all three blocks in the group are lost or if only two blocks are lost and Voting Adaptation is selected as 3–2–0, the GMR system software will use a selected minimum or maximum value (see below) in voting, or hold the last value updated. For a duplex group, select what should happen if both inputs for a channel are lost or if one block is lost and Voting Adaptation is selected as 3–2–0. The input can be: H H H set to its configured maximum value.
6 Threshold Discrepancy: Specify by what percent an individual input for the channel may deviate from the voted input value. During operation, if any of the corresponding physical inputs deviates from the voted input value by more than this amount (in either direction), it will generate a fault that must be cleared by the application program. For example, if the physical inputs for a channel were 91, 100, and 111 degrees, the voted input value would be 100 degrees.
6 Configuring the Output Subsystem for a Bus Controller Group Next, configure the output subsystem for that bus controller group. Select Output Group from the menu. Repeat the following procedure for each group in the output subsystem: Note: It is possible for a bus to include output blocks that are not part of the GMR system. Do not include non–GMR blocks in the GMR configuration. Non-GMR blocks are included in the Logicmaster configuration and in the Genius block configuration, however.
6 Autotest: By default, each circuit is set up for autotesting, as shown by the X next to the circuit number. To turn off autotesting for any circuit, select that circuit (click on the circuit or select it using the cursor keys). Press the space bar key to remove (or replace) the X. Note: It is possible for an output block to include circuits that are not part of the GMR system, and which are not to be autotested. Be sure to turn autotest off for any unused and non-GMR circuits.
6 Options Finally, for each 4-block group, specify the bus and location (serial bus address) of the fourth block (the “D” block) in the group. While the A, B, and C blocks are installed on busses A, B, and C, respectively, the D block must be installed on either bus A or bus B (as in the illustration shown below).
6 Configuring the Non-Voted Discrete I/O for a Bus Controller Group If the bus controller group includes any non-voted discrete I/O, select nonVoted D I/O. (Inputs and outputs may be mixed on a block.) Non-voted I/O are inputs and outputs on individual blocks (blocks that are not part of an input or output group) that are present on the GMR busses. A sub-menu appears where you specify whether the blocks in that particular group are 16-point or 32-point blocks.
6 Options Select this item to display additional configuration choices. Input Autotest: This feature applies to 16- and 32-circuit DC Sink/Source I/O Blocks IC660BBD020, 021, 024, and 025 only. The block can be either in GMR mode or not in GMR mode. If any input circuits on the blocks in the group should be autotested, select them here. Circuit 16 must have autotest enabled.
6 Configuring the Non-Voted Analog I/O for a Bus Controller Group If the bus controller group includes any non-voted analog I/O, select nonVoted A I/O. Note: Non-voted analog I/O blocks that are configured here are considered part of the GMR system. It is possible for a bus to include I/O blocks that are not part of the GMR system. Do not include non–GMR blocks in the GMR configuration. Non-GMR blocks are included in the Logicmaster configuration and in the Genius block configuration, however.
6 Creating the G_M_R10 Output File The output of the GMR configuration process is a program block named G_M_R10, which can be imported to the application program folder in Logicmaster 90. The Write Output function of the GMR configuration software automatically creates a file named G_M_R10.EXE. This is the file required by Logicmaster 90. If the configuration you want to use is not the one currently displayed, first use the file utilities of the GMR configuration software to load it into RAM memory.
6 In this example, you decide that you don’t want to keep CONFIG4, so you go to the file functions and select Close. That ends the configuration session without creating a .SAV file. Next, you select Open a Configuration File. A list of files appears: Click on the name of the .SAV file you want, or type in its filename. When the filename appears in the name box, click on Open. The configuration file is loaded into RAM.
6 Completing the Logicmaster 90 Configuration Logicmaster 90 configuration steps for a PLC In a GMR system are the same as for a non-GMR system. A typical configuration is summarized on the following pages. You should refer to the Logicmaster 90 Software User’s Manual for detailed configuration instructions.
6 Creating and Copying the PLC Configuration The recommended method of completing the PLC configuration is described below. A. Create a Folder for PLC A, PLC B, and PLC C. In this discussion, PLC A is considered to be the PLC using serial bus address 31, PLC B is the one that uses serial bus address 30, and PLC C is the one that uses 29. B. Select the folder for PLC A. With the GMR configuration printout as a reference, complete its Logicmaster configuration.
6 Logicmaster Configuration Summary 1. Change the CPU to the correct type (in this example, it is a CPU 789) and add appropriate memory. 2. Move the cursor to the rack and slot location for the first Bus Controller. Be sure the location matches the entry made with the GMR Configuration Software. 3. Press F2 (genius). 4. From the Catalog # screen, press F1 (gbc). 5. From the Description screen, press Enter. 6. Complete the entries on the left side of the screen.
6 12. On the bus configuration screen, the Bus Controller appears at its configured Bus Address, 31 in this example. 13. From here, you can configure the devices on the bus, including the other bus controllers in the group. Each bus controller must be configured both individually and as a device on the bus of the other bus controller(s) on the same bus. In addition, the bus controllers on a Global Data bus must be configured with an appropriate Global Data address and length.
6 Configuring GMR Bus Controllers and I/O Blocks Each bus controller that serves the same input and/or output groups is configured similarly; so it is usually easiest to copy the first completed bus/bus controller in a group to configure the other bus controller(s) in the same group. Any additional changes can be made to the individual bus controller/bus configurations as needed (for example, to accommodate non-voted I/O on a bus, or the “D” block of a 4-block output group.
6 Configuring Genius I/O Blocks Genius I/O block configuration for a GMR system is similar to configuration for a non-GMR system. You should refer to the Genius Discrete and Analog Blocks User’s Manual for specific configuration instructions. A copy of the configuration prepared with the GMR Configuration Software should be used for reference during block configuration, to assure consistency.
6 Configuring 16-Circuit and 32-Circuit Discrete DC Blocks The table below lists configuration parameters for 16-circuit and 32-circuit discrete blocks. Configuration options with special requirements in GMR systems are described after the table. Configuration options that are not changed for GMR systems are not described here. Note that blocks do not prevent selecting incorrect parameters for a GMR system. It is important to configure blocks appropriately for GMR use.
6 Block I/O Type Any discrete block that is part of a redundant input group (triplex, duplex, or simplex) must be configured as a “combination” (I/O) type block. Any block that is part of an output group must be set up as an outputs-only block. Baud Rate Baud rate should be selected on the basis of the calculations in the Genius I/O System and Communications User’s Manual (GFK-90486). Note that for correct autotesting in a GMR system, the Genius bus scan time should not be be more than 60mS.
6 Hold Last State If the block will use Input Autotest, circuit 16 must be configured as an output, as explained above. For circuit 16, Hold Last State must be configured to NO. Output Default If the block will use Input Autotest, circuit 16 must be configured with Output Default set to ON. Redundancy Mode Portions of the overall system can be configured for no CPU redundancy, duplex redundancy, hot standby redundancy, or GMR mode.
6 Duplex Default For output blocks set up for GMR redundancy, the duplex default state is used when a block determines that only two PLCs are online. The Duplex Default state of On or Off is used by the 2 out of 3 voting algorithm in the block, instead of the state that would have been supplied by the third PLC. The Duplex Default state determines whether voting will be 1 out of 2 or 2 out of 2 in the On or Off state when only two PLCs are providing outputs. This is explained below.
6 Results of Block Voting with Only Two PLCs Online In the two tables below, PLC C is shown as offline, but it could be either of the other two instead. Using 0 as the Duplex Default state means that when only two PLCs are online, the voted output state will be 0 if either PLC sets it to 0. It will not be 1 unless both online PLCs set it to 1.
Chapter 7 Programming Information 7 section level 1 1 figure bi level 1 table_big level 1 This chapter describes the following aspects of the application program interface to the GMR software: H H H H H H H H H H H H H H H H H GFK-0787B Programming Overview Program Instruction Set for GMR Estimating Memory Usage Reserved References Input and Output Addressing for GMR Register (%R) Memory Assignment for GMR System Status (%S) References GMR Status and Control (%M) References Programming for Startup I/
7 Programming Overview The following figure represents the basic GMR programming steps. As explained previously, the GMR configuration, which assigns I/O reference addresses and produces the G_M_R10 Program Block should be done first. GMR Diskette G_M_R10 Program Block CONFIG.EXE LM90 Copy Folder GMRxxyy Download utilities LM90 PROGRAMMING LM90 Librarian The Application Program CONFIGA CONFIGB CONFIGC future program updates 7-2 LM90 Store LM90 Store LM90 Store PLC A PLC B PLC C 1.
7 Program Instruction Set for GMR The CPUs used for GMR support the all of the following Series 90-70 ladder logic instructions: Contacts Any Contact –| |– –|/|– –| ↑|– –| ↓|– –[F AULT]– –|NOFL T]– –[HIALR]– –[LO ALR]– <+>––– Coils Any Coil –( )– –(/)– –( ↑)– –( ↓)– –(S)– –(r)– –(SM)– –(RM)– –(M)– –(/M)– –––<+> BitOperation AND OR XOR NOT SHL SHR ROL ROR BTST BSET BLCR BPOS MCMP Conversion to BCD–4 to BCD–8 to UINT to INT to DINT BCD–4 to UINT BCD–4 to INT BCD–8 to DINT Control CALL DOIO SUSIO MCR ENDM
7 Reserved References In a GMR system, the following references are reserved or assigned special functions: References Reserved For: %I0001 to %I1024 (788 CPU) %I00001 to %I12288 (789 CPU) Input Table. Some references are automatically assigned by the GMR Configuration Software. Others are available for use, as explained in this chapter. %Q0001 to %Q1024 (788 CPU) %Q00001 to %Q12288 (789 CPU) Output Table. Some references are automatically assigned by the GMR Configuration Software.
7 Input and Output Addressing for GMR I/O addressing for GMR is unlike a that of conventional Series 90-70 application. In a conventional application, input and output addresses are assigned sequentially, starting at the beginning of the Input Table and Output Table. In a GMR application, the GMR software automatically divides the Discrete Input and Output Tables and the Analog Input Table into special-purpose areas.
7 Discrete I/O Tables: Example In this very simple example, there are: H H a model 788 CPU (with 352 physical I/O). One output group of four discrete 16-circuit blocks. The application program will use logical outputs at addresses %Q0001 to %Q0016. h This requires just 16 output references, because the references used by all four blocks in the group are the same. The references that these blocks will be configured to respond to are assigned to the 16 bits at the end of the output table.
7 Analog I/O Addressing The size of the Analog Input Table is defined during configuration. The maximum size is 8192 analog channels (words). Like the discrete Input and Output Tables, the Analog Input Table is divided into sections. Analog Input Table Input Voting Logic ÉÉÉÉÉÉÉÉ ÉÉÉÉÉÉÉÉ Voted Inputs non-voted Inputs A A inputs B inputs B C inputs C The voted analog references are assigned starting at %AI0001.
7 Example: An application has sixteen analog input groups (each of which is a 6–input group), including spares. The total number of analog inputs from these blocks would be: 16 x 6 = 96 words required. If the Analog Input Table had a configured length of 1024, these inputs would be located in the table as shown below..
7 Register (%R) Memory Assignment for GMR The GMR software uses several areas of %R memory for specific functions, as diagrammed below. Only the area labelled “Application Registers” should be used by the application program. Within that area, a portion is reserved for initialization data, as explained below. %R Memory Allocation for GMR %R1 Application Registers %R and %M Initialization Data Defaults %Rmax–320+66xN 66 words .. .
7 System Status (%S) References System status references are pre-defined locations and nicknames. They can be included in the application program to check for fault-related conditions. For example, status references can be used to: H H Detect forces and overrides. Monitor the fault tables. For a complete listing of %S references, see the Series 90-70 PLC Reference Manual.
7 GMR Status and Control (%M) References The GMR system software uses several %M references as status or control bits. Status bits are used by the GMR software to provide information about GMR operations. These references can be read as needed by the application program. The control bits can be used by the application program to provide information to the GMR software. %M Status References The following table lists the GMR system status flags.
7 PLC OK Flags The meanings associated with the three PLCOK flags are listed below: At PLC A PLCAOK PLC A outputs enabled PLCBOK PLC B communications with PLC A healthy and PLC B outputs enabled PLC C communications with PLC A healthy and PLC C outputs enabled. PLC A communications with PLC B healthy and PLC A outputs enabled PLC B outputs enabled PLC C communications with PLC B healthy and PLC C outputs enabled.
7 %M Control References The application program can use the following %M references to provide information to the GMR software. The references are located at %M12257 – %M12288. Reference Nickname Description Meaning %M12257 CONTINU %M12258 IORES %M12259 PLCRES Perform PLC Fault Table clear. At an individual PLC %M12260 ATMANIN Autotest Manual Initiate Initiates a single autotest (both input and outout) any time it is turned on, even if the Autotest Inhibit bit is on.
7 %M12262 (Report) When this control bit is turned on, it causes the GMR software to report and record the following into the PLC Fault Table of the PLC(s) that turned it on: H The GMR Software Version currently running in the PLC. Example: Application message (10840): GMR Ver:02.06 H The GMR Configuration Utility Version used to create the G_M_R10 Program Block. Example: Application message (10841): Config Util Ver:04.01 H The GMR Configuration File (G_M_R10 Program Block) Checksum.
7 Programming for Startup The PLC Subsystem chapter of this book describes the sequence of actions that occur when the PLCs in a GMR system are started up. H The GMR software in the PLCs only allows one PLC to come online at a time. First, a PLC determines its ID by reading the serial bus addresses of the GMR Bus Controllers (PLC A = 31, PLC B = 30, PLC C = 29). It then sets the corresponding PLC Identification status bit (see page 7-11): %M12225 for PLC A or %M12226 for PLC B, or %M12227 for PLC C.
7 h If both of the other PLCs are already online, the initializing PLC reads the %R (only) initialization data from the other PLC with the higher serial bus address. It then sets its own data to match as shown above. Word type data that will be included in the initialization data exchanged among the PLCs at startup, such as timer and counter accumulators, should be located at the top of the configured %R memory space.
7 Prior to sending the outputs, the application program may check the status flags. If any are found to be 1, the application program may decide to process the initialized data before continuing. When the application program has computed valid outputs that can be sent to output blocks, the application program must set control bit %M12257 (CONTINUE) to 1. When this is done, outputs to the blocks are enabled.
7 an I/O Fault Reset be performed when any of the GMR CPUs are initialized, which will cause any current I/O fault information to be re–reported. If manual output controls are used in a GMR system and the appropriate GMR Autotest inhibit inputs are used to block faults created by the manual controls, any standard Genius type fault (open, overload, short, etc.) is also blocked during the time the inhibit input is on.
7 | | << RUNG 12 >> | |IORESIP IORES |——|# |—————————————————————————————————————————————————————————————————(R)——— | | | In rung 12, the transition of IORESIP (I/O Reset in Progress) to the Off | state indicates that the requested I/O fault reset has been completed. | | This rung resets command bit IORES (I/O Reset) to the Off state.
7 I/O Point Faults The GMR system can optionally use the standard Series 90-70 I/O Point Fault references. The I/O Point Faults feature allocates a bit reference for each potential discrete point fault and a byte reference for each potential analog point fault. Note that space for these references is taken from the space available for the application logic. With I/O Point Faults enabled, when a fault occurs the fault reference (IO_FLT) is set.
7 Programming for Fault and Alarm Contacts The GMR system software can optionally utilize the Fault and Alarm contacts capability of the Series 90-70 PLC to make fault and alarm information available to the application program logic. Conditions that cause Fault and Alarm contacts to be set are described in the Diagnostics chapter. Programming for Fault and Alarm contacts is explained on the following pages.
7 Discrete Input Fault Contacts for GMR In the discrete Input Table there are fault contacts associated with each item of voted input data, non-voted input data, and “raw” data input from bus A, B, and C: ÉÉÉÉÉÉ ÉÉÉÉÉÉ Discrete Input Table Input Voting Logic Voted Inputs Non-voted Inputs A Bus A inputs Bus B inputs B Bus C inputs C Reserved inputs Fault contacts are set for: H H H H Input Genius faults Input discrepancy faults for A, B, and C inputs Input autotest faults Line faults See page 5-
7 Analog Fault Contacts for GMR As for discrete inputs, voted analog inputs have fault contacts associated with both the raw data inputs and the corresponding voted inputs. Non-voted analog inputs also have associated fault contacts.
7 Reading GMR Diagnostics The application program can obtain the following diagnostic information from the GMR system software: H H H H H Autotest faults Discrepancy faults Genius faults Point faults Analog alarms This information is described in detail in the Diagnostics chapter. To obtain this information, the application program should CALL an external Program Block named G_M_R09. Information is read-only; it cannot be written to.
7 Data Table Numbers Table Range for Start Value Range for End Value Digital Input Discrepancy faults Greater than or equal to the first digital input address for A, B, or C. Less than the start plus the maximum digital input address for A, B, or C.
7 Error Codes for GMR Diagnostics The following error codes may be generated by the GMR diagnostics routine (see page 7-24): Code 7-26 Meaning 10908 An attempt was made to read an I/O shutdown timer for an invalid block 10909 An attempt was made to read all I/O shutdown timers for an invalid GBC.
7 Programming for Global Data In a Series 90-70 PLC/Genius system, Global Data is data that is automatically broadcast by a PLC bus controller, each bus scan. The GMR software uses this Global Data capability as the vehicle for exchanging system information between the PLCs. Each PLC provides 8 words of system data to the other PLCs as Global Data.
7 Adding the GMR System Software to a New Application Program Folder The GMR system software provided on the diskette must be added to the folder containing the application program. Follow the steps below to add the GMR system software to a new application program folder. 1. Place the GMR software diskette in a drive where it can be accessed by the Logicmaster programming software. 2. Enter the Logicmaster programming software and go to the folder functions (F8). 3. Create a new Program Folder (F1).
7 Adding the GMR Configuration to the Application Program Folder The GMR configuration software outputs a program block file named G_M_R10.EXE, which must be added to the folder containing the application program. By default, this file is located in the GMR Configuration Utility subdirectory. To add the G_M_R10 program block to the application program folder, use the Librarian function of the Logicmaster software. There are two basic procedures to complete: H H Add G_M_R10 to the Logicmaster librarian.
7 Important . 5. Add G_M_R10 to the library by pressing the Enter key. 6. When prompted for the number of paired input and output parameters, enter 2. 7. Press ESC to return to the Librarian menu. Importing G_M_R10 from the Librarian to the Application Program After G_M_R10 has been added to the Librarian, it can be imported to the Program Folder that contains the application program at any time. 1. From the Librarian menu, select Import (F3). 2.
7 Storing a Program to the PLC All redundant PLCs in the GMR system must use the same application program, but different configurations: PLC A PLC B PLC C y y y Program: GMRPROG Program: GMRPROG Program: GMRPROG Configuration: CONFIGA Configuration: CONFIGB Configuration: CONFIGC Supplying the configuration and program as separate files, as shown above, makes it easier to perform program updates in the future.
7 Things to Consider when Storing to the PLC from the Programmer Use the Store function to copy program logic, configuration data, and /or reference tables from the programmer to the PLC. The Store function copies the program, which remains unchanged in the programmer. If the PLC program name is not the same as the folder name, the Store function clears the program from the PLC. The selected data is then stored from the new program folder.
7 Using the Store Function To use the Store function, press Store (F4) from the Program Utility Functions menu. The Store Program screen appears. The screen shows the currently-selected program folder, which cannot be changed. Three types of data can be stored from the programmer to the PLC: program logic, configuration data, and reference tables. When this screen first appears, only the program logic is set to Y (yes), which is the default selection.
7 Storing a Program to the PLC: the System is NOT Configured for Online Changes If the GMR system is configured not to allow online changes, the PLC must be placed in Stop mode to store a program or make a change to the GMR system. Storing an Identical Program Following CPU Replacement If a PLC is to be stored with an identical program, following replacement of a faulty CPU, then only the PLC to be stored to needs to be placed in Stop mode.
7 Using the Program Download Utility If the redundant PLCs are linked by an SNP network, you can use the Download utility provided on the GMR software diskette when making future application program updates. The Download utility: 1. works with the Logicmaster 90 programming software. 2. stops each of the PLC CPUs, with outputs disabled. 3. stores the updated application program to each of the CPUs. The Download utility assures more efficient, accurate downloading. However, its use is optional.
7 Customizing the Download Utility for Other PLC IDs For PLCs with other PLC IDs, you need to edit the file KEY0.DEF before adding it to the Program Folder in Logicmaster. 1. Install the GMR software diskette in your computer’s diskette drive. 2. At the DOS prompt, log onto that drive. 3. Copy the Download utility files from the diskette to your fixed disk drive: UPLC.EXE LM_KEYS.LST KEY0.DEF 4.
7 Storing a Program to the PLC: the System IS Configured for Online Changes For a system configured to allow online changes, the following sequence illustrates how an online ladder logic program change could be done in a triplex CPU System. System configuration changes are not intended to be done online. (Online ladder logic changes are intended for system debug and commissioning). 1. Using the Logicmaster 90-70 Programming Software in the Monitor mode, make a direct or multidrop connection to PLC “A”.
7 CPU being stored to in Stop mode and store a complete program from the programmer to the PLC. This cleans up any fragmentation that exists and enables future online changes. H 7-38 If an online program change is made to a single PLC and subsequently deleted before the same change is made to the other PLCs in the system, it is possible that the program checksum will not match, even though the programs in the CPUs appear to be the same.
Chapter 8 Installation Information 8 section level 1 1 figure bi level 1 table_big level 1 H H H Genius Bus Connections Termination Boards Input Wiring h h h h H Single Sensor to Three Blocks (Triple Bus) Three Sensors to Three Blocks (Triple Bus) Block Wiring for a 16-Circuit Block in an Input Group Block Wiring for a 32-Circuit Block in an Input Group Output Wiring h h Block Wiring for a 16-Circuit, Four-block Output Group Block Wiring for a 32-Circuit, Four-block Output Group Note The informa
8 Genius Bus Connections When planning and installing a Genius bus, it is extremely important to follow the guidelines given in the Genius I/O System and Communications User’s Manual. That manual describes correct cable types, wiring guidelines, bus length, bus termination, baud rate, and bus ambient electrical information. In GMR system, “GMR busses” can operate at any baud rate with the following restrictions: D. All busses in a group must use the same baud rate. E.
8 Input Wiring Calculating Voltage Drops on Tristate Inputs It is important to consider the field wiring runs required for devices configured as tristate inputs. Devices that are powered by 24V DC will have a voltage-reducing component inserted at the field device to provide an input threshold range for three states. The table on page 2-7 shows appropriate ranges. Wiring runs can reduce the voltage at the input block terminal further, to an inoperable level, depending on the length, conductor, and gauge.
8 Single Sensor to Three Blocks (Triple Bus) PLC A PLC B PLC C P C G G G S P B B B U C C C P C G G G S P B B B U C C C P C G G G S P B B B U C C C A B C A B C A B C 6.2V Zener Diodes for Line Monitoring (optional) DC+ I1 Input 1 I15/32 O16 Input 15 or 32 DC+ I1 I15/32 O16 DC+ I1 I15/32 O16 8-4 H 6.2 volt Zener diodes are used for optional line monitoring on circuits configured as tristate inputs. This option is only available with 16-circuit DC blocks.
8 Input Wiring (continued) Three Sensors to Three Blocks (Triple Bus) PLC A PLC B PLC C P C G G G S P B B B U C C C P C G G G S P B B B U C C C P C G G G S P B B B U C C C A B C A B C A B C 6.2V Zener Diodes for Line Monitoring (optional) DC+ I1 Input 1 I15/32 Input 15 or 32 O16 DC+ Input 1 I1 Input 15 or 32 I15/32 O16 DC+ Input 1 I1 Input 15 or 32 I15/32 O16 GFK-0787B H 6.2 volt Zener diodes are used for optional line monitoring on circuits configured as tristate inputs.
8 Input Wiring (continued) Block Wiring for 16-Circuit Source Block in an Input Group DC Source Block IC660BBD020 If single sensor, it must also be wired to corresponding point on two other input blocks Connection if no points on the block are to be autotested (must disconnect output 16). S1 22V to 56V DC S2 Genius Bus Connections SHLD IN SHLD OUT DC+ 1 * Tristate input requires series zener diode, voltage rating 6.2V * Zener should be wired at the input device.
8 Input Wiring (continued) Block Wiring for 16-Circuit Sink Block in an Input Group DC Sink Block IC660BBD021 If single sensor, it must also be wired to corresponding point on two other input blocks S1 22V to 56V DC S2 Genius Bus Connections SHLD IN SHLD OUT DC+ 1 2 * Tristate input requires parallel zener diode, voltage rating 6.2V 3 Required at each input (for Input Autotesting). 1N5400 or equivalent. 4 5 6 * Zener should be wired at the input device.
8 Input Wiring (continued) Block Wiring for 32-Circuit Source Block in an Input Group DC Source Block IC660BBD024 Connection if no points on the block are to be autotested (must disconnect output 16). If single sensor, it must also be wired to corresponding point on two other input blocks S1 22V to 30V DC S2 Genius Bus Connections SHLD IN SHLD OUT DC+ DC+ DC+ DC+ DC+ 10 Device #1 12 14 Required at each input (for Input Autotesting). 1N5400 or equivalent.
8 Input Wiring (continued) Block Wiring for 32-Circuit Sink Block in an Input Group DC Sink Block IC660BBD025 If single sensor, it must also be wired to corresponding point on two other input blocks S1 22V to 30V DC S2 Genius Bus Connections SHLD IN SHLD OUT +5V DC+ DC+ DC+ DC+ 10 Device #1 12 Required at each input (for Input Autotesting). 1N5400 or equivalent.
8 Output Wiring for a 16-Circuit, 4-Block Group 16- Circuit, 4-Block Output Group P C G G G S P B B B U C C C P C G G G S P B B B U C C C P C G G G S P B B B U C C C A B C A B C A B C Bus B Bus A DC+ DC+ Q1 Q1 Block A (Source) Block B (Source) Q16 Q16 Hi DC+ Hi Output 1 Low Output 16 Low DC+ Bus C Q1 Q1 Block C (Sink) Block D (Sink) Q16 8-10 Q16 H H All blocks in an output group must have the same number of circuits (16 or 32).
8 Output Wiring for a 16-Circuit, 4-Block Group (continued) Block Wiring for a 16-Circuit 4-Block Output Group More detailed installation information is provided in the block datasheets. The labels Block A, Block B, Block C, and Block D refer to the previous system diagram.
8 Output Wiring for a 16-Circuit, 4-Block Group (continued) Output Load Considerations for 16-Circuit 4-Block “H” Pattern Redundant Output Groups Minimum load: Maximum load: Maximum inrush current: Maximum total load for block group: Output Off Leakage Current: For Outputs to be Autotested: Minimum pickup time: Minimum dropout time: 100 milliamps 2.0 Amps 10 Amps for up to 10 milliseconds 15 Amps at 35 degrees C 2.0 milliamps Greater than 20 milliseconds Greater than 7.
8 commanded state. If it does not, the point is pulsed Off again for about 7.5mS. A maximum of two pulses of approximately 5mS and 7.5mS duration can occur. The 7.5mS pulse occurs only if the volts feedback for the first pulse is incorrect. Each output device’s characteristics should be checked against the list above to verify that it can be autotested and/or used in the 4-block output group.
8 Output Wiring for a 32-Circuit, 4-Block Group 32- Circuit, 4-Block Output Group P C G G G S P B B B U C C C P C G G G S P B B B U C C C P C G G G S P B B B U C C C A B C A B C A B C Bus B DC+ DC+ Q1 Q1 Block A (Source) Block B (Source) Q32 Q32 Bus A Hi Low Output 1 Output 32 Hi Low DC+ DC+ Bus C Q1 Q1 Block C (Sink) Block D (Sink) Q32 8-14 H H All blocks in an output group must have 32 circuits. H Unused voted outputs cannot be used as non-voted I/O points.
8 Output Wiring for a 32-Circuit, 4-Block Group (continued) Block Wiring for a 32-Circuit 4-Block Output Group More detailed installation information is provided in the block datasheets. The labels Block A, Block B, Block C, and Block D refer to the previous system diagram.
8 Warning In certain cases, removing the DC power source from an output block or blocks which are part of a 32-circuit 4-block output group, causes leakage currents through the output driver circuits of the powered down block(s). To ensure that these potential leakage currents do not adversly affect the output devices being controlled, the following installation instructions must be followed. A. All 4 blocks in an output group must be powered from the same common power source.
8 Output Wiring for a 32-Circuit, 4-Block Group (continued) Output Load Considerations for 32-Circuit 4-Block “H” Pattern Redundant Output Groups Minimum load: Maximum load: Maximum inrush current: Maximum total load for block group: Output Off Leakage Current: For Outputs to be Autotested: Minimum pickup time: Minimum dropout time: 1.0 milliamp 0.
GFT-166 Revision 1.3 April 4, 1995 Appendix A TÜV Certification A section level 1 1 figure_ap level 1 table_ap level 1 TÜV is an acronym for “Technischer Überwachungs–V erein”, which has a rough translation to English of “Technical Supervisory Group”. TÜV is an independent German technical inspection agency and test laboratory, widely recognized and respected for their testing and approval of electronic components and systems for use in safety critical applications.
A GFT-166 Revision 1.3 April 4, 1995 TÜV Restrictions For all safety relevant applications the safe state must be the de-energized (0) state. A Functional test must be performed to check for the correct design and operation of the system as a whole. This is to include the user’s application program. No change of the system software (operating system, I/O drivers, diagnostics, etc.) is allowed without TÜV type approval and recommissioning.
GFT-166 Revision 1.3 April 4, 1995 A The installation procedures in the Series 90-70 Programmable Controller Installation Manual (GFK-0262D) and this GMR User’s Manual (GFK-0787A) are to be closely observed and complied with, especially the grounding procedures in chapter 3 of the Series 90–70 Programmable Controller Installation Manual (GFK-0262D). All GMR components must be installed in a panel or cabinet which offers protection equal to or greater than specification IP54.
A GFT-166 Revision 1.3 April 4, 1995 Configuration worksheets are available for all I/O block types in the Genius I/O Discrete and Analog Blocks User’s Manual (GEK-90486-2). Each I/O block used in the safety-relevant portion of the system must have a worksheet prepared. Configuration Protect must be Enabled in each block. The HHM must be configured to use serial bus address 0 (the default).
Appendix B Maintenance Override section level 1 1 figure_ap level 1 table_ap level 1 B The information in this appendix is reprinted by permission of TUV. Abstract Suggestions are made about the use of maintenance override of safety relevant sensors and actuators. Ways are shown to overcome the safety problems and the inconvenience of hardwired solutions. A checklist is given.
B The following table shows common requirements. The differences between solution A and B are shown by typeface italic. Requirements for maintenance override handling Responsibility Alreadyduring the software configuration of the PLC system it is determined in a table or in the application program, whether the signal is allowed to be overridden. Project engineer and commissioner responsible for correctconfiguration.
B Recommendations The following recommendations are given to improve the primary safety as described by the list: ' A program in the DCS that checks regularly that no discrepancies exist between the override command signals from the DCS and the override activated signals received by the DCS from the PLC. ' The use of the maintenance override function should be documented on the DCS and on the programming environment if connected. The printout should include: h time stamp of begin and end.
Index A Alarm and Fault contacts, 5-25 , 5-28 , 7-21 Analog blocks, 1-8 AnalogI/O, addressing, 7-7 Analog inputs, 4-12 configuring memory for, 6-18 configuring references for, 6-33 discrepancy, 5-13 , 6-36 maximum, minimum, 6-35 Application program inhibiting, 4-4 , 7-11 storing to PLC, 7-31 updating on SNP network, 1-3 Asynchronous autotest, 4-18 , 6-29 Autotest, 1-7 , 4-18 , 6-29 configuring for inputs, 6-29 configuring for outputs, 6-37 discrete inputs, 2-6 fault, 5-25 , 5-26 sequence, 5-4 B Block I/O t
Index Duplex state, 6-34 F Failed Switch detection, 3-9 , 5-2 Failed Switch fault, 5-26 Fault actions, configuring, 6-22 , 6-23 Fault and Alarm contacts, 5-25 , 5-28 , 7-21 Fault Reporting, 5-3 Fault reporting, 2-2 configuring for I/O blocks, 6-52 in GMR mode, 3-9 Fault Reportting, 6-50 Fault Tables, 5-15 clearing, 5-15 , 7-14 messages for GMR, 5-18 monitoring, 7-10 Fault–locating references, 7-21 Forces and Overrides, 7-10 G GMR mode, 2-6 , 3-9 GMR software adding to application program, 7-28 files on d
Index Inputs and outputs, number available, 1-9 Installation information, 8-1 Internal Channel fault, 5-28 L LED, Block OK, 3-9 Limit discrepancy, 5-12 , 6-36 Line fault, 5-2 , 5-25 Line monitoring, 2-7 Load sharing by output blocks, 3-6 , 5-16 Logicmaster software, version required, 1-2 Logon control, 7-17 Loss of Block fault, 4-18 , 6-30 M configuring autotest, 6-37 disabled at startup, 4-2 discrepancy reporting, 5-12 discrepancy status, 7-11 discrete, in PLC, 4-17 discrete, voting, 3-3 enabled, 7-12 e
Index References for inputs, 6-28 Synchronous Autotest, 4-18 , 6-29 References, reserved, 7-4 Register memory assignments for GMR, 7-9 configuring amount, 6-18 reserved, 7-4 RTD blocks, 1-8 T Test interval, 6-16 Thermocouple blocks, 1-8 Threshold discrepancy, 5-12 , 6-36 S %S status references, 7-10 Serial bus address, configuring, 6-28 , 6-33 , 6-37 , 6-45 , 6-51 Short Circuit fault, 5-2 , 5-26 SNP communications, 1-3 Thresholds, voltage, 2-6 , 3-9 Tristate inputs, 2-6 , 2-7 , 5-14 , 6-52 , 8-3 , 8-5
