The connection fails when a Modicon M340 uses a BMXNOE Ethernet module directly with an AB7832. The interfaces do not share an application protocol: the AB7832 uses EtherNet/IP on its Ethernet side, while BMXNOE supports Modbus/TCP rather than EtherNet/IP. Select a compatible architecture before configuring the Ramsey MT2000 data.
Connection architecture comparison
Two supported approaches resolve the protocol mismatch. The installed M340 Ethernet module and the preferred location for PROFIBUS configuration decide between them.
| Approach | M340 interface | PROFIBUS master path | Device file location | When to select it |
|---|---|---|---|---|
| EtherNet/IP gateway | BMXNOC0401 |
AB7832 to MT2000 |
AB7832 EDS in the M340 project; MT2000 GSD in the AB7832 configuration | Select when the AB7832 will remain and an EtherNet/IP-capable M340 module is available. |
| PROFIBUS Remote Master | Existing BMXNOE installation |
TCSEGPA23F14F to MT2000 |
MT2000 GSD in the PRM configuration | Select when the NOE is already installed and replacing the AB7832 is acceptable. |
Do not place BMXNOE, AB7832, and the MT2000 in one control path and expect configuration changes to bridge the mismatch. No EDS or GSD file can add EtherNet/IP capability to the NOE.
Recommended architecture
Before anything else, confirm which hardware must remain. If the installation already has BMXNOE, use the TCSEGPA23F14F PROFIBUS Remote Master and remove the AB7832 from the data path. This avoids purchasing BMXNOC0401 solely to provide EtherNet/IP connectivity.
If the AB7832 must remain, install and configure BMXNOC0401. The resulting path is:
M340 / BMXNOC0401 → AB7832 → Ramsey MT2000
The NOC resolves only the Ethernet-side protocol requirement. It does not configure the MT2000 automatically. Treat the installation as two separate exchanges:
| Exchange | Configuration object | Completion check |
|---|---|---|
| M340 to AB7832 | AB7832 EDS and EtherNet/IP I/O configuration | The M340 exchanges cyclic input and output data with the gateway. |
| AB7832 to MT2000 | MT2000 GSD and PROFIBUS network configuration | The gateway reports the MT2000 as an operational PROFIBUS slave. |
AB7832 commissioning procedure
Install
BMXNOC0401in the M340 configuration and assign the network settings required by the control network. Confirm that the engineering workstation and NOC can communicate before adding the gateway.Import the AB7832 EDS into the M340 programming environment, then add the gateway to the NOC EtherNet/IP configuration. Set the gateway address and cyclic I/O sizes from the AB7832 configuration. Do not move on until the NOC recognizes the gateway connection without a configuration-size mismatch.
Open the AB7832 configuration environment and import the Ramsey MT2000 GSD. Add the MT2000 as a PROFIBUS slave, select the modules represented by the GSD, and set the slave address to match the instrument.
Build the PROFIBUS input and output map. Record the byte offset, length, data direction, and data type for every value passed between the MT2000 and M340. The total PROFIBUS data lengths must fit the EtherNet/IP data areas configured for the AB7832.
Download the PROFIBUS configuration to the gateway. Confirm that the gateway accepts the configuration and establishes the MT2000 connection before testing PLC tags.
Map the NOC input and output data to M340 variables. Apply byte-order or word-order handling only after comparing raw gateway bytes with a known MT2000 value.
EDS and GSD ownership
The M340 sees the AB7832 as its Ethernet-side device; it does not directly enumerate the MT2000. Importing the AB7832 EDS into the PLC project is therefore correct, but it covers only the EtherNet/IP connection.
The MT2000 GSD belongs in the configuration of whichever component acts as the PROFIBUS master. With the gateway architecture, that component is the AB7832. With the PRM architecture, load the GSD through the TCSEGPA23F14F configuration path.
| File | Describes | Does not configure |
|---|---|---|
| AB7832 EDS | EtherNet/IP identity and I/O interface presented to the M340 | MT2000 PROFIBUS modules or slave address |
| MT2000 GSD | PROFIBUS capabilities and selectable cyclic data modules | M340 EtherNet/IP scanning |
A common commissioning error is matching only the total byte count. Also verify direction and ordering: PROFIBUS inputs from the MT2000 must arrive in the gateway area exposed as inputs to the PLC, while PLC commands must follow the reverse path.
PRM DTM communication recovery
For a TCSEGPA23F14F installation using Unity Pro 13 and the PROFIBUS Remote Master V1.3 package, a DTM message stating that no response was received at the default IP address indicates that engineering communication with the PRM has not been established. A solid STS indication and blinking SF can occur together: the operational network has assigned an IP address through the I/O scanner, but the PRM still has no valid PROFIBUS configuration.
Read the address assigned to the PRM from the M340 I/O-scanner or DHCP configuration. Confirm the assigned address rather than continuing to target an assumed default address.
Place the engineering workstation on a network path that reaches that address. Check its subnet selection, adapter binding, routing, and duplicate-address status. Confirm basic IP reachability before opening the DTM.
Set the DTM communication target to the PRM address actually assigned by the controller. If the DTM workflow requires initial access at the device default address, temporarily connect through the required commissioning network arrangement, then apply the operational settings.
Connect with the DTM and load a configuration containing the MT2000 GSD, slave address, baud-rate selection, and module layout required by the instrument. Use the values selected in the device manuals and project configuration rather than inferred defaults.
Download the PRM configuration and restart communication through the normal engineering workflow. Do not move on until
SFno longer indicates the missing-configuration condition.
Layered verification
Verify the Ethernet layer first. With the gateway path, confirm the
BMXNOC0401-to-AB7832 EtherNet/IP connection. With the PRM path, confirm that the assigned PRM address is reachable and that the DTM is online.Verify the PROFIBUS layer independently. Confirm that the MT2000 slave address matches the master configuration and that the selected GSD module layout matches the instrument setup.
Monitor raw input bytes while applying a known change at the MT2000. Identify the exact bytes that change, then validate signedness, scaling, byte order, and word order before converting the value into engineering units.
Test outputs with a controlled command permitted by the process. Confirm the PLC value changes the intended gateway bytes and that the MT2000 receives the corresponding PROFIBUS output.
Power-cycle or restart the participating equipment using the approved commissioning sequence. Confirm that address assignment, EtherNet/IP communication, PROFIBUS operation, and mapped data all recover without an engineering workstation connection.
Frequently asked questions
Why does BMXNOE not connect to an AB7832?
The AB7832 requires EtherNet/IP on its Ethernet side, while BMXNOE provides Modbus/TCP rather than EtherNet/IP. Use BMXNOC0401 with the gateway or replace the gateway path with TCSEGPA23F14F.
Why does the M340 see only the AB7832?
The M340 communicates with the gateway as its Ethernet device. The AB7832 separately operates the PROFIBUS network and exchanges mapped cyclic data with the MT2000.
Why does the MT2000 GSD go into the AB7832?
The GSD describes the PROFIBUS slave and belongs in the PROFIBUS master configuration. When the AB7832 is the master-side gateway, import the MT2000 GSD there, not in the M340 EtherNet/IP configuration.
Why does the PRM DTM report no response at the default IP address?
The DTM is targeting an address it cannot reach or the PRM is operating at the address assigned through the I/O-scanner or DHCP configuration. Read the assigned address, establish IP reachability, and point the DTM to the active commissioning address.
Why does PRM show blinking SF with solid STS?
A solid STS can show that the PRM received its IP address while blinking SF indicates that the PROFIBUS configuration is still missing. Download the configuration, confirm the MT2000 reaches the operational PROFIBUS state, and perform the final power-cycle test to verify automatic recovery.