General tab – Rockwell Automation 1732E-IR4IM12R ArmorBlock Dual-Port EtherNet/IP 4-Point Thermocouple and RTD User Manual
Page 30

22
Rockwell Automation Publication 1732E-UM004A-EN-E - July 2012
Chapter 3 Configure Your Thermocouple and RTD Input Modules with RSLogix 5000 Software
General Tab
The General tab allows you to edit general properties such as Name, IP Address,
and Description for your module.
You also can edit Module Definition properties such as revision, electronic
keying, and data. To do so, click Change.
Module Definition Fields
Field Name
Description
Series
Specifies the module series.
Revision
Specifies the module’s major and minor revision.
Electronic Keying
The electronic keying feature automatically compares the expected
module, as shown in the RSLogix 5000 I/O Configuration tree, to the
physical module before I/O communication begins. You can use electronic
keying to help prevent communication to a module that does not match
the type and revision expected.
For each module in the I/O Configuration tree, the user-selected keying
option determines if, and how, an electronic keying check is performed.
Typically, three keying options are available:
• Exact Match
• Compatible Module (default value)
• Disable Keying
Exact Match is an electronic keying protection mode that requires the
physical module and the module configured in the software to match
according to vendor, catalog number, major revision and minor revision.
Compatible Module indicates that the module determines whether to
accept or reject communication. Compatible Keying is the default setting.
It allows the physical module to accept the key of the module configured
in the software, provided that the configured module is one the physical
module is capable of emulating. The exact level of emulation required is
product and revision specific.
Disable Keying indicates the keying attributes are not considered when
attempting to communicate with a module. Other attributes, such as data
size and format, are considered and must be acceptable before I/O
communication is established. With Disabled Keying, I/O communication
may occur with a module other than the type specified in the I/O
configuration tree with unpredictable results. We generally do not
recommend using Disabled Keying.