Table of Contents
Advertisement
Chapter 3. Configuration
Genius Duplex Configuration
In Duplex redundancy mode, a block compares outputs received from two CPUs and sets any outputs for which
there is disagreement to their Duplex Default state.
All other devices on the Genius Bus (at SBA #1-29) that control discrete outputs need to be properly
configured in order to handle the two sets of output data they will be receiving from SBA#30 and SBA#31. This
parameter is called Duplex Default State. For Genius blocks and Field Control, use the Genius Hand-Held
Monitor (HHM) to set this parameter.
Duplex Default State is configured for each output point on each active I/O device on the Genius bus. The
options are:
•
Default ON
•
Default OFF
•
Hold Last State.
Duplex Default State is employed whenever the output point data received in real time from SBA#30 and
SBA#31 disagree.
NOTE: PNC Critical Network Ports feature does not cause a fatal fail-over in GCG-only PROFINET systems
because GCGs are Simplex devices. Users must monitor in logic both for a Loss of all Critical Ports (either by
monitoring the Controller port bits or watching for the Critical Network Ports diagnostic message) and cause a
logic-initiated roll-over, as well as watching in logic for any GCGs to fail to then also cause a logic-initiated
rollover.
Genius Dual Bus Configuration
In Genius Dual Bus, two Bus Controllers are active on separate Genius busses. Both are typically configured to
use SBA#31. Each I/O device controls which bus it is connected to via a Bus Switching Module (BSM). Thus, if
the Bus Controller on the active bus ceases to transmit, or the bus is physically broken, the I/O device
controlling the BSM senses that condition and switches to the alternate bus. The Genius devices connected in
this fashion must be configured for BSM Present. For Genius blocks and Field Control this is accomplished
using the Handheld Monitor. For VersaMax and 90-70 I/O Scanner Racks, this is accomplished by configuring a
target in the project folder.
Note that the Genius Bus Controller on the inactive bus will not be able to detect traffic from the I/O devices.
Following a bus switch, the newly active Bus Controller then needs to log in all the I/O devices and begin
servicing their I/O and alarms.
When GCG001 is used as the Bus Controller in this manner, application logic is required to overcome the
inherent delays resulting from Genius devices logging into the new bus connections after a bus-switching
event. The application must hold the last state of all inputs (analog and discrete) until all devices have logged
in and are broadcasting their input data to the PLCs.
Each I/O device on the bus that does control a BSM needs to be configured as a BSM Controller. Each such
device will then be able to support the Switch BSM datagram (refer to Section 6.4.9), which is typically used to
test the behavior of the bus following a bus switch. Devices configured as a BSM Controller will automatically
switch away from a defective bus, expecting that the alternate bus is intact and can function properly.
34
1. To change the Duplex Default state, press F2 (tgl).
2. Press F3 (entr) to save the new selection.
3. Press F4 (next) to advance to the next
configuration display.
PACSystems RX3i Genius Communications Gateway
GFK-2892F
Advertisement
Table of Contents
