Huang, Jason, Author at LINGKONG

August 25, 2025 BY Huang, Jason

Vibro-Meter ® VM600 CPUM and IOCN modular CPU card and input/output card

KEY FEATURES AND BENEFITS

• From the Vibro-Meter® product line

• VM600 CPUM/IOCN rack controller and

communications interface card pair with

support for Modbus RTU/TCP and PROFINET,

and a front-panel display

• “One-Shot” configuration management of

protection cards (MPC4 and AMC8) in a

VM600 rack using an Ethernet or RS-232 serial

connection to a computer running the

VM600 MPSx software

• Front-panel display for visualisation of

monitored outputs and alarm limits from

protection cards

• Front-panel alarm reset (AR) button

• VM600 MPS rack (CPUM) security

• Industry standard fieldbus communications

interfaces: Modbus RTU/TCP and PROFINET

• Two Ethernet connections and up to three

serial connections (RS-232 / RS-422 / RS-485)

can run simultaneously

• Communications redundancy with multiple

fieldbuses: Ethernet and/or serial

KEY BENEFITS AND FEATURES (continued)

• VM600 system event and measurement event

logs available via the VM600 MPSx software

• Supports live insertion and removal of

protection cards (“hot-swapping”) with

automatic configuration

• Ethernet (100 Mbps) communication

• Front-panel status indicators (LEDs)

• Compatible with all VM600 ABE04x

system racks

APPLICATIONS

• Rack controller for a VM600 system

• Communications gateway between VM600

and third-party systems, such as a DCS or PLC

• Enables sharing of measurement data from

VM600 monitoring cards in machinery

protection, condition monitoring and/or

combustion monitoring applications

Information contained in this document may be subject to export control regulations of the European Union, USA or other countries.

Each recipient of this document is responsible for ensuring that transfer or use of any information contained in this document

complies with all relevant export control regulations. ECN N/A

DESCRIPTION

Introduction

The VM600 CPUM and IOCN modular CPU card

and input/output card is a rack controller and

communications interface card pair that acts as

a system controller and data communications

gateway for a VM600 rack-based machinery

protection system (MPS) and/or condition

monitoring system (CMS) from Meggitt’s

Vibro-Meter® product line.

Different versions of CPUx/IOCx card pair

Different versions of CPUx/IOCx rack controller

and communications interface card pair are

available, as follows:

• The CPUM/IOCN is the original version with a

front-panel display and support for

Modbus RTU/TCP and PROFINET

(PNR 200-595-VVV-VVV).

• The CPUR/IOCR is a version with rack controller

redundancy and support for Modbus RTU/TCP

(PNR 600-007-VVV-VVV).

• The CPUR2/IOCR2 is a version with

mathematical processing of fieldbus data and

support for Modbus TCP and PROFIBUS DP

(PNR 600-026-000-VVV).

VM600 rack-based monitoring systems

The Vibro-Meter® VM600 rack-based monitoring

system is part of Meggitt’s solution for the

protection and monitoring of rotating machinery

used in the power generation and oil & gas

industries. The VM600 is recommended when a

centralised monitoring system with a medium to

large number of measurement points (channels)

is required. It is typically used for the monitoring

and/or protection of larger machinery such as

gas, steam and hydro turbines, and generators,

smaller machines such as compressors, fans,

motors, pumps and propellers, as well as balanceof-plant (BOP) equipment.

A VM600 system consists of a 19″ rack, a rack

power supply and one or more monitoring card

pairs. Optionally, relay cards and rack controller

and communications interface cards can also be

included.

Two types of VM600 rack are available: a VM600

ABE04x system rack (6U) that can house up to 12

monitoring card pairs, and a VM600 ABE056

slimline rack (1U) that can house 1 monitoring

card pair. VM600 racks are typically mounted in

standard 19″ rack cabinets or enclosures installed

in an equipment room.

Different VM600 monitoring cards are available

for machinery protection, condition monitoring

and/or combustion monitoring applications. For

example, machinery protection cards such as the

MPC4/IOC4T machinery protection card pair and

AMC8/IOC8T analogue monitoring card pair,

and condition monitoring cards such as the

XMV16/XIO16T monitoring card pair for vibration

and XMC16/XIO16T monitoring card pair for

combustion.

The RLC16 relay card is an optional card used to

provide additional relays when the four relays per

MPC4/IOC4T or AMC8/IOC8T card pair are not

enough.

The CPUx/IOCx rack controller and

communications interface card pairs (CPUM/

IOCN, CPUR/IOCR or CPUR2/IOCR2) are optional

cards used to provide additional VM600 system

functionality such as configuration management,

“hot-swapping” with automatic reconfiguration,

front-panel display, CPUx/IOCx card pair

redundancy, fieldbus data processing, frontpanel alarm reset (AR) button, MPS rack (CPUx)

security, system event and measurement event

logging, fieldbus communications (Modbus,

PROFIBUS and/or PROFINET) and/or

communications redundancy.

Note: Different versions of CPUx/IOCx rack

controller and communications interface card

pair support different combinations of VM600

system functionality.

VM600 rack-based monitoring systems

complement the VibroSmart® module-based

distributed monitoring systems that are also

available from Meggitt’s Vibro-Meter® product

line.

DESCRIPTION (continued)

CPUM/IOCN card pair and VM600 racks

The CPUM/IOCN card pair is used with a VM600

ABE04x system rack and a CPUM card can be

used either alone or with an associated IOCN

card as a card pair, depending on the

application/system requirements.

The CPUM is a double-width card that occupies

two VM600 rack slots (card positions) and the

IOCN is a single-width card that occupies a single

VM600 slot. The CPUM is installed in the front of the

rack (slots 0 and 1) and an associated IOCN is

installed in the rear of the rack in the slot directly

behind the CPUM (slot 0). Each card connects

directly to the rack’s backplane using two

connectors.

Note: The CPUM/IOCN card pair is compatible

with all VM600 ABE04x system racks.

CPUM rack controller and communications

interface functionality

The modular, highly versatile design of the CPUM

means that all VM600 rack configuration, display

and communications interfacing can be

performed from a single card in a “networked”

rack. The CPUM card acts as a “rack controller”

and allows an Ethernet link to be established

between the rack and a computer running one

of the VM600 MPSx software packages (MPS1 or

MPS2).

The CPUM front panel features an LCD display

that shows information for the CPUM itself and for

protection cards in a VM600 rack. The SLOT and

OUT (output) keys on the CPUM front panel are

used to select which signal to display.

As a fieldbus communications interface for a

VM600 monitoring system, the CPUM

communicates with MPC4 and AMC8 cards via

the VME bus and with XMx16/XIO16T card pairs

via an Ethernet link in order to obtain

measurement data and then share this

information with third-party systems such as a DCS

or PLC.

LEDs on the CPUM front panel indicate the OK,

Alert (A) and Danger (D) status for the currently

selected signal. When Slot 0 is selected, the LEDs

indicate the overall status of the whole rack.

When the DIAG (diagnostic) LED shows green

continuously, the CPUM card is operating

normally, and when the DIAG LED blinks, the

CPUM card is operating normally but access to

the CPUM card is restricted due to VM600 MPS

rack (CPUM) security.

The ALARM RESET button on the front panel of the

CPUM card can be used to clear the alarms

latched by all protection cards (MPC4 and

AMC8) in the rack. This is a rack-wide equivalent

of resetting alarms individually for each card using

discrete signal interface alarm reset (AR) inputs or

VM600 MPSx software commands.

The CPUM card consists of a carrier board with

two PC/104 type slots that can accept different

PC/104 modules: a CPU module and an optional

serial communications module.

All CPUM cards are fitted with a CPU module that

supports two Ethernet connections and two serial

connections. That is, both the Ethernet redundant

and serial redundant versions of the card.

The primary Ethernet connection is used for

communication with the VM600 MPSx software

via a network and for Modbus TCP and/or

PROFINET communications. The secondary

Ethernet connection is used for Modbus TCP

communications. The primary serial connection is

used for communication with the VM600 MPSx

software via a direct connection. The secondary

serial connection is used for Modbus RTU

communications.

Optionally, a CPUM card can be fitted with a

serial communications module (in addition to the

CPU module) in order to support additional serial

connections. This is the serial redundant version of

the CPUM card.

The CPUM module’s primary Ethernet and serial

connections are available via connectors (NET

and RS232) on the front panel of the CPUM.

However, if the associated IOCN card is used, the

primary Ethernet connection can be routed to a

connector (1) on the front panel of the IOCN

(instead of the connector on the CPUM (NET)).

When the associated IOCN card is used, the

secondary Ethernet and serial connections are

available via connectors (2 and RS) on the front

panel of the IOCN.

IOCN card

The IOCN card acts as a signal and

communications interface for the CPUM card. It

DESCRIPTION (continued)

also protects all inputs against electromagnetic

interference (EMI) and signal surges to meet

electromagnetic compatibility (EMC) standards.

The IOCN card’s Ethernet connectors (1 and 2)

provide access to the primary and secondary

Ethernet connections, and the serial connector

(RS) provides access to the secondary serial

connection.

In addition, the IOCN card includes two pairs of

serial connectors (A and B) that provide access to

the additional serial connections (from the

optional serial communications module) that can

be used to configure multi-drop RS-485 networks

of VM600 racks.

Front-panel display

The CPUM front panel features an LCD display

that uses display pages to show important

information for the cards in a VM600 rack. For the

CPUM itself, card run time, rack system time, rack

(CPUM) security status, IP address/netmask and

version information are displayed. While for MPC4

and AMC8 cards, measurements, card type,

version and run time are displayed.

For MPC4 and AMC8 cards, the level of the

selected monitored output is displayed on a

bargraph and numerically, with the Alert and

Danger levels also indicated on the bar-graph.

Measurement identification (slot and output

number) is shown at the top of the display.

VM600 MPS rack (CPUM) security

The CPUM supports features that can be used to

limit the functionality of a VM600 rack’s

machinery protection system (MPS) that is

available via the system Ethernet connections of

a CPUM/IOCN card pair. Enabling VM600 MPS

rack (CPUM) security helps to reduce the

possibility of interference in the machinery

protection function of the rack itself and in the

machinery being monitored. Accordingly, CPUM

rack security makes it easier for operators to

comply with international security/critical

infrastructure regulations.

The security features consists of two specific levels

of protection integrated in the CPUM card: CPUM

access lock (a “hardware” security feature) and

VM600 MPSx password validation (a “software”

security feature). Refer to the VM600 machinery

protection system (MPS) hardware manual and

the VM600 MPSx software manuals for further

information.

VM600 event logging

The CPUM card automatically logs VM600 system

events and measurement events to non-volatile

memory in order to provide valuable information

on the operating history of a system. Up to 10000

of the most recent events are stored on the card

for download as user-readable event log files

using the VM600 MPSx software.

Software

The CPUM/IOCN is software configurable using

the CPUM Configurator software.

The VM600 MPSx software supports the

configuration and operation of MPC4/IOC4T

card pairs for machinery protection applications,

including the processing and presentation of

measurement data for analysis. VM600 MPSx is

also used to configure and manage CPUM/IOCN

card pairs.

Note: The VM600 MPSx software is from the

Vibro-Meter® product line.

Applications information

The VM600 CPUM/IOCN rack controller and

communications interface card pair is

recommended for applications using multiple

monitoring cards in a VM600 rack.

The rack controller functionality makes it easier to

work with a VM600 machinery monitoring system –

for installation, configuration, management and

general operation. The CPUM/IOCN can

manage the configuration of MPC4/IOC4T and

AMC8/IOC8T card pairs, including hot-swapping.

It can also manage the configuration of XMx16/

XIO16T card pairs, eliminating the need for a

VibroSight Server in certain applications.

The communications interface functionality

makes it easy to further process and share data

from the monitoring cards (MPC4, AMC8 and/or

XMC16) in a VM600 machinery protection,

condition monitoring and/or combustion

monitoring system with third-party systems such as

a DCS or PLC using industry standard fieldbuses.

For further information, contact your local

Meggitt representative.

Processing functions

Rack controller

• VM600 monitoring card configuration

management

: Acts as a rack controller that manages the configuration of MPC4/

IOC4T and AMC8/IOC8T card pairs, including support for

“hot-swapping” with automatic configuration.

Can also manage the configuration of XMx16/XIO16T card pairs,

for applications that do not require a VibroSight Server.

• Front-panel display : LCD display that uses display pages to show important information

for the cards in a VM600 rack:

• Card run time, rack system time, rack (CPUM) security status,

IP address/netmask and version info are displayed for the CPUM.

• Measurements (bargraph with alarm levels, and numerically),

card type, version, and run time are displayed for the MPC4 and

AMC8 cards in the rack.

• Fieldbus data processing

(mathematical processing)

: Further processing of system data (measurement data and status

information) before being shared by fieldbus.

The further processing supported includes basic mathematical

functions such as arithmetic and logical operations, data selection,

comparison, min/max and scaling functions, bit manipulation and

packing/unpacking functions, and many supporting functions.

There is also a data freeze detection function that can be used to

help detect if a data value has stopped being updated.

• Alarm reset : CPUM front-panel button used to manually clear the alarms (and

relays) latched by MPC4/IOC4T and AMC8/IOC8T card pairs in the

rack

• VM600 MPS rack (CPUM) security : Used to limit the functionality of a machinery protection system

(MPS) that is available via the system Ethernet connections of a

CPUM/IOCN card pair, helping to reduce the possibility of

interference in the machinery protection function of the rack itself

and/or in the machinery being monitored

• Event logging : VM600 system event and measurement event logging with up to

10000 of the most recent events stored on the CPUM (in nonvolatile memory).

Note: System event logs and measurement event logs are

downloaded from a CPUM using the VM600 MPSx software.

• Status indication : CPUM front-panel LEDs (front of VM600 rack) indicate the mode of

operation and status of the CPUM card

Communications interface

• VM600 rack (system)

communications

: Uses a VME communications link for communications with

MPC4/IOC4T and AMC8/IOC8T card pairs (via the VME bus on the

VM600 rack’s backplane).

Uses a system Ethernet connection for communications with a

computer running software such as VM600 MPSx.

• Fieldbus communications

(data gateway)

: Acts as a fieldbus server (slave) device that obtains data from

cards in the VM600 rack (that is, from MPC4/IOC4T and

AMC8/IOC8T card pairs) to share with fieldbus client (master)

devices such as a DCS or PLC:

• The CPUM can act as a Modbus server and use the fieldbus

interfaces to share data via Modbus RTU and/or Modbus TCP.

Note: The configuration of the fieldbus interfaces and the definition

of the data to be shared via fieldbus is defined by a Modbus

configuration file that is uploaded to the CPUM card using the

CPUM Configurator software.

Fieldbus interfaces

Number of channels : Multiple fieldbus interfaces (ports).

Ethernet and/or serial: Modbus and/or PROFINET.

Data transfer

• Modbus : Up to 131072 registers/words and 131072 coils/bits total.

That is, up to 2 × 65536 registers/words and 2 × 65536 coils/bits

(holding and discrete).

• PROFINET : Maximum slot size of 128 bytes.

Note: PROFINET is supported by later versions of the CPUM card

running firmware version 081 or later.

It was originally only supported by earlier versions of the CPUM card

running a special PROFINET version of firmware (version 801) that is

no longer supported.

Contact your local Meggitt representative or Meggitt SA for further

information.

CPU module (CPUM PC/104 slot 1)

Note: The CPU module is fitted to all versions of the CPUM card.

Module type : PFM-541I or equivalent

Processor type : AMD Geode™ LX800

Processor Speed : 500 MHz

Memory : 256 MB DRAM

Power supply to module (input) : 5 VDC, <1.8 A

Operating system : QNX

Communication interfaces – serial

Number : 2

Primary serial interface

• Network interface : RS-232

• Data transfer rate : Up to 115.2 kBaud

• Network topologies : Point-to-point

• Protocols : Meggitt TCP/IP proprietary protocol for communication with the

VM600 MPSx software

• Function : VM600 rack configuration and communications using the

VM600 MPSx software

• Connector : RS232 on CPUM card (see Connectors on page 10)

Secondary serial interface (requires IOCN card)

• Network interface : RS-232 or RS-485 (half-duplex (2-wire) or full-duplex (4-wire))

• Data transfer rate : Up to 115.2 kBaud

• Distance between devices : According to the relevant standard

• Network topologies : Point-to-point for RS-232 links.

Point-to-point or linear (daisy-chained) for RS-485 networks.

• Protocols : Modbus RTU

• Function : Fieldbus Modbus RTU communications

• Connector : RS on IOCN card (see Connectors on page 10)

• RS-485 (fieldbus) isolation : 500 VDC

Communication interfaces – Ethernet

Number : 2

Primary Ethernet interface

• Network interface : 10/100BASE-TX – Ethernet / Fast Ethernet

• Data transfer rate : Up to 100 Mbps

• Distance between devices : Up to 100 m

• Protocols : Meggitt TCP/IP proprietary protocol for communication with the

VM600 MPSx software, Modbus TCP and/or PROFINET

• Function : VM600 rack configuration and communications using the

VM600 MPSx software, fieldbus Modbus TCP communications

and/or fieldbus PROFINET communications

• Connectors : NET on CPUM card or 1 on IOCN card (see Connectors on page 10)

Secondary Ethernet interface (requires IOCN card)

• Network interface : 10/100BASE-TX – Ethernet / Fast Ethernet

• Data transfer rate : Up to 10 Mbps

• Distance between devices : Up to 100 m

• Protocols : Modbus TCP

• Function : Fieldbus Modbus TCP communications

• Connector : 2 on IOCN card (see Connectors on page 10)

Serial communications module (CPUM PC/104 slot 2)

Note: The serial communications module is optional and is only fitted to the serial redundant version of the

CPUM card.

Module type : AIM104-COM4 or equivalent

Power supply to module (input) : 5 VDC, <220 mA

Isolation : >100 VDC

Communication interfaces – serial

Number : 2

Serial interfaces

• Network interface : RS-422 or RS-485 (half-duplex (2-wire) or full-duplex (4-wire))

• Data transfer rate : Up to 115.2 kBaud

• Distance between devices : According to the relevant standard

• Network topologies : Point-to-point for RS-232 links.

Point-to-point or linear (daisy-chained) for RS-422/ RS-485 networks.

• Protocols : Modbus RTU

• Function : Fieldbus Modbus RTU communications

• Connectors : A and B on IOCN card (see Connectors on page 10)

• RS-485 (fieldbus) isolation : 500 VDC

Notes

Jumpers on the CPUM and IOCN cards are used to configure the required operation of serial and Ethernet

interfaces and connectors. Refer to the VM600 machinery protection system (MPS) hardware manual for

further information.

System communications

Internal : VME bus interface (A24 / D16 master mode) for communication

with protection cards (MPC4 and AMC8) via VM600 rack

backplane

External : System communication interfaces (serial and Ethernet) for

communication with VM600 MPSx software running on an external

computer.

See Communication interfaces – serial on page 6 and

Communication interfaces – Ethernet on page 7.

External communication links/connections

• Connection to a computer/network : A serial communication interface (RS232 on CPUM card) can be

used for connections/communications between a CPUM/IOCN

card pair and a computer/network, using a standard serial cable.

See Communication interfaces – serial on page 6 and Connectors

on page 10.

An Ethernet communication interface (NET on CPUM card or 1 on

IOCN card) can be used for connections/communications

between a CPUM/IOCN card pair and a computer/network, using

standard cabling.

See Communication interfaces – Ethernet on page 7 and

Connectors on page 10.

• Connection to a fieldbus

(third-party system)

: A serial fieldbus communication interface (RS on IOCN card) can

be used for connections/communications between a CPUM/IOCN

card pair and serial-based fieldbuses (Modbus RTU).

See Communication interfaces – serial on page 6 and Connectors

on page 10.

An Ethernet fieldbus communication interface (NET on CPUM card

or 1 on IOCN card, or 2 on IOCN card) can be used for

connections/communications between a CPUM/IOCN

card pair and Ethernet-based fieldbuses (Modbus TCP).

See Communication interfaces – Ethernet on page 7 and

Connectors on page 10.

• VM600 MPSx software : Used for the configuration and operation of MPC4/IOC4T and

AMC8/IOC8T card pairs (using the CPUM/IOCN card pair as a

communications gateway)

• VibroSight® software : Used for the configuration of CPUM cards

Configuration

CPUM/IOCN card pair : Software configurable via Ethernet or serial, using a computer

running the VM600 MPSx and CPUM Configurator software.

Note: Serial (RS-232 / RS-422 / RS-485) line configuration and

Ethernet port to connector routing is determined by jumpers on the

CPUM and IOCN cards.

Time synchronisation

Time reference for CPUM : Network time protocol (NTP) server or

CPUM’s internal real-time clock (RTC) with battery backup

Protocol used between VM600 cards

and host computer

: Network time protocol (NTP)

Note: When VM600 system event and/or measurement event logging is used, the time and date must be

configured for the CPUM in order for the timestamps in the event log files to be correct.

Environmental

Operating

• Temperature : −20 to 65°C (−4 to 149°F)

• Humidity : 0 to 90% relative humidity, non-condensing

Storage

• Temperature : −25 to 80°C (−13 to 176°F)

• Humidity : 0 to 90% relative humidity, non-condensing

Approvals

Conformity : CE marking, European Union (EU) declaration of conformity.

EAC marking, Eurasian Customs Union (EACU) certificate/

declaration of conformity.

Electromagnetic compatibility : TR CU 020/2011

Electrical safety : TR CU 004/2011

Environmental management : RoHS compliant

Russian federal agency for technical

regulation and metrology (Rosstandart)

: Pattern approval certificate CH.C.28.004.A N° 60224,

dated 11.11.2015

Power supply (to CPUM/IOCN)

Source : VM600 rack power supply

Voltage : 5 VDC

Power consumption

• CPUM : <10 W

• IOCN : <2 W

Total power consumption

(CPUM/IOCN card pair)

: ≤12 W

Control inputs (buttons)

CPUM

ALARM RESET : Used to reset all latched alarms (and associated relays) for all

protection cards in the VM600 rack (MPC4/IOC4T and AMC8/

IOC8T)

OUT+ and OUT− : Used to select a measurement channel for the currently selected

protection card (slot)

SLOT+ and SLOT− : Used to select a slot (protection card) in the VM600 rack

Note: OUT and SLOT button combinations are also used to enable

or disable VM600 rack (CPUM) security, that is, limit the VM600 MPSx

software to “read only” operations.

Status indicators (LEDs)

CPUM

DIAG : Green LED used to indicate the status of the CPUM card: off,

normal operation and status of VM600 MPS rack (CPUM) security

OK : Green LED used to indicate the status of the OK system check

(sensor OK link check) for the currently selected measurement

channel

(Alert)

: Yellow LED used to indicate the status of the alarm monitoring (Alert

or Alert−) for the currently selected measurement channel

(Danger)

: Red LED used to indicate the status of the alarm monitoring

(Danger or Danger−) for the currently selected measurement

channel

Note: In addition to the LED indicators, a front-panel display is fitted to all versions of the CPUM card.

Connectors

CPUM

• NET : 8P8C (RJ45), female.

Used for the primary Ethernet connection.

• RS232 : DE-9 (9-pin D-sub), female

Used for the primary serial connection.

IOCN

• RS : 6P6C (RJ12/RJ25), female.

Used for the secondary serial connection.

• A : Two 6P6C (RJ12/RJ25), female.

Used for additional serial connections (requires the optional serial

communications module).

• B : Two 6P6C (RJ12/RJ25), female.

Used for additional serial connections (requires the optional serial

communications module).

• 1 : 8P8C (RJ45), female.

Can be used for the primary Ethernet connection (instead of the

CPUM connector (NET)).

• 2 : 8P8C (RJ45), female.

Used for the secondary Ethernet connection.

Physical

CPUM

• Height : 6U (262 mm, 10.3 in)

• Width : 40 mm (1.6 in)

• Depth : 187 mm (7.4 in)

• Weight : 0.40 kg (0.88 lb) approx.

IOCN

• Height : 6U (262 mm, 10.3 in)

• Width : 20 mm (0.8 in)

• Depth : 125 mm (4.9 in)

• Weight : 0.25 kg (0.55 lb) approx.

ORDERING INFORMATION

To order please specify

Type Designation Ordering number (PNR)

CPUM Different versions of the VM600 modular CPU card:

– Ethernet redundant

Modular CPU card with a CPU module that supports two

Ethernet interfaces and two serial interfaces.

This CPUM supports Ethernet interfaces on the front panel

(CPUM) and the rear panel (IOCN), a serial interface (RS-232)

on the front panel (CPUM) and a serial interface (isolated

RS-232/RS-485) on the rear panel (IOCN).

200-595-0Ss-33h

(601-003-000-VVV3610-1CC-CCC

when pre-configured See notes)

– Ethernet redundant varnished

Same as the (standard) Ethernet redundant version, with a

conformal coating for additional environmental protection.

200-595-0Ss-33hl

(601-003-000-VVV3V610-1CC-CCC

when pre-configured See notes)

– Serial redundant

Modular CPU card with a CPU module that supports two

Ethernet interfaces and two serial interfaces, and a serial

communications module that supports additional serial

interfaces.

This CPUM supports Ethernet interfaces on the front panel

(CPUM) and the rear panel (IOCN), a serial interface (RS-232)

on the front panel (CPUM) and a serial interface (isolated

RS-232/RS-485) on the rear panel (IOCN). It also supports two

additional serial interfaces

(RS-422/RS-485) on the rear panel (IOCN).

200-595-0Ss-53h

(601-003-000-VVV5610-1CC-CCC

when pre-configured See notes)

IOCN Different versions of the input/output card for the CPUM:

– Ethernet redundant 200-566-000-1Hh

– Ethernet redundant varnished

Same as the (standard) Ethernet redundant version, with a

conformal coating for additional environmental protection.

200-566-000-1HhL

Notes

Different versions of the CPUM card can be supplied pre-configured with different configurations, as denoted by the 9-digit code in

the ordering number (610-1CC-CCC).

“1CC-CCC” represents the different configurations that can be used by a finished product. For example, 610-100-000 corresponds

to the ‘standard’ configuration that is uploaded to a CPUM card (200-595-0Ss-HHh), if no other configuration is specified. For

information on other configurations. Contact your local Meggitt representative or Meggitt SA for further information.

“Ss” represents the firmware (embedded software) version and “Hh” the hardware version of a card. “S/H” increments for major

modifications that can affect product interchangeability and “s/h” increments for minor modifications that have no effect on

interchangeability.

“VVV” represents the different firmware (embedded software) versions and hardware versions that can be used by a

finished produc

Vibro-Meter ® VM600 CPUM and IOCN modular CPU card and input/output card

KEY FEATURES AND BENEFITS

• From the Vibro-Meter® product line

• VM600 CPUM/IOCN rack controller and

communications interface card pair with

support for Modbus RTU/TCP and PROFINET,

and a front-panel display

• “One-Shot” configuration management of

protection cards (MPC4 and AMC8) in a

VM600 rack using an Ethernet or RS-232 serial

connection to a computer running the

VM600 MPSx software

• Front-panel display for visualisation of

monitored outputs and alarm limits from

protection cards

• Front-panel alarm reset (AR) button

• VM600 MPS rack (CPUM) security

• Industry standard fieldbus communications

interfaces: Modbus RTU/TCP and PROFINET

• Two Ethernet connections and up to three

serial connections (RS-232 / RS-422 / RS-485)

can run simultaneously

• Communications redundancy with multiple

fieldbuses: Ethernet and/or serial

KEY BENEFITS AND FEATURES (continued)

• VM600 system event and measurement event

logs available via the VM600 MPSx software

• Supports live insertion and removal of

protection cards (“hot-swapping”) with

automatic configuration

• Ethernet (100 Mbps) communication

• Front-panel status indicators (LEDs)

• Compatible with all VM600 ABE04x

system racks

APPLICATIONS

• Rack controller for a VM600 system

• Communications gateway between VM600

and third-party systems, such as a DCS or PLC

• Enables sharing of measurement data from

VM600 monitoring cards in machinery

protection, condition monitoring and/or

combustion monitoring applications

Information contained in this document may be subject to export control regulations of the European Union, USA or other countries.

Each recipient of this document is responsible for ensuring that transfer or use of any information contained in this document

complies with all relevant export control regulations. ECN N/A.

DESCRIPTION

Introduction

The VM600 CPUM and IOCN modular CPU card

and input/output card is a rack controller and

communications interface card pair that acts as

a system controller and data communications

gateway for a VM600 rack-based machinery

protection system (MPS) and/or condition

monitoring system (CMS) from Meggitt’s

Vibro-Meter® product line.

Different versions of CPUx/IOCx card pair

Different versions of CPUx/IOCx rack controller

and communications interface card pair are

available, as follows:

• The CPUM/IOCN is the original version with a

front-panel display and support for

Modbus RTU/TCP and PROFINET

(PNR 200-595-VVV-VVV).

• The CPUR/IOCR is a version with rack controller

redundancy and support for Modbus RTU/TCP

(PNR 600-007-VVV-VVV).

• The CPUR2/IOCR2 is a version with

mathematical processing of fieldbus data and

support for Modbus TCP and PROFIBUS DP

(PNR 600-026-000-VVV).

VM600 rack-based monitoring systems

The Vibro-Meter® VM600 rack-based monitoring

system is part of Meggitt’s solution for the

protection and monitoring of rotating machinery

used in the power generation and oil & gas

industries. The VM600 is recommended when a

centralised monitoring system with a medium to

large number of measurement points (channels)

is required. It is typically used for the monitoring

and/or protection of larger machinery such as

gas, steam and hydro turbines, and generators,

smaller machines such as compressors, fans,

motors, pumps and propellers, as well as balanceof-plant (BOP) equipment.

A VM600 system consists of a 19″ rack, a rack

power supply and one or more monitoring card

pairs. Optionally, relay cards and rack controller

and communications interface cards can also be

included.

Two types of VM600 rack are available: a VM600

ABE04x system rack (6U) that can house up to 12

monitoring card pairs, and a VM600 ABE056

slimline rack (1U) that can house 1 monitoring

card pair. VM600 racks are typically mounted in

standard 19″ rack cabinets or enclosures installed

in an equipment room.

Different VM600 monitoring cards are available

for machinery protection, condition monitoring

and/or combustion monitoring applications. For

example, machinery protection cards such as the

MPC4/IOC4T machinery protection card pair and

AMC8/IOC8T analogue monitoring card pair,

and condition monitoring cards such as the

XMV16/XIO16T monitoring card pair for vibration

and XMC16/XIO16T monitoring card pair for

combustion.

The RLC16 relay card is an optional card used to

provide additional relays when the four relays per

MPC4/IOC4T or AMC8/IOC8T card pair are not

enough.

The CPUx/IOCx rack controller and

communications interface card pairs (CPUM/

IOCN, CPUR/IOCR or CPUR2/IOCR2) are optional

cards used to provide additional VM600 system

functionality such as configuration management,

“hot-swapping” with automatic reconfiguration,

front-panel display, CPUx/IOCx card pair

redundancy, fieldbus data processing, frontpanel alarm reset (AR) button, MPS rack (CPUx)

security, system event and measurement event

logging, fieldbus communications (Modbus,

PROFIBUS and/or PROFINET) and/or

communications redundancy.

Note: Different versions of CPUx/IOCx rack

controller and communications interface card

pair support different combinations of VM600

system functionality.

VM600 rack-based monitoring systems

complement the VibroSmart® module-based

distributed monitoring systems that are also

available from Meggitt’s Vibro-Meter® product

line.

DESCRIPTION (continued)

CPUM/IOCN card pair and VM600 racks

The CPUM/IOCN card pair is used with a VM600

ABE04x system rack and a CPUM card can be

used either alone or with an associated IOCN

card as a card pair, depending on the

application/system requirements.

The CPUM is a double-width card that occupies

two VM600 rack slots (card positions) and the

IOCN is a single-width card that occupies a single

VM600 slot. The CPUM is installed in the front of the

rack (slots 0 and 1) and an associated IOCN is

installed in the rear of the rack in the slot directly

behind the CPUM (slot 0). Each card connects

directly to the rack’s backplane using two

connectors.

Note: The CPUM/IOCN card pair is compatible

with all VM600 ABE04x system racks.

CPUM rack controller and communications

interface functionality

The modular, highly versatile design of the CPUM

means that all VM600 rack configuration, display

and communications interfacing can be

performed from a single card in a “networked”

rack. The CPUM card acts as a “rack controller”

and allows an Ethernet link to be established

between the rack and a computer running one

of the VM600 MPSx software packages (MPS1 or

MPS2).

The CPUM front panel features an LCD display

that shows information for the CPUM itself and for

protection cards in a VM600 rack. The SLOT and

OUT (output) keys on the CPUM front panel are

used to select which signal to display.

As a fieldbus communications interface for a

VM600 monitoring system, the CPUM

communicates with MPC4 and AMC8 cards via

the VME bus and with XMx16/XIO16T card pairs

via an Ethernet link in order to obtain

measurement data and then share this

information with third-party systems such as a DCS

or PLC.

LEDs on the CPUM front panel indicate the OK,

Alert (A) and Danger (D) status for the currently

selected signal. When Slot 0 is selected, the LEDs

indicate the overall status of the whole rack.

When the DIAG (diagnostic) LED shows green

continuously, the CPUM card is operating

normally, and when the DIAG LED blinks, the

CPUM card is operating normally but access to

the CPUM card is restricted due to VM600 MPS

rack (CPUM) security.

The ALARM RESET button on the front panel of the

CPUM card can be used to clear the alarms

latched by all protection cards (MPC4 and

AMC8) in the rack. This is a rack-wide equivalent

of resetting alarms individually for each card using

discrete signal interface alarm reset (AR) inputs or

VM600 MPSx software commands.

The CPUM card consists of a carrier board with

two PC/104 type slots that can accept different

PC/104 modules: a CPU module and an optional

serial communications module.

All CPUM cards are fitted with a CPU module that

supports two Ethernet connections and two serial

connections. That is, both the Ethernet redundant

and serial redundant versions of the card.

The primary Ethernet connection is used for

communication with the VM600 MPSx software

via a network and for Modbus TCP and/or

PROFINET communications. The secondary

Ethernet connection is used for Modbus TCP

communications. The primary serial connection is

used for communication with the VM600 MPSx

software via a direct connection. The secondary

serial connection is used for Modbus RTU

communications.

Optionally, a CPUM card can be fitted with a

serial communications module (in addition to the

CPU module) in order to support additional serial

connections. This is the serial redundant version of

the CPUM card.

The CPUM module’s primary Ethernet and serial

connections are available via connectors (NET

and RS232) on the front panel of the CPUM.

However, if the associated IOCN card is used, the

primary Ethernet connection can be routed to a

connector (1) on the front panel of the IOCN

(instead of the connector on the CPUM (NET)).

When the associated IOCN card is used, the

secondary Ethernet and serial connections are

available via connectors (2 and RS) on the front

panel of the IOCN.

IOCN card

The IOCN card acts as a signal and

communications interface for the CPUM card. It

DESCRIPTION (continued)

also protects all inputs against electromagnetic

interference (EMI) and signal surges to meet

electromagnetic compatibility (EMC) standards.

The IOCN card’s Ethernet connectors (1 and 2)

provide access to the primary and secondary

Ethernet connections, and the serial connector

(RS) provides access to the secondary serial

connection.

In addition, the IOCN card includes two pairs of

serial connectors (A and B) that provide access to

the additional serial connections (from the

optional serial communications module) that can

be used to configure multi-drop RS-485 networks

of VM600 racks.

Front-panel display

The CPUM front panel features an LCD display

that uses display pages to show important

information for the cards in a VM600 rack. For the

CPUM itself, card run time, rack system time, rack

(CPUM) security status, IP address/netmask and

version information are displayed. While for MPC4

and AMC8 cards, measurements, card type,

version and run time are displayed.

For MPC4 and AMC8 cards, the level of the

selected monitored output is displayed on a

bargraph and numerically, with the Alert and

Danger levels also indicated on the bar-graph.

Measurement identification (slot and output

number) is shown at the top of the display.

VM600 MPS rack (CPUM) security

The CPUM supports features that can be used to

limit the functionality of a VM600 rack’s

machinery protection system (MPS) that is

available via the system Ethernet connections of

a CPUM/IOCN card pair. Enabling VM600 MPS

rack (CPUM) security helps to reduce the

possibility of interference in the machinery

protection function of the rack itself and in the

machinery being monitored. Accordingly, CPUM

rack security makes it easier for operators to

comply with international security/critical

infrastructure regulations.

The security features consists of two specific levels

of protection integrated in the CPUM card: CPUM

access lock (a “hardware” security feature) and

VM600 MPSx password validation (a “software”

security feature). Refer to the VM600 machinery

protection system (MPS) hardware manual and

the VM600 MPSx software manuals for further

information.

VM600 event logging

The CPUM card automatically logs VM600 system

events and measurement events to non-volatile

memory in order to provide valuable information

on the operating history of a system. Up to 10000

of the most recent events are stored on the card

for download as user-readable event log files

using the VM600 MPSx software.

Software

The CPUM/IOCN is software configurable using

the CPUM Configurator software.

The VM600 MPSx software supports the

configuration and operation of MPC4/IOC4T

card pairs for machinery protection applications,

including the processing and presentation of

measurement data for analysis. VM600 MPSx is

also used to configure and manage CPUM/IOCN

card pairs.

Note: The VM600 MPSx software is from the

Vibro-Meter® product line.

Applications information

The VM600 CPUM/IOCN rack controller and

communications interface card pair is

recommended for applications using multiple

monitoring cards in a VM600 rack.

The rack controller functionality makes it easier to

work with a VM600 machinery monitoring system –

for installation, configuration, management and

general operation. The CPUM/IOCN can

manage the configuration of MPC4/IOC4T and

AMC8/IOC8T card pairs, including hot-swapping.

It can also manage the configuration of XMx16/

XIO16T card pairs, eliminating the need for a

VibroSight Server in certain applications.

The communications interface functionality

makes it easy to further process and share data

from the monitoring cards (MPC4, AMC8 and/or

XMC16) in a VM600 machinery protection,

condition monitoring and/or combustion

monitoring system with third-party systems such as

a DCS or PLC using industry standard fieldbuses.

For further information, contact your local

Meggitt representative.

Processing functions

Rack controller

• VM600 monitoring card configuration

management

: Acts as a rack controller that manages the configuration of MPC4/

IOC4T and AMC8/IOC8T card pairs, including support for

“hot-swapping” with automatic configuration.

Can also manage the configuration of XMx16/XIO16T card pairs,

for applications that do not require a VibroSight Server.

• Front-panel display : LCD display that uses display pages to show important information

for the cards in a VM600 rack:

• Card run time, rack system time, rack (CPUM) security status,

IP address/netmask and version info are displayed for the CPUM.

• Measurements (bargraph with alarm levels, and numerically),

card type, version, and run time are displayed for the MPC4 and

AMC8 cards in the rack.

• Fieldbus data processing

(mathematical processing)

: Further processing of system data (measurement data and status

information) before being shared by fieldbus.

The further processing supported includes basic mathematical

functions such as arithmetic and logical operations, data selection,

comparison, min/max and scaling functions, bit manipulation and

packing/unpacking functions, and many supporting functions.

There is also a data freeze detection function that can be used to

help detect if a data value has stopped being updated.

• Alarm reset : CPUM front-panel button used to manually clear the alarms (and

relays) latched by MPC4/IOC4T and AMC8/IOC8T card pairs in the

rack

• VM600 MPS rack (CPUM) security : Used to limit the functionality of a machinery protection system

(MPS) that is available via the system Ethernet connections of a

CPUM/IOCN card pair, helping to reduce the possibility of

interference in the machinery protection function of the rack itself

and/or in the machinery being monitored

• Event logging : VM600 system event and measurement event logging with up to

10000 of the most recent events stored on the CPUM (in nonvolatile memory).

Note: System event logs and measurement event logs are

downloaded from a CPUM using the VM600 MPSx software.

• Status indication : CPUM front-panel LEDs (front of VM600 rack) indicate the mode of

operation and status of the CPUM card

Communications interface

• VM600 rack (system)

communications

: Uses a VME communications link for communications with

MPC4/IOC4T and AMC8/IOC8T card pairs (via the VME bus on the

VM600 rack’s backplane).

Uses a system Ethernet connection for communications with a

computer running software such as VM600 MPSx.

• Fieldbus communications

(data gateway)

: Acts as a fieldbus server (slave) device that obtains data from

cards in the VM600 rack (that is, from MPC4/IOC4T and

AMC8/IOC8T card pairs) to share with fieldbus client (master)

devices such as a DCS or PLC:

• The CPUM can act as a Modbus server and use the fieldbus

interfaces to share data via Modbus RTU and/or Modbus TCP.

Note: The configuration of the fieldbus interfaces and the definition

of the data to be shared via fieldbus is defined by a Modbus

configuration file that is uploaded to the CPUM card using the

CPUM Configurator software.

Fieldbus interfaces

Number of channels : Multiple fieldbus interfaces (ports).

Ethernet and/or serial: Modbus and/or PROFINET.

Data transfer

• Modbus : Up to 131072 registers/words and 131072 coils/bits total.

That is, up to 2 × 65536 registers/words and 2 × 65536 coils/bits

(holding and discrete).

• PROFINET : Maximum slot size of 128 bytes.

Note: PROFINET is supported by later versions of the CPUM card

running firmware version 081 or later.

It was originally only supported by earlier versions of the CPUM card

running a special PROFINET version of firmware (version 801) that is

no longer supported.

Contact your local Meggitt representative or Meggitt SA for further

information.

CPU module (CPUM PC/104 slot 1)

Note: The CPU module is fitted to all versions of the CPUM card.

Module type : PFM-541I or equivalent

Processor type : AMD Geode™ LX800

Processor Speed : 500 MHz

Memory : 256 MB DRAM

Power supply to module (input) : 5 VDC, <1.8 A

Operating system : QNX

Communication interfaces – serial

Number : 2

Primary serial interface

• Network interface : RS-232

• Data transfer rate : Up to 115.2 kBaud

• Network topologies : Point-to-point

• Protocols : Meggitt TCP/IP proprietary protocol for communication with the

VM600 MPSx software

• Function : VM600 rack configuration and communications using the

VM600 MPSx software

• Connector : RS232 on CPUM card (see Connectors on page 10)

Secondary serial interface (requires IOCN card)

• Network interface : RS-232 or RS-485 (half-duplex (2-wire) or full-duplex (4-wire))

• Data transfer rate : Up to 115.2 kBaud

• Distance between devices : According to the relevant standard

• Network topologies : Point-to-point for RS-232 links.

Point-to-point or linear (daisy-chained) for RS-485 networks.

• Protocols : Modbus RTU

• Function : Fieldbus Modbus RTU communications

• Connector : RS on IOCN card (see Connectors on page 10)

• RS-485 (fieldbus) isolation : 500 VDC

SPECIFICATIONS (continued)

Communication interfaces – Ethernet

Number : 2

Primary Ethernet interface

• Network interface : 10/100BASE-TX – Ethernet / Fast Ethernet

• Data transfer rate : Up to 100 Mbps

• Distance between devices : Up to 100 m

• Protocols : Meggitt TCP/IP proprietary protocol for communication with the

VM600 MPSx software, Modbus TCP and/or PROFINET

• Function : VM600 rack configuration and communications using the

VM600 MPSx software, fieldbus Modbus TCP communications

and/or fieldbus PROFINET communications

• Connectors : NET on CPUM card or 1 on IOCN card (see Connectors on page 10)

Secondary Ethernet interface (requires IOCN card)

• Network interface : 10/100BASE-TX – Ethernet / Fast Ethernet

• Data transfer rate : Up to 10 Mbps

• Distance between devices : Up to 100 m

• Protocols : Modbus TCP

• Function : Fieldbus Modbus TCP communications

• Connector : 2 on IOCN card (see Connectors on page 10)

Serial communications module (CPUM PC/104 slot 2)

Note: The serial communications module is optional and is only fitted to the serial redundant version of the

CPUM card.

Module type : AIM104-COM4 or equivalent

Power supply to module (input) : 5 VDC, <220 mA

Isolation : >100 VDC

Communication interfaces – serial

Number : 2

Serial interfaces

• Network interface : RS-422 or RS-485 (half-duplex (2-wire) or full-duplex (4-wire))

• Data transfer rate : Up to 115.2 kBaud

• Distance between devices : According to the relevant standard

• Network topologies : Point-to-point for RS-232 links.

Point-to-point or linear (daisy-chained) for RS-422/ RS-485 networks.

• Protocols : Modbus RTU

• Function : Fieldbus Modbus RTU communications

• Connectors : A and B on IOCN card (see Connectors on page 10)

• RS-485 (fieldbus) isolation : 500 VDC

Notes

Jumpers on the CPUM and IOCN cards are used to configure the required operation of serial and Ethernet

interfaces and connectors. Refer to the VM600 machinery protection system (MPS) hardware manual for

further information.

System communications

Internal : VME bus interface (A24 / D16 master mode) for communication

with protection cards (MPC4 and AMC8) via VM600 rack

backplane

External : System communication interfaces (serial and Ethernet) for

communication with VM600 MPSx software running on an external

computer.

See Communication interfaces – serial on page 6 and

Communication interfaces – Ethernet on page 7.

External communication links/connections

• Connection to a computer/network : A serial communication interface (RS232 on CPUM card) can be

used for connections/communications between a CPUM/IOCN

card pair and a computer/network, using a standard serial cable.

See Communication interfaces – serial on page 6 and Connectors

on page 10.

An Ethernet communication interface (NET on CPUM card or 1 on

IOCN card) can be used for connections/communications

between a CPUM/IOCN card pair and a computer/network, using

standard cabling.

See Communication interfaces – Ethernet on page 7 and

Connectors on page 10.

• Connection to a fieldbus

(third-party system)

: A serial fieldbus communication interface (RS on IOCN card) can

be used for connections/communications between a CPUM/IOCN

card pair and serial-based fieldbuses (Modbus RTU).

See Communication interfaces – serial on page 6 and Connectors

on page 10.

An Ethernet fieldbus communication interface (NET on CPUM card

or 1 on IOCN card, or 2 on IOCN card) can be used for

connections/communications between a CPUM/IOCN

card pair and Ethernet-based fieldbuses (Modbus TCP).

See Communication interfaces – Ethernet on page 7 and

Connectors on page 10.

• VM600 MPSx software : Used for the configuration and operation of MPC4/IOC4T and

AMC8/IOC8T card pairs (using the CPUM/IOCN card pair as a

communications gateway)

• VibroSight® software : Used for the configuration of CPUM cards

Configuration

CPUM/IOCN card pair : Software configurable via Ethernet or serial, using a computer

running the VM600 MPSx and CPUM Configurator software.

Note: Serial (RS-232 / RS-422 / RS-485) line configuration and

Ethernet port to connector routing is determined by jumpers on the

CPUM and IOCN cards.

SPECIFICATIONS (continued)

Time synchronisation

Time reference for CPUM : Network time protocol (NTP) server or

CPUM’s internal real-time clock (RTC) with battery backup

Protocol used between VM600 cards

and host computer

: Network time protocol (NTP)

Note: When VM600 system event and/or measurement event logging is used, the time and date must be

configured for the CPUM in order for the timestamps in the event log files to be correct.

Environmental

Operating

• Temperature : −20 to 65°C (−4 to 149°F)

• Humidity : 0 to 90% relative humidity, non-condensing

Storage

• Temperature : −25 to 80°C (−13 to 176°F)

• Humidity : 0 to 90% relative humidity, non-condensing

Approvals

Conformity : CE marking, European Union (EU) declaration of conformity.

EAC marking, Eurasian Customs Union (EACU) certificate/

declaration of conformity.

Electromagnetic compatibility : TR CU 020/2011

Electrical safety : TR CU 004/2011

Environmental management : RoHS compliant

Russian federal agency for technical

regulation and metrology (Rosstandart)

: Pattern approval certificate CH.C.28.004.A N° 60224,

dated 11.11.2015

Power supply (to CPUM/IOCN)

Source : VM600 rack power supply

Voltage : 5 VDC

Power consumption

• CPUM : <10 W

• IOCN : <2 W

Total power consumption

(CPUM/IOCN card pair)

: ≤12 W

Control inputs (buttons)

CPUM

ALARM RESET : Used to reset all latched alarms (and associated relays) for all

protection cards in the VM600 rack (MPC4/IOC4T and AMC8/

IOC8T)

OUT+ and OUT− : Used to select a measurement channel for the currently selected

protection card (slot)

SLOT+ and SLOT− : Used to select a slot (protection card) in the VM600 rack

Note: OUT and SLOT button combinations are also used to enable

or disable VM600 rack (CPUM) security, that is, limit the VM600 MPSx

software to “read only” operations.

Status indicators (LEDs)

CPUM

DIAG : Green LED used to indicate the status of the CPUM card: off,

normal operation and status of VM600 MPS rack (CPUM) security

OK : Green LED used to indicate the status of the OK system check

(sensor OK link check) for the currently selected measurement

channel

(Alert)

: Yellow LED used to indicate the status of the alarm monitoring (Alert

or Alert−) for the currently selected measurement channel

(Danger)

: Red LED used to indicate the status of the alarm monitoring

(Danger or Danger−) for the currently selected measurement

channel

Note: In addition to the LED indicators, a front-panel display is fitted to all versions of the CPUM card.

Connectors

CPUM

• NET : 8P8C (RJ45), female.

Used for the primary Ethernet connection.

• RS232 : DE-9 (9-pin D-sub), female

Used for the primary serial connection.

IOCN

• RS : 6P6C (RJ12/RJ25), female.

Used for the secondary serial connection.

• A : Two 6P6C (RJ12/RJ25), female.

Used for additional serial connections (requires the optional serial

communications module).

• B : Two 6P6C (RJ12/RJ25), female.

Used for additional serial connections (requires the optional serial

communications module).

• 1 : 8P8C (RJ45), female.

Can be used for the primary Ethernet connection (instead of the

CPUM connector (NET)).

• 2 : 8P8C (RJ45), female.

Used for the secondary Ethernet connection.

Physical

CPUM

• Height : 6U (262 mm, 10.3 in)

• Width : 40 mm (1.6 in)

• Depth : 187 mm (7.4 in)

• Weight : 0.40 kg (0.88 lb) approx.

IOCN

• Height : 6U (262 mm, 10.3 in)

• Width : 20 mm (0.8 in)

• Depth : 125 mm (4.9 in)

• Weight : 0.25 kg (0.55 lb) approx.

To order please specify

Type Designation Ordering number (PNR)

CPUM Different versions of the VM600 modular CPU card:

– Ethernet redundant

Modular CPU card with a CPU module that supports two

Ethernet interfaces and two serial interfaces.

This CPUM supports Ethernet interfaces on the front panel

(CPUM) and the rear panel (IOCN), a serial interface (RS-232)

on the front panel (CPUM) and a serial interface (isolated

RS-232/RS-485) on the rear panel (IOCN).

200-595-0Ss-33h

(601-003-000-VVV3610-1CC-CCC

when pre-configured See notes)

– Ethernet redundant varnished

Same as the (standard) Ethernet redundant version, with a

conformal coating for additional environmental protection.

200-595-0Ss-33hl

(601-003-000-VVV3V610-1CC-CCC

when pre-configured See notes)

– Serial redundant

Modular CPU card with a CPU module that supports two

Ethernet interfaces and two serial interfaces, and a serial

communications module that supports additional serial

interfaces.

This CPUM supports Ethernet interfaces on the front panel

(CPUM) and the rear panel (IOCN), a serial interface (RS-232)

on the front panel (CPUM) and a serial interface (isolated

RS-232/RS-485) on the rear panel (IOCN). It also supports two

additional serial interfaces

(RS-422/RS-485) on the rear panel (IOCN).

200-595-0Ss-53h

(601-003-000-VVV5610-1CC-CCC

when pre-configured See notes)

IOCN Different versions of the input/output card for the CPUM:

– Ethernet redundant 200-566-000-1Hh

– Ethernet redundant varnished

Same as the (standard) Ethernet redundant version, with a

conformal coating for additional environmental protection.

200-566-000-1HhL

Notes

Different versions of the CPUM card can be supplied pre-configured with different configurations, as denoted by the 9-digit code in

the ordering number (610-1CC-CCC).

“1CC-CCC” represents the different configurations that can be used by a finished product. For example, 610-100-000 corresponds

to the ‘standard’ configuration that is uploaded to a CPUM card (200-595-0Ss-HHh), if no other configuration is specified. For

information on other configurations. Contact your local Meggitt representative or Meggitt SA for further information.

“Ss” represents the firmware (embedded software) version and “Hh” the hardware version of a card. “S/H” increments for major

modifications that can affect product interchangeability and “s/h” increments for minor modifications that have no effect on

interchangeability.

“VVV” represents the different firmware (embedded software) versions and hardware versions that can be used by a

finished product.

WATLOWCLS200 Communications Specification Includes CLS200, MLS300 and CAS200

Overview

This reference guide is designed to help applications software programmers interface with Watlow®

CLS200 and MLS300 controllers and CAS200 alarm scanners via serial communication.

The following chapters are included in this guide:

• Anafaze/AB Protocol—gives an overview and explanation of the Anafaze/Allen Bradley

communications protocol

• Modbus®-RTU Protocol—gives an overview and explanation of the Modbus®-RTU

communications protocol

• Data Table Summary—provides standard controller data table maps for the parameters (one for

each protocol)

• Parameters Description—describes each parameter

• Glossary—explanations of commonly used terms and acronyms

Chapter 1: Anafaze/AB

Protocol

This chapter explains the ANAFAZE/Allen Bradley protocol.

Anafaze/AB Protocol Basics

This protocol is used with a serial communications link (EIA/TIA-232 or EIA-TIA-485) configured as

follows:

• 2400 or 9600 baud

• 8 data bits

• One or 2 stop bits

• No parity

Protocol Syntax

The controllers use a half-duplex (master-slave) protocol to interface to high-level software. The host

software is considered the “master” and the controller is considered the “slave.” In other words, the

software can request information from the controller or download information to the controller. The

controller can only respond to communications transactions initiated by the host software. The controller

cannot initiate communications.

Control Codes

The controller and host software communicate by sending and receiving information in a “packet”

format. A packet consists of a sequence of bytes in a specific format; it can be as large as 256 bytes of

data. (For more information about packets, see the Packet Format section later in this chapter.)

The numbers in the packet are sent in binary format. However, our examples show bytes in hexadecimal

forma

Control code abbreviations in this manual

Transaction Sequence

Here are the four steps in a transaction between the host software and the controller. The following

example shows the transaction as an exchange of packets. The example also assumes that there are no

communication errors in the exchange.

1. The host software sends a packet that contains a read command or write command.

2. The controller sends a DLE ACK to the host software.

3. The host software receives a reply packet from the controller.

4. The host software sends a DLE ACK.

Transaction flow with no error handling

NOTE Due to the difference between the processing speeds of the controller and PC, it may be

necessary to delay the computer’s acknowledgement (ACK) in order for the controller to receive it.

A delay of 200ms should suffice.

The flowchart below shows one way for the host software to handle error checking. If you are writing

simple software, you don’t necessarily need to use error handling routines as complete as these

Transaction flow with error handling

Packet Format

Messages are transmitted in the form of packets. Command and reply packets specify the source and

destination addresses, whether to read or write, the block of data to read or write, etc.

A packet contains a sequence of binary bytes formatted this way:

Sending Control Codes

To send a control code, send a DLE before the control code to distinguish it from data.

Sending a DLE as Data

When you send a byte with 0x10, (a DLE), the controller and software interpret it as a command.

Therefore, to send a DLE as data, send another DLE immediately before it (DLE DLE).

Codes in a Packet

This section describes the sequence of bytes in a packet, in the order the host software or controller

sends them

DLE STX (byte) signals the beginning of a transmission. Every packet of information starts with the

control codes DLE STX.

DST (byte) the address of the destination device (usually a controller; the first CLS200 controller is at

0x08).

NOTE: When host software communicates with a CLS200 controller via the ANAFAZE or AB

protocol, it does not send the controller’s actual address. Since the protocol reserves device

addresses 0 to 7, the host software sends the value (controller address + 7), instead of the actual

device address.

SRC (byte) the device address of the packet’s source. The host software is usually designated address

0x00.

CMD (byte) indicates the command that the host software sends to the controller. The software sends a

read (0x01) or write (0x08). When the controller replies, it returns the read or write command with the

7th bit set—in other words, it sends 0x41 or 0x48.

STS (byte) indicates the controller’s general status and error flags to the host software. The controller

ignores the status byte in the host software’s command packet. The table below lists status byte values

and definitions.

An “n” in the status bytes below indicates that the associated nibble may contain additional information.

In most cases, the status byte is composed of two independent nibbles. Each nibble is independent so

that two codes can return at once. For example, status code F1 indicates that data has changed (Fn) and

the controller is being updated through the front panel (0x1).

TNSL least significant byte of the transaction number. This is the first half of a “message stamp.” The

controller sends back the TNSL and TNSH exactly as it received them, so host software can use the

TNSL and TNSH bytes to keep track of message packets.

TNSH most significant byte of the transaction number. This is the second half of the “message stamp.

ADDL the low byte of the beginning data table address of the block of data to read or write.

ADDH the high byte of the beginning data table address of the block of data to read or write.

DATA the new values to be set with a write command, or the requested data in a response to a read

command.

DLE ETX ends every packet of information. Signals the end of a transmission.

BCC or CRC one or two-byte error check at the end of the packet. There are two error check methods:

Block Check Character (BCC), which requires 1 byte, and Cyclic Redundancy Check (CRC), which

requires 2 bytes.

Error Checking

The default error check method, BCC is easier to implement than CRC, and is acceptable for most

applications.

Select one error check method and configure both software and controller for that method, or they will

be unable to communicate.

The error check methods work this way:

Block Check Character (BCC)

BCC checks the accuracy of each message packet transmission. It provides a medium level of security.

The BCC is the 2’s complement of the 8-bit sum (modulo-256 arithmetic sum) of the data bytes between

the DLE STX and the DLE ETX. (1’s complement +1)

• BCC does not detect transposed bytes in a packet.

• BCC cannot detect inserted or deleted 0 values in a packet.

• If you have sent 0x10 as data (by sending DLE 0x10) only one of the DLE data bytes is included in

the BCC’s sum (the DLE = 0x10 also).

For instance, the block read example shown in the examples section, adds 0x08 00 01 00 00 80 02 10.

Note that the 0x10 representing DLE has been left out of the calculation. The sum should come to 0x9B.

1001 1011 = 0x9B

0110 0100 = 1’s complement

______ +1 = 2’s complement

0110 0101 = 0x65

Cyclic Redundancy Check (CRC)

CRC is a more secure error check method than BCC. It provides a very high level of data security. It can

detect:

• All single-bit and double-bit errors.

• All errors of odd numbers of bits.

• All burst errors of 16 bits or less.

• 99.997% of 17-bit error bursts.

• 99.998% of 18-bit and larger error bursts.

The CRC is calculated using the value of the data bytes and the ETX byte. At the start of each message

packet, the transmitter must clear a 16-bit CRC register.

When a byte is transmitted, it is exclusive-ORed with the right 8 bits of the CRC register and the result

is transferred to the right 8 bits of the CRC register. The CRC register is then shifted right 8 times by

inserting 0’s on the left.

Each time a 1 is shifted out on the right, the CRC register is Exclusive-ORed with the constant value

0xA001. After the ETX value is transmitted, the CRC value is sent, least significant byte (LSB) first.

Structured English procedure from AB Manual

data_byte = all application layer data, ETX

CLEAR CRC_REGISTER

FOR each data_byte

GET data_byte

XOR (data_byte, right eight bits of CRC_REGISTER)

PLACE RESULT in right eight bits of CRC_REGISTER

DO 8 times

Shift bit right, shift in 0 at left

IF bit shifted =1

XOR (CONSTANT, CRC_REGISTER)

PLACE RESULT in CRC_REGISTER

END IF

END DO

END FOR

TRANSMIT CRC_REGISTER as 2-byte CRC field

Examples

The host software sends two kinds of commands: block reads and block writes. This section shows

examples of both commands.

Note: If you read data from a loop set to SKIP, the controller will send an empty packet for that loop.

This section does not show how to calculate the error check value included with every packet. For help

calculating the error check value, see the section on BCC or CRC.

Block Read

This example shows the block read command the host software sends, the controller’s responses, and the

software’s acknowledgment.

Situation: Read process variables for loops 1 to 8.

• 8 process variables 2 bytes each = 16 bytes from data table address 0x0280.

Block Write

This section describes the block write command.

This example shows the block write command the master sends, the controller’s responses, and the

master’s acknowledgment:

Situation: Write setpoint of 100 to loop 6.

• 1 setpoint 2 bytes per setpoint = 2 bytes to address 0x01CA (0x01C0 + xA, a 10-byte offset).

• Character values are represented in hexadecimal.

• The sender is device address 0.

• The destination is device address 8 (controller address 1).

• The software sends transaction number 00.

Message Data

Some messages contain data. What the data is and how much depends on the command used and the

purpose of the message.

Data for a Read Command

For a block read command, the data block consists of one byte that indicates the number of bytes to read

(up to 244 bytes of data). The controller sends back a packet with a data block that contains the

requested bytes.

Data for a Write Command

For a block write command, the block contains the bytes to write (up to 242 bytes of data). The

controller sends back a message packet without data.

Two-Byte Data Types

For two-byte data types, like process variable and setpoint, the controller or host software sends the data

in two-byte pairs with the least significant byte first.

Figuring Block Size

To read parameter values, you must know how many bytes to request. Parameter values are stored

contiguously such that the setpoints for all the loops are stored together and in loop number order. For

example, to read the deviation alarm deadband value for loops one to five, you would read five bytes

starting at 0x05A0. Some parameters, such as setpoint, require two bytes of memory to store. So, for

example, if you want to read the setpoint for four loops, you must read eight bytes.

Calculate total block size in bytes for most loop parameters this way (do not forget the pulse loop):

(Data Size) * (Number of Loops)

Some parameters have values for both heat and cool. Calculate block size for such a parameter this way:

2 * (Data Size) * (Number of Loops)

One exception is the units for each loop. Calculate the data size for the units this way:

3 * (Number of Loops)

Parameters that are not loop parameters (like system status, digital inputs, or digital outputs) have

specific data sizes. These data sizes are listed in the data table in the next section.

Anafaze/AB Data Table Summary

Each address holds one byte of data. Each parameter value requires one or two addresses to store

depending on the type of data. The tablebelow indicates the number of bytes for each data type. The

data type for each parameter is indicated in the tables on the following pages.

Because each loop is individually configurable, the number of instances of many parameters depends on

the number of loops in the controller. Therefore, the number of bytes for these parameters is listed in the

tables on the following pages in terms of the number of loops in the controller.

The storage requirements for some parameters depend on the number of digital inputs or digital outputs

in the controller (MAX_DIGIN_BYTES and MAX_DIGOUT_BYTES). The storage of ramp-soak

profile parameters depend on the number of profiles (MAX_RSP), the number of segments per profile

(MAX_SEG), the number of triggers per segment (MAX_TRIG) and the number of events per segment

(MAX_EVENT).

The table below shows the values for each of these factors. Use them to calculate the number of bytes

for each parameter.

Ordering of Heat and Cool Channel Parameters

For parameters that have both heat and cool settings the heat values are stored in the first registers and

the cool values are stored in the registers starting at the listed address plus MAX_CH.

Note: Data table parameters 46 to 60 and 100 are ramp-soak parameters. They are only used in

controllers with the ramp-soak option. Parameters 81 to 95 are enhanced features and only available in

controllers with the enhanced features option.

Ordering of Ramp-Soak Profile Parameters

Ramp-soak profile parameters are ordered first by profile, then by segment where applicable. So, for

example, the first eight bytes of the Ready Events parameter are the ready segment event states for the

first profile (profile A) and the next eight bytes are for profile B and so on. In the case of the segment

triggers, the first byte contains the first trigger setting for the first segment of profile A, the second byte

contains the settings for the second trigger for the first segment of profile A, the third byte contains the

settings for the first trigger for the second segment of profile A and so on.

August 25, 2025 BY Huang, Jason

WATLOWCAS200 User’s GuideSystem Overview

This manual describes how to install, setup, and operate a

CAS200. Included are six chapters and a glossary of terms.

Each chapter covers a different aspect of the alarm scanner

and may apply to different users. The following describes

the chapters and their purpose.

• Chapter 1: System Overview provides a component

list and summary of features for the CAS200 series

alarm scanners.

• Chapter 2: Installation provides detailed

instructions on installing the CAS200 and its

peripherals.

• Chapter 3: Using the CAS200 provides an overview

of operator displays used for system monitoring and

job selection.

• Chapter 4: Setup provides detailed descriptions of all

menus and parameters for scanner setup.

• Chapter 5: Troubleshooting and

Reconfiguration provides some basic guidelines for

solving operational problems and provides procedures

for changing some of the hardware options (e.g.

installing special input resistors and changing EIA/

TIA-232 to EIA/TIA-485).

• Chapter 6: Linear Scaling Examples provides

three examples where linear scaling is used.

• Chapter 7: Specifications lists detailed

specifications of the scanner and optional components.

Product Features

The CAS200 is a modular monitoring system with 16

analog inputs. It can function as a stand-alone system; the

CAS200 1/8 DIN front panel has a Vacuum Fluorescent

Display (VFD) and touch keypad for local display and local

parameter entry. You can also use it as the key element in

a computer supervised data acquisition system; the

CAS200 can be locally or remotely controlled via an EIA/

TIA-232 or EIA/TIA-485 serial communications interface.

Features include:

Direct Connection of Mixed Thermocouple Sensors:

Connect most thermocouples to the scanner with no

hardware modifications. Thermocouple inputs feature

reference junction compensation, linearization, process

variable offset calibration to correct for sensor

inaccuracies, detection of broken, shorted or reversed

thermocouples, and a choice of Fahrenheit or Celsius

display.

Automatic Scaling for Linear Analog Inputs: The

CAS200 series automatically scales linear inputs used with

industrial process sensors. Enter two points and all input

values are automatically scaled in your units. Scaling

resistors must be installed.

Flexible Alarm Outputs: Independently set high/low

process alarms and a high/low deviation band alarm for

each channel. Alarms can activate a digital output by

themselves, or they can be grouped with other alarms to

activate an output.

Alarm Outputs: You can set high/low deviation and high/

low process alarm setpoints to operate digital outputs as

latched or unlatched functions.

Global Alarm Output: When any alarm is triggered, the

global alarm output is also triggered, and it stays on until

you acknowledge it.

CPU Watchdog: The CAS200 series CPU watchdog timer

output notifies you of system failure. Use it to hold a relay

closed while the system is running, so you are notified if the

microprocessor shuts down.

Front Panel or Computer Operation: Set up and run

the scanner from the front panel or from a local or remote

computer. Watlow Anafaze offers WatView, a Windows®

compatible Human Machine Interface (HMI) software

package that includes data logging and graphing features

in addition to process monitoring and parameter setup

screens.

Multiple Job Storage: Store up to eight jobs in protected

memory, and access them locally by entering a single job

number or remotely via digital inputs. Each job is a set of

alarm conditions.

Pulse Counter Input: Use the pulse counter input for

precise monitoring of motor or belt speed.

System Diagram

The illustration below shows how the parts of the CAS200

are connected. When unpacking your system, use the

diagram and parts list below to ensure all parts have been

shipped. Please don’t hesitate to call Watlow Anafaze if you

have problems with your shipment, or if any CAS200

components are missing or damaged.

Figure 1.1 System Components

• CAS200 Scanner

• Mounting Kit

• TB50 Terminal Board

• 50-Pin SCSI Cable

• DC Power Supply

Mounting Scanner Components

Install the scanner in a location free from excessive heat

(>50°C), dust, and unauthorized handling.

Electromagnetic and radio frequency interference can

induce noise on sensor wiring. Select locations for the CAS

200 and TB50 such that wiring can be routed clear of

sources of interference such as high voltage wires, power

switching devices and motors.

∫

WARNING! To reduce the risk of fire or electric shock, install

CAS200 in a controlled environment, relatively

free of contaminants.

Safety

Watlow Anafaze has made efforts to ensure the reliability

and safety of the CAS200 and to recommend safe uses in

systems applications. Note that in any application failures

can occur.

Good engineering practices, electrical codes, and insurance

regulations require that you use independent external

safety devices to prevent potentially dangerous or unsafe

conditions. Assume that the CAS200 can fail or that other

unexpected conditions can occur.

Install high or low temperature protection in systems

where an overtemperature or undertemperature fault

condition could present a fire hazard or other hazard.

Failure to install temperature control protection where a

potential hazard exists could result in damage to

equipment and property, and injury to personnel.

For additional process safety, program a computer or other

host device to automatically reload your desired operating

parameters after a power failure. However, this safety

feature does not eliminate the need for other external,

independent safety devices in dangerous conditions.

The CAS200 should never be used as a safety

shutdown device. It should only be used with

other approved independent safety shutdown

devices.

Contact Watlow Anafaze immediately if you have any

questions about system safety or system operation.

This chapter describes how to install the CAS200 series

scanner and its peripherals. Installation of the scanner

involves the following procedures:

• Determining the best location for the scanner

• Mounting the scanner and TB50

• Power Connection

• Input Wiring

• Communications Wiring (EIA/TIA-232 or EIA/TIA485)

• Output Wiring

Typical Installation

The illustrations below show typical installations of the

scanner with the TB50 terminal block. Observe the

illustration below to determine potential space

requirements.

We recommend that you read this entire chapter first

before beginning the installation procedure. This will help

you to carefully plan and assess the installation.

Figure 2.1 System Components

Safety

∫

WARNING! Ensure that power has been shut off to your entire

process before you begin installation of the

scanner

Watlow Anafaze has made every effort to ensure the

reliability and safety of this product. In addition, we have

provided recommendations that will allow you to safely

install and maintain this scanner.

∫

WARNING! In any application, failures can occur. These

failures can result in full control output (100%

power), or the occurrence of other output failures

which can cause damage to the scanner, or to the

equipment or process connected to the scanner.

Therefore, always follow good engineering

practices, electrical codes, and insurance

regulations when installing and operating this

equipment.

External Safety Devices

External safety devices should be used to prevent

potentially dangerous and unsafe conditions upon

equipment failure. Always assume that this device can fail

with outputs full-On, or full-Off, by the occurrence of an

unexpected external condition.

∫

WARNING! Always install high or low temperature protection

in installations where an overtemperature or

undertemperature fault will present a potential

hazard. Failure to install external protection

devices where hazards exist can result in damage

to equipment, property, or human life.

Mounting

We recommend you mount the scanner in a panel not more

than 0.2 inches thick.

∫

WARNING! To reduce the risk of fire or electric shock, install

the CAS200 in a controlled environment,

relatively free of contaminants.

Location

Install the scanner in a location free from excessive (>50°C)

heat, dust, and unauthorized handling.

Ensure there is enough clearance for mounting brackets,

terminal blocks, and cable and wire connections; the

scanner extends 7.0 in. behind the panel face and the screw

brackets extend 0.5 in. above and below it. Allow an

additional 1 to 3 inches for the SCSI cable.

Figure 2.2 Clearance Recommendations

Other Tools:

You will also need these tools:

• Phillips head screwdriver

• Flathead screwdriver for wiring

• Multimeter

Mounting the Scanner

Mount the scanner before you mount the TB50 or do any

wiring. The scanner’s placement affects placement and

wiring considerations for the other components of your

system.

You receive one of two types of mounting brackets with

your scanner, the mini-bracket or the collar bracket. Refer

to the corresponding sections below for instructions.

Steps Using the Mini-Bracket

1. Cut a hole in the panel to the dimensions shown in the

illustration below. To do this, use a punch, nibbler, or

jigsaw, and file the edges of the hole.

2. Insert the scanner into the hole through the front of

the panel.

3. Screw the top and bottom clips in place: insert the

clip’s lip into the cutout in the scanner’s metal housing

just behind the front panel. Tighten the screws.

4. If you expect much panel vibration, use a rear support

for the scanner and its interconnecting cables.

Figure 2.3 Mounting with the Mini-Bracket

Steps Using the Collar Bracket

Installing and mounting requires access to the back of the

panel.

NOTE! Removing the scanner chassis from its case

makes mounting easier.

1. Make a panel cutout. Refer to Figure 2.3 on page 11 for

dimensions of the cutout.

2. Slide the scanner into the panel cutout.

3. Slide the mounting collar over the back of the scanner,

making sure the mounting screw indentations face

toward the back of the scanner.

4. Loosen the mounting bracket screws enough to allow

for the mounting collar and panel thickness. Place

each mounting bracket into the mounting slots (head

of the screw facing the back of the scanner). Push each

bracket backward then to the side to secure it to the

scanner case.

5. Make sure the case is seated properly. Tighten the

installation screws firmly against the mounting collar

to secure the unit. Ensure that the end of the mounting screws fit into the indentations on the mounting

collar.

Figure 2.4 Mounting with the Collar Bracket

Mounting the TB50

There are two ways you can mount the TB50, by using the

pre-installed DIN rail mounting brackets provided or by

using the plastic standoffs. Follow the procedures for each

to mount the board.

August 25, 2025 BY Huang, Jason

CLS200 and MLS300 Cascade Control Setup and Tuning of CascadeFunctions

This paper describes the use of cascade control utilized for processes with long lag times between a change in the

control output level and a change in the process variable such as temperature. A lag time period of 10 to 30 minutes

or longer would be suitable conditions for considering cascade control. A commonly used process that is described

as needing cascade control is the water tank example. Another common process that uses cascade control is

aluminum melt furnaces.

It is not the type of process; rather the qualifying condition is the long lag time of a slow process that is always out

of control. The PV will be lagging so far behind the change in the output so that no amount of PID tuning will

correct the condition. The water tank example is using the input (cold) water temperature and looking at the outlet

(hot) water temperature that is the controlling point. The outlet temperature may always lag behind the heating of the

inlet water thus providing a variance of the outlet water temperature that is out of tolerance no matter the PID

settings.

The aluminum melt furnace has a problem in the melting of cold aluminum bars as the bars are introduced into the

melt furnace. The temperature of the heating zone will rise so high due to a “cooler” condition of the melt pot and to

the long lag time that it will overheat the melt furnace. Cycling will be very severe and the melt pot will be out of

control.

The use of two TC or other types of temperature sensors at two different locations can provide for control of long

lag time response process. By placing one sensor to measure the outlet of the process temperature and another one to

measure the process product inlet temperature, we can now measure the process for cascade control.

The outlet sensor as it measures the process product outlet temperature will provide for the desired product

temperature. This is known as the temperature Setpoint Control and has other labels as well such as Outer Loop.

This loop will provide the SP level for the temperature Heat Control zone also known as the Inner Loop.

The inlet sensor will measure the process product inlet temperature and using the SP level from the Setpoint Control

of the outlet sensor provide the heat control required for controlling the inlet temperature to meet the desired

temperature for the outlet temperature. It does this by using the control output level of the SP Control Loop to set the

SP level of the Control Loop.

As the outlet temperature decreases it will increase the SP level for control of the inlet temperature control zone. As

the outlet temperature increases it will decrease the SP level for control of the inlet temperature control zone. In

providing this cascade of control it overcomes the long lag time of the process. By looking at the difference between

the two sensors and making corrections as to the heat control level, the output level can be maintained at a closer

level of control.

CLS200 and MLS300 Cascade Control Terms

Nominal heat only control cascade has two parameters for adjustments. Dual heat and cool control would have four

parameters.

The Control Loop Setpoint (Inner Loop) for heat or cool outputs has a parameter for setting the desired SP value

when the SP Control Loop (Outer Loop) output level is at 0%. It also has a parameter for setting the desired SP

value when the SP Control output level is at 100%. Full PID control modes of the Control Loop will be used for

controlling the control output level.

Watlow Winona OH 07/28/06

1241 Bundy Blvd

Winona, MN 55987

Telephone (507) 494-5656

CLS200 and MLS300 Cascade Control

Setup and Tuning of Cascade Functions

The Setpoint Loop will use the loop’s SP as set by the operator for the desired temperature of the product or process.

The Setpoint Loop PID control modes will only use P and I control modes.

There is a possibly of six parameters that will need to be set for using cascade control when using the CLS200 or

MLS300 Dual Control Outputs. There are five when only using the Heating Control Output.

Follow User Guide instructions for changing parameters from the front panel keys.

First, the assignment as to which loop will be the temperature SP control loop (Primary Loop) and which loop will

be the cascade temperature Control Loop (Secondary Loop).

In the front panel display, select the Cascade Menu while in the loop number that the inlet sensor is connected to,

which is the heat control loop or Secondary Loop. For instance if Loop 2 is the heat control loop with an output to

the heat control device, the display should show Loop 2 before going into the Cascade Menu.

While in the Cascade Menu and using the keys select the PRIM. Loop or the SP Control Loop. Select any number,

but number 2. The number selected should be the output sensor loop. For instance if the outlet sensor is connected to

Loop 1, select Loop 1.

Second, the Base SP, Min SP, Max SP, and Heat Span, and Cool Span parameters need to be set. All parameters are

in the engineering units of the Control Loop or Secondary Loop.

If the process is controlling a process with a SP at 140°F and at -22°F while not wanting any control output at

ambient, which is consider to be 75°F, the following will apply.

BASE SP = 75, this is the base value at which all other values will be referenced from. This value must be set

whenever using heat, cool, or heat and cooling control outputs.

Min SP = -35, this is the value at which the lower SP value cannot exceed and must be greater than the cooling SP

of -30. This value can be set to the input range lowest value, if desired so that it would not need to be included in

any future resetting of cascade parameters.

Max SP = 145, this is the value at which the higher SP value cannot exceed and must be greater than the heating SP

of 140. This value can be set to the input range highest value, if desired so that it would not need to be included in

any future resetting of cascade parameters.

Heat Span = 65, this is the value which is the span between the Base SP and the desired heat SP. i.e. 140 – 75 = 65.

This is the value that must be set if using heat only or heat and cooling outputs as well as the Base SP.

Cool Span = 105, this is the value which is the span between the Base SP and the desired cool SP i.e. -75 + -30 =

105. This value must be set when using heat and cooling or cooling only outputs as well as the Base SP.

Heat only example: Low SP = 1200 and High SP =1600.

Base SP = 1200 and Heat Span = 400.

Cool only example: High SP = 50 and Low SP = 30.

Base SP = 50 and Cool Span = 20

Watlow Winona OH 07/28/06

1241 Bundy Blvd

Winona, MN 55987

Telephone (507) 494-5656

CLS200 and MLS300 Cascade Control

Setup and Tuning of Cascade Functions

Tuning Cascade Loops

The proper procedure for tuning cascade control loops is to first tune the secondary (inner) heat or cool control loop

using all three of the PID modes. This loop must first be tuned to good PID control parameters before doing any

tuning of the SP temperature control loop. Do not try tuning both loops at the same time unless you are an expert in

tuning PID loops and have experience with cascade control systems.

If cooling is in use and there is a proportional component to the cooling control such as using a TP output with a

solenoid valve, then the PID modes can be tune as well.

The use of autotuning or adaptive tuning can be used to achieve the PID control parameters. If these tuning

functions are not available then use manual PID tuning methods. After a satisfactory control is achieved with the

heat control loop, take note of the P and I values.

To tune the primary (outer) SP control loop, first check the actual range of the SP of the secondary loop by placing

the SP loop control into manual mode. With a heat output of 0%, the SP of the heat control loop should be at the low

SP value as set in the cascade menu. Change the output to 100%, the SP of the heat control loop should be at the

high SP value as set in the cascade menu. If using cooling control do the same thing with the heat output at 0% and

then changing the cooling output to achieve the same values as set in the cascade menu.

Use the values as noted in the PB mode and TI or RM of the Integral/Reset mode of the heat control loop and place

them in the PID parameters of the heat control output. If PID values are obtained for the cooling, use them for the

cooling PID parameters. DO NOT USE THE DERIVATIVE MODE. IT MUST BE TURNED OFF.

Place the control mode of the SP loop into Auto control mode. The SP loop control output should start changing

which in turn will be changing the SP of the secondary or heat control loop. Allow the process to settle down. If

there is any unwanted cycling of the temperature, use and change the PID parameters of the SP control loop for

changing any unwanted control deviations from SP. Do not use the heat control loop for making any changing to the

PID parameters.

A slow process will take time to see how the tuning is doing so don’t be in a hurry. A space of 20 to 30 minutes is

not too long in most cases.

If you are not knowledgeable or trained and have experience with PID and tuning be sure to see the instructions on

PID and PID tuning before attempting to tune cascade loops.

Watlow TRU-TUNE+ can do the tuning for you. First, perform an auto tune of the heat control loop by placing the

control mode into Tune. After the adaptive mode has been active for a while such as 1 or 2 hours, use the P and I

values as obtained in the adaptive mode for the P and I values of the SP loop. Place the SP loop directly into

Adaptive Mode for final tuning of the SP PID values.

TRU-TUNE+ is not available in the CLS200 or MLS300 Series controllers, but is available in the CPC400. Also

cascade is standard firmware in the CPC400 as well. Order option “EF” in the CLS200 and MLS300 to use cascade

control.

Watlow Winona OH 07/28/06

1241 Bundy Blvd

Winona, MN 55987

Telephone (507) 494-5656

August 25, 2025 BY Huang, Jason

WATLOWCLS200, MLS300, and CAS200 Communications Specification

This reference guide is designed to help applications software

programmers with the following tasks:

• Interface to Watlow Anafaze MLS300, CLS200, MLS and CLS controllers, and the CAS200 and CAS scanners via serial communications.

• Modify the communications Anafaze protocol driver in the Watlow

Anafaze Communications Driver Kit. (If you have the communications driver kit, you don’t need to read this manual unless you want

to modify the communications driver.)

In This Manual

The following sections are included in this guide:

Chapter 1: Anafaze/AB Protocol. Gives an overview and explanation

of the Anafaze/Allen Bradley communications protocol.

Chapter 2: Modbus-RTU Protocol. Gives an overview and

explanation of the Modbus-RTU communications protocol

Chapters 1 and 2: Data Table Summary. Provides standard controller

data table maps for the parameters (one for each protocol).

Chapter 3: Parameters Description. Describes each parameter.

Appendix A: Communications driver.

Glossary: Explanation of commonly used terms and acronyms.

NOTE

This reference guide is not a tutorial. It does not explain

how to use the controller; it is not a programming reference; it also does not explain PID control, alarms, linear

scaling, or other topics that are explained in detail in the

controller manuals. If you need additional information

about a topic covered in this reference guide, consult the

documentation included with your controller.

Chapter 1: ANAFAZE/AB Protocol

This section explains the ANAFAZE/Allen Bradley protocol used in

Watlow Anafaze MLS, CLS, and CAS devices. These controllers

operate on serial communications links (EIA/TIA-232 or EIA-TIA-485)

at either 2400 or 9600 baud. They use 8 data bits, one or 2 stop bits, and

no parity.

Protocol Syntax

The controllers use a half-duplex (master-slave) protocol to interface to

high-level software. The host software is considered the “master” and

the controller is considered the “slave.” In other words, the software can

request information from the controller or download information to the

controller. The controller can only respond to communications

transactions initiated by the host software. The controller cannot initiate

communications.

The controller and host software communicate by sending and receiving

information in a “packet” format. A packet consists of a sequence of

bytes in a specific format; it can be as large as 256 bytes of data. (For

more information about packets, see the Packet Format section later in

this chapter.)

The numbers in the packet are sent in binary format. However, our

examples show bytes in hexadecimal format.

Control Codes

Watlow Anafaze abbreviates control codes this way

Chapter 1: ANAFAZE/AB Protocol

Transaction Sequence

Here are the four steps in a transaction between the host software and

the controller. The following example shows the transaction as an

exchange of packets. The example also assumes that there are no

communication errors in the exchange.

(1) The host software sends a packet that contains a read command or

write command.

(2) The controller sends a DLE ACK to the host software.

(3) The host software receives a reply packet from the controller.

(4) The host software sends a DLE ACK.

The following flowchart shows a transaction with no error handling.

NOTE

Due to the difference between the processing speeds of the

controller and PCs, it may be necessary to delay the computer’s acknowledgement (ACK) in order for the controller

to receive it. A delay of 200 ms should suffice

Packet Format

Messages are transmitted in the form of packets. Command and reply

packets specify the source and destination addresses, whether to read or

write, the block of data to read or write, etc.

A packet contains a sequence of binary bytes formatted this way:

Sending Control Codes

To send a control code, send a DLE before the control code to

distinguish it from data.

Sending a DLE as Data

When you send a byte with an x10, (a DLE), the controller and software

interpret it as a command. Therefore, to send a DLE as data, send

another DLE immediately before it (DLE DLE).

Codes in a Packet

This section describes the sequence of bytes in a packet, in the order the

host software or controller sends them.

DLE STX

• The DLE STX byte signals the beginning of a transmission. Every

packet of information starts with the control codes DLE STX.

DST

• The DST byte is the address of the destination device (usually a controller; the first Watlow Anafaze controller is at x08).

NOTE

When host software communicates with an MLS, a CLS, or

a CAS in ANAFAZE or AB protocol, it does not send the

controller’s actual address. Since the protocol reserves

device addresses 0 to 7, the host software sends the value

(controller address + 7), instead of the actual device

address.

SRC

• The SRC byte is the device address of the packet’s source. The host

software is usually designated address x00.

DLE STX DLE ETX BCC/CRC

DST SRC CMD STS TNSL TNSH ADDL ADDH DAT

CMD

• The CMD byte indicates the command that the host software sends

to the controller. The software sends a read (x01) or write (x08).

When the controller replies, it returns the read or write command

with the 7th bit set—in other words, it sends an x41 or x48.

STS (The Status Byte)

• The controller uses the status byte, or STS, to return general status

and error flags to the host software. (The controller ignores the status

byte in the host software’s command packet.) The next table shows

status byte values and definitions.

• An “x” in the status bytes below indicates that the associated nibble

may contain additional information. In most cases, the status byte is

composed of two independent nibbles. Each nibble is independent

so that two codes can return at once. For example, status code F1

indicates that data has changed (Fx) and the controller is being

updated through the front panel (x1).

Status

in Hex Description

00 The controller has nothing to report, or AB protocol is selected.

01 Access denied for editing. The controller is being updated through the

front panel.

02 AIM Comm failure.

A0 A controller reset occurred.

Cx The controller received a command that was not a block read or block

write. (Command Error)

Dx The block write command attempted to write beyond a particular parameter block boundary, or the host software attempted to access a data table

block that does not exist. (Data Boundary Error)

Ex The Alarm_Status variable has changed. The software should query the

alarm status block to determine the particular alarm flag that changed.

Fx The controller altered shared data, either internally (from the firmware) or

externally (from the keyboard). The host software should read the Data

Changed Register to determine which data has been altered and update

its own run-time memory

TNSL

• Least significant byte of the transaction number. This is the first half

of a “message stamp.”

• The controller sends back the TNSL and TNSH exactly as it received

them, so host software can use the TNSL and TNSH bytes to keep

track of message packets.

TNSH

• Most significant byte of the transaction number. This is the second

half of the “message stamp.”

ADDL

• The low byte of the beginning data table address of the block of data

to read or write.

ADDH

• The high byte of the beginning data table address of the block of data

to read or write.

DATA

• The new values to be set with a write command, or the requested data

in a response to a read command.

DLE ETX

• Every packet of information must end with the codes DLE ETX.

These codes signal the end of a transmission.

BCC or CRC

• Communications packets include a one- or two-byte error check at

the end of the packet. There are two error check methods: Block

Check Character (BCC), which requires 1 byte, and Cyclic Redundancy Check (CRC), which requires 2 bytes.

Watlow Anafaze recommends that you use the default error check

method, BCC. It is easier to implement than CRC, and it is acceptable

for most applications.

Select one error check method and configure both software and

controller for that method, or they will be unable to communicate.

The error check methods work this way:

Block Check Character (BCC)

BCC checks the accuracy of each message packet transmission. It

provides a medium level of security. The BCC is the 2’s complement of

the 8-bit sum (modulo-256 arithmetic sum) of the data bytes between

the DLE STX and the DLE ETX. (1’s complement +1)

• BCC does not detect transposed bytes in a packet.

• BCC cannot detect inserted or deleted 0 values in a packet.

• If you have sent an x10 as data (by sending DLE x10) only one of the

DLE data bytes is included in the BCC’s sum (the DLE = x10 also).

For instance, the block read example shown in the examples section,

adds x08 00 01 00 00 80 02 10. Note that the x10 representing DLE

has been left out of the calculation. The sum should come to x9B.

Cyclic Redundancy Check (CRC)

CRC is a more secure error check method than BCC. It provides a very

high level of data security. It can detect:

• All single-bit and double-bit errors.

• All errors of odd numbers of bits.

• All burst errors of 16 bits or less.

• 99.997% of 17-bit error bursts.

• 99.998% of 18-bit and larger error bursts.

The CRC is calculated using the value of the data bytes and the ETX

byte. At the start of each message packet, the transmitter must clear a

16-bit CRC register.

When a byte is transmitted, it is exclusive-ORed with the right 8 bits of

the CRC register and the result is transferred to the right 8 bits of the

CRC register. The CRC register is then shifted right 8 times by inserting

0’s on the left.

Each time a 1 is shifted out on the right, the CRC register is ExclusiveORed with the constant value xA001. After the ETX value is

transmitted, the CRC value is sent, least significant byte (LSB) first.

Below is a structured English procedure from AB Manual:

data_byte = all application layer data, ETX

CLEAR CRC_REGISTER

FOR each data_byte

GET data_byte

XOR (data_byte, right eight bits of CRC_REGISTER)

PLACE RESULT in right eight bits of CRC_REGISTER

DO 8 times

Shift bit right, shift in 0 at left

IF bit shifted =1

XOR (CONSTANT, CRC_REGISTER)

PLACE RESULT in CRC_REGISTER

END IF

END DO

END FOR

TRANSMIT CRC_REGISTER as 2-byte CRC field

The host software sends two kinds of commands: block reads and block

writes. This section shows examples of both commands.

NOTE

If you read data from a loop set to SKIP, the controller will

send an empty packet for that loop.

This section does not show how to calculate the error check value

included with every packet. For help calculating the error check value,

see the section on BCC or CRC earlier in this chapter.

Block Read

This example shows the block read command the host software sends,

the controller’s responses, and the software’s acknowledgment.

Situation: Read process variables for loops 1 to 8.

• 8 process variables 2 bytes each = 16 bytes from data table address

x0280.

• Character values are represented in hex.

• The sender is device address 0.

• The destination is device address 8 (controller address 1).

• The software sends transaction number 00

Data for a Write Command

For a block write command, the block contains the bytes to write (up to

242 bytes of data). The controller sends back a message packet without

data.

Two-Byte Data Types

For two-byte data types, like process variable and setpoint, the

controller or host software sends the data in two-byte pairs with the least

significant byte first.

Figuring Block Size

In order to read parameter values, you must know how many bytes to

request. Parameter values are stored contiguously such that the setpoints

for all the loops are stored together and in loop number order. For

example, to read the deviation alarm deadband value for loops one to

five, you would read five bytes starting at x05A0. Some parameters,

such as setpoint, require two bytes of memory to store. So, for example,

if you want to read the setpoint for four loops, you must read eight

bytes.

Figure total block size in bytes for most loop parameters this way (do

not forget the pulse loop):

(Data Size) * (Number of Loops)

Some parameters have values for both heat and cool. Figure block size

for such a parameter this way:

2 * (Data Size) * (Number of Loops)

One exception is the units for each loop. Figure the data size for the

units this way:

3 * (Number of Loops)

Parameters that are not loop parameters (like system status, digital

inputs, or digital outputs) have specific data sizes. These data sizes are

listed in the data table in the next section

Anafaze/AB Data Table Summary

Each address holds one byte of data. Each parameter value requires one

or two addresses to store depending on the type of data. The table below

indicates the number of bytes for each data type. The data type for each

parameter is indicated in the tables on the following pages.

Because each loop is individually configurable, the number of instances

of many parameters depends on the number of loops in the controller.

Therefore, the number of bytes for these parameters is listed in the

tables on the following pages in terms of the number of loops in the

controller.

The storage requirements for some parameters depend on the number of

digital inputs or digital outputs in the controller (MAX_DIGIN_BYTES

and MAX_DIGOUT_BYTES). The storage of ramp-soak profile

parameters depend on the number of profiles (MAX_RSP), the number

of segments per profile (MAX_SEG), the number of triggers per

segment (MAX_TRIG) and the number of events per segment

(MAX_EVENT).

The table below shows the values for each of these factors. Use them to

calculate the number of bytes for each parameter.

Data Type and Symbol Data Size

Unsigned char (UC) 1 byte

Signed char (SC) 1 byte

Unsigned int (UI) 2 bytes

Signed int (SI) 2 bytes

Ordering of Heat and Cool Channel Parameters

For parameters that have both heat and cool settings the heat values are

stored in the first registers and the cool values are stored in the registers

starting at the listed address plus MAX_CH.

NOTE

Data table parameters 46 to 60 and 100 are ramp-soak

parameters. They are only used in controllers with the

ramp-soak option. Parameters 81 to 95 are enhanced features and only available in controllers with the enhanced

features option.

Ordering of Ramp-Soak Profile Parameters

Ramp-soak profile parameters are ordered first by profile, then by

segment where applicable. So, for example, the first eight bytes of the

Ready Events parameter are the ready segment event states for the first

profile (profile A) and the next eight bytes are for profile B and so on. In

the case of the segment triggers, the first byte contains the first trigger

setting for the first segment of profile A, the second byte contains the

settings for the second trigger for the first segment of profile A, the third

byte contains the settings for the first trigger for the second segment of

profile A and so on.

Anafaze/AB Protocol Data Table

Number Description Address

in Hex Type Number of Bytes

0 Proportional Band/Gain 0020 UC MAX_CH * 2

1 Derivative Term 0060 UC MAX_CH * 2

2 Integral Term 00A0 UI MAX_CH * 4

3 Input Type 0120 UC MAX_CH

4 Output Type 0180 UC MAX_CH * 2

5 Setpoint 01C0 SI MAX_CH * 2

6 Process Variable 0280 SI MAX_CH * 2

7 Output Filter 0340 UC MAX_CH * 2

8 Output Value 0380 UI MAX_CH * 4

9 High Process Alarm Setpoint 0400 SI MAX_CH * 2

10 Low Process Alarm Setpoint 04C0 SI MAX_CH * 2

11 Deviation Alarm Band Value 05A0 UC MAX_CH

12 Alarm Deadband 0600 UC MAX_CH

13 Alarm Status 0660 UI MAX_CH * 2

14 Not used 06A0 128

August 22, 2025 BY Huang, Jason

MotorolaMVME55006E Single-Board Computer Installation and Use

About this Manual

Overview of Contents

This manual is divided into the following chapters and appendices:

Chapter 1, Hardware Preparation and Installation, provides MVME5500 board preparation and

installation instructions for both the board and accessories. Also included are the power-up

procedure.

Chapter 2, Functional Description, describes the MVME5500 on a block diagram level.

Chapter 3, RAM55006E Memory Expansion Module, provides a description of the RAM5500

memory expansion module, as well as installation instructions and connector pin assignments.

Chapter 4, MOTLoad Firmware, describes the basic features of the MOTLoad firmware

product.

Chapter 5, Connector Pin Assignments, provides pin assignments for various headers and

connectors on the MMVE5500 single-board computer.

Appendix A, Specifications, provides power requirements and environmental specifications.

Appendix B, Thermal Validation, provides information to conduct thermal evaluations and

identifies thermally significant components along with their maximum allowable operating

temperatures.

Appendix C, Related Documentation, provides a listing of related Emerson manuals, vendor

documentation, and industry specifications.

The MVME55006E Single-Board Computer Installation and Use manual provides the

information you will need to install and configure your MVME55006E single-board computer. It

provides specific preparation and installation information, and data applicable to the board. The

MVME55006E single-board computer will hereafter be referred to as the MVME5500.

As of the printing date of this manual, the MVME5500 supports the models listed below.

Model Number Description

MVME55006E-0161 1 GHz MPC7457 processor, 512MB SDRAM, Scanbe handles

MVME55006E-0163 1 GHz MPC7457 processor, 512MB SDRAM, IEEE handles

RAM55006E-007 Memory expansion, 512MB SDRAM

IPMC7126E-002 Multifunction rear I/O PMC module; 8-bit SCSI, Ultra Wide SCSI, one

parallel port, three async and one sync/async serial ports.

MVME712M6E Transition module with one DB-25 sync/async serial port, three DB-25

async serial port, one AUI connector, one D-36 parallel port and one 50-

pin 8-bit SCSI; includes 3-row DIN P2 adapter board and cable.

Model Number Description

MVME7616E-001 Multifunction rear I/O PMC module; 8-bit SCSI, one parallel port, two

async and two sync/async serial ports. Transition module with two DB-9

async serial port connectors, two HD-26 sync/async serial port

connectors, one HD-36 parallel port connector, one RJ-45 10/100 Ethernet

connector; includes 3-row DIN P2 adapter board and cable (for 8-bit

SCSI).

MVME7616E-011 Transition module with two DB-9 async serial port connectors, two HD-26

sync/async serial port connectors, one HD-36 parallel port connector, one

RJ-45 10/100 Ethernet connector; includes 5-row DIN P2 adapter board

and cable (for 16-bit SCSI); requires backplane with 5-row DIN

connectors.

PMCSPAN26E-002 Primary PMCSPAN with original VME IEEE ejector handles.

PMCSPAN26E-010 Secondary PMCSPAN with original VME IEEE ejector handles.

PMCSPAN16E-002 Primary PMCSPAN with Scanbe ejector handles.

PMCSPAN16E-010 Secondary PMCSPAN with Scanbe ejector handles.

The following table describes the conventions used throughout this manual.

MVME7616E-001 Multifunction rear I/O PMC module; 8-bit SCSI, one parallel port, two

async and two sync/async serial ports. Transition module with two DB-9

async serial port connectors, two HD-26 sync/async serial port

connectors, one HD-36 parallel port connector, one RJ-45 10/100 Ethernet

connector; includes 3-row DIN P2 adapter board and cable (for 8-bit

SCSI).

MVME7616E-011 Transition module with two DB-9 async serial port connectors, two HD-26

sync/async serial port connectors, one HD-36 parallel port connector, one

RJ-45 10/100 Ethernet connector; includes 5-row DIN P2 adapter board

and cable (for 16-bit SCSI); requires backplane with 5-row DIN

connectors.

PMCSPAN26E-002 Primary PMCSPAN with original VME IEEE ejector handles.

PMCSPAN26E-010 Secondary PMCSPAN with original VME IEEE ejector handles.

PMCSPAN16E-002 Primary PMCSPAN with Scanbe ejector handles.

PMCSPAN16E-010 Secondary PMCSPAN with Scanbe ejector handles.

Model Number Description

Notation Description

0x00000000 Typical notation for hexadecimal numbers (digits

are 0 through F), for example used for addresses

and offsets

0b0000 Same for binary numbers (digits are 0 and 1)

bold Used to emphasize a word

Screen Used for on-screen output and code related

elements or commands in body text

Courier + Bold Used to characterize user input and to separate it

from system output

Reference Used for references and for table and figure

descriptions

File > Exit Notation for selecting a submenu

<text> Notation for variables and keys

[text] Notation for software buttons to click on the screen

and parameter description

… Repeated item for example node 1, node 2, …,

node 12

Omission of information from example/command

that is not necessary at the time being

.. Ranges, for example: 0..4 means one of the

integers 0,1,2,3, and 4 (used in registers)

| Logical OR

Summary of Changes

This manual has been revised and replaces all prior editions

Comments and Suggestions

We welcome and appreciate your comments on our documentation. We want to know what you

think about our manuals and how we can make them better.

Mail comments to us by filling out the following online form:

http://www.emersonnetworkpowerembeddedcomputing.com/ > Contact Us > Online Form

In “Area of Interest” select “Technical Documentation”. Be sure to include the title, part number,

and revision of the manual and tell us how you used it

Overview

This chapter contains the following information:

z Board and accessory preparation and installation instructions

z ESD precautionary notes

1.2 Introduction

The MVME5500 is a single-board computer based on the PowerPC MPC7457 processor and

the Marvell GT-64260B host bridge with a dual PCI interface and memory controller. On-board

payload includes two PMC slots, two SDRAM banks, an expansion connector for two additional

banks of SDRAM, 8MB boot Flash ROM, one 10/100/1000 Ethernet port, one 10/100 Ethernet

port, 32MB expansion Flash ROM, two serial ports, NVRAM and a real-time clock.

The MVME5500 interfaces to a VMEbus system via its P1 and P2 connectors and contains two

IEEE 1386.1 PCI mezzanine card (PMC) slots. The PMC slots are 64-bit and support both front

and rear I/O.

Additionally, the MVME5500 is user-configurable by setting on-board jumpers. Two I/O modes

are possible: PMC mode or SBC mode (also called 761 or IPMC mode). The SBC mode uses

the IPMC712 I/O PMC and the MVME712M transition module, or the IPMC761 I/O PMC and

the MVME761 transition module. The SBC mode is backwards compatible with the MVME761

transition module and the P2 adapter card (excluding PMC I/O routing) used on the MVME5100

product. This mode is accomplished by configuring the on-board jumpers and by attaching an

IPMC761 PMC in PMC slot 1. Secondary Ethernet is configured to the rear.

PMC mode is backwards compatible with the MVME5100 and is accomplished by configuring

the on-board jumpers.

1.3 Getting Started

This section provides an overview of the steps necessary to install and power up the

MVME5500 and a brief section on unpacking and ESD precautions.

1.4 Overview of Startup Procedures

The following table lists the things you will need to do before you can use this board and tells

where to find the information you need to perform each step. Be sure to read this entire chapter,

including all Caution and Warning notes, before you begin.

1.5 Unpacking Guidelines

Unpack the equipment from the shipping carton. Refer to the packing list and verify that all items

are present. Save the packing material for storing and reshipping of equipment.

If the shipping carton is damaged upon receipt, request that the carrier’s agent be present

during the unpacking and inspection of the equipment.

Table 1-1 Startup Overview

ESD

Emerson strongly recommends that you use an antistatic wrist strap and a

conductive foam pad when installing or upgrading a system. Electronic components,

such as disk drives, computer boards, and memory modules can be extremely

sensitive to electrostatic discharge (ESD). After removing the component from its

protective wrapper or from the system, place the component flat on a grounded,

static-free surface (and, in the case of a board, component side up). Do not slide the

component over any surface.

If an ESD station is not available, you can avoid damage resulting from ESD by

wearing an antistatic wrist strap (available at electronics stores) that is attached to an

active electrical ground. Note that a system chassis may not be grounded if it is

unplugged.

Personal Injury or Death

Dangerous voltages, capable of causing death, are present in this equipment.

Use extreme caution when handling, testing, and adjusting.

Configuring the Hardware

This section discusses certain hardware and software tasks that may need to be performed

prior to installing the board in a chassis.

To produce the desired configuration and ensure proper operation of the MVME5500, you may

need to carry out certain hardware modifications before installing the module.

Most options on the MVME5500 are software configurable. Configuration changes are made

by setting bits in control registers after the board is installed in a system.

Jumpers and switches are used to control those options that are not software configurable.

These settings are described further on in this section. If you are resetting the board jumpers

or switches from their default settings, it is important to verify that all settings are reset properly.

Configuring the Board

Figure 1-1 illustrates the placement of the jumpers, headers, switches, connectors, and various

other components on the MVME5500. There are several manually configurable headers and

switches on the MVME5500 and their settings are shown in Table 1-2. Each default setting is

enclosed in brackets. For pin assignments on the MVME5500, refer to Chapter 5, Connector

Pin Assignments.

Table 1-2 MVME5500 Jumper Settings

Jumpers /

Switches Function Settings

J6, J100, J7,

J101

Ethernet 2 Selection

Headers

(see also J34, J97, J98,

J99)

Refer to the hint on page 7

for a configuration

limitation.

2-3 on all

[1-2 on all]

Rear P2 Ethernet (SBC mode)

Front-panel Ethernet

J8 Flash Boot Bank Select

Header

No jumper installed

[1-2]

2-3

Boots from Flash 0

Boots from Flash 1

S3-1 Flash 0 Programming

Enable Header

OFF

[ON]

Disables Flash 0 writes

Enables Flash 0 writes

S5-1 Safe Start ENV Header [OFF]

Normal ENV settings used

during boot

Safe ENV settings used during

boot

S3-2 Flash 0 Block Write

Protect Header

OFF

[ON]

Disables Flash 0 J3 block

writes

Enables Flash 0 J3 block writes

S3-4 Non-Standard Option

Header

[OFF] For factory use only

S5-2 SROM Initialization

Enable Switch

OFF

[ON]

Enables SROM initialization

Disables SROM initialization

S4-1 PCI Bus 0.0 Speed

Header

[OFF]

PMC board controls whether

the bus runs at 33 MHz or

66 MHz

Forces PCI bus 0.0 to remain at

33 MHz

J27 VME SCON Select

Header

No jumper installed

1-2

[2-3]

Always SCON

No SCON

Auto-SCON

J28, J32 PMC/SBC Mode Selection

Headers

(set both jumpers)

Refer to page 7 for a

notice about configuring

for IPMC mode.

1-2 on both

2-3 on both

[1-2 on J28]

[2-3 on J32]

PMC mode

SBC/IPMC761 mode

SBC/IPMC712 mode

Table 1-2 MVME5500 Jumper Settings

The MVME5500 is factory tested and shipped with the configuration described in the following

section.

1.6.2 Ethernet 2, PMC/SBC Mode, and P2 I/O Selection Headers (J6,

J7, J28, J32, J34, J97 – J110)

All of the headers described below are used in conjunction with each other to select various

modes of operation for 10/100BaseT Ethernet, PMC/SBC mode, and P2 I/O mode.

1.6.2.1 Ethernet

Four 3-pin planar headers (J6, J7, J100, J101) and four 2-pin planar headers (J34, J97, J98,

J99) are for 10/100/BaseT Ethernet 2 selection.

Ethernet 1 is the Gigabit Ethernet port and is front panel only.

Figure 1-1 MVME5500 Board Layout

For J6, J100, J7 and J101, install jumpers across pins 2-3 on all four headers for rear P2 Ethernet. For front-panel Ethernet, install jumpers across pins 1-2 on all four headers. For J34, J97, J98 and J99, no jumpers are installed for front-panel Ethernet. For rear P2 Ethernet, install jumpers across pins 1-2 on all four headers when in SBC/IPMC761 mode. 1.6.2.2 PMC/SBC Mode Selection The MVME5500 is set at the factory for PMC mode. The SBC/IPMC761 mode should only be selected when using the IPMC761 module in conjunction with the MVME761 transition module.The PMC mode should be selected when using PMC modules with specific user I/O in conjunction with the corresponding transition module. PMC mode should also be selected when using PrPMC modules. Two 3-pin planar headers (J28, J32) control the supply of +/- 12 volts to the P2 connector; one or both of these voltages are required by the MVME712 or MVME761 module when operating in SBC mode. For PMC mode, jumpers are installed across pins 1-2 on both headers. For SBC/IPMC761 mode, install jumpers across pins 2-3 on both headers. For SBC/IPMC712 mode, install a jumper across pins 2-3 for J32 and install a jumper across pins 1-2 for J28. 1.6.2.3 P2 I/O Selection Nine 3-pin planar headers (J102 –J110) are for P2 I/O selection. Jumpers are installed across pins 1-2 on all nine headers when in PMC mode. Install jumpers across pins 2-3 on all nine headers when in SBC/IPMC761 or SBC/IPMC712 mode to connect the extended SCSI signals to P2. If the rear P2 Ethernet is selected by jumpers J6, J7, J100, and J101, the Ethernet signals also connect to PMC 1 user I/O connector J14. If a PMC card is plugged into PMC slot 1, there may be a conflict between the I/O from the PMC card and the rear Ethernet signals. This conflict does not occur with the IPMC761 or IPMC712 modules. Product Damage When J28 is configured for SBC/IPMC mode, –12V is supplied to P2 pin A30. If there is an incompatible board plugged into this P2 slot, damage may occur. When J32 is configured for SBC/IPMC mode, +12V is supplied to P2 pin C7. If there is an incompatible board plugged into this P2 slot, damage may occur.

Flash Boot Bank Select Header (J8)

A 3-pin planar header selects the boot Flash bank. No jumper or a jumper installed across pins

1-2 selects Flash 0 as the boot bank. A jumper installed across pins 2-3 selects Flash 1 as the

boot bank

Flash 0 Programming Enable Switch (S3-1)

This switch enables/disables programming of Flash 0 as a means of protecting the contents

from being corrupted. The switch set to OFF disables all Flash 0 programming. The switch set

to ON enables the programming, this is the factory setting.

Safe Start ENV Switch (S5-1)

This switch selects programmed or safe start ENV settings. When set to OFF, it indicates that

the programmed ENV settings should be used during boot. Set to ON indicates that the safe

ENV settings should be used.

Flash 0 Block Write Protect Switch (S3-2)

This switch supports the Intel J3 Flash family write protect feature. Set to OFF, it enables the

lock-down mechanism. Blocks locked down cannot be unlocked with the unlock command. The

switch must be set to ON in order to override the lock-down function and enable blocks to be

erased or programmed through software. Refer to the Intel J3 Flash data sheet, listed in

Appendix C, Related Documentation, for further details.

SROM Initialization Enable Switch (S5-2)

This switch enables/disables the GT-64260B SROM initialization. When set to 2, it enables the

GT-64260B device initialization via I2C SROM. Set to ON disables this initialization sequence.

SROM Initialization Enable Switch (S5-2)

This switch enables/disables the GT-64260B SROM initialization. When set to 2, it enables the

GT-64260B device initialization via I2C SROM. Set to ON disables this initialization sequence.

PCI Bus 0.0 Speed Switch (S4-1)

This switch can force PCI bus 0.0 to run at 33 MHz rather than the standard method of allowing

the PMC board to control whether the bus runs at 33 MHz or 66 MHz. Set to 1, it allows the

PMC board to choose the PCI 0.0 bus speed. Set to ON forces PCI bus 0.0 to run at 33 MHz.

9 VME SCON Select Header (J27)

A 3-pin planar header allows the choice for auto/enable/disable SCON VME configuration. A

jumper installed across pins 1-2 configures for SCON disabled. A jumper installed across pins

2-3 configures for auto SCON. No jumper installed configures for SCON always enabled.

0 PCI Bus 1.0 Speed Switch (S4-2)

This switch can force PCI bus 1.0 to run at 33 MHz rather than the standard method of allowing

the PMC board to control whether the bus runs at 33 MHz or 66 MHz. Set to 1, it allows the

PMC board to choose the PCI 1.0 bus speed. Set to ON forces PCI bus 1.0 to run at 33 MHz.

1 EEPROM Write Protect Switch (S3-3)

This switch enables/disables programming of the on-board EEPROMs as a means of protecting

the contents from being corrupted. Set to 1, it disables EEPROM programming by driving the

WP pin to a logic high. Set to ON to program any of the EEPROMs at addresses A0, A6, A8,

and/or AA.

Setting the PMC Vio Keying Pin

Signalling voltage (Vio) is determined by the location of the PMC Vio keying pin. Each site can

be independently configured for either +5V or +3.3V signalling. The option selected can be

determined by observing the location of the Vio keying pin.

Installing the RAM5500 Module

Procedure

To upgrade or install a RAM5500 module, refer to and proceed as follows:

1. Attach an ESD strap to your wrist. Attach the other end of the ESD strap to the

chassis as a ground. The ESD strap must be secured to your wrist and to ground

throughout the procedure.

2. Perform an operating system shutdown. Turn the AC or DC power off and remove

the AC cord or DC power lines from the system. Remove the chassis or system

cover(s) as necessary for access to the VME boards.

3. Carefully remove the MVME5500 from its VME card slot and lay it flat, with

connectors P1 and P2 facing you.

4. Inspect the RAM5500 module that is being installed on the MVME5500 host board

to ensure that standoffs are installed in the four mounting holes on the module.

5. With standoffs installed in the four mounting holes on the RAM5500 module, align

the standoffs and the P1 connector on the module with the four holes and the P4

connector on the MVME5500 host board and press the two connectors together

until they are firmly seated in place.

6. Turn the entire assembly over and fasten the four short Phillips screws to the

standoffs of the RAM5500.c

August 22, 2025 BY Huang, Jason

MotorolaPMC expansion combined with a high-performance VME processor

PMC expansion combined with a high-performance VME processor

The MVME2600 series is a family of VME processor modules based on the Motorola

PowerPlus VME architecture with PowerPC architecture-compatible microprocessors.

The flexibility of the MVME2600 provides an excellent base platform that can be

quickly and easily customized for a variety of industry-specific applications.

Designed to meet the needs of military and aerospace, industrial automation, and

medical imaging market segments, the MVME2600 applies to a variety of applications.

DRAM expansion mezzanines enable memory upgrades to the maximum 512MB of

ECC DRAM without requiring additional VME slots.

■ MPC60x class of microprocessors

■ 16KB/16KB or 32KB/32KB L1 cache

■ 256KB L2 cache

■ Up to 512MB ECC DRAM on-board memory

■ 8MB on-board Flash, 1MB socketed

■ 64-bit PCI mezzanine connector

■ On-board debug monitor with self-test diagnostics

■ IEEE P1386.1 compatible 32/64-bit PMC expansion

slot

■ Two or three async, one or two sync/async serial

ports

■ Ethernet transceiver interface with 32-bit PCI local

bus DMA

■ 8- or 16-bit Fast SCSI-2 bus interface

■ Parallel, floppy, keyboard, and mouse interfaces

■ 8KB x 8 NVRAM and time-of-day clock with

replaceable battery backup

■ Four 32-bit timers, one watchdog timer

PCI Expansion

MVME2600 modules have a 64-bit PCI connection to

support PCI expansion carriers such as Motorola

PMCspan. Design details for the connector and electrical

specifications are available from your local Motorola

sales representative.

Memory Modules

The MVME2600 series has a modular memory design.

Mezzanine arrays support up to 512MB.

Transition Modules

Two artwork variants of the MVME2600 are available.

One series provides backward compatibility with the

MVME712M transition module I/O, while the other

series accepts the MVME761 transition module

featuring an additional sync/async serial port, a

10/100BaseTX Ethernet interface, Fast 16-bit SCSI, and

an IEEE 1284 compatible parallel port.

MVME761

The MVME761 transition module provides

industry-standard connector access to the IEEE 1284

parallel port, a 10BaseT or 100BaseTX Ethernet port via

an RJ-45 connector, two DB-9 connectors providing

access to the asynchronous serial ports configured as

EIA-574 DTE and two HD-26 connectors providing access

to the sync/async serial ports. These serial ports,

labeled as Serial 3 and Serial 4 on the face plate of the

MVME761, are individually user configurable as

EIA-232, EIA-530, V.35, or X.21 DCE/DTE via the

installation of Motorola serial interface modules (SIMs).

A P2 adapter provides interface module signals to the

MVME761 transition module. The 3-row P2 adapter can

be used for 8-bit SCSI. A 5-row P2 adapter supports

16-bit SCSI and PMC I/O.

MVME712M

The MVME712M transition module provides

industry-standard connector access to the Centronics

parallel port, an AUI port and four DB-25 connectors,

providing access to the asynchronous/synchronous

serial ports jumper configurable as EIA-232 DCE or DTE.

A P2 adapter provides interface signals to the

MVME712M transition module. The 3-row P2 adapter

can be used for 8-bit SCSI.

To gain access to the additional user-definable I/O pins

provided via the 5-row VME64 extension connector, a

special P2 adapter board is available. This adapter panel

replaces the traditional 3-row P2 adapter and extends its

capability by providing access to the PMC I/O pins.

Several other variations of the MVME712M are

available for combinations of I/O and connectors.

Firmware Monitor

Firmware must fulfill the traditional functions of test and

initialization, in addition to operating system boot

support. The MVME2600 firmware monitor exceeds

these requirements with a proven monitor from the

embedded VME leader. It expands features like

power-up tests with extensive diagnostics, as well as a

powerful evaluation and debug tool for simple checkout

or when high-level development debuggers require

additional support. All this is included with the

MVME2600 firmware, plus it supports booting both

operating systems and kernels.

Operating Systems and Real-Time Kernels

MVME2600 DETAILS

Motorola Computer Group: AIX

Integrated Systems, Inc.: pSOSystem

Lynx Real-Time Systems,

Inc.:

LynxOS

Microware Systems

Corporation:

OS-9/OS-9000

Microtec: VRTX32

Wind River Systems, Inc.: VxWorks

Processor

Memory

PCI Expansion Connector

VMEbus ANSI/VITA 1-1994 VME64 (IEEE STD 1014)

Ethernet Interface

SCSI Interface

Asynchronous Serial Ports

SPECIFICATIONS

Microprocessor: MPC603 MPC604 MPC604

Clock Frequency: 200 MHz 333 MHz 400 MHz

On-chip Cache (I/D): 16K/16K 16K/16K 16K/16K

Memory Type: 60 ns FPM or 50 ns EDO 60 ns FPM or 50 ns EDO 60 ns FPM or 50 ns EDO

MAIN MEMORY: Dynamic RAM

Capacity (60ns FPM): 32MB on RAM200

Capacity (50ns EDO): 128, 256, or 512MB on RAM200

Single Cycle Accesses: 9 read/4 write

Read Burst Mode (60ns

FPM):

9-1-2-1 idle; 3-1-2-1 aligned page hit

Read Burst Mode (50ns

EDO):

8-1-1-1 idle; 2-1-1-1 aligned page hit

Write Burst Mode: 4-1-1-1 idle; 3-1-1-1 aligned page hit

Architecture: 128-bit, two-way interleaved

Parity/ECC: No/Yes

L2 CACHE: 256KB

Cache Bus Clock

Frequency:

Processor clock divided by 2

FLASH: On-board programmable

Capacity: 1MB via two 32-pin PLCC/CLCC sockets;

8MB surface mount

Read Access (8MB

port):

68 clocks (32 byte burst)

Read Access (1MB

port):

260 clocks (8 byte burst)

Write Access

(1MB/8MB):

19 clocks (2 bytes/8 bytes)

NVRAM: 8KB (4KB available for users)

Cell Storage Life: 50 years at 55° C

Cell Capacity Life: 10 years at 100% duty cycle

Removable Battery: Yes

Address/Data: A32/D32/D64

PCI Bus Clock: 33 MHz

Signaling: 5 V

Connector: 114-pin connector located on the planar of

the MVME2600 between P1 and P2

Controller: Tundra Universe

DTB Master: A16–A32; D08–D64, BLT

DTB Slave: A24–A32; D08–D64, BLT, UAT

Arbiter: RR/PRI

Interrupt

Handler/Generator:

IRQ 1–7/Any one of seven IRQs

System Controller: Yes, jumperable or auto detect

Location Monitor: Two, LMA32

MVME761 MVME712M

Controller: DEC 21140 DEC 21140

Interface

Speed:

10/100Mb/s AUI (10Mb/s)

PCI Local bus

DMA:

Yes, with PCI burst Yes, with PCI burst

Connector: Routed to P2,

RJ-45 on MVME761

Routed to P2,

DB-15 AUI on

MVME712M

MVME761 MVME712M

Controller: Symbios 53C825A Symbios 53C825A

PCI Local Bus

DMA:

Yes, with PCI local bus

burst

Yes, with PCI local bus

burst

Asynchronous: 5.0MB/s 5.0MB/s

Synchronous: 10.0MB/s (8-bit mode),

20.0MB/s (16-bit mode)

10.0MB/s (8-bit mode),

20.0MB/s (16-bit mode)

Connector: Routed to P2, 50- or

68-pin on

MVME761EXT

Routed to P2, SCSI D-50

on MVME712M

MVME761 MVME712M

Controller: PC87308 PC87308,

85230/8536

Number of

Ports:

Two, 16550 compatible Two, 16550 compatible

and one 85230/8536

Configuration: EIA-574 DTE EIA-232 DCE/DTE

Async Baud

Rate, bps

max.:

38.4K EIA-232, 115Kb/s

raw

38.4K EIA-232, 115Kb/s

raw

Connector: Routed to P2, DB-9 on

MVME761

Routed to P2, DB-25 on

MVME712M

Synchronous Serial Ports

Parallel Port

Counters/Timers

Floppy

Mouse Interface

Keyboard Interface

IEEE P1386.1 PCI Mezzanine Card Slot

Board Size

Miscellaneous

Reset and abort switches on front panel; six LEDs for FAIL, CHKSTP,

CPU, PCI, SCON and FUSE

Transition Module I/O Connectors

Board Size

MVME761 MVME712M

Controller: 85230/8536 85230/8536

Number of

Ports:

Two One

Configuration: TTL to P2 (both ports),

SIM on MVME761

EIA-232 DCE/DTE

Baud Rate, bps

max.:

2.5MB sync, 38.4KB

async

2.5MB sync, 38.4KB

async

Oscillator

Clock Rate

(PCLK):

10 MHz/5 MHz 10 MHz/5 MHz

Connector: Routed to P2, HD-26 on

MVME761

Routed to P2, DB-25 on

MVME712M

MVME761 MVME712M

Controller: PC87308 PC87308

Configuration: 8-bit bidirectional, full

IEEE 1284 support;

Centronics compatible

8-bit bidirectional, IEEE

1284 minus EPP and

ECP

Modes: Master only Master only

Connector: Routed to P2, HD-36 on

MVME761

Routed to P2, D-36 on

MVME712M

TOD Clock Device: M48T18; 8KB NVRAM

Real-Time

Timers/Counters:

Four, 32-bit programmable

Watchdog Timer: Time-out generates reset

Controller: PC87308

Compatible Controllers: DP8473, 765A, N82077

Configuration: 3.5″ 2.88MB and 1.44MB; 5.25″ 1.2MB

Connector: HD-50 on front panel

Controller: PC87308

Connector: 6-pin circular female mini DIN on front

panel

Controller: PC87308

Connector: 6-pin circular female mini DIN on front

panel

Address/Data: A32/D32/D64, PMC PN1, PN2, PN3, PN4

connectors

PCI Bus Clock: 33 MHz

Signaling: 5 V

Power: +3.3 V, +5 V, ±12 V; 7.5 watts maximum

per PMC slot

Module Types: Basic, single-wide, front panel I/O or P2

I/O (Note: P2 I/O is only accessible to

systems equipped for VME64 extension

connectors.)

Height: 233.4 mm (9.2 in.)

Depth: 160.0 mm (6.3 in.)

Front Panel Height: 261.8 mm (10.3 in.)

Width: 19.8 mm (0.8 in.)

Max. Component

Height:

14.8 mm (0.58 in.)

Asynchronous Serial Ports: Two, DB-9 labeled as COM1 and COM2 Three, DB-25 labeled as Serial 1, Serial 2 and Serial 3

Synchronous Serial Ports: Two, HD-26 labeled as Serial 3 and Serial 4 (user

configurable via installation of SIMs;

two 60-pin connectors on MVME761 planar for

installation of two SIMs

One, DB-25 labeled as Serial 4

Parallel Port: HD-36, Centronics compatible D-36, Centronics compatible

Ethernet: 10BaseT or 100BaseTX RJ-45 10Mb/s Ethernet;

DB-15 AUI

SCSI: 8- or 16-bit, 50- or 68-pin connector via P2 adapter 8-bit, standard SCSI D-50

August 22, 2025 BY Huang, Jason

MotorolaMVME187 RISC Single Board Computer Installation Guide MVME187IG/D4

Safety Summary

Safety Depends On You

The following general safety precautions must be observed during all phases of operation, service, and

repair of this equipment. Failure to comply with these precautions or with specific warnings elsewhere in

this manual violates safety standards of design, manufacture, and intended use of the equipment.

Motorola, Inc. assumes no liability for the customer’s failure to comply with these requirements.

The safety precautions listed below represent warnings of certain dangers of which Motorola is aware. You,

as the user of the product, should follow these warnings and all other safety precautions necessary for the

safe operation of the equipment in your operating environment.

Ground the Instrument.

To minimize shock hazard, the equipment chassis and enclosure must be connected to an electrical ground.

The equipment is supplied with a three-conductor ac power cable. The power cable must be plugged into

an approved three-contact electrical outlet. The power jack and mating plug of the power cable meet

International Electrotechnical Commission (IEC) safety standards.

Do Not Operate in an Explosive Atmosphere.

Do not operate the equipment in the presence of flammable gases or fumes. Operation of any electrical

equipment in such an environment constitutes a definite safety hazard.

Keep Away From Live Circuits.

Operating personnel must not remove equipment covers. Only Factory Authorized Service Personnel or

other qualified maintenance personnel may remove equipment covers for internal subassembly or

component replacement or any internal adjustment. Do not replace components with power cable

connected. Under certain conditions, dangerous voltages may exist even with the power cable removed. To

avoid injuries, always disconnect power and discharge circuits before touching them.

Do Not Service or Adjust Alone.

Do not attempt internal service or adjustment unless another person capable of rendering first aid and

resuscitation is present.

Use Caution When Exposing or Handling the CRT.

Breakage of the Cathode-Ray Tube (CRT) causes a high-velocity scattering of glass fragments (implosion).

To prevent CRT implosion, avoid rough handling or jarring of the equipment. Handling of the CRT should

be done only by qualified maintenance personnel using approved safety mask and gloves.

Do Not Substitute Parts or Modify Equipment.

Because of the danger of introducing additional hazards, do not install substitute parts or perform any

unauthorized modification of the equipment. Contact your local Motorola representative for service and

repair to ensure that safety features are maintained.

Dangerous Procedure Warnings.

Warnings, such as the example below, precede potentially dangerous procedures throughout this manual.

Instructions contained in the warnings must be followed. You should also employ all other safety

precautions which you deem necessary for the operation of the equipment in your operating environment.

WARNING

Dangerous voltages, capable of causing death, are

present in this equipment. Use extreme caution when

handling, testing, and adjusting.

All Motorola PWBs (printed wiring boards) are manufactured by UL-recognized

manufacturers, with a flammability rating of 94V-0.

WARNING

This equipment generates, uses, and can radiate electromagnetic energy. It may cause or be susceptible to

electro-magnetic interference (EMI) if not installed and

used in a cabinet with adequate EMI protection.

The computer programs stored in the Read Only Memory of this device contain

material copyrighted by Motorola Inc., 1995, and may be used only under a license

such as those contained in Motorola’s software licenses.

Motorola® and the Motorola symbol are registered trademarks of Motorola, Inc.

All other products mentioned in this document are trademarks or registered

trademarks of their respective holders.

Printed in the United States of America

This Chapter Covers

❏ Details about this manual

❏ Terminology, conventions, and definitions used

❏ Other publications relevant to the MVME187

About this Manual

This manual supports the setup, installation, and debugging of the

RISC-based MVME187 Single Board Computer; a highperformance engine for VMEbus-based low- and mid-range OEM

and integrated systems, embedded controllers, and other singleboard computer applications.

This manual provides:

❏ A general Board Level Hardware Description in Chapter 2

❏ Hardware Preparation and Installation instructions in Chapter 3

❏ Debugger General Information in Chapter 4

❏ Debugger/monitor commands, and other information about

Using the 187Bug Debugger in Chapter 5

❏ Other information needed for start-up and troubleshooting of

the MVME187 RISC Single Board Computer, including

– Configure and Environment Commands in Appendix A

– Disk/Tape Controller Data in Appendix B for controller

modules supported by 187Bug

– Network Controller Data in Appendix C

– Procedures for Troubleshooting CPU Boards in Appendix D

– EIA-232-D Interconnections in Appendix E

Terminology, Conventions, and Definitions

Used in this Manual

Data and Address Parameter Numeric Formats

Throughout this manual, a character identifying the numeric

format precedes data and address parameters as follows:

For example, “12” is the decimal number twelve, and “$12” is the

decimal number eighteen.

Unless otherwise specified, all address references are in

hexadecimal.

Signal Name Conventions

An asterisk (*) follows signal names for signals which are level or

edge significant:

$ dollar specifies a hexadecimal character

% percent specifies a binary number

& ampersand specifies a decimal number

Term * Indicates

level

significant The signal is true or valid when the signal is low.

edge

significant

The actions initiated by that signal occur on high

to low transition.

Assertion and Negation Conventions

Assertion and negation are used to specify forcing a signal to a

particular state. These terms are used independently of the voltage

level (high or low) that they represent.

Data and Address Size Definitions

Data and address sizes are defined as follows:

Big-Endian Byte Ordering

This manual assumes that the MPU on the MVME187 always

programs the CMMUs with big-endian byte ordering, as shown

below. Any attempt to use little-endian byte ordering will

immediately render the MVME187Bug debugger unusable.

Term Indicates

Assertion and assert The signal is active or true.

Negation and negate The signal is inactive or false.

Name Size Numbered Significance Called

Byte 8 bits 0 through 7

bit 0 is the

least

significant

Two-byte 16 bits 0 through 15

bit 0 is the

least

significant

halfword

Four-byte 32 bits 0 through 31

bit 0 is the

least

significant

word

BIT BIT

31 24 23 16 15 08 07 00

ADR0 ADR1 ADR2 ADR3

Control and Status Bit Definitions

The terms control bit and status bit are used extensively in this

document to describe certain bits in registers.

❏ The status bit can be read by software to determine

operational or exception conditions.

True/False Bit State Definitions

True and False indicate whether a bit enables or disables the

function it controls:

Bit Value Descriptions

In all tables, the terms 0 and 1 are used to describe the actual value

that should be written to the bit, or the value that it yields when

read.

Term Describes

Control bit The bit can be set and cleared under software

control.

Status bit The bit reflects a specific condition.

Term Indicates

True Enables the function it controls.

False Disables the function it controls.

EMERSONMVME5500 Series VMEbus Single-Board Computer

The MVME5500 is the

flagship of our VME product

line that enables higher levels

of performance in a single

VMEbus slot

MPC7457 PowerPC® processor

at 1 GHz

512KB of on-chip L2 cache and

2MB of L3 cache

AltiVec coprocessor for highperformance computational

applications

512MB of on-board 133 MHz

SDRAM ECC memory and

512MB additional memory via

a memory mezzanine card for a

total of 1GB of memory

Two banks of soldered flash

memory (32MB and 8MB)

Dual independent 64-bit PCI

buses and PMC sites with a bus

speed of up to 66 MHz

Gigabit Ethernet interface plus

an additional 10/100BaseTX

Ethernet interface

64-bit PCI expansion mezzanine

connector allowing up to four

more PMCs

I/O compatibility with

MVME51xx family

Single VME slot even when fully

configured with two PMC modules or one PMC module and an

add-on memory mezzanine

Support for processor PMCs

(PrPMCs)

The Emerson Network Power MVME5500 series is designed to meet the needs of

OEMs including those in defense and aerospace, industrial automation and medical

imaging market segments. Customers looking for a technology refresh for their

application while maintaining backward compatibility with their existing VMEbus

infrastructure can upgrade to the MVME5500 series and take advantage of the

enhanced performance features.

The MVME5500 utilizes the MPC7457 processor running at 1 GHz, which is ideal for

data intensive applications. The MVME5500 provides more than just better processor

performance; it also provides balanced performance from the processor, memory,

dual independent local buses and I/O subsystems.

The powerful Marvell system controller, with support for a 133 MHz host bus and

a 133 MHz SDRAM memory bus, is well matched to the high speed processor. To

match the system I/O to the outstanding processor performance, the MVME5500

provides dual 64-bit, 33/66 MHz PCI buses. Each PCI bus has a PMC site supporting

cards running at 33 or 66 MHz. The Universe II VME interface and PMCspan connector are isolated from the PMC sites on a dedicated 33 MHz PCI bus segment so that

both PMC sites are capable of 66 MHz operation.

The MVME5500 also offers a Gigabit Ethernet interface, a 10/100BaseTX Ethernet

interface and two serial ports. All of this adds up to a set of well-balanced,

high-performance subsystems for unparalleled performance.

Backwards Compatibility

The MVME5500 continues the direction that Emerson

started with the MVME5100 series of providing a

migration path from Emerson’s embedded controllers

and single-board computers (SBCs) to a single

platform. This migration path enables OEMs to

support varying I/O requirements with the same base

platform, simplifying part number maintenance,

technical expertise requirements and sparing.

The MVME5500 series offers customers a migration

path from the MVME2300, MVME2400, MVME2600,

MVME2700 and MVME5100 boards to allow them to

take advantage of features such as the MPC7455

processor, Gigabit Ethernet and dual independent

33/66 MHz PMC sites.

IPMC Modules

The IPMC761 and IPMC712 are optional add-on PMC

modules that provide backward compatibility with

previous generation Emerson products (such as

MVME2600, MVME2700 and MVME5100 in IPMC mode)

using the MVME761 or MVME712M transition module.

IPMC modules provide rear I/O support for the following:

One single-ended Ultra Wide SCSI port

One parallel port

Four serial ports (two or three async and one or two

sync/async, depending on module)

With an IPMC installed, one PMC slot is still available,

providing support for OEM product customization.

P2 I/O Modes

The MVME5500 series supports two, jumper-configurable

P2 I/O modes: PMC mode and IPMC mode. PMC mode

is backward compatible with the MVME2300/

MVME2400 and MVME5100 in PMC mode. In PMC

mode, 64 pins from PMC slot 1 and 46 pins from PMC

slot 2 are available on P2 for PMC rear I/O. In IPMC

mode, the MVME5500 series supports legacy

MVME761 or MVME712M I/O modules (with limited

PMC I/O) when an IPMC761 or IPMC712 PMC card is

populated in PMC slot 1. In this configuration, PMC

slot 2 contains some signals that are reserved for

extended SCSI.

Transition Modules

The MVME761 transition module provides industrystandard connector access to the IEEE 1284 parallel

port, a 10BaseT or 100BaseT port via an RJ-45

connector, two DB-9 connectors providing access to

the asynchronous serial ports configured as EIA-574

DTE and two HD-26 connectors providing access to

the sync/async serial ports. These serial ports, labeled

as Serial 3 and Serial 4 on the faceplate of the MVME761,

are individually user-configurable as EIA-232, DCE or

DTE via the installation of Emerson Serial Interface

Modules (SIMs). A P2 adapter board provides interface

signals to the MVME761 transition module. Two

separate P2 adapter boards are available: one for 3-row

backplanes and one for 5-row backplanes. The 3-row

P2 adapter board provides connection for 8-bit SCSI.

A 5-row P2 adapter board supports 16-bit SCSI and

PMC I/O.

The MVME712M transition module provides

industry-standard connector access to the Centronics

parallel port, a narrow SCSI port, and four DB-25

connectors providing access to the asynchronous/

synchronous serial ports jumper configurable as

EIA-232 DCE or DTE. A P2 adapter board provides

interface signals to the MVME712M transition

module. The 3-row P2 adapter board also provides

connection for 8-bit SCSI. To gain access to the

additional user-definable I/O pins provided via the 5-row

VME64 extension connector, a special P2 adapter

board is available. This adapter panel replaces the

traditional 3-row P2 adapter board and extends its

capability by providing access to the PMC I/O pins.

Software Support

Firmware Monitor

Firmware must fulfill the traditional functions of

power-on self-test (POST), initialization, low-level

setup and debug, and operating system booting.

Emerson’s innovative firmware (known as MOTLoad)

that is resident on the MVME5500 exceeds these

requirements with expanded features such as

interrupt driven I/O, more comprehensive power-up

tests and extensive diagnostics with new scripting

capability. And of course, MOTLoad provides a

debugger interface similar to the time proven “bug”

interface on previous VMEbus boards from Emerson.

Operating Systems and Kernels

WindRiver Systems VxWorks, TimeSys Linux, Green

Hills Software INTEGRITY and LynuxWorks LynxOS are

available for the MVME5500.

Libraries

VSI/Pro VSIPL libraries from MPI Software Technology

are available on the MVME5500. BETA 4.0 NDDS from

Real Time Innovations (RTI) running over GbE and Native

VME are available on the MVME5500 through RTI.

Specifications

Processor

Microprocessor: MPC7457

Clock Frequency: 1 GHz

On-chip L1 Cache (I/D): 32KB/32KB

On-chip L2 Cache (I/D): 512KB

L3 Cache: 2MB

System Controller

Marvell GT-64260B

Main Memory

Type: PC133 ECC SDRAM

Speed: 133 MHz

Configurations: 512MB in two banks

Capacity: 512MB on-board, expandable to 1GB

with add-on memory mezzanine card.

Note: If a PMC module is plugged into PMC slot 1,

the memory mezzanine card cannot be used

because the PMC module covers the memory

mezzanine connector.

Flash Memory

Type: EEPROM, on-board programmable

Capacity: 40MB total in two banks of 32MB and

8MB, both soldered

Write Protection: 32MB of surface-mount flash is

write protectable via jumper

NVRAM

Capacity: 32KB (4KB available for users)

Cell Storage Life: 50 years at 55° C

Cell Capacity Life: 5 years at 100% duty cycle, 25° C

Removable Battery: Yes

Counters/Timers

TOD Clock Device: M48T37V

Real-Time Timers/Counters: Eight, 32-bit

programmable

Watchdog Timer: Time-out generates reset

VMEbus Interface: ANSI/VITA 1-1994 VME64

(IEEE STD 1014)

Controller: Tundra Universe II

DTB Master: A16-A32; D08-D64, SCT, BLT

DTB Slave: A24-A32; D08-D64, BLT, UAT

Arbiter: RR/PRI

Interrupt Handler/Generator: IRQ 1-7/Any one of

seven IRQs

System Controller: Yes, jumperable or auto detect

Location Monitor: Two, LMA32

Ethernet Interfaces

Port 1

Controller: Intel® 82544EI Gigabit Ethernet controller

Interface Speed: 10/100/1000Mbps

Connector: Routed to front panel RJ-45

Port 2

Controller: Controller integrated into

GT-64260B system controller

Interface Speed: 10/100Mbps

Connector: Routed to front panel RJ-45 or

optionally routed to P2, RJ-45 on MVME761

Asynchronous Serial Ports

Controller: Two TL16C550C UARTs

Number of Ports: Two, 16550 compatible

Async Baud Rate, bps max.: 38.4K EIA-232,

115Kbps raw

Connector: Routed to front panel RJ-45; one on

planar for development use

Dual IEEE P1386.1 PCI Mezzanine Card Slots

Address/Data: A32/D32/D64, PMC PN1, PN2, PN3,

PN4 connectors

PCI Bus Clock: 33/66 MHz

Signaling: 3.3V or 5V, configurable with keying pin

Power: +3.3V, +5V, ±12V

Module Types: Two single-wide or one doublewide, front panel or P2 I/O, PMC and PrPMC support

Note: If a PMC module is plugged in PMC slot 1, the

memory mezzanine card cannot be used because

the PMC module covers the memory mezzanine

connector.

PCI Expansion Connector

Address/Data: A32/D32/D64

PCI Bus Clock: 33 MHz

Signaling: 5V

Power: +3.3V, +5V, ±12V

Connector: 114-pin connector located on MVME5500

planar, same location as on MVME5100 planar

Power Requirements

+5V ± 5%

MVME5500-0163: 6.7 A typ., 8.0 A max.

MVME5500-0163

with memory mezzanine: 7.5 A typ., 9.0 A max.

MVME5500-0163

with IPMC712/761: 7.6 A typ., 9.2 A max.

Note: In a 3-row chassis, PMC current should be

limited to 19.8 watts (total of both PMC slots). In a

5-row chassis, PMC current should be limited to 46.2

watts (total of both PMC slots).

Board Size

Height: 233.4 mm (9.2 in.)

Depth: 160.0 mm (6.3 in.)

Front Panel Height: 261.8 mm (10.3 in.)

Width: 19.8 mm (0.8 in.)

Max. Component Height: 14.8 mm (0.58 in.)

IPMC Modules

PMC Interface

Address/Data: A32/D32/D64, PMC PN1, PN2, PN3,

PN4 connectors

PCI Bus Clock: 33 MHz

Signaling: 5V

Module Type: Basic single-wide; P2 I/O

SCSI Bus

Controller: Symbios 53C895A

PCI Local Bus DMA: Yes, with PCI local bus burst

Asynchronous (8-bit mode): 5.0MB/s

Ultra SCSI: 20.0MB/s (8-bit mode), 40.0MB/s

(16-bit mode)

Note: 16-bit SCSI operation precludes the use of

some PMC slot 2 signals.

Synchronous Serial Ports

Controller: 85230/8536

Number of Ports: Two (IPMC761); one (IPMC712)

Configuration: IPMC761: TTL to P2 (both ports), SIM

configurable on MVME761; IPMC712: EIA-232 to P2

Baud Rate, bps max.: 2.5M sync, 38.4K async

Oscillator Clock Rate (PCLK): 10 MHz/5 MHz

Asynchronous Serial Ports

Controller: 16C550 UART; 85230/8536

Number of Ports: Two (IPMC761); three (IPMC712)

Configuration: EIA-574 DTE (IPMC761);

EIA-232 (IPMC712)

Async Baud Rate, bps max.: 38.4K EIA-232,

115Kbps raw

Parallel Port

Controller: PC97307

Configuration: 8-bit bi-directional, full IEEE 1284

support; Centronics compatible (minus EPP and

ECP on MVME712M)

Modes: Master only

Power Requirements

(Additional power load placed on MVME5500 with

IPMC installed)

IPMC761 IPMC712

+5V: 0.5 A max. 0.5 A max.

+3.3V: 0.75 A max. 0.75 A max

DEMONSTRATED MTBF

Predicted MTBF 207,058 hours, calculated using

Bellcore Standard: Issue 6, Method 1, Case 3

Electromagnetic Compatibility (EMC)

Intended for use in systems meeting the following

regulations:

U.S.: FCC Part 15, Subpart B, Class A (non-residential)

Canada: ICES-003, Class A (non-residential)

Emerson board products are tested in a representative

system to the following standards, results pending:

CE Mark per European EMC Directive 89/336/EEC

with Amendments; Emissions: EN55022 Class B;

Immunity: EN55024

Safety

All printed wiring boards (PWBs) are manufactured

with a flammability rating of 94V-0 by UL recognized

manufacturers.

Ordering Information

Part Number Description

MVME55006E-0161 1 GHz MPC7457 PowerPC processor, 512MB SDRAM, Scanbe handles 6E

MVME55006E-0163 1 GHz MPC7457 PowerPC processor, 512MB SDRAM, IEEE handles 6E

Memory

RAM55006E-007 512MB memory mezzanine expansion card

Vibro-Meter ® VM600 CPUM and IOCN modular CPU card and input/output card

Vibro-Meter ® VM600 CPUM and IOCN modular CPU card and input/output card

WATLOWCLS200 Communications Specification Includes CLS200, MLS300 and CAS200

WATLOWCAS200 User’s GuideSystem Overview

CLS200 and MLS300 Cascade Control Setup and Tuning of CascadeFunctions

WATLOWCLS200, MLS300, and CAS200 Communications Specification

MotorolaMVME55006E Single-Board Computer Installation and Use

MotorolaPMC expansion combined with a high-performance VME processor

MotorolaMVME187 RISC Single Board Computer Installation Guide MVME187IG/D4

EMERSONMVME5500 Series VMEbus Single-Board Computer

schneiderFBM232 Field Device System Integrator Module, 10/ 100 Mbps Ethernet, Single PSS 41H-2S232

schneiderFBM232 Field Device System Integrator Module, 10/ 100 Mbps Ethernet, Single PSS 41H-2S232

schneiderFoxboro Evo™ Process Automation System Product Specifications

schneiderFBM232 Field Device System Integrator Module, 10/ 100 Mbps Ethernet, Single PSS 41H-2S232

Contact Us

MY ACCOUNT

PRODUCT

Menu

Search for products

Archives

Contact Us​

MY ACCOUNT

PRODUCT

Menu

Search for products

Contact Us