Vibro-Meter Relay expansion RLC16 Mk2 600-045
Relay expansion RLC16 Mk2 600-045
DESCRIPTION (continued)
The CPUMMk2 + IOCNMk2 rack controller and
communications interface module is an optional
module used to provide additional VM600Mk2 system
functionality such as fieldbus communications
(Modbus TCP and/or PROFIBUS DP); module data
aggregation, processing and sharing; fieldbus
(module-level) and/or module (rack-level)
communications redundancy; front-panel alarm reset
(AR); MPS rack (CPUx) security; system event and
measurement event logging.
VM600Mk2 rack-based monitoring systems
complement the VibroSmart ® distributed monitoring
systems that are also available from Parker Meggitt’s
vibro-meter ® product line, and are compatible with
the same VibroSight ® machinery monitoring
software suite.
CPUMMk2 + IOCNMk2 modules and
VM600Mk2 racks
The CPUMMk2 + IOCNMk2 rack controller and
communications interface module is used as part of a
VM600Mk2 rack-based monitoring system.
The CPUMMk2 module is always used with an
associated IOCNMk2 module as a pair/set of
modules. Both the CPUMMk2 and the IOCNMk2 are
single-width modules that occupy a single VM600Mk2
rack slot (module position). The CPUMMk2 + IOCNMk2
module can only be used in VM600Mk2 system racks
(ABE04x).
When one CPUMMk2 + IOCNMk2 module is installed in
a VM600Mk2 system rack as a standard rack
controller and communications interface (no module
redundancy), the CPUMMk2 is installed in the front of
a VM600Mk2 rack (typically slot 0) and the associated
IOCNMk2 is installed in the rear of the rack (typically
slot 0), in the slot directly behind the CPUMMk2. Each
module connects directly to the rack’s backplane
using two connectors.
IOCN
When two CPUMMk2 + IOCNMk2 modules are installed
in a VM600Mk2 system rack for rack-level
communications redundancy, the “master” module is
typically installed in slots 0 (front and rear) and the
“subordinate” module is typically installed in slots 1
(front and rear).
Note: The CPUMMk2 + IOCNMk2 module is
compatible with all VM600Mk2 system racks (ABE04x)
and later VM600 system racks (ABE04x) with an
I2C interface (VME utility bus)
CPUMMk2 + IOCNMk2 module functionality
As a fieldbus communications interface for a
VM600Mk2 monitoring system, the CPUMMk2 module
communicates with other VM600Mk2 processing
modules in the rack (such as the MPC4Mk2 and/or
future AMCxMk2 ) via the rack’s VME bus and with
XMx16 modules via a system Ethernet link in order to
obtain measurement data and then share this
information with third-party systems such as a DCS
or PLC.
Note: The CPUMMk2 is not compatible with first
generation VM600Mk1 cards such as the
MPC4 /IOC4T and AMC8 /IOC8T card pairs.
The data shared via fieldbus can be the “raw”
measurement data obtained from MPC4Mk2 or
XMx16 modules, and/or the status (health) data
obtained from the CPUMMk2 modules, or the data
can be further processed as required (defined by the
fieldbus configuration file). For example, the
processing supported includes basic mathematical
functions such as arithmetic and logical operations,
and many other supporting functions.
Note: The CPUMMk2 can be used as a data
communications gateway for XMx16 modules in low
data-bandwidth applications. For example, handling
hundreds of bytes of static data via Modbus TCP and/
or PROFIBUS DP. However, the CPUMMk2 cannot be
used as a gateway for XMx16 modules in high data
bandwidth applications as the dynamic data
(waveforms and spectra) generated by XMx16
modules typically requires a direct connection to the
VibroSight ® software.