Vibro-Meter Relay expansion RLC16 Mk2 600-045L



Relay expansion RLC16 Mk2    600-045L

As a rack controller for a VM600Mk2 monitoring

system, the CPUMMk2 module can manage the

configuration of XMx16 + XIO16T modules that are

operating without a VibroSight Server.

(Note: MPC4Mk2 + IOC4Mk2 modules are configured

using the VibroSight ® software.) The ALARM RESET

button on the front panel of the CPUMMk2 module

can be used to clear the alarms latched by the

monitoring modules (MPC4Mk2) in the rack. This is a

rack-wide equivalent of resetting alarms individually

for each module using discrete signal interface alarm

reset (AR) inputs or VibroSight ® software

commands.

A security key lock, with a removable key, on the front

panel of the CPUMMk2 module can be used to enable

VM600Mk2 rack (CPUMMk2) security.

DESCRIPTION (continued)

LEDs on the front panel of the CPUMMk2 module

(front of VM600Mk2 rack) indicate the mode of

operation and status of the CPUMMk2 + IOCNMk2

module, and the status of its system Ethernet and

fieldbus communications.

IOCNMk2 module

The IOCNMk2 module acts as a signal and

communications interface for the CPUMMk2 module.

It also protects all inputs against electromagnetic

interference (EMI) and signal surges to meet

electromagnetic compatibility (EMC) standards.

LEDs on the front panel of the IOCNMk2 module (rear

of VM600Mk2 rack) indicate the status of its system

Ethernet and fieldbus communications.

Fieldbus communications

The CPUMMk2 + IOCNMk2 module has two fieldbus

interfaces (ports), FIELDBUS1 and FIELDBUS2.

available on the IOCNMk2 module (rear of VM600Mk2

rack).

The fieldbus ports allow the CPUMMk2 module to act

as a data communications gateway between a

VM600Mk2 rack and external devices that use

fieldbus networks. In order to do this, the CPUMMk2

acts as a fieldbus server (slave) device that obtains

data from the modules in the VM600Mk2 rack

(MPC4Mk2 and XMx16 modules, and the CPUMMk2

module itself) to share with fieldbus client (master)

devices such as a DCS or PLC via one of the

CPUMMk2 + IOCNMk2 module’s fieldbus interfaces:

Modbus TCP and/or PROFIBUS DP.

Each fieldbus port, FIELDBUS1 and FIELDBUS2.

consists of two connectors, one for serial-based

fieldbus standards and one for Ethernet-based. Both

fieldbus ports can be active at the same time but only

one connector can be used per interface/port

(that is, connector J1 or J2 for FIELDBUS1. and

connector J4 or J5 for FIELDBUS2).