Rockwell Automation 1732E-OB8M8SR EtherNet/IP Dual Port 8-Point SOE Input and Scheduled Output Modules UM - Manual (Page 59)

Rockwell Automation Publication 1732E-UM003B-EN-E - March 2014 49
Common Features of the 1732E-IB8M8SOER and 1732E-OB8M8SR Modules Chapter 7
The following table describes the keying options available with your module.
Module Inhibiting With module inhibiting, you can indefinitely suspend a connection between an
owner-controller and a module. This process can occur in the following way:
• You write configuration for a module but inhibit the module to prevent it
from communicating with the owner-controller. In this case, the owner-
controller does not establish a connection and configuration is not sent to
the module until the connection is uninhibited.
The following examples are instances where you may need to use module
inhibiting:
• You want to FLASH upgrade your module. We recommend you:
Keying option Definition
Exact Match All of the parameters listed above must match or the inserted module rejects a connection to the
controller.
Compatible Module The Compatible Module mode allows the module to determine whether it can emulate the module
defined in the configuration sent from the controller. Some modules can emulate older revisions. The
module will accept the configuration if the configuration’s major.minor revision is less than or equal to
the physical module’s revision.
For example, if the configuration contains a major.minor revision of 1.7, the module must have a
firmware revision of 1.7 or higher for a connection to be made. When a module is inserted with a
major.minor revision that is less than the revision configured (that is, the module has a revision of 1.6
and the slot is configured for a module with revision 1.8), no connection is made between the controller
and the I/O module.
TIP We recommend using Compatible Module whenever possible. Remember, though,
with major revision changes, the module only works to the level of the
configuration.
At the time of this printing, the module uses a major.minor revision of 1.6
(1) .
However, if a new major revision for the module is released, consider this example.
If a module is configured for major.minor revision of 1.7 and you insert a module
with a major.minor revision of 2.3, the module works at the 1.7 level, with respect
to module functions that are related to RSLogix 5000 software such as interface
changes. Anomaly updates that are affected by the module’s firmware, though,
would work at the 2.3 revision level.
If possible, we recommend that you make sure configuration is updated to match
the revision levels of all I/O modules, including your module. Failure to do so may
not prevent the application from working but may defeat the purpose of upgrading
your modules revision levels.
Disable Keying The inserted module attempts to accept a connection to the controller regardless of its type.
Be extremely cautious when using the disable keying option; if used incorrectly, this
option can lead to personal injury or death, property damage or economic loss.
If keying is disabled, a controller makes a connection with most modules of the same type as that used in
the configuration.
A controller will NOT establish a connection if any of the following conditions exist, even if keying is
disabled:
• The module is configured for one module type (for example, input module) and a module of another
type (for example, output module) is used.
• The module cannot accept some portion of the configuration. For example, if a non-diagnostic input
module is configured for a diagnostic input module, the controller cannot make a connection because
the module will not accept/process the diagnostic configuration.
(1) Minor revisions are incremented by single counts such that minor level 10 (major.minor revision level = 1.10) follows minor revision level 9 (1.9).