Product Overview

The Honeywell 2MLL-PMEB is a PROFIBUS-DP Master Module for the MasterLogic-200 PLC platform. It provides a fieldbus communication interface between the PLC controller and distributed PROFIBUS-DP slave devices, allowing process information and equipment status to be exchanged over an industrial network.

Unlike conventional I/O modules that acquire individual electrical signals, the 2MLL-PMEB manages communication with networked devices. These may include remote I/O stations, motor drives, distributed control equipment, and other compatible PROFIBUS-DP devices.

One of its defining characteristics is support for PROFIBUS-DP V1. This extends the communication capabilities beyond the cyclic data exchange associated with DP V0 by supporting asynchronous acyclic communication services. In applications involving intelligent field devices, this distinction is useful when additional device parameters, diagnostic information, or configuration data need to be accessed.

The module uses an RS-485 electrical interface and shielded twisted-pair cabling for PROFIBUS-DP communication. It also supports automatic baud-rate detection, reducing the amount of manual communication-speed configuration required during network integration.

For example, in a manufacturing plant with several distributed drive systems and remote I/O stations, the 2MLL-PMEB can coordinate communication between the MasterLogic-200 controller and the connected field devices. The PLC processes the received information and uses it to coordinate machine sequences, equipment interlocks, and operating conditions.

The PMEB should not be confused with the 2MLL-PMEA. Although both belong to the MasterLogic-200 PROFIBUS-DP communication family, their protocol versions and supported communication functions differ.

Technical Specifications

Product Features

1. PROFIBUS-DP V1 Master Functionality

The 2MLL-PMEB supports PROFIBUS-DP V1, allowing the MasterLogic-200 PLC to communicate with compatible slave devices through cyclic and acyclic data exchange. This is particularly useful when an application requires access to both operating data and additional device information.

2. RS-485 Electrical Interface

The module uses an RS-485 physical interface with shielded twisted-pair cabling. This provides the electrical communication connection required for PROFIBUS-DP fieldbus installations.

3. Automatic Baud Rate Detection

Automatic baud-rate detection helps the module identify the communication speed used by the network. This simplifies network commissioning when integrating compatible PROFIBUS-DP equipment.

4. Sync and Freeze Functions

The Sync and Freeze functions support coordinated data handling across participating slave devices. They are useful in applications where multiple distributed I/O stations need to update or maintain their data according to a coordinated control sequence.

5. High-Speed Communication

The module supports communication speeds from 9.6 kbps to 12 Mbps. The selected speed depends on the network configuration, cable characteristics, and connected equipment.

6. Distributed Data Exchange

The module supports up to 244 bytes of input data and 244 bytes of output data per slave. This allows compatible network devices to exchange substantial process information with the PLC.

7. Acyclic Device Communication

DP-V1 supports asynchronous communication services in addition to cyclic process-data exchange. This allows supported devices to provide additional parameter and diagnostic information when requested.

8. Multiple Module Installation

The MasterLogic-200 Pnet architecture supports installation of up to 12 Pnet interface modules, subject to CPU configuration and system restrictions. This allows communication capacity to be expanded in larger automation installations.

Working Principle

The 2MLL-PMEB operates as the master interface of a PROFIBUS-DP network. It manages communication with configured slave devices and exchanges their process information with the MasterLogic-200 CPU.

During network initialization, the master establishes communication with the configured slave stations. The communication system checks the participating devices and prepares the data exchange according to the network configuration.

During normal operation, cyclic communication transfers process information between the master and slave devices. Input information from remote I/O stations, for example, becomes available to the PLC application, while output information can be transmitted to the connected equipment.

DP-V1 adds acyclic communication capabilities. This allows supported devices to exchange additional information, such as parameter data and diagnostic details, without relying exclusively on the regular cyclic process-data exchange.

The module also supports Sync and Freeze functions. These can be used to coordinate the handling of data across multiple participating devices.

Typical Communication Path:

MasterLogic-200 CPU → 2MLL-PMEB → RS-485 PROFIBUS-DP Network → Slave Devices → Remote I/O / Drives / Field Equipment

Example Industrial Operation:

1. A remote I/O station collects sensor signals from a production machine.
2. The slave device prepares its process data for network communication.
3. The 2MLL-PMEB receives the information through the PROFIBUS-DP network.
4. The received data becomes available to the MasterLogic-200 CPU.
5. The CPU evaluates the sensor information and checks programmed interlocks.
6. The PLC sends the corresponding output data to the networked equipment.
7. Additional device parameters or diagnostic information can be accessed through supported DP-V1 services.

Role in MasterLogic-200 Control Architecture

Within the MasterLogic-200 architecture, the 2MLL-PMEB serves as the PROFIBUS-DP master communication interface. Its role is different from that of local digital and analog I/O modules because it manages communication with distributed network devices rather than directly handling individual field wiring points.

The module is particularly useful when remote I/O stations, drives, and intelligent field devices are distributed across a production facility. Instead of bringing every individual signal back to the main PLC cabinet, equipment can exchange data through the PROFIBUS-DP network.

The MasterLogic-200 CPU remains responsible for application execution and control decisions. The PMEB manages the fieldbus communication, making the exchanged information available to the PLC application.

The following components belong to the broader MasterLogic-200 architecture. Individual hardware compatibility and supported communication services should be checked against the installed CPU configuration.

Industrial Applications

Installation and Maintenance

1. Verify the Module Model: Confirm that the installed unit is 2MLL-PMEB and distinguish it from the DP-V0 2MLL-PMEA variant.
2. Check CPU Compatibility: Verify the supported Pnet interface configuration for the installed MasterLogic-200 CPU. The available module count and communication services can vary between CPU models.
3. Inspect the Base Connection: Check the module’s installation position and ensure that its connection to the PLC base is secure.
4. Use Suitable Network Cable: Use shielded twisted-pair cable appropriate for the PROFIBUS-DP RS-485 network.
5. Check Network Topology: Follow the PROFIBUS-DP bus topology requirements and avoid unauthorized branch connections.
6. Verify Bus Termination: Ensure that termination is correctly applied at the two physical ends of the network segment.
7. Check Device Addresses: Assign unique PROFIBUS-DP addresses to all participating slave devices.
8. Verify Communication Speed: Confirm that the network devices support the selected transmission speed and that the installation meets the corresponding cable requirements.
9. Configure Slave Parameters: Use the appropriate PROFIBUS configuration software and device descriptions to establish the network configuration.
10. Check Data Mapping: Verify that the configured input and output data lengths match the requirements of each slave device.
11. Monitor Communication Diagnostics: Review module status and slave diagnostic information during commissioning and normal operation.
12. Maintain Network Records: Document slave addresses, device configurations, communication settings, cable arrangements, and diagnostic results for future troubleshooting.

Compatible System Components

Recommended Related Models

Key Advantages

• PROFIBUS-DP V1 master communication functionality.
• RS-485 electrical network interface.
• Automatic baud-rate detection.
• Supports Sync and Freeze functions.
• Communication speeds from 9.6 kbps to 12 Mbps.
• Maximum 244 bytes of input data per slave.
• Maximum 244 bytes of output data per slave.
• Supports up to 10 kB of master data.
• Supports cyclic and acyclic communication services.
• Integration with the MasterLogic-200 PLC architecture.

Technical FAQs

What is the difference between the 2MLL-PMEB and 2MLL-PMEA?

The main difference is the supported PROFIBUS-DP version. The 2MLL-PMEA supports DP-V0, while the 2MLL-PMEB supports DP-V1. DP-V1 adds acyclic communication services for accessing additional device parameters and diagnostic information.

Can the 2MLL-PMEB communicate with PROFIBUS-DP drives?

Yes, it can communicate with compatible PROFIBUS-DP slave devices, including supported motor drives. The drive must have a compatible PROFIBUS-DP interface, and its device configuration and data mapping must be included in the network setup.

What is the maximum data capacity supported by the 2MLL-PMEB?

The module supports up to 244 bytes of input data and 244 bytes of output data per slave. The documented maximum data size is 10 kB per master. Actual usable data capacity depends on the network configuration and connected slave devices.

Why is automatic baud-rate detection useful during commissioning?

Automatic baud-rate detection allows the module to identify the communication speed used by the PROFIBUS-DP network. This helps simplify network initialization, although the connected devices, cable installation, and overall network configuration must still meet the selected communication requirements.