Schneider Modicon M340: EtherNet/IP Scanner Setup for Factory Automation

Q: What Does EtherNet/IP Scanner Enable on Schneider Modicon M340?

Schneider Modicon M340 supports EtherNet/IP scanner functionality, enabling direct communication with Allen-Bradley devices including remote I/O and drives. The Schneider Modicon BMX NOE0100 Ethernet Module provides the EtherNet/IP scanner interface, supporting both implicit (cyclic I/O) and explicit (parameter access) messaging. The Schneider Modicon BMXNOE0110 Ethernet TCP/IP Network Module provides the enhanced Ethernet interface for M340 systems requiring additional network services alongside EtherNet/IP scanning.

Q: How Do I Install and Configure the BMX NOE0100 Module?

• Step 1: Install the BMX NOE0100 in an available M340 rack slot.
• Step 2: Connect the Ethernet cable to the module front port.
• Step 3: Configure the IP address, subnet mask, and gateway parameters in Unity Pro software.
• Step 4: Verify network connectivity with a ping test from the engineering station to the module IP address.

Configure the EtherNet/IP scanner function: enable the scanner service in module configuration and set the RPI (Requested Packet Interval) values for each adapter device. Typical RPI ranges from 10 ms to 100 ms — balance speed requirements with network bandwidth.

Q: How Do I Import EDS Files and Configure Adapter Devices?

• Step 1: Download EDS files for Allen-Bradley devices from the Rockwell website. Install files in the Unity Pro EDS library.
• Step 2: Add adapter devices to the scanner device tree in Unity Pro. Configure device IP addresses and connection parameters.
• Step 3: Configure the input and output assembly sizes for each adapter device matching device expectations.
• Step 4: Map assembly data to M340 word addresses. Verify data alignment and byte ordering — Allen-Bradley uses Little-Endian while Schneider uses Big-Endian for some data types.

Q: How Do I Configure Explicit Messaging for Parameter Access?

Use MSG instructions in ladder logic for explicit messaging. Set the message type to CIP Generic. Define the service code for read (0x0E) or write (0x10) operations. Configure the target class and instance attributes per the device EDS file.

Explicit messaging adds network overhead — use implicit I/O connections for time-critical data and reserve explicit messaging for configuration and diagnostics. Monitor message execution times carefully and handle timeout conditions gracefully in program logic.

Q: How Do I Diagnose EtherNet/IP Communication Faults?

• Step 1: Check module status LEDs on the BMX NOE0100. Green LED indicates active communication. Flashing red shows configuration or connection errors.
• Step 2: Monitor scanner status in Unity Pro online diagnostics view.
• Step 3: Verify each adapter device shows online status in the scanner tree.
• Step 4: Review error counters for each connection. Increasing error counts indicate network issues or device configuration mismatches.

What Is the Key Action Advice?

Install EDS files correctly for each device type before adding them to the scanner configuration. Set RPI values based on application requirements — avoid setting all devices to minimum RPI as this saturates network bandwidth. Use implicit messaging for real-time I/O data and explicit messaging only for configuration and diagnostics. Document all device IP addresses and assembly mappings in the site I/O database. For critical applications, consider redundant Ethernet modules. Partner with certified integrators for complex multi-vendor EtherNet/IP projects.

Author: Luo Xin is an industrial automation engineer with over 10 years of experience in PLC, DCS, and control systems.