ProSoft Technology PLX32-EIP-MBTCP

Technical Dossier

Product Details And Specifications

ProSoft Technology PLX32 Series Technical Notes

The Evolution of PLX32 Architecture

The PLX32 series succeeded ProSoft Technology's earlier AN-X and MVI series gateway cards, which required host PLC racks (Allen-Bradley, Modicon) for operation. The architectural shift to standalone Ethernet-based gateways reflected the industry transition from proprietary fieldbus topologies to Ethernet-centric plant networks during the 2010s. Early PLX32 units shipped with a single-port Ethernet interface and relied on static IP configuration via a dedicated USB configuration port and ProSoft Configuration Builder (PCB) software. Subsequent hardware revisions introduced dual Ethernet ports with independent IP addressing, enabling daisy-chain topologies without external switches — a critical feature for IEC 62443-compliant network segmentation. Firmware architecture uses a dual-processor design: one processor handles protocol stack execution while a second manages the internal data table and web server, preventing protocol timeouts during configuration changes. The PLX32 platform is now in a mature/sustaining lifecycle phase. ProSoft Technology continues to supply firmware updates and replacement units, but the architecture is not receiving new feature development. For new installations, ProSoft's PLX8x series (multi-port, higher throughput) is the designated successor. However, PLX32 units remain the correct replacement part for existing installations due to configuration file compatibility.

PLX32 Full Catalog & Functionalities (SKU List)

The following SKUs represent the verified PLX32 series production catalog, organized by protocol pairing. Each unit translates bidirectionally between the two named protocols unless otherwise noted.

EtherNet/IP & Modbus Variants

• PLX32-EIP-MBTCP: EtherNet/IP adapter/scanner to Modbus TCP client/server gateway — the subject SKU; supports up to 100 Modbus TCP connections.
• PLX32-EIP-MBS: EtherNet/IP to Modbus RTU/ASCII serial (RS-232/485) gateway; supports Master and Slave modes on serial port.
• PLX32-EIP-MBRTU: EtherNet/IP to Modbus RTU dedicated variant; optimized for high-speed serial polling of field instruments.
• PLX32-EIP-DFNT: EtherNet/IP to DF1 (Allen-Bradley serial) gateway; used for legacy SLC 500 and MicroLogix integration.
• PLX32-EIP-ASCII: EtherNet/IP to ASCII serial gateway; used for barcode readers, weigh scales, and custom serial devices.

Modbus TCP & Serial Variants

• PLX32-MBTCP-MBS: Modbus TCP to Modbus RTU/ASCII serial gateway; isolates Ethernet and serial Modbus segments.
• PLX32-MBTCP-DFNT: Modbus TCP to DF1 serial gateway; connects Modbus SCADA systems to Allen-Bradley SLC/MicroLogix PLCs.
• PLX32-MBTCP-ASCII: Modbus TCP to ASCII serial gateway; integrates non-standard serial devices into Modbus TCP networks.

PROFIBUS & PROFINET Variants

• PLX32-EIP-PDPS: EtherNet/IP to PROFIBUS DP Slave gateway; connects EtherNet/IP scanners to PROFIBUS DP master networks.
• PLX32-EIP-PDPM: EtherNet/IP to PROFIBUS DP Master gateway; allows EtherNet/IP PLCs to control PROFIBUS DP field devices.
• PLX32-MBTCP-PDPS: Modbus TCP to PROFIBUS DP Slave gateway; used in DCS-to-PROFIBUS integration projects.
• PLX32-EIP-PND: EtherNet/IP to PROFINET Device (IO-Device) gateway; integrates EtherNet/IP controllers into PROFINET IO systems.

DeviceNet & Other Fieldbus Variants

• PLX32-EIP-DNM: EtherNet/IP to DeviceNet Master gateway; manages DeviceNet I/O devices from an EtherNet/IP controller.
• PLX32-EIP-DNS: EtherNet/IP to DeviceNet Slave gateway; presents the PLX32 as a DeviceNet slave to an existing DeviceNet master.
• PLX32-MBTCP-DNM: Modbus TCP to DeviceNet Master gateway; connects Modbus TCP SCADA to DeviceNet field device networks.
• PLX32-EIP-CCLINK: EtherNet/IP to CC-Link gateway; used in Japanese and Asian automotive and process plants running Mitsubishi CC-Link networks.
• PLX32-EIP-HART: EtherNet/IP to HART Multiplexer gateway; aggregates HART instrument data into EtherNet/IP data tables for asset management systems.

Quality Control for the PLX32 Range

PLX32 units undergo a structured verification process at DriveKNMS before dispatch. Each unit is powered and connected to a test bench running ProSoft Configuration Builder (PCB) software. Firmware version is confirmed and updated if required. Protocol translation is verified by establishing live communication between a test EtherNet/IP scanner (emulated via RSLinx or equivalent) and a Modbus TCP server (emulated via Modscan or equivalent), confirming bidirectional data table read/write integrity. For units with serial ports (RS-232/RS-485), loopback and multi-drop polling tests are executed. The unit's web diagnostic interface is accessed to confirm all connection status indicators are nominal. MAC address, serial number, and hardware revision are logged against the shipment record. Units that fail any protocol handshake or show abnormal current draw are quarantined and not shipped.