Emerson DeltaV Distributed Control System MX Controller

INTRODUCTION

The MX controller provides communication and control between ffeld devices and other nodes on the control network. Control strategies and system configurations created on earlier DeltaV™ systems can be used in this powerful controller.The MX controller has all the features and functionality of the MD Plus controller, but twice the capacity.

The control language implemented in the controller is described in the Control Software Suite product data sheet.

Advantages

Right-Sized Controller

The MX controllers complement the MQ controllers by providing a larger capacity controller for applications requiring greater control capability:

2 X control capacity

2 X user configurable memory

2 X DST counts

DeltaV™ MX controllers and DeltaV I/O subsystems are easy and quick to install.

Post change. You can easily upgrade an MQ controller to an MX to handle project scope changes later in the project The MX has the same installed footprint as an MQ controller, but twice the performance. Simply replace the MQ with the MX, and then

All existing configurations, documentation, and hardware design remain intact.

Redundant Architecture: MX controllers support 1:1 redundancy for increased availability. Existing MD/MD Plus or MQ controllers are upgradable and powerful online!

Increased Productivity

Self-addressing.The DeltaV controller is unique in its ability to automatically identify itself within the DeltaV control network.

When the controller is powered up, it is automatically assigned a unique address - no dip switches, no connections - plug and play!

Automatic Location. The physical location of the controller is easy to find.

LEDs on the face of the controller can flash to provide a strong visual cue.

Automatic I/O Detection. The controller recognises all I/O interface channels on the subsystem. As soon as an I/O interface is plugged in, the controller knows the general characteristics of the ffeld device managed by that I/O interface. This reduces the worthless engineering associated with configuration - simple!

Connection to electronic commissioning and wireless I/O.

Starting with DeltaV v14.3. CHARM and wireless devices connected via the CHARM I/O card (CIOC) and the Wireless I/O card (WIOC) can be assigned to the MX controller.

This makes it easier than ever to add I/O to existing controllers by simply adding a CIOC and/or WIOC to the DeltaV zone control network.

Easy to Use

The DeltaV controller manages all control activities for the I/O interface channels and all communication functions with the zone control network.

The DeltaV controller manages all control activities on the I/O interface channels and all communication functions with the area control network. Sequential control function block diagrams, sequential function diagrams, and phasing logic provide powerful control structures that are further enhanced by user-defined structured text algorithms. The controller time stamps alarms and events to accurately record the sequence of events. The controller executes your control strategy at a rate of 100 milliseconds and transmits up to 4000 abnormal values per second.

Data Protection. All online changes made to control parameters are automatically stored for later upload to the engineering database. In this way, the system always keeps a complete record of all data changed online.

Cold start. This function automatically restarts the controller in the event of a power failure. Since the entire control strategy is stored in the controller's NVM RAM, the reboot is completely autonomous. Simply set the controller's reboot state to the current condition.

Flexibility to meet your needs

MX controllers can handle DeltaV batch options as well as advanced control functions.

The MX controller uses the same I/O subsystem as the MD Plus or MQ controller, but with a larger CPU and memory capacity. It is primarily used to configure large devices on a single controller node, which previously required two MD Plus or MQ controllers.

Previously, two MD Plus or MQ controllers needed to be combined into a single controller due to CPU, memory, or DST limitations.