GFK 2017
GFK 2017
GFK 2017
Series 90-70
Genius® Bus Controller
User's Manual
GFK-2017 July 2003
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.
Note
Notes merely call attention to information that is especially significant to understanding and
operating the equipment.
This document is based on information available at the time of its publication. While efforts
have been made to be accurate, the information contained herein does not purport to cover all
details or variations in hardware or software, nor to provide for every possible contingency in
connection with installation, operation, or maintenance. Features may be described herein
which are not present in all hardware and software systems. GE Fanuc Automation assumes no
obligation of notice to holders of this document with respect to changes subsequently made.
Chapter 1 Introduction............................................................................................................1-1
Product Documentation .........................................................................................1-1
Content of this Manual.............................................................................................. 1-1
Related Publications.................................................................................................. 1-2
System Overview ..................................................................................................1-3
Number of Bus Controllers in a PLC........................................................................ 1-3
Bus Controller Description....................................................................................1-4
Status LEDs............................................................................................................... 1-4
Hand-held Monitor Connector .................................................................................. 1-4
Terminal Assembly ................................................................................................... 1-4
The Genius Bus .....................................................................................................1-5
Bus Controller Operation ......................................................................................1-6
The Genius Bus Scan ................................................................................................ 1-6
Input Data from Devices on the Bus ......................................................................... 1-7
Output Data from the CPU........................................................................................ 1-7
Outputs for 4 Input/2 Output Analog Blocks ............................................................ 1-7
Diagnostics................................................................................................................ 1-9
Input Defaults if the Bus Controller is Lost .............................................................. 1-9
Datagrams............................................................................................................1-10
Global Data..........................................................................................................1-11
Sending Global Data ............................................................................................... 1-11
Receiving Global Data ............................................................................................ 1-12
Chapter 2 Installation..............................................................................................................2-1
Installing the Bus Controller .................................................................................2-2
Removing the Bus Controller.................................................................................... 2-2
Connecting the Serial Bus .....................................................................................2-3
Replacing an Older Bus Controller ........................................................................... 2-3
Shield In and Shield Out Connections in an Existing Installation ........................... 2-3
Terminating the Bus.................................................................................................. 2-4
Wiring for Bus Continuity ........................................................................................ 2-4
GFK-2017 iii
Contents
Chapter 4 Diagnostics..............................................................................................................4-1
System Status References......................................................................................4-2
Fault and No Fault Contacts ..................................................................................4-3
Fault Locating References......................................................................................... 4-3
How FAULT and NO FAULT Contacts Handle Bus Controller Faults in an RX7i
System....................................................................................................................... 4-3
High Alarm and Low Alarm Contacts...................................................................4-4
Fault Table Definitions for Genius Devices..........................................................4-5
Clearing Faults in the Fault Table............................................................................. 4-5
Removing I/O Force Messages from the I/O Fault Table ......................................... 4-5
Loss of Device Faults Caused by High Bus Error Rate ............................................ 4-5
GFK-2017 Contents v
Contents
This manual describes the features and operation of a Series 90™-70 Genius® Bus
Controller when it is used in a PACSystems RX7i or Series 90-70 PLC system. This
manual also provides the configuration and programming information needed to
complete the interface between the system CPU and a Genius bus.
Product Documentation
Content of this Manual
Chapter 1. Introduction: Chapter 1 describes the Bus Controller and explains how it
operates.
Chapter 2. Installation: Chapter 2 explains how to install or remove a Bus Controller,
and how to connect it to a Genius serial bus.
Chapter 3. Bus Controller Configuration: Chapter 3 explains how to complete the
software configuration steps for a Bus Controller and its bus.
Chapter 4. Diagnostics: Chapter 4 describes diagnostics capabilities provided by the
Bus Controller.
Chapter 5. Communication Request: Chapter 5 describes the use of the COMMREQ
program instruction with a Bus Controller.
Chapter 6. Reading Bus Status Information: Chapter 6 explains how the application
program can read the Serial Bus Addresses of active devices or read the status of the
Datagram queue.
Chapter 7. Data Monitoring, Distributed Control, and Redundancy: Chapter 7
describes basic types of data monitoring, distributed control and redundancy systems
that are supported by the Bus Controller.
Appendix A. ASCII Code List: Lists ASCII characters and their decimal and
hexadecimal equivalents.
GFK-2017 1-1
1
Related Publications
Series 90-70 PLC Genius Bus Controller Manual (GFK-0398). This book describes
the use of the Series 90-70 Genius Bus Controller in a Series 90-70 PLC system, and
explains its configuration and programming using the Logicmaster software.
Series 90-70 Remote I/O Scanner User’s Manual (GFK-0579). Reference manual for
the Remote I/O Scanner, which interfaces a drop containing Series 90-70 modules to a
Genius bus. Any CPU capable of controlling the bus can be used as the host. This
book describes the Remote I/O Scanner features, configuration, and operation.
Series Six™ Bus Controller User’s Manual (GFK-0171). Reference manual for the
Bus Controller, which interfaces a Genius bus to a Series Six PLC. This book
describes the installation and operation of the Bus Controller. It also contains the
programming information needed to interface Genius I/O devices to a Series Six PLC.
Series Five™ Bus Controller User’s Manual (GFK-0248). Reference manual for the
Bus Controller, which interfaces a Genius bus to a Series Five PLC. This book
describes the installation and operation of the Bus Controller. It also contains the
programming information needed to interface Genius I/O devices to a Series Five PLC.
System Overview
The Genius Bus Controller (catalog number IC697BEM731) can be used to interface a
PACSystems RX7i controller or Series 90-70 PLC to a broad range of other devices on
a Genius I/O serial bus.
Host Computer
RX7i or Series 90-70 PLC
with Genius Bus Controller
PCIM
Genius Bus
Genius
BIU
LEDs
HHM
Connector
Removable
bus wiring
terminal
assembly
Status LEDs
The LEDs on the front of the Bus Controller indicate its operating status. The top two
LEDs should be on during normal operation. The bottom LED is not used.
Module Shows the status of the Bus Controller. This LED blinks during
OK powerup diagnostics.
Channel Shows the status of the bus. This LED is on steadily when the bus is
OK operating properly. It blinks for intermittent bus errors and is off for a
failed bus. It is also off when no configuration has been received from
the PLC CPU.
Terminal Assembly
Serial bus and shield wiring connections are made to the removable terminal strip on
the front of the Bus Controller. Only the upper three terminals are used. To remove
the Terminal Assembly without disturbing the continuity of the bus, jumpers are used.
See chapter 2.
Conservative wiring practices, as well as national and local codes, require physical
separation between control circuits and power distribution or motor power. Refer to
sections 430 and 725 of the National Electric Code.
Bus Type Daisy-chained bus cable; single twisted pair plus shield or Twinax.
Fiber optics cable and modems can also be used.
Bus 75, 100, 120, or 150 ohm resistor at both ends of electrical bus
Termination cable.
Baud Rate Configurable. 153.6 Kbaud standard, 153.6 Kbaud extended, 76.8
Kbaud, or 38.4 Kbaud.
Maximum Bus 7500 feet at 38.4 Kbaud, 4500 feet at 76.8 Kbaud, 3500 feet at
Length 153.6 Kbaud extended, 2000 feet at 153.6 Kbaud, standard.
Maximum length at each baud rate also depends on cable type.
Chapter 2 provides a complete list of cable types, showing
corresponding bus lengths and baud rates.
Greater bus lengths are possible using sections of fiber optics cable
with modems.
Maximum 32 devices at 153.6 Kbaud standard, 153.6 Kbaud extended, or 76.8
Number of Kbaud. 16 devices at 38.4 Kbaud. Includes bus controller and
Devices
typically a Hand-held Monitor.
Data Encoding Each bit is encoded into three dipulses, majority voted at the
receiver to correct any single dipulse errors. A dipulse is an AC
code consisting of a positive then negative excursion of voltage.
Dipulses are individually sampled to reject low and high frequency
interference.
Modulation Frequency Shift Keying (FSK) 0 to 460.8 KHz max. (153.6 Kilobaud)
Technique
Isolation 2000 volts Hi-Pot, 1500 volts transient common mode rejection.
Signal/noise 60 db
Ratio
Bus
Token Path
Controller
(Device 31)
1 2 3 30
As mentioned earlier, these devices may include other Bus Controllers, or Remote I/O
Scanners, in addition to (or instead of) the Genius blocks illustrated above.
During a bus scan, the Bus Controller automatically:
▪ Receives all input data that has been sent by devices on the bus.
▪ Broadcasts Global Data.
▪ Updates outputs, as permitted, to the devices on the bus. Transmission of outputs
from the Bus Controller can be disabled for one or more devices on the bus.
▪ Receives any fault messages issued by devices on the bus and sets diagnostic
status references for use by the CPU.
▪ Sends a single command received from the CPU (for example, Clear Circuit
Faults) to the appropriate devices.
The amount of time it takes for the communications token to pass to all devices
depends on the baud rate, the number and types of devices on the bus, and the use of
Global Data and datagram communications.
1 2 3 4
Token
The Bus Controller stores all the input data it receives. Once per CPU sweep, the CPU
reads all discrete and analog inputs from the Bus Controller. (Analog data is not
multiplexed).
Bus
1 2 3 4
Controller
has token
Token
The amount of I/O data exchanged during one Genius bus cycle depends on the types
of devices on the bus.
Many Genius I/O blocks have both inputs and outputs on the same block. Blocks
configured in the software as having both inputs and outputs will occupy identical
references in both %I and %Q memory. Unused references cannot be assigned to
other inputs or outputs, and should not be used in the application program.
Diagnostics
Genius blocks and other devices on the bus will automatically report faults, alarms and
certain other predefined conditions to the CPU.
Inputs and Fault Message
Bus from Block 3
Controller
1 2 3 4
Token
F F
F Fault
Only one diagnostic message can be sent during any bus scan. If a fault message has
already been sent (by another device) during that scan, a device saves its own
diagnostic message until the next available bus scan. For example, if the
communications token is currently at device 2, and faults occur at devices 3 and 4 at
the same time, device 3 can send its diagnostic message if another message has not
already been sent. Device 4 must wait at least one more bus scan to send its
diagnostic message.
The Bus Controller stores any diagnostic messages it receives. They are read
automatically by the CPU. Faults may then be displayed in the fault table. Details are
in chapter 4.
▪ System Status References that have been defined for Genius use.
▪ Fault and No Fault contacts that can be used to detect fault and lack of fault
conditions.
▪ Alarm contacts that can be used to indicate when an analog value has reached an
assigned alarm limit.
See chapter 4 for details.
In a Series 90-70 system, if a Bus Controller fails, the Series 90-70 CPU holds all
input data from that Bus Controller at its last valid states, regardless of each block's
configured input default parameter.
Datagrams
The Bus Controller supports all Genius datagrams:
Additional datagrams, not listed above, are sent as system messages; they do not
involve any application programming. The Genius I/O System User’s Manual explains
datagrams in detail. It also shows the formats of the data that is transferred by
datagrams.
In the application program, COMMREQ instructions are used to send datagrams and to
read any unsolicited datagrams that have been received. See chapter 5 for
information.
Global Data
Global Data is data that is automatically and repeatedly broadcast by a Bus Controller.
The Genius Bus Controller can send up to 128 bytes of Global Data each bus scan. It
can receive up to 128 bytes of Global Data each bus scan from each Bus Controller on
its bus.
PACSystems RX7i %I, %Q, %G, %R, %AI, %AQ memory if manually-configured, or %G
CPU memory if automatically-configured. Memory type and beginning
address are chosen during configuration of the receiving bus
controller.
Series 90-70 CPU %I, %Q, %G, %R, %AI, %AQ memory if manually-configured, or %G
memory if automatically-configured. Memory type and beginning
address are chosen during configuration of the receiving bus
controller.
Series Six CPU Register memory. Beginning address selected during configuration
of the Series 90-70 Bus Controller that sent the data.
Series Five CPU Register memory. Beginning address selected during configuration
of the Series 90-70 Bus Controller that sent the data.
Example
In the following example, CPU 1 sends 64 bits of Global Data beginning at %I0101 to
CPU 2. CPU 2 places this data into its own memory beginning at %I0017. CPU 2
sends 8 words of %AQ data beginning at %AQ0001 to CPU 1. CPU 1 places this data
into its own memory beginning at %AI0032.
CPU 1 CPU 2
GFK-2017 2-1
2
2. If the PLC is not part of a redundant system, the bus wiring can be removed from
the Bus Controller.
If the PLC is part of a redundant system and another CPU on the bus is now
functioning as the controller, the Bus Controller can be removed without powering
down the bus, provided the Bus Controller’s Serial 1 terminals and Serial 2
terminals have been jumpered as described in this chapter. If this has been done,
do not disconnect the bus cable or any terminating resistor. Remove the terminal
assembly from the Bus Controller carefully. Avoid contact with exposed cable
wiring. Place the terminal assembly with the bus wiring still attached, in a
protected location.
Caution
If exposed wiring comes in contact with conductive material, data on the bus
may be corrupted, possibly causing the system to shut down.
3. Squeeze the retaining clips at the top and bottom of the cover to disengage them
from the rack rails.
4. Pull the board firmly to remove it from the backplane connector.
5. Slide the board out of the card guide to remove it from the rack.
IN OUT
SERIAL 1 SERIAL 1
SERIAL 2 SERIAL 2
SHIELD SHIELD
OUT IN
NOT
USED
SERIAL 1 SERIAL 1
SERIAL 2 SERIAL 2
SERIAL 1 SERIAL 1
SERIAL 2 SERIAL 2
SHIELD SHIELD
OUT IN
A Bus Controller and the devices on its bus must be configured in two basic, different
procedures.
1. The Bus Controller and the devices on its bus must be configured as part of the
PLC system using the programming software.
2. The devices on the bus must also be configured separately. This includes:
A. Configuring I/O blocks with a Hand-held Monitor and/or Write
Configuration COMMREQs. For a Series 90-70 PLC, some devices can be
configured directly from the programmer on an operating Genius bus.
This book only covers configuration of Bus Controllers with the programming software.
Chapter 7, which describes data monitoring, distributed control, and redundant control
systems.
The Genius Analog and Discrete Blocks Manual, which includes instructions for
configuring I/O blocks.
The Genius I/O System and Communications Manual, which details the data that can
be transferred using Read Configuration and Write Configuration COMMREQs.
The Series 90-70 Remote I/O Scanner User’s Manual, which covers configuration of
Remote Drops.
GFK-2017 3-1
3
Click OK.
To edit a previously-selected module's operating characteristics, double-click
the module in the Project tab or right-click on it and choose Configure.
The Parameter Editor window appears.
The default entries can be used as is, or changed. Until a valid configuration is stored
to the CPU, the Bus Controller will not operate on the Bus, and its Channel OK LED
will not light.
Error Rate This entry determines how the Bus Controller will respond to errors on the
bus. If the Bus Controller should drop off the bus when a specified number of
errors occurs within a 10-second period, enter that number of errors here. If
the Bus Controller should remain on the bus when errors occur and try to
maintain communications, enter 0 here.
Caution
If the bus includes a Bus Switching Module (BSM) or another device that
controls bus switching, the Error Rate MUST be set to 0. Otherwise, the Bus
Controller may drop off the bus when the BSM is switching a device to the
bus.
If the error rate is set to 0, the Bus Controller will use a rate of 10 errors in 10
seconds. If the detected error rate exceeds 10, the Bus Controller will remain
on the bus and flash the Communications LED. The LED will continue to
flash until the number of detected errors is less than 10 errors in 10 seconds.
If the error rate is set to a value greater than 0, the Bus Controller will monitor
the bus for errors. If the number of errors exceeds the configured error rate,
the Bus Controller will turn off the Communications LED and drop off the bus.
The Bus Controller will remain off the bus until the number of detected errors
is less than the configured error rate.
Reference This entry can be used to verify that references already configured for
Address devices on the Genius bus match the status references assigned to the same
Check
devices with the programmer software. If ENABLED, references are checked
for all configured devices except PowerTRAC blocks or “GENA”-based bus
devices. This feature will not detect or configure an unconfigured device, or
correct references that do not match.
I/O Scan Set The Scan Set (as defined in the CPU's Scan Sets tab) assigned to this
module. This can be used only on RX7i and on Release 7 or later 900-series
90-70 CPUs. For all other CPUs, leave this field at its default setting (1).
Redundancy The type of redundancy, if any. See chapter 7 for more detailed
Mode descriptions of redundancy modes. Configuration examples for
redundancy are also shown on the following pages.
Note: if you set up a Bus Controller for redundancy, then either
COPY or UNDELETE the Bus Controller’s configuration, the
Redundancy Mode of the copy or restored version is reset to
NONE and the Redundancy of blocks on the bus is reset to NO.
None: This is the default. None means the Bus Controller
communicates with a single bus, it is the only controller on the bus
sending outputs, and no I/O devices on the bus are set up for any
type of redundancy.
If, during subsequent configuration of devices on the bus, any
device is set up for redundancy, Redundancy Mode is
automatically changed to Dual Bus.
Similarly, if Redundancy Mode is set to anything except NONE,
any devices on the bus that have already been configured
automatically have their Redundancy parameter set to YES.
Dual Bus:
Select Dual Bus if there are two busses, each of which has its own Bus Controller. The
Bus Controllers can be in the same PLC or separate PLCs. Switching devices, usually
Genius Bus Switching Modules (BSMs), each link up to seven additional devices to the
dual busses.
Bus Bus
Controller Controller
BUS A
BUS B
BSM
BSM
CONTROLLER UP TO 7 MORE
BLOCK BLOCKS
Redundant Controller:
Select this for redundant Bus Controllers, either in the same PLC or separate PLCs:
CPU CPU
Bus Bus
Controller Controller
1 2 3 4 5
Select Dual Bus and Redundant Controller for a system that combines redundant Bus
Controllers with a dual bus. It requires two PLCs and four Bus Controllers:
CPU CPU
BUS A
BUS B
1 2 3 4A 4B
BSM BSM
For rack # and slot #, enter the rack and slot number where the other Bus
Controller is located. The bus # entry should be left as 1.
Redundancy Wizards
The Redundancy wizards that are selectable will depend on whether you are
configuring a Series 90-70 or RX7i system. For example:
▪ Set up a Primary Rack System for CPU Redundancy. This wizard configures
Hot Standby CPU Redundancy for a Series 90-70 CPU IC697CPU780,
IC697CGR772, or IC697CGR935 only.
▪ Add GBCs for Genius Redundancy, selects a Genius redundancy scheme and
the location of the Bus Controllers.
▪ Copy a Redundant Genius Bus, synchronizes two redundant busses. You can
choose whether the destination bus is cleared before the copy and whether all
devices or only devices marked redundant are copied. The source Bus Controller
defaults to the slot that is currently selected. If the source and destination are not
properly paired, including Redundancy Mode and Serial Bus Address, the copy
operation is not allowed.
2. Select Next.
3. Choose the CPU type and redundancy type to configure. For example, “Single Bus
with Preferred Master”:
4. Select Next.
5. Review the configuration parameters:
6. If the CPU, redundancy type, Bus Transmitter location and Redundancy module
location are correct, select Finish to complete the redundancy configuration.
7. Another wizard, also accessed from the Redundancy: Wizards menu can be used
to generate the secondary hardware configuration, as described later in this
chapter.
BUS A
BUS B
BSM
BSM
CONTROLLER UP TO 7 MORE
BLOCK BLOCKS
1. In the Redundancy wizard, select: Add GBCs for Genius Redundancy, then Dual
Bus One PLC:
2. Click Next.
3. Select rack and slot locations for the primary Bus Controller and the paired Bus
Controller. On a PACSystems RX7i, if you cannot select the expansion rack you
want, you need to add it to the rack system.
4. Click Next.
5. Review the settings for Redundancy Scheme and Bus Controller locations.
Bus Bus
CPU
Controller Controller
30 31
1 2 3 4 5
6. Click Next.
7. Review the settings for Redundancy Scheme and Bus Controller locations. If
settings are correct, click Finish.
When you click Finish, the software adds two Bus Controllers to the PLC. The
parameter settings of the second Bus Controller (except for the rack and slot numbers,
and Serial bus Address) are a copy of those of the first Bus Controller. The two Bus
Controllers are, by default, assigned Serial Bus Addresses 30 and 31. Those Serial
Bus Addresses should not be changed.
CPU CPU
Bus Bus
Controller Controller
31 30
1 2 3 4 5
4. Click Next. Select the rack and slot location for the primary Bus Controller. On a
PACSystems RX7i, if you cannot select the expansion rack you want, you need to
add it to the rack system.
5. Click Next.
6. Review the settings for Redundancy Scheme and Bus Controller locations. If
settings are correct, click Finish. If you need to make changes, click Back.
When you click Finish, a second Genius Bus Controller is added to the PLC. The
parameter settings of this second Bus Controller (except the rack and slot numbers,
and Serial Bus Address) are the same as the first Bus Controller. The Serial Bus
Address for the primary Bus Controller is, by default, 31. The Serial Bus Address of the
other Bus Controller is 30. You should leave the Serial Bus Addresses at their default
settings.
Add GBCs for Genius Redundancy: Dual Bus and Redundant Controllers with Two PLCs
This Genius Redundancy option consists of two PLCs, each with two Bus Controllers,
controlling dual busses. Two open rack slots must be available in this PLC for the Bus
Controllers. The paired Bus Controller may be in any rack.
Select Dual Bus and Redundant Controller for a system that combines redundant Bus
Controllers with a dual bus. It requires two PLCs and four Bus Controllers:
CPU CPU
BUS A
BUS B
1 2 3 4A 4B
BSM BSM
1. In Redundancy wizard, select Add GBCs for Genius Redundancy and click the
Next button.
2. Select Dual Bus and Redundant Controllers, Two PLCs:
3. Click Next.
4. Select the rack and slot locations for the two Bus Controllers. On a
PACSystems RX7i, if you cannot select the expansion rack you want, you
need to add it to the rack system.
5. Click Next.
6. Review the settings for Redundancy Scheme and Bus Controller locations. If
settings are correct, click Finish. If you need to make changes, click Back.
When you click Finish, two Genius busses are created and two Bus Controllers are
added to the PLC. The parameter settings of the second Bus Controller (except for the
rack and slot numbers and Serial Bus Address) are the same as for the first Bus
Controller. The two Bus Controllers are, by default, assigned Serial Bus Addresses 30
and 31. Each bus contains an image of both Bus Controllers.
2. Click Next.
From here you can add, copy, cut, replace, paste, and delete modules on the bus.
2. After selecting the Serial Bus Address, the Device Catalog appears. Use the tabs
to display lists of modules. For example:
3. Select the device to add at the selected Serial Bus Address and click OK. A
configuration screen for that device will appear.
You must enter a configuration screen for each device. This assigns program
references to the device's data and establishes certain system parameters. It does
NOT configure the characteristics of the bus devices themselves. That separate
configuration is normally done using a Hand-held Monitor, but may also be done using
Communication Request instructions in the application program. For information about
Communication Request instructions, see chapter 5. For a Series 90-70 PLC CPU, it
may be possible to directly configure device parameters as described later in this
chapter.
1 2 3 4 5
BLOCK REFERENCE TYPE QI AQI Q AI I
INPUT REFERENCES 17-24 1-4 5-10 1-16
31 OUTPUT REFERENCES 17-24 1-4 1-16
1 2 3 4 5
1 2 3 4 5
1 2 3 4 5
%I x x x x x x x x x x x x x x x x x x x x x x x x
1 16 32
%Q x x x x x x x x x x x x x x x x x x x x x x x x
1 16 32
1 2 3 4 5
1 2 3 4 5
%I x x x x x x x x x x x x x x x x x x x x x x x x
1 16 32
x x x x x x x x x x x x x x x x
%Q 1 16 32
x x x x x x x x
33 40
In this case, the Reference Address %Q0001 could be entered from the keyboard,
resulting in the memory usage shown first.
Disabling Outputs
If outputs are disabled, the Bus Controller will not send output data from the CPU to the
designated device(s). Output Disable is not selectable for inputs-only devices. Inputs-
only blocks are ALWAYS sent a dummy message to turn on their I/O Enabled LEDs.
It is possible for outputs to be disabled or re-enabled using Communication Request
instructions in the application program. If this capability will be needed, the outputs
should be enabled during I/O configuration.
Ordinarily, the configuration software would be used to disable outputs that should
remain disabled. To re-enable such inputs, it would be necessary to change the
configuration and re-store the new configuration to the PLC.
Outputs might be disabled in a system where multiple CPUs are used for distributed
control, or a system using the CPU as an assigned monitoring device. Examples are
shown below.
Example
Selectively Disabling Outputs for Distributed Control of I/O Blocks: Some systems use
two or more CPUs on the same bus for distributed control of I/O blocks. In a distributed
control system, each CPU sends outputs to (and receives fault reports from) certain
blocks on the bus and not others. This is accomplished by selectively enabling or
disabling outputs to the blocks.
OUTPUTS
1 2 3 4 5 6
Example
Disabling Outputs for an Assigned Monitor: If the CPU will be used to monitor
inputs from certain blocks on the bus, outputs to those blocks should be disabled.
When being used as a monitor, the CPU will also receive fault reports and
configuration change messages if the blocks have been sent Assign Monitor
datagrams.
CONTROLLER MONITOR
PLC PLC
Outputs
1 2 3 4
Output data for these blocks will be supplied by one or more other CPUs on the
same bus.
CONTROLLER MONITOR
PLC PLC
Bus Bus
Controller Controller
Inputs
1 2 3 4
If a CPU is used as a monitor, it may NOT have two of its Bus Controllers located
on the same bus. Otherwise, the CPU would receive input data from both Bus
Controllers for the same references, and internal system errors will result.
If Redundancy is set to YES for any device on a bus, the Bus Controller must also be
configured for a form of redundancy: dual bus, redundant control, or dual
bus/redundant control.
The configuration software will automatically attempt to supply a correct configuration
when you set device Redundancy to YES:
▪ If the Bus Controller is configured for a Redundancy Mode of NONE, and you set
the Redundancy of any device on the bus to YES, the Bus Controller’s
configuration is automatically changed to Redundancy: DUAL BUS and Paired
GBC: EXTERNAL.
▪ If the Bus Controller is configured for a Redundancy Mode of either DUAL BUS or
Redundant Control (Redundant Controller), and Paired GBC is INTERNAL, each
device on the bus is automatically configured at the same bus address (Serial Bus
Address) on the redundant bus, and given the same reference addresses.
If Paired GBC is set to EXTERNAL, the block is not automatically configured on
the other bus of the pair.
▪ If the Bus Controller is configured for a Redundancy Mode of dual bus/redundant
controllers each device on the bus is automatically configured at the same bus
address (Serial Bus Address) on the redundant bus, and given the same reference
address.
Edit the Serial Bus Address as required. It can be any value from 0 through 31. You
cannot change a bus device's Serial Bus Address to that used by the Bus Controller. If
you change the selected device's Serial Bus Address to one already that is assigned to
a device on the bus, the existing device will be replaced.
Note
If a Remote I/O Scanner has an SBA conflict on an operating bus, it
will not scan the modules in the remote drop until the fault is cleared.
Select the Remote I/O Scanner from the Genius Interface tab:
The redundancy mode of the Remote I/O Scanner is automatically matched to the
Redundancy Mode configuration of the Bus Controller.
Please refer to the Series 90-70 Remote I/O Scanner User’s Manual for information
about selecting input defaults, enabling outputs, and defining the I/O mapping for the
Remote I/O Scanner.
If Redundancy is set to YES, the local Bus Controller must also be configured for a
form of redundancy. The configuration software will automatically attempt to supply a
correct configuration when you set device Redundancy to YES.
If it will accept the Global Data, select the CPU reference address for the data to be
placed after it is received.
To: The beginning address in %I, %Q, %G, %AI, %AQ, or %R memory.
Input The amount of Global Data expected to be received. For bit-oriented
Length: data, this is the number of bits. For word-oriented data, it is the
number of words. If the expected data length (defined by
configuration) and the actual data length (defined by the content of the
Read ID Reply message from the module) don’t agree, a System
Configuration Mismatch fault is placed in the PLC Fault Table.
If Redundancy is set to YES, the Bus Controller must also be configured for a form of
redundancy. The configuration software will automatically attempt to supply a correct
configuration when you set device Redundancy to YES.
For more information about the content and format of PowerTRAC block data, please
see the PowerTRAC Block User’s Manual.
For more information about the content and format of this data, please see the High-
speed Counter User’s Manual.
If Redundancy is set to YES, the Bus Controller must also be configured for a form of
redundancy. The configuration software will automatically attempt to supply a correct
configuration when you set device Redundancy to YES.
Press the Enter key. A configuration screen like this will appear:
Select the beginning references and lengths for the module’s bit and word data. The
combined lengths of bit and word inputs (%I and %AI) must exactly match the amount
of data that will be sent by the device. The combined lengths of bit and word outputs
(%Q and %AQ) must exactly match the amount of data that will be sent by the Bus
Controller to the device. If the generic device being configured is a Bus Controller,
assign it INPUTS ONLY.
You can also select the default state for the device’s input data, and enable or disable
CPU outputs to the device.
If the generic module's Redundancy is set to YES, the local Bus Controller must also
be configured for a form of redundancy. The configuration software will automatically
attempt to supply a correct configuration when you set device Redundancy to YES.
3. The Copy Bus dialog box appears. Select the rack and slot location of the
destination Bus Controller and click OK.
3. Expand the Rack that contains the GBC and expand the slot containing the GBC.
4. Right-click the Genius device and choose:
This chapter describes the following diagnostics capabilities in a system that uses
Genius I/O and communications:
▪ Fault and No Fault Contacts, which can be used with program references or with
the built-in fault-locating references.
▪ High Alarm and Low Alarm Contacts, which will indicate when an analog reference
has reached one of its alarm limits.
▪ Fault Table faults related to the Bus Controller and Genius devices.
GFK-2017 4-1
4
These references and their Nicknames can be used like any other type of reference.
Example:
A PLC system includes one Bus Controller. During CPU configuration, the system
status fault LOS_IOC has been designated a diagnostic (rather than fatal) fault.
LOS_IOC represents loss of the Bus Controller; if this occurs, the Loss of IOC fault will
be placed in the I/O Fault Table. In this example, the application program also
monitors the LOS_IOC reference. If this reference is set, the contact passes power
flow to an output coil, which energizes a warning light on an operator panel.
LOSS_IOC %Q00023
Example:
%AI0034 %M00053
[ FAULT ]
When used with a %I, %Q, %AI, or %AQ reference, a fault associated with the FAULT
contact must be cleared to remove it from the fault table and stop the contact passing
power flow. Clearing such a fault with a Hand-held Monitor does not remove it from the
fault table or stop the contact passing power flow.
NOFAULT contacts will also detect faults in discrete or analog inputs and outputs. A
NO FAULT contact passes power flow if its associated reference does not have a
circuit fault.
Example:
%I00167 %Q00168
[ NOFLT ]
How FAULT and NO FAULT Contacts Handle Bus Controller Faults in an RX7i System
For an RX7i system (only), if a Bus Controller failure fault is reported to the fault tables,
all bus and module fault-locating references associated with that Bus Controller are
set. The FAULT contact passes power flow and the NO FAULT contact does not pass
power flow. When a Bus Controller reset fault is reported to the fault tables, all of the
bus and module fault-locating references are cleared. The FAULT contact does not
pass power flow and the NO FAULT contact passes power flow.
Example
The analog input assigned to reference %AI00015 has been configured to have the
following Alarm Limits:
150 ft/sec High Alarm
25 ft/sec Low Alarm
If the input exceeds a rate of 150 feet per second, a HI ALARM contact energizes
internal coil %M00002.
%AI0015 %M00002
[ HIALR ]
Example
If the same analog input slows to a rate of 22 feet per second, its LO ALARM contact
energizes internal coil %M00003.
%AI0015 %M00003
[ LOALR ]
Clearing the Fault Table causes the Bus Controller to send a Clear All Circuit Faults
background message to all blocks on the bus. Faults can be cleared from the Fault
Table either from the programmer screen or by the application program.
Clearing the Fault Table removes the faults it contains; it does not clear fault conditions
in the system. If the condition that caused a fault still exists and is detected, the fault
will be reported again.
Diag.
Fault or Indicates Fault Indicates Fault Indicates
Category Fatal Type Description
CIRCUIT D Short DISCRETE Circuit fault on LOSS POWER Loss of user side power
FAULT circuit, FAULT discrete I/O SHORT CIRCUIT Short in user wiring
open wire, point
etc. OVERLOAD Sustained overcurrent
NO LOAD Very low or no current flow
OVER TEMP Switch temperature too high
SWITCH FAIL Genius “smart switch” failure
POINT FAULT Integral individual point fault
FUSE BLOWN Integral output fuse blown.
ANALOG Fault on AI LOW ALARM Input channel low alarm
FAULT analog I/O
AI HI ALARM Input channel high alarm
channel
AI UNDER RANGE Input channel under range
AI OVER RANGE Input channel over range
OPEN WIRE Open wire detected on input
channel
AQ UNDER RANGE Output channel under range
AQ OVER RANGE Output channel over range
CS FEEDBACK ERR Feedback error from Current-
source Analog block
GENA Fault on a GENA CKT FLT Fault on a GENA analog or
FAULT GENA discrete point
LL Fault on a AI LOW ALARM Input channel low alarm
ANALOG low-level
AI HI ALARM Input channel high alarm
FAULT analog
channel AI UNDER RANGE Input channel under range
AI OVER RANGE Input channel over range
OPEN WIRE Open wire detected on input
channel
WIRING ERROR Improper RTD connection or
thermocouple reverse junction
fault
INTERNAL FAULT Cold junction sensor fault on
thermocouple block, or internal
error in RTD block.
INPUT SHORT Input channel shorted
REMOTE Fault on a n/a Any fault detected by a Remote
FAULT Remote I/O I/O Scanner and sent to the PLC.
Scanner
Diag
Fault or Indicates Fault Indicates Fault Indicates
Category Fatal Type Description
LOSS OF D Block no NOT SPEC No reason specified
DEVICE longer FAULT
responding. AD COMM Loss of A/D
FAULT communications.
ADDITION D New block
OF DEVICE appeared
GENIUS D Redundant
BUS
SWITCH
bus switched
I/O BUS D Genius bus BUS FAULT Genius bus fault
FAULT fault
BUS OUT Bus Controller disabled
DISABLE all outputs on the bus
because
communications timed
out between the PLC
CPU and the Bus
Controller.
SBA Bus Controller’s Device
CONFLICT Number duplicated
elsewhere on bus.
I/O D EEPROM HEADEND Block Fault (EEPROM, CONFIG MEM Genius EEPROM or
MODULE fault, watch FAULT Watchdog, etc..) FAIL NVRAM failure
FAULT
dog timeout
CAL MEM FAIL Genius calibration
memory failure
SHARE RAM Genius Shared RAM
FAIL fault
INTRNAL CKT Genius internal circuit
FLT fault
WD TIMEOUT Watchdog Timeout
(discrete I/O modules
only)
POINT FAULT Point fault (also
indicated for CIRCUIT
FAULT category)
FUSE BLOWN Integral output fuse
blown (also indicated
for CIRCUIT FAULT
category)
A TO D Analog to digital
COMM communications fault or
FAULT calibration error
USER Scaling error cause out
SCALING of range values
ERROR
Diag. or
Fault Fatal Indicates Fault Indicates Fault
Category Type Description
ADDITION D Addition of Bus
OF IOC Controller
LOSS OF IOC F* Loss of or missing
Bus Controller
BUS F* Bus Controller
CONTROLLER software fault
SOFTWARE
FAULT
FORCED D Genius I/O point
CIRCUIT forced (eg: from
Hand-held Monitor)
UNFORCED D Last forced circuit
CIRCUIT released (eg: from
Hand-held Monitor)
EXTRA DEVICE D Found extra device on
Genius bus
EXCESSIVE D Bus Controller has HIGH ERROR Bus Controller has
FAULTS stopped reporting RATE dropped off the bus for at
faults because too least 1.5 seconds.
many have occurred
GBC D Bus Controller DG QUEUE Incoming datagram queue
SOFTWARE software exception FULL is full
EXCEPTION
RW QUEUE The queue for Read/Write
FULL requests in the Bus
Controller is full. The
requests may be from the
Genius bus or from
COMREQs.
LP MAIL The low-priority mail
REJECTED queue from the Bus
Controller to the PLC is
full. The response to the
PLC was lost.
Level 1 and 2 passwords, which prevent write access, cannot be used in applications
that include COMMREQs. COMMREQs require write access to return their completion
status.
GFK-2017 5-1
5
Second, the program must use a COMMREQ instruction to perform the intended
function.
Application
Program
Sends COMMREQ
Bus Controller
to Device
Third, the program should check the status of the requested task by looking at an
area of CPU memory that is referred to as the Status Block.
The length of the Command Block depends on the type of COMMREQ being sent. 70
words is the maximum, for a COMMREQ that transfers a 128-byte datagram; most
Command Blocks are much shorter. A table on page 5-5 gives an overview of the
contents of each type of COMMREQ that may be sent to a Series 90-70 Genius Bus
Controller.
Length: The first word of the Command Block indicates the “data block” length.
This is the amount of data from [address + 6] to the end of the
Command Block Each type of COMMREQ command has a unique
Data Block, as shown in this chapter.
Wait/No Wait This must be set to 0 for No Wait.
Flag:
Status The Status Pointer Memory Type and Offset (see below) identify the
Pointer location of the function’s associated Status Block. The Status Block is
Memory where the COMMREQ will return its status. If one of the bit-oriented
memories (%I or %Q) is used as the status location, its bits can be
Type:
monitored (see page 5-9).
Location Data
address + 1 Status Pointer Memory
address + 2 Status Pointer offset
The high byte of address + 2 of the pointer is not used; it must be zero.
The low byte of address + 2 specifies the type of memory where the
Status Pointer will be located.
Status Address + 3 of the Command Block contains the address within the
Pointer memory type selected. The offset of the status location is 0-based.
Offset: For example, if the Status Block were located at %R099, memory type
would be specified as 08 (for %R memory) and the offset would be 98.
If %W memory is used, the address must be in the range %W00001 to
%W65536.
Idle Timeout This field is not used for the No Wait mode of communication.
Value:
Maximum This field is not used for the No Wait mode of communication.
Communication
Time:
Data Block: The Data Block contains the parameters of the command. Complete
descriptions of all commands appear later in this chapter. The Data
Block begins with a Command Number in Address +6. The Command
Number identifies the type of communications function to be
performed. The following Command Numbers are used for the Genius
Bus Controller:
Command Function
1 Pulse Test Outputs
2 Read Configuration
3 Write Configuration
4 Read Diagnostics
5 Clear Circuit Fault
6 Clear All Circuit Faults
7 Assign Monitor
8 Outputs enable/disable
9 Global Data enable/disable
10 Switch BSM
11 Read Device
12 Write Device
13 Dequeue Datagram
14 Send Datagram
15 Request Datagram Reply
16 I/O Fault Category enable/disable
Application
Program
Sends COMMREQ
Bus Controller
to Device
Enable COMM_
REQ
First word of command block IN FT
Location SYSID
COMMREQ Inputs
(enable) Permissive logic that controls power flow to the COMMREQ function
block.
The memory location of the Command Block, which contains the
IN:
specific command information. The Command Block may be located
in any word-oriented area of memory (%P, %L, %R, %AI, or %AQ).
A hex value that gives the rack and slot location of the Bus Controller.
SYSID:
Use this format:
R S 1 2
rack rack 1
slot slot 2
Examples
TASK: For Bus Controller version IC697BEM731, the task is always “1”.
COMMREQ Outputs
The function’s OK and FT outputs can provide power flow to optional logic which can
verify successful completion of the COMMREQ. The OK and FT outputs may have
these states:
The OK and FT outputs are never both true at the same time; OK indicates correct
execution while FT indicates a fault condition. The COMMREQ passes power flow to
OK unless:
▪ The specified task is not valid for the device. This is not checked if the specified
device is a Genius Bus Controller.
Note
Because COMMREQs require write access to return their status, level
1 and 2 passwords, which prevent write access, cannot be used with
COMMREQs.
If one of the bit-oriented memories (%I or %Q) is used as the status location, its bits
can be monitored. These bits correspond to the binary values listed below. For
example, if %I048 were selected as the beginning location, reference %I050 would be
set to 1 each time the COMMREQ completed successfully.
When the previous COMMREQ has completed, the program should set the Status
Block to a value not in the list on the next page. Establishing this initial condition
allows the program to differentiate between the result of an earlier command and the
currently-executing command.
The upper word of the status location provides additional status information.
VALUE
decimal DESCRIPTION
(word)
11 Non-discrete block specified for Pulse Test
21 Non-I/O device specified for Read Configuration
51 Invalid circuit number
71 Non-controller device specified for Assign Monitor
101 Switch BSM - device not BSM
102 Switch BSM - bus position greater than 1
121 P and L access not available
141 Function code greater than 111
142 Sub function code greater than 255
143 Priority greater than 1
144 Datagram length greater than 134
201 Invalid Device Number (greater than 31, but not 255)
202 Incorrect length for the command type
203 Device Number not configured or not active
204 Previous No Wait command in progress; current No Wait command not accepted
205 Invalid status pointer location specified
206 Command number is out of range
207 Subcommand code is out of range
208 Only partial data transferred
209 Device Number 255 not allowed for this command
210 Command specified is not valid for Genius Bus Controller
211 Command specified is only valid for controller devices
212 Command specified is not supported by the device to which it was sent
213 Invalid Alarm Enable/Disable mask
Programming Examples
The following example shows how a Communication Request can be used to clear a
circuit fault on point 4 of a Genius I/O block whose Device Number is 20.
FST_SCN
MOVE MOVE MOVE
UINT UINT UINT
CONST IN Q %R00100 CONST IN Q %R00101 CONST IN Q %R00102
00003 00000 00008
LEN LEN LEN
0001 0001 0001
FST_SCN
MOVE MOVE MOVE
UINT UINT UINT
CONST IN Q %R00103 CONST IN Q %R00104 CONST IN Q %R00105
00098 00000 00000
LEN LEN LEN
0001 0001 0001
FST_SCN
MOVE MOVE MOVE
UINT UINT UINT
CONST IN Q %R00106 CONST IN Q %R00107 CONST IN Q %R00108
00005 00020 00004
LEN LEN LEN
0001 0001 0001
%Q00128 %Q00129
S
COMM_
REQ
%Q00130
%R00100 IN FT S
CONST SYSID
00002
CONST TASK
00001
This example logic uses a series of Move instructions to assemble the data that will be
used as inputs for the Communication Request instruction, and for its associated
Command Block.
Address Contents Value Description
%R100 Command length 3 No wait
%R101 Wait/No Wait Flag 0 Selects %R memory type
%R102 Status Pointer Memory 08 Address in %R memory (%R099)
%R103 Status Pointer Offset 98 Unused (No Wait selected)
%R104 Idle Timeout Value 0 Unused (No Wait selected)
%R105 Max.Communication Time 0 Clear Circuit Fault
%R106 Command Number 5 Device Number of the block
%R107 Device Number 20 Clear 4th point on block (For a COMMREQ, points
%R108 Point to be cleared 4 are numbered starting at 1 (not 0). If this were a
datagram message instead of a COMMREQ
command, points would begin at 0).
The Move instructions are executed during the first CPU sweep, when the special
reference FST_SCN is true. This assures that the Communication Request will never
be executed with incomplete or incorrect parameters.
The example uses the reference %Q128 as a permissive to the Communication
Request. Output %Q129 is set if the Communication Request executes successfully.
If it does not, output %Q130 is set instead. For the Communication Request, failure
might occur if the Communication Request has been set up incorrectly, or for any of
the other errors specified in the beginning of this chapter. A fault output is NOT caused
by failure to receive a reply. This must be detected from the contents of the status
location.
%Q00128 %Q00129
S
COMM_
REQ
%Q00130
%R00100 IN FT S
CONST SYSID
00002
CONST TASK
00001
Another way to assemble the data for the example Command Block would be to use a
Block Move instruction:
FST_SCN
BLKMV BLKMV
INT INT
CONST IN1 Q %R00100 CONST IN1 Q %R00107
+00002 +00020
CONST IN2 CONST IN2
+00000 +00004
CONST IN3 CONST IN3
+00008 +00000
CONST IN4 CONST IN4
+00098 +00000
CONST IN5 CONST IN5
+00000 +00000
CONST IN6 CONST IN6
+00000 +00000
CONST IN7 CONST IN7
+00005 +00000
Before a block can be sent this command, its Device Number (serial bus address) must
be set up by software configuration. In addition, the block must have had its Device
Number entered using a Hand-held Monitor.
The length of the data sent with this command must exactly match the length required
by the device. If the lengths are not equal the Bus Controller returns a Syntax Error to
the COMMREQ status location.
Address: Command Length This number equals the amount of configuration data
to be sent, plus 3. For example, for an RTD block,
which has 42 words of configuration data, you would
enter 45 here. Configuration data formats for all
Genius I/O blocks are shown in the Genius I/O
System User’s Manual.
Address +1: No Wait 0
Address +2: Status Block memory 70 (%I), 72 (%Q), 8 (%R), 10 (%AI), or 12 (%AQ).
type For RX71 only, also 196 (%W).
Address +3: Status Block offset Beginning address for the COMMREQ status. For
%W, this must be in the range 00001 – 65536.
Address +4: Idle timeout value 0
Address +5: Max. communications 0
time
Address +6: Command number 3
Address +7: Device Number 0 - 31. (SBA of the block to which configuration data
will be written).
Address +8: Length of configuration Up to 248 bytes (128 words) of configuration data
data in bytes. may be written to a device. See “COMMREQ #2:
Read Configuration” for data lengths.
Address +9 to Configuration Data Configuration data formats are given in the Genius
Address +n: I/O System User’s Manual.
CONTROLLER MONITOR
PLC COMPUTER
BUS PCIM
CONTROLLER
I/O BLOCKS
Multiple CPUs might be used to monitor different blocks on the same bus. However,
only one device can be assigned to monitor any given block.
When the Bus Controller receives the Assign Monitor COMMREQ command from the
CPU, it issues a normal-priority Assign Monitor Datagram to one block or to all blocks
on the bus. If sent to bus interface modules, it has no effect.
Memory Specification: RX7i, Series 90-70 PLC, or Series 90-30 PLC CPU
In address + 8 enter the memory type, using one of the numbers listed in the table
below.
Memory Offset
In address +9, enter a numerical offset within this memory type, for the beginning of
the data. Memory offsets start at 0; thus %R1 and %I1 are both accessed using a
Memory Offset of 0.
Example A: For 3 bits starting at %I0014, you would enter the offset 13, and a data length of 3 bits.
Example B: To write data to an RX7i, Series 90-70 PLC, or Series 90-30 PLC CPU beginning at
%R100, you would enter the Memory Type 8 (decimal) and the Memory Offset 99
(decimal).
Bit Mode or Byte Mode for an RX7i, Series 90-70 PLC, or Series 90-30 PLC CPU
Bit-oriented memories (%I and %Q) can be accessed either on byte boundaries (byte
mode) or as a string of bits (bit mode). Bit mode is used to access a single point within
a discrete memory, or a collection of points within a discrete memory which need not
start or end on a byte boundary. Byte mode is used to access one or more groups of 8
contiguous points within a discrete memory, and must start on a byte boundary.
In byte mode, the Message Offset reflects the byte being read or written. Offset 0
corresponds to bits 1-8, offset 1 to bits 9-16, and so on.
In bit mode, the Message Offset reflects the bit being read or written, offset 0
corresponds to bit 1, offset 1 to bit 2, and so on.
In bit mode, one or more bytes of data are read or written, even though some of the
bits within the bytes might be ignored. The bit or bits will be in the correct offset
position within the byte. For example, if three bits starting a %I0020 are requested,
they will appear in the middle of the returned data byte. The “-” indicates unused bits.
On READ, they are guaranteed to be 0. On WRITE, they are ignored.
- - I22 I21 I20 - - -
b7 b6 b5 b4 b3 b2 b1 b0
If four bits starting at %I00007 are requested, two bytes are transferred.
- - - - - - I10 I9 I8 I7 - - - - - -
b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
byte boundary byte boundary
Hex ASCII equivalents are listed in appendix A. Lowercase letters are not valid in
names.
Absolute Address
Series Six Memory Type
Decimal Hexadecimal
I/O Status Table Outputs 08192 - 08319 2000 - 207F
Inputs 08320 - 08447 2080 - 20FF
Register Memory R00001-R16384 16384 - 32767 4000 - 7FFF
Caution
To find the exact offset in the register table, follow these steps:
1. Subtract 1 from the register number.
2. Multiply the result by 2 to find the decimal byte offset.
3. Continue as described below.
For a decimal offset in the register or I/O tables:
1. Convert the decimal number to hex.
2. Add the hex number to the beginning offset for that memory type.
%Q00001 PLC
PLC
COMM
REQ
%Q00002
%R00001 IN FT Genius
GBC #31 Bus GBC #29
CONST SYSID
00002
CONST TASK
00001
When the data is received from the target PLC, the requesting PLC will store it
beginning at %AQ0050 in its own memory.
* In hex, the two values in Address +12 are 31h (ASCII 1) and 00h (ASCII nul).
▪ Replies that are received after sending Reply-type datagrams with the Send
Datagram command. (If Send Datagram with Reply is used instead, it
automatically handles replies).
▪ Unsolicited datagrams that are not recognized by the Bus Controller (Function
Code not 20).
If the Bus Scan Time is Greater than the CPU Sweep Time
If all Datagrams on the bus are sent with Normal Priority, there is a limit of one
incoming Datagram per CPU sweep. Therefore, only one Dequeue Datagram
command per sweep will be needed to handle incoming Datagrams.
If all Datagrams on the bus are sent with High Priority, the Bus Controller can
potentially receive one Datagram from each transmitting device during a scan. The
program should include the same number of Dequeue Datagram commands as
incoming Datagrams.
If the Bus Scan Time is Less than the CPU Sweep Time
If the bus scan time is significantly shorter than the CPU sweep time, you can estimate
the number of Dequeue Datagram commands that must be sent to the Bus Controller
to accommodate incoming Datagrams on that bus.
First, determine how many scans can occur in one CPU sweep. For example, if the
bus scan were 20ms and the CPU sweep were 90ms, the ratio between them would be
4.5 to 1. This should be rounded upward to 5.
This is the maximum number of Normal Priority Datagrams that might be received in a
single CPU sweep. Plan to have the same number of Dequeue Datagram commands
to that Bus Controller in the program to handle the incoming Datagrams.
For High Priority Datagrams, multiply the number found above by the total number of
devices on the bus that might send a High Priority Datagram to the Bus Controller in
one bus scan. This is the total number of incoming Datagrams from that bus that the
program might have to handle in a single CPU sweep. Plan on this number of
Dequeue Datagram commands to the Bus Controller.
Program logic should be used to assure that no datagrams are lost by being
accidentally written over. This might be done by copying each datagram to another
memory location, or by changing the data memory location specified in the Command
Block after each incoming datagram is received.
Status Byte: The status byte reports the Device Number of the device that sent the
datagram. It also indicates whether the message was broadcast or
directed by the other device.
bit 7 6 5 4 3 2 1 0
B/D x x n n n n n
Device Number
(5 bits: 0-31 decimal)
Unused
Broadcast (1)
Directed (0)
Data Length: The number (0 to 134) of data bytes after the subfunction code.
Function The function code of the received message: 0 to 111 decimal or 0 to
Code: 6F hex.
Subfunction The subfunction code of the received message: 0 to 255 decimal or 0
Code: to FF hex.
▪ Read Device and Write Device datagrams that are broadcast, but which should be
ignored by another Series 90-70 Bus Controller.
▪ Datagrams that must be guaranteed transmission during the next bus scan. This
should be done with restraint, for the reasons explained on the following pages.
▪ Datagrams that do not cause another device to send back a reply, such as Pulse
Test, or Write Configuration.
Datagrams that DO cause another device to send back a reply, such as Read
Diagnostics or Read Configuration, are usually programmed using their assigned
COMMREQ numbers or the Request Datagram Reply command (COMMREQ
#15). However, if Send Datagram is used to send datagrams that cause replies,
the Dequeue Datagram command must be used to transfer the replies to the CPU.
Before using Send Datagram, refer to the table on page 5-12 for more information
about COMMREQs and datagrams.
Datagram Priority
A Bus Controller can send one datagram per bus scan. That datagram may be
assigned either normal priority or high priority. Therefore, during one bus scan, there
may be one normal priority datagram followed by up to 31 high priority datagrams, or
up to 32 high priority datagrams sent by the devices on the bus.
In one bus scan (one complete rotation of the bus token among all devices on the bus),
there can be just one normal priority datagram sent by any device. If a normal priority
datagram or similar system message (such as a fault report) has already been sent by
any device (including itself), a device must wait until its next turn on the bus before it
can send a normal priority datagram.
Effect of Datagrams on the Genius I/O Bus: Normal Priority Datagrams allow fault
reports and Hand-held Monitor communications on a bus to continue undisturbed.
Only one Normal Priority Datagram is allowed each bus scan, so the scan time stays
relatively constant, and I/O update timing varies only by small increments.
If High Priority Datagrams are being transmitted constantly, the Hand-held Monitor will
not function properly; fault reports from blocks will be prevented from being transmitted
on the bus, and regular Communication Request commands (such as Write
Configuration commands) to that Bus Controller will fail with a transmission error. For
these reasons, use of High Priority Datagrams on a bus with I/O blocks should be
avoided if possible.
If High Priority Datagrams are transmitted infrequently, they will cause some delay in
the Hand-held Monitor communications and other normal system messages, but the
delay should not be noticeable.
High Priority Datagrams will typically put more pressure on the Bus Controller to
transfer multiple Datagrams per CPU sweep. However, this can also occur with
Normal Priority Datagrams if the bus scan time is much shorter than the CPU sweep
time.
Maximum CPU Sweep Time Increase for Datagrams: To estimate the impact of
Datagrams on CPU sweep time, add together the times required for all Datagrams that
might be sent between the Bus Controller and the CPU during one sweep if No Wait
mode is selected. Repeat this for each Bus Controller in the PLC that sends or
receives Datagrams.
+ 1.200ms = ______ms
It is also possible to disable only reports of Addition or Loss of Block conditions, while
still forwarding other faults from the devices on the bus. This can be useful in a system
where blocks are intentionally switched on and off the bus, or in other applications
where these messages are not wanted.
If the passing of some or all fault reports is disabled for non-redundant devices, the
corresponding point-specific fault contacts will operate. They are not affected by the
use of this COMMREQ. Some system-level and block-level fault contacts are affected
by the loss of the inhibited information. For redundant devices, the CPU won't set the
point faults for redundant devices if fault reporting is turned off. In addition, when fault
reporting is turned off, the associated fault locating references are not updated.
Caution: none of the outputs on a targeted device should be updated in any other way
during the PLC sweep.
Example
In this example, there are two blocks on the bus that should be updated using Do
Outputs. The first is a 16-circuit block located at Device Number 1. All 16 of its circuits
are used as outputs. The second device is a 32-circuit block located at Device Number
2. On this block, circuits 17 to 32 are used as outputs. (In this application, Device
Number 0 is used by the Hand-held Monitor).
Address +0: Command Length For this example, the length is 9 (the number of words from
(number of words from Address +6 to Address +14). This limits the number of
Address +6 to the end of registers used, and only serial bus addresses 0, 1 and 2 will
the data.) be affected.
Address +1: No Wait 0
Address +2: Status Block memory type 8 (%R)
Address +3: Status Block offset Beginning address for the COMMREQ status.
Address +4: Idle timeout value 0
Address +5: Max. communications time 0
Address +6: Command number 17
Address +7: Flags for Device Numbers This marks serial bus addresses 1 and 2 as the targets.
0-15
LSB
0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0
Address +9, Outputs for Device 32 bits: “don’t care” in this example, because the flag for
Address +10 Number 0 serial bus address 0 is set to 0.
Address +11 Outputs for Device 32 bits. In this example, Device Number 1 is a 16-circuit
Address +12 Number 1 block. All 16 circuits (shown below as 1s for clarity) are
outputs.
LSB
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MSB
To use the command, in [address+7] and [address+8] set the flag corresponding to the
serial bus address of the Bus Controller that will send the Global Data. Enter the data
into the COMMREQ addresses that correspond to those devices (for example, you
would enter output data into locations [address+71] and [address+72] to update a Bus
Controller at serial bus address #31).
LSB
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
MSB Device Numbers (SBAs)
Set to 1 the bit that corresponds to the serial bus address of
the Bus Controller that will be sending the Global Data.
Address +9 Global Data Each serial bus address is assigned 2 words in the command.
up to Enter the data into the 2 words that correspond to the device
Address +72 you are updating.
This chapter explains how the application program in a PACSystems or Series 90-70
CPU can read information about the status of the Genius bus:
Reading the Serial Bus Addresses of Active Devices
Format of the Bus Status Data that is Returned
RX7i CPU: Reading Serial Bus Addresses
Series 90-70 CPU: Reading Serial Bus Addresses
Reading the Status of the Datagram Queue
Format of the Datagram Queue Status Data that is Returned
RX7i CPU: Reading Datagram Queue Status
Series 90-70 CPU: Reading Datagram Queue Status
GFK-2017 6-1
6
byte 1 7 6 5 4 3 2 1 0 byte 2 7 6 5 4 3 2 1 0
SBA 0 SBA 8
SBA 1 SBA 9
SBA 2 SBA 10
SBA 3 SBA 11
SBA 4 SBA 12
SBA 5 SBA 13
SBA 6 SBA 14
SBA 7 SBA 15
LSB MSB
byte 3 7 6 5 4 3 2 1 0 byte 4 7 6 5 4 3 2 1 0
SBA 16 SBA 24
SBA 17 SBA 25
SBA 18 SBA 26
SBA 19 SBA 27
SBA 20 SBA 28
SBA 21 SBA 29
SBA22 SBA 30
SBA 23 SBA 31
Bits are set to 1 for devices that are on the network and properly configured with the
correct data length. Bits for devices that are configured as outputs-only are off if the
CPU is not controlling the device.
BUS RD
WORD
2
Rack R ST Read Status
Region RGN
Offset OFF
No special configuration is required to use this function. The CPU automatically defines
region 1 for the Bus Controller to be the Bus Controller's 32k dual port memory.
Program the Bus Read parameters as shown below.
BUS RD
BYTE
1
Rack R ST Read Status
Region RGN
Offset OFF
No special configuration is required to use this function. The CPU automatically defines
region 1 for the Bus Controller to be the Bus Controller's 32k dual port memory.
Program the Bus Read parameters as shown below.
These types of systems are possible because of the unique operation and
communications capabilities of Genius I/O devices on a bus. Each Genius I/O block
broadcasts its input messages to all other devices on the bus. Therefore, more than
one CPU can receive inputs from the same blocks.
The CPUs can communicate on the same bus, allowing formation of a common
database. In addition, any CPU can send datagram messages to any other device on
the bus.
GFK-2017 7-1
7
Data Monitoring
In addition to the PLC or computer running the application program, other CPUs on the
bus can monitor inputs, diagnostics, and Configuration Change messages sent by
Genius I/O devices.
CONTROLLER MONITOR
CPU CPU
BUS BUS
CONTROLLER CONTROLLER
I/O BLOCKS
Monitoring Inputs
Genius I/O devices broadcast their inputs once per bus scan. These inputs may be
accessed by any PLC or computer on the bus.
If the RX7i or Series 90-70 CPU will be used to monitor inputs from I/O devices not
being controlled by its application program, the devices will be configured in the same
manner as other I/O devices on the bus. The PLC will use the Reference Number
assigned to each I/O device to store its inputs. Even though the monitoring PLC would
not ordinarily be expected to send outputs to devices being monitored, outputs to those
devices should be disabled when the PLC’s I/O configuration is done. This will prevent
any unwanted outputs being sent to the I/O devices from the monitoring PLC.
If a computer is used to monitor I/O data on the bus, it is important to consider data
type, message length, and message format when programming the computer. For
example, a High-speed Counter block sends its word-type data first, followed by
discrete data. Other devices have different data formats.
Monitoring Diagnostics and Configuration Change Messages
In addition to receiving the broadcast input data, one PLC or computer on the bus may
also receive extra copies of any fault reports and configuration change messages that
may be sent by the bus devices. This PLC or computer, referred to as the Assigned
Monitor, may not send control outputs to an I/O device. If the monitor is capable of
sending outputs to a I/O device it is monitoring, those outputs must be disabled.
The monitoring device can communicate with other devices on the bus through Global
Data or datagram messages. For example, it would be possible for a monitoring
device to send a Read Diagnostics datagram to an I/O device that was not configured
to send it fault reports automatically.
This feature is compatible with both redundant and non-redundant Genius
configurations.
Distributed Control
Distributed control means that two or more Bus Controllers are sending control outputs
to different I/O devices on the same bus. Ordinarily, these Bus Controllers would be in
different PLCs, but with the Series 90-70 Bus Controller, they can be in the same PLC.
Diagnostics are only automatically sent from the block to the Bus Controller that is
controlling its outputs. The Assign Monitor datagram can be used to command blocks
on the bus to also direct fault reports to a second Bus Controller.
This is a form of split control, not a type of redundancy. Bus Controllers and devices
on the bus are set up for CPU Redundancy Mode = None, since each I/O device is
receiving outputs from only one Bus Controller. Remember that all I/O devices on the
bus broadcast inputs to all bus interface modules automatically.
For example, a Bus Controller is configured at Bus Address 31, and the I/O devices it
will control are configured at Bus Addresses 1 and 2. A Bus Controller in another PLC
is located at Bus Address 30. The I/O blocks it will control are located ate Bus
Addresses 3 and 4. A third Bus Controller is at Bus Address 7. Two I/O blocks on its
bus are located at Bus Addresses 5 and 6. All devices are connected by the same
bus.
1 2 3 4 5 6
When setting up an RX7i or Series 90-70 system for distributed control, there are two
different ways to assign references to I/O devices:
A. Each Bus Controller can be assigned just those I/O devices whose outputs it
controls. If this is done, devices that are not configured for a Bus Controller (but
which are actually present on the bus) will generate Extra Device faults in that PLC
at startup. Once these faults are cleared, they will not reappear unless power is
cycled to the Bus Controller or I/O device.
B. Each Bus Controller can be assigned all of the I/O devices actually present on the
bus. Outputs are disabled to I/O devices controlled by another Bus Controller.
This means that each I/O device must be assigned a Reference Number in each
CPU. References assigned to devices controlled by another CPU are unavailable
for further use.
Redundancy
Redundancy provides extra protection for critical processes through duplication of
system components. For an RX7i or Series 90-70 (rev 4.0 or later) PLC CPU and Bus
Controller (rev. 4.0 or later), the following can be configured:
▪ Dual bus, one PLC
▪ Dual bus, two PLCs
▪ Redundant controllers, one PLC
▪ Redundant controllers, two PLCs
▪ Dual bus and redundant controllers, two PLCs
These redundant systems are described on the following pages. If the Series 90-70
PLC is rev. 3, see page 7-17 instead.
Important Considerations
The suitability of a redundancy scheme depends on the requirements of the
application. Some important factors to be considered are described below.
1. CPU synchronization is not supported.
▪ Using a Genius bus, transferring data from the master CPU to the backup CPU
can take 10 to 20 CPU sweeps, depending on the quantity of data.
▪ The RX7i or Series 90-70 CPU has transitional bits, but does not have a table
that can be transferred from one CPU to another for synchronization. One-
shots, counters, and transitional contacts cannot be guaranteed to be the
same in both CPUs.
▪ The timebase is not transferrable, so timers (real time and running time)
cannot be guaranteed to be the same. Timers and counters in program blocks
that are not called every sweep may produce different results.
▪ For PID function blocks, elapsed time may be different in the two PLCs,
because it represents the total time since PLC powerup.
2. Hot Standby redundancy should only be used for systems that do not require
bumpless transfer of control from one CPU to the other.
Specific Series 90-70 PLC CPUs provide advanced redundancy features that are not
described here.
▪ Three CPU models support GMR (Genius Modular Redundancy):
IC697CPM790, CPU789, and CPU788. A GMR system normally consists of
one to three identical CPUs running identical application programs. Control
and diagnostic functions are provided by special GMR software. For
information about GMR, please see the GMR User's Manual, GFK-1277, which
is online at www.GEFanuc.com.
▪ Series 90-70 PLC CPU models IC697CGR772 and CGR935, used with a
Redundancy Communications Module, provide Enhanced Hot Standby CPU
Redundancy for one or more Genius I/O networks. For information about
Enhanced Hot Standby CPU Redundancy, please see the Series 90™-70
Enhanced Hot Standby CPU Redundancy User's Guide, GFK-1527, also
available at www.GEFanuc.com.
Note
If bumpless transfer is a requirement, bus redundancy with two PLCs
is not recommended since the second PLC is essentially off-line
before the switch.
BUS BUS
CONTROLLER CONTROLLER
BUS A
BUS B
BSM
BSM
UP TO 7
CONTROLLER
MORE BLOCKS
BLOCK
If, after switching due to loss of communications on the original bus, no outputs are
received on the new bus, the bus switching device does not switch back. It waits until
communications are restored on the newly-connected bus, or until power is cycled.
This prevents unnecessary switching when no communications are available.
BUS BUS
CONTROLLER CONTROLLER
A B
(DEVICE 31) (DEVICE 31)
BUS A
BUS B
1 2 3 4A 4B
BSM
Both of the Bus Controllers are configured at Bus Address 31 on their respective
busses. A Bus Switching Module interfaces three redundant I/O blocks to the dual bus.
The redundant blocks are configured at Bus Addresses 1, 2, and 3 on both busses.
There are also two non-redundant I/O blocks. Each of them is configured at Bus
Address 4 on its bus.
During normal operation, both bus A and bus B operate in the same way as a single
bus:
▪ Blocks 1, 2, and 3 interface to either bus A or bus B, as selected by the BSM.
▪ Block 4A communicates with the Bus Controller on bus A only.
▪ Block 4B communicates with the Bus Controller on bus B only.
A B
(DEVICE 31) (DEVICE 31)
BUS A
BUS B
1 2 3 4A 4B
BSM
If Bus Controller A stops communicating with the redundant blocks (due to program
action, a Bus Controller fault, a cable break, or loss of power), then:
▪ The BSM will switch the cluster of blocks 1, 2, and 3 to bus B.
▪ Block 4A, which is a non-redundant block, will no longer receive outputs from its
Bus Controller, and will no longer be able to send inputs or diagnostics to the PLC.
If there are outputs on block 4A, they will either hold their last state or default,
depending on the block’s configuration. Although communications have been
interrupted, the block is still receiving power, so any outputs that were ON or that
default to ON will continue to operate.
A B
(DEVICE 31) (DEVICE 31)
BUS A
BUS B
1 2 3 4A 4B
BSM
BUS A BUS B
BSM BSM
NOTE
30 BLOCKS TOTAL
In a large system, grouping non-redundant devices on the same bus or busses will
permit the greatest number of Bus Controllers to be used in the PLC. For example, a
PLC could have 30 Bus Controllers with all redundant devices, and 1 Bus Controller
with all non-redundant devices.
CPU CPU
1 2 3 4 5
The illustration shows an optional Bus Controller in each CPU, connected via an
additional Genius bus, for data sharing between the CPUs. In this example, the
additional Bus Controllers are for communications only; they do not control I/O. In that
case, it is not necessary to give them the same Bus Addresses.
Redundant Controllers
Redundant controllers provide backup controller protection for devices on a bus. The
redundant controllers can be in the same PLC (in the same rack or in different racks),
or in two PLCs.
Bus Controller redundancy with one PLC provides protection against failure of the Bus
Controller.
Bus Controller redundancy with two PLCs, represented below, provides protection
against failure in the Bus Controller or elsewhere in the primary PLC.
CPU CPU
BUS BUS
CONTROLLER CONTROLLER
1 2 3 4 5
Either PLC can monitor the outputs of the other using the Outputs with Feedback
feature of discrete Genius I/O blocks. Since I/O blocks can monitor the actual state of
the load and feed this state back to the PLC as input data, both PLCs can monitor the
actual state of all outputs.
outputs
In Hot Standby mode, blocks receive outputs from both Bus Controllers, but they are
normally controlled directly by the Bus Controller at Bus Address (Device Number) 31.
If no output data is available from Bus Address 31 for a period of three bus scans, the
outputs are immediately controlled by the Bus Controller at Bus Address 30. If output
data is not available from either 30 or 31, outputs go to their configured default or hold
their last state. The Bus Controller at Bus Address 31 always has priority, so that when
31 is on-line, it always has control of the outputs.
Analog blocks, when configured for CPU redundancy, must be operated in Hot
Standby redundancy mode.
outputs outputs
If both outputs are the same, the device sets the output to that state. If both outputs
are not the same, the device sets the output to its preselected Duplex Default State.
The following table shows how outputs operate in Duplex redundancy.
If either 30 or 31 stops sending outputs to a device, the outputs are directly controlled
by the remaining device.
Only discrete blocks can be configured for Duplex redundancy mode. If there are
analog blocks on the same bus, they can be configured in Hot Standby mode or no
CPU redundancy.
Note
In both Hot Standby and Duplex modes, both CPUs get the inputs
from the blocks automatically. In addition, the blocks automatically
send fault reports to both Bus Controllers.
CPU CPU
A B A B
(DEVICE 31) (DEVICE 31) (DEVICE 30) (DEVICE 30)
BUS A
BUS B
1 2 3 4A 4B
BSM BSM
In the example system represented above, both bus A and bus B operate in the same
way as a single bus, dual CPU system. Blocks 1, 2, and 3 interface to both PLCs via
Bus Controllers 31(A) and 30(A) whenever the active bus is bus A, or via Bus
Controllers 31(B) and 30(B) whenever the active bus is bus B. Block 4(A) interfaces to
both PLCs via Bus Controllers 31(A) and 30(A). Block 4(B) interfaces to both PLCs via
Bus Controllers 31(B) and 30(B).
Outputs
All four Bus Controllers are capable of sending outputs, although only outputs from the
Bus Controllers on the active bus are actually received. It may be necessary to disable
the outputs sent by the backup Bus Controller until the application program has logged
in all the devices, then enable outputs under program control. If this is done, the
additional time without outputs must not cause the total time without outputs to exceed
the 2.5 or 10 second timeout selected for the block.
Inputs and Diagnostics
Both Bus Controllers on the selected bus automatically receive all inputs and fault
reports from any device on the bus that has been configured as being in “CPU
Redundancy” mode.
31 30
Normal Operation
A B A B
outputs
A
31 30
Control Passes to Backup PLC on Bus A
A B A B
outputs
A
A
31
B A
30
B
Control Passes to Bus B
If the device that controls bus switching stops receiving
outputs from bus A for a period of three bus scans, it
outputs
switches to bus B. Normal operation then resumes on
B
bus B. Bus Controller 31B controls (in the primary PLC)
controls all devices set up for Hot Standby CPU
A
redundancy.
A
31
B A
30
B
Control Passes to Backup PLC on Bus B
If the device fails to receive valid output data from Bus
Controller 31 for three bus scans,it will permit Bus
outputs Controller 30B to control its outputs.
B
Because the PLCs are operating independently, each time the control switches from
one PLC to the other there may be a “bump” in the process. This may be of no
consequence in some applications, and of significant consequence in others.
31 30
Normal Operation
A B A B
outputs outputs
A
31 30
Devices Controlled by Bus Controller 30 on Bus A
A B A B
outputs
A
A
31
B A
30
B
Control Passes to Bus B
If the device that controls bus switching stops receiving
outputs from bus A for a period of three bus scans, it
outputs outputs
switches to bus B. Normal operation then resumes on
B bus B. Bus Controllers 31B and 30B jointly control any
devices set up for Duplex CPU redundancy.
A
A
31
B A
30
B
Control Passes to Backup PLC on Bus B
If a duplex device fails to receive output data from Bus
Controller 31B for three bus scans, it will permit Bus
outputs Controller 30B to control its outputs.
B
Operation Remains with Primary PLC, Dual Bus and Dual Controllers
The following application is for devices configured in Hot Standby CPU Redundancy
mode. It is not suitable for devices that operate in Duplex CPU redundancy mode. The
order of control is:
primary PLC, bus A
► primary PLC, bus B
► backup PLC, bus B
► backup PLC, bus A
This provides “bumpless” transfer of control within the primary PLC, and within the
backup PLC, although there will still be a bump in the process when control is
transferred from PLC to PLC.
Outputs
31 disabled 30
Normal Operation
A B A B
BUS A
BUS B
BSM
BSM UP TO 7
CONTROLLER MORE BLOCKS
BLOCK
A system like the one depicted above provides protection against single point failure in
a CPU or Bus Controller or on a bus trunk cable. It does not protect against failure of a
bus switching device, a BSM controller block, or a bus stub connecting blocks in a
cluster.
The devices in each cluster communicate only with the bus that is currently selected.
The other CPU does not receive inputs, Report Fault datagrams, or Configuration
Change datagrams from the blocks. Therefore, if the switching device switches busses,
the newly-selected CPUs will not have the most current inputs or diagnostics from the
devices in the cluster.
In a version 3 system, bus devices MUST be configured with one set of references for
operations on bus A, and a separate set of references for operations on bus B. The
application program must decide which bus is operational, and use the appropriate set
of references for the devices’ I/O data.
GFK-2017 A-1
A-2 Series 90-70 Genius® Bus Controller – July 2003 GFK-2017
Index
GFK-2017 Index-1
Index
Index-2 Series 90-70 Genius® Bus Controller User's Manual–July 2003 GFK-2017
Index
U
R User Scaling Error fault, 4-7
Read Configuration COMREQ, 5-1, 5-5, 5-14,
6-1
Read Configuration Datagram, 5-36 W
Read Data Datagram, 5-36 WD Timeout fault, 4-7
Read Device COMREQ, 5-1, 5-5, 5-23, 6-1 Wiring Error fault, 4-6
Read Device Datagram, 5-36 Write Configuration COMREQ, 5-1, 5-5, 5-15,
Read Diagnostics COMREQ, 5-1, 5-5, 5-16, 6- 6-1
1 Write Device COMREQ, 5-1, 5-5, 5-28, 6-1
Read Diagnostics Datagram, 5-36
Redundancy, 3-31, 7-4
Redundancy Mode
Index-4 Series 90-70 Genius® Bus Controller User's Manual–July 2003 GFK-2017