XM-220 Dual Speed Module Users Guide PDF
XM-220 Dual Speed Module Users Guide PDF
FIRMWARE REVISION 5
USER MANUAL
1440-SPD02-01RB
Important User Information Solid state equipment has operational characteristics differing from those of
electromechanical equipment. Safety Guidelines for the Application, Installation and
Maintenance of Solid State Controls (Publication SGI-1.1 available from your local
Rockwell Automation sales office or online at
http://www.rockwellautomation.com/literature) describes some important
differences between solid state equipment and hard-wired electromechanical devices.
Because of this difference, and also because of the wide variety of uses for solid state
equipment, all persons responsible for applying this equipment must satisfy
themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or
consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes.
Because of the many variables and requirements associated with any particular
installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of
information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written
permission of Rockwell Automation, Inc. is prohibited.
Throughout this manual we use notes to make you aware of safety considerations.
Listen. Think. Solve, Allen-Bradley and XM are trademarks of Rockwell Automation, Inc.
DeviceNet is a trademark of the Open DeviceNet Vendor Association (ODVA).
Microsoft and Windows are registered trademarks of the Microsoft Corporation.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
European Communities (EC) If this product has the CE mark it is approved for installation within the European
Union and EEA regions. It has been designed and tested to meet the following
Directive Compliance directives.
EMC Directive
This product is tested to meet Council Directive 73/23/EEC Low Voltage by applying
the safety requirements of EN 61131-2 Programmable Controllers, Part 2 —
Equipment Requirements and Tests.
ATEX Directive
Chapter 1
Introduction Introducing the XM-220 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
XM-220 Module Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Using this Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Organization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2
Installing the XM-220 Dual Speed XM Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Module Wiring Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Grounding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Mounting the Terminal Base Unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Interconnecting Terminal Base Units . . . . . . . . . . . . . . . . . . . . . . . 14
Panel/Wall Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Connecting Wiring for Your Module . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Terminal Block Assignments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Connecting the Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Connecting the Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Connecting the Buffered Outputs . . . . . . . . . . . . . . . . . . . . . . . . . 22
Connecting the Switched Buffered Output . . . . . . . . . . . . . . . . . . 23
Connecting the 4-20mA Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Connecting the Remote Relay Reset Signal . . . . . . . . . . . . . . . . . . 25
Connecting the Startup Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Connecting the Transducer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Sensor Placement for Reverse Rotation . . . . . . . . . . . . . . . . . . . . . 33
PC Serial Port Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
DeviceNet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Mounting the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Module Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Basic Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Powering Up the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Manually Resetting Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 3
Configuration Parameters Measurement Mode Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Channel Tachometer Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Alarm Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Relay Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
4-20mA Output Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
I/O Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Monitor Data Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Alarm and Relay Status Parameters . . . . . . . . . . . . . . . . . . . . . . . . 59
Device Mode Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Appendix A
Specifications Technical Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Appendix B
DeviceNet Information Electronic Data Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Changing Operation Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Transition to Program Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Transition to Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
XM Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Invalid Configuration Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
XM-220 I/O Message Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Poll Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
COS Message Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
ADR for XM Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Appendix C
DeviceNet Objects Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
DeviceNet Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Assembly Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Connection Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Discrete Input Point Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Parameter Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Acknowledge Handler Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Alarm Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Device Mode Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Relay Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Speed Measurement Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Tachometer Channel Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Transducer Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
4-20mA Output Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Introduction
This chapter provides an overview of the XM-220 Dual Speed module. It also
discusses the components of the module.
Introducing the XM-220 The XM-220 Dual Speed module is a member of the Allen-Bradley™ XM®
Module Series, a family of DIN rail mounted condition monitoring and protection
modules that operate both in stand-alone applications or integrate with
Programmable Logic Controllers (PLCs) and control system networks.
The XM-220 is a two channel module that accepts input from any two
tachometers of any standard type including eddy current probes, magnetic
pickups, optical tachometers, and TTL output devices. It measures speed,
rotor acceleration, and peak speed and is capable of detecting zero speed,
locked rotor, and reverse rotation conditions. It is also used as a component of
the XM Electronic Overspeed Detection system.
• Dual Channel Mode - This is the default mode. The two sensors are
used independently to perform two separate sets of speed, acceleration,
and peak speed measurements.
• Reverse Rotation Mode - The two sensors are used to monitor speed
and direction of a single shaft. The two sensors must be mounted out of
phase from each other so that the rotational direction can be determined
by monitoring which sensor the shaft keyway passes first. Refer
to Sensor Placement for Reverse Rotation on page 33.
The module includes a single on-board relay (expandable to five), two 4-20mA
outputs, and a buffered output for each input. A third buffered output is
available when the module is functioning in the single redundant channel
mode. This buffered output signal corresponds to the active input signal so
that the machine speed can be accurately tracked regardless of which of the
redundant sensors is active.
The module can be configured remotely via the DeviceNet network, or locally
using a serial connection to a PC or laptop. Refer to Chapter 3 for a list of the
configuration parameters.
XM-220 Module The XM-220 module consists of a terminal base and an instrument module.
The XM-220 Dual Speed module and the XM-941 Position/Speed Terminal
Components Base are shown below.
Using this Manual This manual introduces you to the XM-220 Dual Speed module. It is intended
for anyone who installs, configures, or uses the XM-220 Dual Speed Module.
Organization
For definitions of terms used in this Guide, see the Glossary at the end of the
Guide.
Document Conventions
There are several document conventions used in this manual, including the
following:
This chapter discusses how to install and wire the XM-220 Dual Speed
module. It also describes the module indicators and the basic operation of the
module.
XM Installation This section describes wire, power and grounding requirements, and
instructions for an XM system.
Requirements
Wiring Requirements
Use solid or stranded wire. All wiring should meet the following specifications:
Power Requirements
Before installing your module, calculate the power requirements of all modules
in each chassis. The total current draw through the side connector cannot
exceed 3A. Refer to the specifications for the specific modules for power
requirements.
Power
Supply
Grounding Requirements
The XM modules make a chassis ground connection through the DIN rail.
The DIN rail must be connected to a ground bus or grounding electrode
conductor using 8 AWG or 1 inch copper braid. See Figure 2.2.
1 DYNAMIC MEASUREMENT
1440-VST02-01RA
EXPANSION RELAY
1440-REX00-04RD
DYNAMIC MEASUREMENT
1440-VST02-01RA
EXPANSION RELAY
1440-REX00-04RD
Power
Supply
1 DYNAMIC MEASUREMENT
1440-VST02-01RA
EXPANSION RELAY
1440-REX00-04RD
DYNAMIC MEASUREMENT
1440-VST02-01RA
EXPANSION RELAY
1440-REX00-04RD
Power
Supply
1 Use 14 AWG wire. If it is desired to isolate the power supply because of possible ground loops, do not connect
24V Common to earth as illustrated in Figure 2.2. When the 24V supply is isolated from earth, it is
recommended to use an isolator on the RS-232 lines. Refer to PC Serial Port Connection on page 34.
The grounding wire can be connected to the DIN rail using a DIN Rail
Grounding Block (Figure 2.3).
1
Power
Supply
Power
Supply
1 Use 14 AWG wire. If it is desired to isolate the power supply because of possible ground loops, do not connect
24V Common to earth as illustrated in Figure 2.2. When the 24V supply is isolated from earth, it is
recommended to use an isolator on the RS-232 lines. Refer to PC Serial Port Connection on page 34.
For applications where redundant power supplies are used, only one power
supply needs to be grounded. The XM module ties the two 24V Common
lines together.
Transducer Grounding
Make certain the transducers are electrically isolated from earth ground. Cable
shields must be grounded at one end of the cable, and the other end left
floating or not connected. It is recommended that where possible, the cable
shield be grounded at the XM terminal base (Chassis terminal) and not at the
transducer.
DeviceNet Grounding
DNet
Power
Supply
V- V+
DNet Power V+
DNet Power V-
The Switch Input circuits are electrically isolated from other circuits. It is
recommended that the Switch RTN signal be grounded at a single point.
Connect the Switch RTN signal to the XM terminal base (Chassis terminal) or
directly to the DIN rail, or ground the signal at the switch or other equipment
that is wired to the switch.
Mounting the Terminal The XM family includes several different terminal base units to serve all of the
measurement modules. The XM-941 terminal base, Cat. No. 1440-TB-B, is the
Base Unit only terminal base unit used with the XM-220.
The terminal base can be DIN rail or wall/panel mounted. Refer to the
specific method of mounting below.
Use the steps below to mount the XM-941 terminal base unit on a DIN rail
(A-B pt no. 199-DR1 or 199-DR4).
Position terminal base at a slight angle and hook over the top of the DIN rail.
2. Slide the terminal base unit over leaving room for the side
connector (B).
3. Rotate the terminal base onto the DIN rail with the top of the rail
hooked under the lip on the rear of the terminal base.
4. Press down on the terminal base unit to lock the terminal base on the
DIN rail. If the terminal base does not lock into place, use a screwdriver
or similar device to open the locking tab, press down on the terminal
base until flush with the DIN rail and release the locking tab to lock the
base in place.
Follow the steps below to install another terminal base unit on the DIN rail.
IMPORTANT Make certain you install the terminal base units in order of
left to right.
2. Make certain the side connector (B) is fully retracted into the base unit.
3. Slide the terminal base unit over tight against the neighboring terminal
base. Make sure the hook on the terminal base slides under the edge of
the terminal base unit.
4. Press down on the terminal base unit to lock the terminal base on the
DIN rail. If the terminal base does not lock into place, use a screwdriver
or similar device to open the locking tab, press down on the terminal
base until flush with the DIN rail and release the locking tab to lock the
base in place.
5. Gently push the side connector into the side of the neighboring terminal
base unit to complete the backplane connection.
Panel/Wall Mounting
Use the following steps to install the terminal base on a wall or panel.
1. Lay out the required points on the wall/panel as shown in the drilling
dimension drawing below.
Side Connector
4. To install another terminal base unit, retract the side connector into the
base unit. Make sure it is fully retracted.
5. Position the terminal base unit up tight against the neighboring terminal
base. Make sure the hook on the terminal base slides under the edge of
the terminal base unit.
6. Gently push the side connector into the side of the neighboring terminal
base to complete the backplane connection.
7. Secure the terminal base to the wall with two #6 self-tapping screws.
Connecting Wiring for Your Wiring to the module is made through the terminal base unit on which the
module mounts. The XM-220 is compatible only with the XM-941 terminal
Module base unit, Cat. No. 1440-TB-B.
The terminal block assignments and descriptions for the XM-220 module are
shown below.
WARNING
EXPLOSION HAZARD
Do not disconnect equipment unless power has been
removed or the area is known to be nonhazardous.
Do not disconnect connections to this equipment unless
power has been removed or the area is known to be
nonhazardous. Secure any external connections that mate
to this equipment by using screws, sliding latches, threaded
connectors, or other means provided with this product.
The power supply to the XM-220 is nominally 24V dc. The XM-220 provides
two 24V dc power supply connections. The connections are electrically
isolated from each other so power interruptions to one connection does not
affect the other connection. This allows you to have a redundant power supply
for systems used in critical applications.
Wire the DC-input power supply to the terminal base unit as shown in
Figure 2.9.
24V dc
Power +
Supply
-
The XM-220 has both Normally Open (NO) and Normally Closed (NC) relay
contacts. Normally Open relay contacts close when the control output is
energized. Normally Closed relay contacts open when the control output is
energized.
The alarms associated with the relay and whether the relay is normally
de-energized (non-failsafe) or normally energized (failsafe) depends on the
configuration of the module. Refer to Relay Parameters on page 51 for details.
Table 2.1 shows the on-board relay connections for the module.
IMPORTANT All XM relays are double pole. This means that each relay
has two contacts in which each contact operates
independently but identically. The following information
and illustrations show wiring solutions for both contacts;
although, in many applications it may be necessary to wire
only one contact.
Configured for
Failsafe Operation Relay 1 Terminals
Nonalarm Alarm Wire Contacts Contact 1 Contact 2
Closed Opened COM 47 50
NO 48 49
Opened Closed COM 47 50
NC 46 51
Configured for
Non-failsafe Operation Relay 1 Terminals
Nonalarm Alarm Wire Contacts Contact 1 Contact 2
Closed Opened COM 47 50
NC 46 51
Opened Closed COM 47 50
NO 48 49
Figures 2.10 and 2.11 illustrate the behavior of the NC and NO terminals
when the relay is wired for failsafe, alarm or nonalarm condition or
non-failsafe, alarm or nonalarm condition.
Figures 2.12 and 2.13 show how to wire both ends of a single external
indicator to the XM terminal base for failsafe, nonalarm or alarm condition or
non-failsafe, nonalarm or alarm condition.
The XM-220 provides buffered outputs of all transducer input signals. The
buffered output connections may be used to connect the module to portable
data collectors or other online systems.
Figure 2.14 shows the buffered output connections for the module.
The module includes an isolated 4-20mA per channel output into a maximum
load of 300 ohms. The measurements that the 4-20mA output tracks and the
signal levels that correspond to the 4mA and 20mA are configurable. Refer
to 4-20mA Output Parameters on page 56.
Wire the 4-20mA outputs to the terminal base unit as shown in Figure 2.16.
If you set the module relay to latching and the relay activates, the relay stays
activated even when the condition that caused the alarm has ended. The
remote relay reset signal enables you to reset your module relay remotely after
you have corrected the alarm condition. This includes latched relays in the
Expansion Relay module when it is attached to the XM-220.
TIP If you set a module relay to latching, make sure that any
linked relays, such as relays in an XM-440 Master Relay
Module, are not configured as latching. When both relays
are set to latching, the relay in each module will have to be
independently reset when necessary.
TIP You can discretely reset a relay using the serial or remote
configuration tool.
Wire the Remote Relay Reset Signal to the terminal base unit as shown in
Figure 2.17.
Figure 2.18 Typical Multiple XM Modules Remote Relay Reset Signal Connection
You can configure the module to detect a locked rotor condition or inhibit the
tachometer fault alarm status during the start-up period. Wire the Startup
switch to the terminal base unit as shown in Figure 2.19.
The XM-220 can accept input signals from any Allen-Bradley non-contact
eddy current probe, magnetic pickups, or TTL output devices.
The figures below show the wiring of a non-contact eddy current probe to the
terminal base unit.
ATTENTION You may ground the cable shield at either end of the cable.
Do not ground the shield at both ends. Recommended
practice is to ground the cable shield at the terminal base
and not at the transducer. Any convenient Chassis terminal
may be used (see Terminal Block Assignments on page 16.
-24
SIG
COM
Shield
Floating
Signal Common
16
Channel 1 Input Signal 0
Shield 37
-24V DC 21 Jumpering terminal
5 5 to terminal 21
configures CH 1 buffer
for -24V to 9V
-24
SIG
COM
Shield
Floating
Signal Common
17
Channel 2 Input Signal 1
Shield 38
-24V DC 21 Jumpering terminal
22 21 to terminal 22
configures CH 2 buffer
for -24V to 9V
The figures below show the wiring of a passive magnetic pickup sensor to the
terminal base unit.
ATTENTION You may ground the cable shield at either end of the cable.
Do not ground the shield at both ends. Recommended
practice is to ground the cable shield at the terminal base
and not at the transducer. Any convenient Chassis terminal
may be used (see Terminal Block Assignments on page 16).
IMPORTANT The module does not power the sensor. It measures only
the input voltage.
Signal Common
16
Channel 1 Input Signal 0
Shield 37
T Y P IC A L W IR IN G F O R M A G N E T IC P IC K U P S E N S O R
TO XM -220 D U AL SPEED M O DU LE C H AN N EL 1
Signal Common
17
Channel 2 Input Signal 1
Shield 38
The figures below show the wiring of a TTL output device to the terminal
base unit.
ATTENTION You may ground the cable shield at either end of the cable.
Do not ground the shield at both ends. Recommended
practice is to ground the cable shield at the terminal base
and not at the transducer. Any convenient Chassis terminal
may be used (see Terminal Block Assignments on page 16).
Signal Common
16
Channel 1 Input Signal 0
Shield 38
+24V DC 6
Signal Common
17
Channel 2 Input Signal 1
Shield 38
+24V DC 6
The XM-220 module uses two input signals for reverse rotation detection.
Connect the first sensor to Channel 1. Connect the second sensor to Channel
2. Refer to Connecting a Non-Contact Sensor on page 28 for wiring details.
CHANNEL 1 SENSOR
DIRECTION
OF ROTATION
CHANNEL 2 SENSOR
• The sensors are more than 10 degrees apart and less than 170 degrees
apart in the direction of forward rotation; 90 degrees is optimum. See
Figure 2.27.
YES CH 2 SENSOR
NO
CH 2 SENSOR
The XM-220 includes a serial port connection that allows you to connect a PC
to it and configure the module’s parameters. There are two methods of
connecting an external device to the module’s serial port.
• Terminal Base Unit - There are three terminals on the terminal base
unit you can use for the serial port connection. They are TxD, RxD, and
RTN (terminals 7, 8, and 9, respectively). If these three terminals are
wired to a DB-9 female connector, then a standard RS-232 serial cable
with 9-pin (DB-9) connectors can be used to connect the module to a
PC (no null modem is required).
1440-SPD02-01RB
DUAL SPEED
mini-connector
WARNING
If you connect or disconnect the serial cable with power
applied to the module or the serial device on the other end
of the cable, an electrical arc can occur. This could cause an
explosion in hazardous location installations. Be sure that
power is removed or the area is nonhazardous before
proceeding.
DeviceNet Connection
Connect To Terminal
Red Wire DNet V+ 26
White Wire CAN High 23
Bare Wire Shield (Chassis) 10
Blue Wire CAN Low 24
Black Wire DNet V- 27
ATTENTION
You must ground the DeviceNet shield at only one
location. Connecting the DeviceNet shield to terminal 10
will ground the DeviceNet shield at the XM module. If you
intend to terminate the shield elsewhere, do not connect
the shield to terminal 10.
The devices are shipped from the factory with the network node address
(MAC ID) set to 63. The network node address is software settable. You can
use the XM Serial Configuration Utility or RSNetWorx™ for DeviceNet™
(Version 3.0 or later) to set the network node address. Refer to the appropriate
documentation for details.
IMPORTANT The baud rate for the XM-220 is set by way of "baud
detection" (Autobaud) at power-up.
Mounting the Module The XM-220 mounts on the XM-941 terminal base unit, Cat. No. 1440-TB-B.
We recommend that you mount the module after you have connected the
wiring on the terminal base unit.
WARNING
When you insert or remove the module while power is on,
an electrical arc can occur. This could cause an explosion in
hazardous location installations. Be sure that power is
removed or the area is nonhazardous before proceeding.
IMPORTANT Install the overlay slide label to protect serial connector and
electronics when the serial port is not in use.
1. Make certain the keyswitch (A) on the terminal base unit (C) is at
position 4 as required for the module.
2. Make certain the side connector (B) is pushed all the way to the left. You
cannot install the module unless the connector is fully extended.
3. Make sure that the pins on the bottom of the module are straight so they
will align properly with the connector in the terminal base unit.
4. Position the module (D) with its alignment bar (E) aligned with the
groove (F) on the terminal base.
5. Press firmly and evenly to seat the module in the terminal base unit. The
module is seated when the latching mechanism (G) is locked into the
module.
6. Repeat the above steps to install the next module in its terminal base.
Module Indicators The XM-220 module has seven LED indicators, which include a module status
(MS) indicator, a network status (NS) indicator, a status indicator for each
channel (CH1 and CH2), an activation indicator for startup, a status indicator
for the Relay, and an indicator (AUX) reserved for future use. The LED
indicators are on top of the module.
1440-SPD02-01RB
DUAL SPEED
Module Indicators
The following tables describe the states of the LED status indicators.
1 Program Mode - Typically this occurs when the module configuration settings are being updated with the XM
Serial Configuration Utility. In Program Mode, the module does not perform its normal functions. The signal
processing/measurement process is stopped, and the status of the alarms is set to the disarm state to prevent
a false alert or danger status.
2 Run Mode - In Run Mode, the module collects measurement data and monitors each vibration measurement
device.
1 Normal condition when the module is not a slave to an XM-440, PLC, or other master device.
Relay Indicator
The device test occurs after the LED test. The Module Status (MS) indicator is
used to indicate the status of the device self-test.
Refer to Module Indicators on page 38 for more information about the LED
indicators.
The XM-220 has an external reset switch located on top of the module, as
shown in Figure 2.30.
1440-SPD02-01RB
DUAL SPEED
The switch can be used to reset all latched relays in the module. This includes
the relays in the Expansion Relay Module when it is attached to the XM-220.
IMPORTANT The Reset switch resets the relays only if the input is no
longer in alarm or the condition that caused the alarm is no
longer present.
Configuration Parameters
Measurement Mode The Measurement Mode parameter controls how the two sensors are used to
calculate the speed, acceleration, and peak measurements. The XM-220
Parameter module operates in three different modes:
• Dual Channel - This is the default mode. The two sensors are used
independently to perform two separate sets of speed, acceleration, and
peak speed measurements.
• Reverse Rotation - The two sensors are used to monitor both speed
and direction. The two sensors must be mounted out of phase from
each other so that the rotational direction can be determined by
monitoring which sensor the shaft keyway passes first. Refer to Sensor
Placement for Reverse Rotation on page 33.
Channel Tachometer The Tachometer parameters define the characteristics of the tachometer and
determine the signal processing that will be performed on the tachometer
Parameters signal. There are two instances of the tachometer parameters, one for each
channel.
TIP The Channel LED will flash red when a transducer fault
condition exists on the channel even if you are not using
the channel. You can keep the Channel LED from flashing
red on unused channels by setting the unused channel’s
Fault High and Fault Low to greater than zero and less
than zero, respectively. For example, set Fault High to +18
volts and set Fault Low to -18 volts.
IMPORTANT If you are not using the tachometer channel, set the Pulses
per Revolution to zero. This will disable the tachometer
measurement, and prevent the module from indicating a
tachometer fault.
Tachometer Parameters
Tachometer Parameters
Tachometer Parameters
Tachometer Parameters
Fault Time-Out The number of seconds the module should wait after Enter a value from 1 to 64 seconds.
the last valid tach pulse before it indicates a
tachometer fault.
Alarm Parameters The Alarm parameters control the operation of the alarms (alert and danger
level) and provide alarm status. The XM-220 provides a total of eight alarms.
Each alarm is permanently associated with a corresponding measurement (for
example, Channel 1 Speed alarm, Channel 2 Acceleration alarm, and so on).
Use the parameters to configure which measurement the alarm is associated
with, as well as the behavior of the alarm.
Alarm Parameters
Alarm Parameters
Condition Controls when the alarm should trigger. Options: Greater Than
Less Than
• Greater than - Triggers the alarm when the Inside Range
measurement value is greater than or equal to the Outside Range
Alert and Danger Threshold values.
The Danger Threshold value must be greater than Note: This parameter is not applicable
or equal to the Alert Threshold value for the trigger for Locked Rotor alarms.
to occur.
• Less than - Triggers the alarm when the
measurement value is less than or equal to the
Alert and Danger Threshold values.
The Danger Threshold value must be less than or
equal to the Alert Threshold value for the trigger to
occur.
• Inside range - Triggers the alarm when the
measurement value is equal to or inside the range
of the Alert and Danger Threshold values.
The Danger Threshold (High) value must be less
than or equal to the Alert Threshold (High) value
AND the Danger Threshold (Low) value must be
greater than or equal to the Alert Threshold (Low)
value for the trigger to occur.
• Outside range - Triggers the alarm when the
measurement value is equal to or outside the
range of the Alert and Danger Threshold values.
The Danger Threshold (High) value must be greater
than or equal to the Alert Threshold (High) value,
AND the Danger Threshold (Low) value must be
less than or equal to the Alert Threshold (Low)
value for the trigger to occur.
Alarm Parameters
Alarm Parameters
Relay Parameters The Relay parameters control the operation of the on-board relay, as well as
the relays on the Expansion Relay (XM-441) module. Use these parameters to
configure which alarm(s) the relay is associated with, as well as the behavior of
the relay.
Relay Parameters
Activation Delay Enter the length of time for which the Activation Enter a value from 0 to 25.5 seconds,
Logic must be true before the relay is activated. This adjustable in increments of 0.1
reduces nuisance alarms caused by external noise seconds.
and/or transient vibration events.
Default is 1 second
Relay Parameters
Relay Parameters
Relay Parameters
4-20mA Output Parameters The 4-20mA output parameters define the characteristics of the two 4-20mA
output signals. The parameters are the same for each output.
4-20mA Parameters
Measurement Sets the type of measurement and the channel that Options: Channel 1 Speed
the 4-20mA output signal will track. Channel 2 Speed
Channel 1 Acceleration
Channel 2 Acceleration
Min Range The measured value associated with the 4mA. RPM for Speed
RPM/min for Acceleration
Max Range The measured value associated with the 20mA.
IMPORTANT Measured values between Min Range and Max Range are
scaled into the range from 4.0 to 20.0 to produce the
output value. The Min Range value does not have to be
less than the Max Range value. If the Min Range value is
greater than the Max Range value, then the output signal
is effectively inverted from the input signal.
IMPORTANT The 4-20mA outputs are either on or off. When they are
on, the 4-20mA outputs overshoot the 4 and 20mA limits
by 10% when the measurement exceeds the minimum and
maximum range. This means the minimum current
produced is 3.6mA and the maximum current produced is
22mA.
When the 4-20mA outputs are off, they produce a current
approximately 2.9mA. The 4-20mA outputs are off under
the following conditions:
• The 4-20mA outputs are set to "Disable" (see Enable
above).
• The module is in Program mode.
• A transducer fault or tachometer fault occurs that affects
the corresponding measurement.
I/O Data Parameters The I/O data parameters are used to configure the content and size of the
DeviceNet I/O Poll response message.
Data Parameters The Data parameters are used to view the measured values of the input
channels, as well as to monitor the status of the channels, alarms, and relays.
Device Mode Parameters The Device Mode parameters are used to control the functions and the
behavior of the device.
Specifications
The Appendix lists the technical specifications for the XM-220 module.
Speed
Acceleration
Peak Speed
Alarm Parameters Alarm and danger pair provided for each of:
Speed
Acceleration
Zero Speed
Locked Rotor
Latching Latching, or
Non-latching
DeviceNet Information
Electronic Data Sheets Electronic Data Sheet (EDS) files are simple text files used by network
configuration tools such as RSNetWorx (Version 3.0 or later) to help you
identify products and easily commission them on a network. The EDS files
describe a product’s device type, product revision, and configurable parameters
on a DeviceNet network.
The EDS files for the XM modules are installed on your computer with the
XM configuration software. The latest EDS files can also be obtained at
http://www.ab.com/networks/eds/ or by contacting your local Rockwell
Automation representative.
Mode Description
Run The XM measurement modules collect measurement data and
monitor each measurement device.
The XM-440 establishes I/O connections with the XM
measurement modules in its scan list and monitors their alarms,
and controls its own relay outputs accordingly.
Program The XM module is idle.
The XM measurement modules stop the signal
processing/measurement process, and the status of the alarms
is set to the disarm state to prevent a false alert or danger
status.
The XM-440 closes the I/O connections with the XM
measurement modules in its scan list and stops monitoring their
alarms, relays are deactivated unless they are latched.
Configuration parameters can be read, updated and downloaded
to the XM module.
To change the operation mode of the module, use the Device Mode parameter
in the EDS file. Note that the Stop and Start services described on page 71 can
also be used to change the operation mode.
TIP You can also use the Stop service described on page 71 to
transition XM modules to Program mode.
TIP You can also use the Start service described on page 71 to
transition XM modules to Run mode.
XM Services The table below defines services supported by the XM modules. The table
includes the service codes, classes, instances, and attributes by their
appropriate hexadecimal codes. Use the Class Instance Editor in RSNetWorx
to execute these services, as illustrated in the example below.
XM Services
Example
Invalid Configuration Errors A Start or Save service request to an XM module may return an Invalid Device
Configuration error when there is a conflict amongst the configuration
settings.
The general error code for the Invalid Device Configuration error is D0hex.
An additional error code is returned with the general error code to specify
which configuration settings are invalid. The table below lists the additional
error codes associated with the Invalid Device Configuration error.
Additional Error Codes returned with the Invalid Device Configuration Error (0xD0)
Error Code
(Hex) Description
01 No specific error information is available.
02 Mismatched transducer, channel, and/or measurement unit.
03 Inverted transducer fault high/low values.
04 Alarm thresholds conflict with the alarm condition.
05 Alarm speed range is invalid.
06 Band minimum frequency is greater than maximum frequency. Or,
maximum frequency is greater than FMAX.
07 Relay is associated with an alarm that is not enabled.
08 Tachometer must be enabled for alarm or channel settings.
09 A senseless speed range is enabled on a speed alarm.
Additional Error Codes returned with the Invalid Device Configuration Error (0xD0)
Error Code
(Hex) Description
0A Too many alarms associated with a single measurement.
0B Invalid node address in the alarm list.
0C Too many alarms in the alarm list. Or, no alarms in the alarm list.
0D Alarm levels cannot be zero for alarms that are enabled.
0E Too many slaves in the scanner’s input data table.
0F The FMAX and Number of Lines do not yield correct vector calculations.
10 Phase (vector) alarms prohibited with synchronous sampling and more
than 1 tachometer pulse per revolution.
11 Can’t have order based band on asynchronous channel.
12 Unsupported Sensor Type and Channel ID combination.
13 Invalid Alarm Type for the associated measurement ID.
14 Synchronous sampling is required for alarm on synchronous
measurements.
15 Integration is not supported with the Bypass High Pass Filter option.
XM-220 I/O Message The XM-220 module supports Poll and Change of State (COS) I/O messages.
Formats The Poll response message is used by the XM modules to produce measured
values, and the COS message is used to produce the Alarm and Relay Status.
The XM-220 Poll request message contains no data. The Poll response
message can contain up to 31 REAL values for a total of 124 bytes.
The XM-220 provides three pre-defined (static) data formats of the Poll
response, as defined in Assembly instance 101-103. It also provides a dynamic
Assembly instance, instance 199, with which you can define a custom data
format for the Poll response. The dynamic Assembly instance can contain any
of the measurement parameters included in Assembly instance 101, as well as
several of the alarm and relay configuration parameters.
The default Assembly instance is 101 and the default size is 32 bytes. You can
change the Assembly instance and define the dynamic Assembly using the
configuration software. Refer to I/O Data Parameters on page 57.
The Poll response data can also be requested explicitly through Assembly
Object (Class ID 0x4), Instance 101 (0x65), Data Attribute (3).
The following tables show the static data formats of Assembly instances 101–
103.
Byte Definition
0–3 Channel 1 Speed measurement value
4–7 Channel 2 Speed measurement value
8–11 Channel 1 Acceleration measurement value
12–15 Channel 2 Acceleration measurement value
16–19 Channel 1 Gap measurement value
20–23 Channel 2 Gap measurement value
24–27 Channel 1 Peak Speed measurement value
28–31 Channel 2 Peak Speed measurement value
Byte Definition
0–3 Channel 1 Gap measurement value
4–7 Channel 2 Gap measurement value
8–11 Channel 1 Speed measurement value
12–15 Channel 2 Speed measurement value
16–19 Channel 1 Peak Speed measurement value
20–23 Channel 2 Peak Speed measurement value
24–27 Channel 1 Acceleration measurement value
28–31 Channel 2 Acceleration measurement value
Byte Definition
0–3 Channel 1 Speed measurement value
4–7 Channel 1 Acceleration measurement value
8–11 Channel 1 Gap measurement value
12–15 Channel 1 Peak Speed measurement value
16–19 Channel 2 Speed measurement value
20–23 Channel 2 Acceleration measurement value
24–27 Channel 2 Gap measurement value
28–31 Channel 2 Peak Speed measurement value
The XM-220 COS message contains five bytes of data as defined in the table
below. The COS data can also be requested explicitly through Assembly
Object (Class ID 0x4), Instance 100 (0x64), Data Attribute (3).
XM Status Values
The following tables describe the XM status values that are included in the
COS messages.
ADR can be used with XM modules but keep the following in mind when
setting up the XM modules.
• The ADR scanner saves and restores only the configuration parameters
contained in the module’s EDS file. Some XM parameters are not
included in the EDS file because they are not supported by either the
EDS specification or the tools that read the EDS files, for example
RSNetWorx for DeviceNet. These configuration parameters will not be
restored with ADR.
– Channel Name
– Tachometer Name
– Alarm Name
– Relay Name
– All Triggered Trend related parameters
DeviceNet Objects
Identity Object The Identity Object provides identification and general information about the
device.
(Class ID 01H)
Class Attributes
Instance Attributes
Access
Attr ID Rule Name Data Type Default Value
1 Get Vendor ID UINT 668 = Entek
2 Get Device Type UINT 109 (Specialty I/O)
3 Get Product Code UINT 35 (0x23)
4 Get Revision: STRUCT OF
Major USINT Value varies with each firmware revision
Minor USINT Value varies with each firmware revision
5 Get Status WORD
6 Get Serial Number UDINT
7 Get Product Name SHORT_ " XM-220 Speed Module"
STRING
Status
Services
Service
Code Class/Instance Usage Name
01h Instance Get_Attributes_All
05h Instance Reset
0Eh Instance Get_Attribute_Single
10h Instance Set_Attribute_Single1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
DeviceNet Object The DeviceNet Object is used to provide the configuration and status of a
physical attachment to DeviceNet.
(Class ID 03H)
Class Attributes
Access
Attr ID Rule Name Data Type Default Value
1 Get Revision UINT 2
Instance Attributes
Access
Attr ID Rule Name Data Type Default Value
1 Get/Set MAC ID1 USINT 63
2 Get/Set Baud Rate2 USINT 0
3 Get Bus-Off Interrupt BOOL 0
4 Get/Set Bus-Off Counter USINT 0
5 Get Allocation Information STRUCT of 0 255
BYTE
USINT
100 Get/Set Autobaud Disable BOOL 0 (Ignore attribute 2 and always autobaud)
1 Setting the MAC ID causes the device to reset automatically, after which it will go online with the new MAC
ID.
2 The Baud Rate setting can not be set while Autobaud Disable is equal to 0. The new baud rate will not take
effect until the module is reset.
The MAC ID, Baud Rate, and Autobaud Disable settings are stored in
non-volatile memory so they do not reset to the default with each power cycle.
The Baud Rate attribute supports the following settings:
• 0 = 125 kbps
• 1 = 250 kbps
• 2 = 500 kbps
The Baud Rate setting is used only when automatic baud rate detection is
disabled (Autobaud Disable = 1). When Autobaud Disable is set to zero
(0), the module ignores its Baud Rate setting and performs automatic baud
rate detection instead. This means that the module will determine the network
baud rate by listening for network traffic before attempting to go online.
Services
Service
Code Class/Instance Usage Name
0Eh Class/Instance Get_Attribute_Single
10h Instance Set_Attribute_Single
4Bh Instance Allocate_Master/Slave_Connetion_Set
4Ch Instance Release_Group_2_Identifier_Set
Assembly Object The Assembly Object binds attributes of multiple objects to allow data to or
from each object to be sent or received in a single message.
(Class ID 04H)
The XM-220 module provide both static and dynamic assemblies.
Class Attribute
Access
Attr ID Rule Name Data Type Description Semantics
1 Get Revision UINT Revision of the 2
implemented object.
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Value
1 Get Number of Members in list UINT Only supported for Dynamic Assembly
instance
2 Set Member List Array of STRUCT: Only supported for Dynamic Assembly
instance
Member Data Description UINT Size of member data value in bits
Member Path Size UINT
Member Path Packed EPATH
3 Get Data Defined in tables
on the following
pages.
This assembly is sent using COS messaging when any of the Alarm or Relay
Status values change.
Table C.10 Instance 100 Data Format (Alarm and Relay Status Values Assembly)
Table C.10 Instance 100 Data Format (Alarm and Relay Status Values Assembly)
This Assembly instance can be created and configured with the XM Serial
Configuration Utility or RSMACC Enterprise Online Configuration Utility.
Using the configuration software, you determine the format of the data. This
assembly instance can be selected to be sent in response to an I/O Poll request
from a Master.
The dynamic Assembly can include all of the measurement values included in
Assembly instance 101. In addition, the dynamic Assembly can include the
following configuration parameters.
The dynamic Assembly instance must be instantiated with a call to the class
level Create service. Then the structure can be defined with the
Set_Attribute_Single service for the Member List attribute. Only one dynamic
Attribute instance is supported so subsequent calls to the Create service will
return a Resource Unavailable (0x02) error. The Delete service can be used to
destroy the dynamic Assembly instance so that it can be re-created.
Services
Service
Code Class/Instance Usage Name
0Eh Class/Instance Get_Attribute_Single
10h Instance Set_Attribute_Single
08h Class Create
09h Instance Delete
Connection Object The Connection Object allocates and manages the internal resources
associated with both I/O and Explicit Messaging Connections.
(Class ID 05H)
Class Attributes
Instances
Instance Description
1 Explicit Message Connection for pre-defined connection set
2 I/O Poll Connection
4 I/O COS (change of state) Connection
11 - 17 Explicit Message Connection
Instance Attributes
Access
Attr ID Rule Name Data Type Description
1 Get State USINT State of the object.
2 Get Instance Type USINT Indicates either I/O or Messaging
Connection.
3 Get Transport Class Trigger BYTE Defines behavior of the Connection.
4 Get Produced Connection ID UINT Placed in CAN Identifier Field when the
Connection transmits.
5 Get Consumed Connection UINT CAN Identifier Field value that denotes
ID message to be received.
6 Get Initial Comm BYTE Defines the Message Group(s) across
Characteristics which productions and consumptions
associated with this Connection occur.
7 Get Produced Connection UINT Maximum number of bytes transmitted
Size across this Connection.
8 Get Consumed Connection UINT Maximum number of bytes received across
Size this Connection.
9 Get/Set Expected Packet Rate UINT Defines timing associated with this
Connection.
12 Get/Set Watchdog Time-out USINT Defines how to handle Inactivity/Watchdog
Action timeouts.
13 Get Produced Connection UINT Number of bytes in the
Path Length production_connection_path attribute.
Access
Attr ID Rule Name Data Type Description
14 Get Produced Connection Array of Specifies the Application Object(s) whose
Path USINT data is to be produced by this Connection
Object. See DeviceNet Specification
Volume 1 Appendix I.
15 Get Consumed Connection UINT Number of bytes in the
Path Length consumed_connection_path attribute.
16 Get Consumed Connection Array of Specifies the Application Object(s) that are
Path USINT to receive the data consumed by this
Connection Object. See DeviceNet
Specification Volume 1 Appendix I.
17 Get Production Inhibit Time UINT Defines minimum time between new data
production.
Services
Service
Code Class/Instance Usage Name
05h Instance Reset
0Eh Instance Get_Attribute_Single
10h Instance Set_Attribute_Single
Discrete Input Point Object The Discrete Input Point Object Instance 1 indicates whether the module is
in the startup period. Instance 2 indicates whether the machine is rotating in
(Class ID 08H) the reverse direction.
Class Attributes
Access
Attr ID Rule Name Data Type Description Semantics
1 Get Revision UINT Revision of the 2
implemented object.
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Value BOOL Value 0 = Off
1 = On
199 Set Backdoor USINT Setting this attribute is Set to one of the
Service equivalent to requesting following values to
the specified service. perform the
specified service:
0x32 = Open
0x33 = Close
For instance 1, a Value of 1 means that the startup period is active. For
instance 2, a Value of 1 means that the machine is rotating in the reverse
direction.
Services
Service
Code Class/Instance Usage Name Description
0Eh Class/Instance Get_Attribute_Single Returns the contents of the
specified attribute.
10h Instance Set_Attribute_Single Sets the contents of the
specified attribute.
32h Instance Open Opens the virtual Startup
switch.
33h Instance Close Closes the virtual Startup
switch.
The Open and Close services are not valid for Instance 2.
Parameter Object The Parameter Object provides the interface to the XM-220 configuration
data.
(Class ID 0FH)
Parameter Object instance 1 is for the Speed Mode setting (dual channel, single
channel redundant, or reverse rotation). Parameter Object instances 2 to 13
provide an alternate method of setting the configuration parameters with
EPATH data types. And Parameter Object instances 14 and 15 provide an
alternate method of setting the Produced Connection Size and Produced
Connection Path attributes for the Poll Connection because these attributes
can be difficult to get/set directly through the Connection Object.
Class Attributes
Access
Attr ID Rule Name Data Type Description Semantics
2 Get Max Instance UINT Maximum instance Total number of parameter
number of an object in object instances.
this class.
8 Get Parameter Class WORD Bits that describe the Bit 0 Supports Parameter
Descriptor parameter. Instances
Bit 1 Supports Full Attrib.
Bit 2 Must do non-volatile store
Bit 3 Params in non-volatile
9 Get Config. UINT Set to 0
Assembly
Instance
Instances
Read
Instance Only Name Data Type Valid Values Default Value
1 No Mode USINT 0 = Dual Channel 0
1 = Single Channel
Redundant
2 = Reverse Rotation
2 No 4-20mA Output 1 USINT 0 = CH 1 Speed 0
Measurement Identifier 1 = CH 2 Speed
2 = CH 1 Accel
3 = CH 2 Accel
3 No 4-20mA Output 2 USINT 0 = CH 1 Speed 1
Measurement Identifier 1 = CH 2 Speed
2 = CH 1 Accel
3 = CH 2 Accel
4 No Relay 1 Alarm Identifier A USINT 0 = CH 1 Speed Alarm 0
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
Read
Instance Only Name Data Type Valid Values Default Value
5 No Relay 2 Alarm Identifier A USINT 0 = CH 1 Speed Alarm 0
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
6 No Relay 3 Alarm Identifier A USINT 0 = CH 1 Speed Alarm 0
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
7 No Relay 4 Alarm Identifier A USINT 0 = CH 1 Speed Alarm 0
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
8 No Relay 5 Alarm Identifier A USINT 0 = CH 1 Speed Alarm 0
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
9 No Relay 1 Alarm Identifier B USINT 0 = CH 1 Speed Alarm 1
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
10 No Relay 2 Alarm Identifier B USINT 0 = CH 1 Speed Alarm 1
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
Read
Instance Only Name Data Type Valid Values Default Value
11 No Relay 3 Alarm Identifier B USINT 0 = CH 1 Speed Alarm 1
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
12 No Relay 4 Alarm Identifier B USINT 0 = CH 1 Speed Alarm 1
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
13 No Relay 5 Alarm Identifier B USINT 0 = CH 1 Speed Alarm 1
1 = CH 2 Speed Alarm
2 = CH 1 Accel Alarm
3 = CH 2 Accel Alarm
4 = CH 1 Zero Speed Alarm
5 = CH 2 Zero Speed Alarm
6 = CH 1 Locked Rotor Alarm
7 = CH 2 Locked Rotor Alarm
14 No Poll Connection Produced USINT 101 - 103, 199 (Assembly 101
Connection Path1 Object instance number)
15 No Poll Connection Produced UINT 4 -124 32
Connection Size1
1 The Poll Connection Produced Connection Path and Size parameters cannot be set while the Poll connection is
already established with a master/scanner. Attempting to do so will result in an "Object State Conflict" error
(error code 0xC). These Parameter instances are a little more flexible than the actual Connection Object
attributes because they can be set while the connection is in the NON-EXISTENT state (before the
master/scanner allocates the connection).
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
1 Set Parameter Actual value of parameter See Table C.23 for a list of valid
Value values for each instance.
2 Get Link Path Size USINT Size of Link Path 0 (These Parameter instances do
not link directly to another
object attribute.)
3 Get Link Path ARRAY of DeviceNet path to the
DeviceNet object for the Parameter
path value.
Segment BYTE See DeviceNet
Type/Port Specification Volume 1
Appendix I for format.
Segment See DeviceNet
Address Specification Volume 1
Appendix I for format.
4 Get Descriptor WORD Description of Parameter Bit 0 Settable Path support
Bit 1 Enum Strings support
Bit 2 Scaling support
Bit 3 Scaling Links support
Bit 4 Read only
Bit 5 Monitor
Bit 6 Ext. Prec. scaling
5 Get Data Type EPATH Data Type Code See DeviceNet Specification
Volume 1 Appendix J.
6 Get Data Size USINT Number of Bytes in
Parameter value.
Services
Service
Code Class/Instance Usage Name Description
0Eh Class/Instance Get_Attribute_Single Returns the contents of the
specified attribute.
10h Class Set_Attribute_Single Sets the contents of the
specified attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
Acknowledge Handler The Acknowledge Handler Object is used to manage the reception of message
acknowledgments. This object communicates with a message producing
Object Application Object within a device. The Acknowledge Handler Object notifies
(Class ID 2BH) the producing application of acknowledge reception, acknowledge timeouts,
and production retry limit errors.
Class Attributes
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Default Value
1 Get/Set Acknowledge Timer UINT 16ms
2 Get/Set Retry Limit USINT 1
3 Get COS Producing UINT 4
Connection Instance
Services
Service
Code Class/Instance Usage Name
0Eh Instance Get_Attribute_Single
10h Instance Set_Attribute_Single
Alarm Object The Alarm Object models a two-stage (alert and danger levels) alarm.
(Class ID 31DH)
Class Attributes
Instances
Instance Measurement
Alarm 1 Channel 1 Speed
Alarm 2 Channel 2 Speed
Alarm 3 Channel 1 Acceleration
Alarm 4 Channel 2 Acceleration
Alarm 5 Channel 1 Zero Speed
Alarm 6 Channel 2 Zero Speed
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Alarm Status 3 BITS The current status of the 0 = Normal
alarm. 1 = Alert (alarm)
2 = Danger (shutdown)
3 = Disarm
4 = Xdcr Fault
5 = Module Fault
6 = Tachometer Fault
4 Get/Set Alarm Enable BOOL Indicates whether this 0 = Disabled
alarm object is enabled. 1 = Enabled
6 Get Threshold Units USINT Indicates whether the Set to 1
threshold and hysteresis 1 = Measurement units
value are specified in
units of measure.
7 Get/Set Condition USINT Indicates on which side of 0 = Greater than
the threshold values the 1 = Less than
alarm and danger 2 = Inside range
conditions exist. 3 = Outside range
Access
Attr ID Rule Name Data Type Description Semantics
8 Get/Set Alert Threshold REAL The threshold value for
(High) the alert (alarm) condition
(greater threshold for
range types).
9 Get/Set Danger REAL The threshold value for
Threshold (High) the danger (shutdown)
condition (greater
threshold for range types).
10 Get/Set Alert Threshold REAL The lesser threshold value
Low for the alert (alarm)
condition for the range
condition types.
11 Get/Set Danger REAL The lesser threshold value
Threshold for the danger (shutdown)
Low condition for the range
condition types.
12 Get/Set Hysteresis REAL The amount on the safe
side of a threshold by
which the value must
recover to clear the alarm.
14 Get/Set Startup Period UINT The amount of time that Seconds
the Tach Fault status may
be inhibited after the
startup signal is received.
18 Get/Set Name STRING2 A name to help identify
this alarm.
20 Get/Set Inhibit Tach BOOL Determines whether the 0 = Tach Fault allowed
Fault Tach Fault status is 1 = Tach Fault inhibited
prohibited during the
startup period.
Services
The settable attributes of this object are not affected by the status of the
Device Mode Object.
Service
Code Class/Instance Usage Name Description
0Eh Instance Get_Attribute_Single Returns a single attribute.
10h Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
Device Mode Object The Device Mode Object is used to control access to the configuration
parameters in the module. This object’s Device Mode attribute must be in
(Class ID 320H) PROGRAM mode to allow the module’s configuration parameters to be "Set"
(see Services). Attempts to set the configuration parameters while the Device
Mode is in RUN mode will return an error. Note that the module collects
measurements while in RUN mode but not while it is in PROGRAM mode.
Class Attributes
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get/Set Device Mode UINT The operating mode of the 0 = Power Up
module. 1 = RUN
2 = PROGRAM
199 Set Backdoor USINT Setting this attribute is Set to one of the following
Service equivalent to requesting values to perform the specified
the specified service. service:
0x05 = Reset
0x09 = Delete
0x15 = Restore
0x16 = Save
Setting the Device Mode attribute to "1" (RUN) is equivalent to executing the
Start service. Setting the Device Mode attribute to "2" (PROGRAM) is
equivalent to executing the Stop service.
Services
Service
Code Class/Instance Usage Name Description
0Eh Instance Get_Attribute_Single Return the value of a single
attribute.
10h Instance Set_Attribute_Single Set the value of a single
attribute.
07h Instance Stop Transitions from Run to the
Program state.
Service
Code Class/Instance Usage Name Description
06h Instance Start Validate the device
configuration settings and
transition to the Run state if
OK.
05h Instance Reset Transition to the Power Up
state. Load the non-volatile
configuration and transition
to the Run state if saved
configuration restored.
16h Instance Save Validate the device
configuration settings if
necessary and save them to
non-volatile memory.
09h Instance Delete Delete the saved
configuration from
non-volatile memory.
15h Instance Restore Load the saved
configuration or the factory
default configuration from
non-volatile memory.
Relay Object The Relay Object models a relay (actual or virtual). A relay can be activated or
deactivated based on the status of one or more alarms.
(Class ID 323H)
Class Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Number of UINT Number of Instances in 5
Instances this class.
100 Set Reset All USINT Setting this attribute is Reset All is an attribute that
equivalent to executing provides a way to perform a
the Class Reset service Class level Reset service via the
Set_Attribute_Single service.
Setting this attribute to any
value is equivalent to
performing the Class level Reset
service. Reading the Reset All
attribute always returns zero.
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Relay Status BOOL The current status of the 0 = Off
relay. 1 = On
4 Get/Set Relay Enable BOOL Indicates whether this 0 = Disabled
relay object is enabled. 1 = Enabled
5 Get/Set Latch Enable BOOL Indicates whether this 0 = Nonlatching
relay latches (requires a 1 = Latching
reset command to
deactivate).
6 Get/Set Failsafe Enable BOOL Indicates whether this 0 = Non-failsafe (not normally
relay is normally energized)
energized (activated 1 = Failsafe (normally energized)
during power loss).
7 Get/Set Delay USINT The time period that the 0 to 25.5 seconds
voting logic must be true (specified in tenths of seconds)
before the relay is
activated.
8 Get/Set Name STRING2 A name to help identify 18 characters maximum
the relay.
9 Get/Set Alarm Level BYTE Specifies what alarm 0 = Normal
status values will cause 1 = Alert
the relay to activate. 2 = Danger
3 = Disarm
4 = Xdcr Fault
5 = Module Fault
6 = Tachometer Fault
10 Get/Set Alarm Identifier EPATH Identifies the first alarm See Parameter Object instances
A status the relay monitors. 4 to 8.
Access
Attr ID Rule Name Data Type Description Semantics
11 Get/Set Alarm Identifier EPATH Identifies the second See Parameter Object instances
B alarm status the relay 9 to 13.
monitors.
12 Get/Set Logic USINT Indicates the number of 0 = Ignore Alarm Identifier B
associated alarms that and activate the relay based on
must have a status value the status of Alarm Identifier
specified by Alarm Level A.
in order to activate the 1 = Activate the relay if the
relay. status of either Alarm
Identifier A or B matches any
of the statuses specified by
Alarm Level.
2 = Activate the relay if the
status of both Alarm Identifier
A and B match any of the
statuses specified by Alarm
Level.
14 Get Relay Installed BOOL Indicates whether an 0 = Not installed
actual relay is associated 1 = Installed
with this instance.
Services
Setting the attributes of this object are not affected by the status of the Device
Mode Object.
Service
Code Class/Instance Usage Name Description
05h Class/Instance Reset Resets latched relay(s).
0Eh Class/Instance Get_Attribute_Single Returns a single attribute.
10h Class/Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
Speed Measurement Object The Speed Measurement Object models a speed measurement of a tachometer
signal.
(Class ID 325H)
Class Attributes
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Speed Value REAL The measured speed CPM
value.
4 Get Status BOOL Indicates if a fault or 0 = Operating without alarms or
alarm has occurred. faults
1 = Alarm or fault condition
exists. The Speed Value
attribute may not represent the
actual field value.
5 Get Maximum REAL The maximum (peak) CPM
Speed measured speed value
(positive or negative)
since the most recent
reset.
6 Get/Set Locked Rotor BOOL Indicates whether the 0 = Disabled
Alarm Enable locked rotor alarm is 1 = Enabled
enabled.
7 Get Locked Rotor USINT The current status of the 0 = Normal
Alarm Status locked rotor alarm. 1 = Alert (alarm)
2 = Danger (shutdown)
3 = Disarm
4 = Xdcr Fault
5 = Module Fault
6 = Tachometer Fault
7 = Unknown
Access
Attr ID Rule Name Data Type Description Semantics
8 Get/Set Locked Rotor REAL The minimum machine CPM
Alert Threshold speed that must be
obtained within the alert
period to avoid an alert
status.
9 Get/Set Locked Rotor REAL The minimum machine CPM
Danger speed that must be
Threshold obtained within the
danger period to avoid a
danger status.
10 Get/Set Locked Rotor USINT The amount of time the Seconds
Alert Period machine has to reach the
alert threshold before an
alert status is indicated.
11 Get/Set Locked Rotor USINT The amount of time the Seconds
Danger Period machine has to reach the
danger threshold before a
danger status is
indicated.
12 Get/Set Time Constant UINT The time constant value Milliseconds
used for exponential
averaging of the Speed
Value (a low pass
filter/output smoothing
filter).
13 Get Acceleration REAL The rate of change of the CPM/min
Speed measurement.
Services
Setting the attributes of this object are not affected by the status of the Device
Mode Object.
Service
Code Class/Instance Usage Name Description
05h Instance Reset Clears Maximum (Peak)
speed to 0.
0Eh Instance Get_Attribute_Single Returns a single attribute.
10h Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
Tachometer Channel Object The Tachometer Channel Object models "front end" processing performed
on a tachometer signal before specific measurements are performed.
(Class ID 326H)
Class Attributes
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get/Set Number of UINT The number of signal 0 = Tachometer disabled
Pulses per pulses per revolution of > 0 = Tachometer enabled
Revolution the shaft (number of gear
teeth).
4 Get/Set Auto Trigger BOOL Indicates whether the 0 = Use specified Trigger Level
trigger level is determined and Hysteresis
automatically from the 1 = Determine trigger level and
signal. hysteresis automatically
5 Get/Set Trigger Level REAL The signal level to be Volts
used as the trigger.
6 Get/Set Trigger Slope USINT The slope of the signal at 0 = Positive
the threshold crossing to 1 = Negative
be used as the trigger.
7 Get/Set Trigger REAL The amount of hysteresis In Auto Trigger mode, this
Hysteresis around the trigger level. value is a percentage of the
peak-to-peak input signal and
can range from 0 to 50%. In
Manual Trigger mode, this
value is a voltage level (the
hysteresis voltage is added or
subtracted to the threshold
voltage to determine the
hysteresis range).
Access
Attr ID Rule Name Data Type Description Semantics
8 Get/Set Name STRING2 A name to help identify 18 character maximum
this channel
9 Get/Set Multiplier REAL A multiplier applied to the > 0
tachometer pulse rate.
10 Get/Set Fault Time-out USINT Number of seconds with 1 to 64 seconds
no pulses before a Tach
Fault is indicated.
Services
Service
Code Class/Instance Usage Name Description
0Eh Instance Get_Attribute_Single Returns a single attribute.
10h Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get DC Bias REAL The measured average DC Volts
bias of the transducer
signal in volts.
4 Get Status BOOL Indicates whether a 0 = No fault
transducer fault exists 1 = A transducer fault exists
(the measured DC Bias is
outside the range
specified by Fault High
and Low).
7 Get/Set Fault High REAL The maximum expected Volts
DC Bias voltage from the
transducer in volts.
8 Get/Set Fault Low REAL The minimum expected Volts
DC Bias voltage from the
transducer in volts.
9 Get/Set Power Type USINT Indicates the type of 0 = No power supplied
power supplied to the 3 = Bias current for passive
transducer. magnetic sensors
13 Get/Set DC Bias Time REAL The time constant value Seconds
Constant used for exponential
averaging of the DC Bias
value (a low pass
filter/output smoothing
filter).
Services
Service
Code Class/Instance Usage Name Description
0Eh Instance Get_Attribute_Single Returns a single attribute.
10h Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
4-20mA Output Object The 4-20mA Output Object models the configuration of a 4-20mA output
signal.
(Class ID 32AH)
Class Attributes
Instances
Instance Attributes
Access
Attr ID Rule Name Data Type Description Semantics
3 Get Value REAL The current output value. mA
4 Get/Set Enable BOOL Indicates whether this 0 = Disabled
4-20mA output is 1 = Enabled
enabled.
5 Get/Set Max Range REAL The measured value
associated with 20mA.
6 Get/Set Min Range REAL The measured value
associated with 4mA.
7 Get/Set Measurement EPATH Identifies the class, See Parameter Object instances
Identifier Path instance, and attribute of 2 and 3.
a measurement value that
this 4-20mA output is See DeviceNet Specification
tracking. Volume 1 Appendix I.
Services
Service
Code Class/Instance Usage Name Description
0Eh Instance Get_Attribute_Single Returns a single attribute.
10h Instance Set_Attribute_Single Sets a single attribute.1
1 Attributes can only be set while the device is in Program Mode. See the description of the Device Mode Object
for more information.
alarm
A means for replacing a malfunctioning device with a new unit, and having the
device configuration data set automatically. The ADR scanner uploads and
stores a device’s configuration. Upon replacing a malfunctioning device with a
new unit (MAC ID 63), the ADR scanner automatically downloads the
configuration data and sets the MAC ID (node address).
baud rate
The baud rate is the speed at which data is transferred on the DeviceNet
network. The available data rates depend on the type of cable and total cable
length used on the network:
bus off
A bus off condition occurs when an abnormal rate of errors is detected on the
Control Area Network (CAN) bus in a device. The bus-off device cannot
receive or transmit messages on the network. This condition is often caused by
corruption of the network data signals due to noise or baud rate mismatch.
current configuration
DeviceNet network
A cable is used to connect devices on the network. It contains both the signal
and power wires. General information about DeviceNet and the DeviceNet
specification are maintained by the Open DeviceNet Vendor’s Association
(ODVA). ODVA is online at http://www.odva.org.
disarm state
EEPROM
EDS files are simple text files that are used by network configuration tools
such as RSNetWorx for DeviceNet to describe products so that you can easily
commission them on a network. EDS files describe a product device type,
revision, and configurable parameters.
Help window
A window that contains help topics that describe the operation of a program.
These topics may include:
• An explanation of a command.
• A description of the controls in a dialog box or property page.
• Instructions for a task.
• Definition of a term.
MAC ID
master device
A device which controls one or more slave devices. The XM-440 Master Relay
module is a master device.
node address
online help
Online help allows you to get help for your program on the computer screen
by pressing F1. The help that appears in the Help window is context sensitive,
which means that the help is related to what you are currently doing in the
program.
Polled
Program mode
The XM module is idle. Typically this occurs when the module configuration
settings are being updated with the XM Configuration program. In Program
mode, the signal processing/measurement process is stopped. The status of
the alarms is set to the disarm state to prevent a false alert or danger status.
Run mode
In Run mode, the module collects measurement data and monitors each
measurement device.
settling time
The amount of time it takes a measurement to reach 90% of the final value
given a step change in the input signal.
slave device
A device that receives and responds to messages from a Master device but
does not initiate communication. Slave devices include the XM measurement
modules, such as the XM-120 Dynamic Measurement module and the XM-220
Dual Speed module.
transducer
virtual relay
XM configuration
For an additional level of technical phone support for installation, configuration and
troubleshooting, we offer TechConnect Support programs. For more information,
contact your local distributor or Rockwell Automation representative, or visit
http://support.rockwellautomation.com.
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of
installation, please review the information that's contained in this manual. You can also
contact a special Customer Support number for initial help in getting your module up
and running:
Rockwell tests all of our products to ensure that they are fully operational when
shipped from the manufacturing facility. However, if your product is not functioning
and needs to be returned:
United States Contact your distributor. You must provide a Customer Support case
number (see phone number above to obtain one) to your distributor in
order to complete the return process.
Outside United Please contact your local Rockwell Automation representative for
States return procedure.