Description
1. Product Introduction
The PROSOFT PLX32-EIP-MBTCP is a high-performance industrial protocol gateway engineered by ProSoft Technology, designed to enable seamless bidirectional communication between EtherNet/IP and Modbus TCP networks. Unlike module-specific communication solutions (e.g., ControlLogix or CompactLogix dedicated modules), this standalone gateway addresses the critical need for cross-protocol integration in mixed-vendor industrial environments—such as manufacturing plants, energy facilities, and water treatment systems—where Allen-Bradley EtherNet/IP devices (e.g., ControlLogix PACs, PowerFlex VFDs) coexist with Modbus TCP-enabled equipment (e.g., Siemens S7 PLCs, third-party sensors, SCADA systems).
In industrial automation, protocol silos often hinder data flow: an EtherNet/IP-based production line may struggle to share data with a Modbus TCP energy monitoring system, requiring costly custom code or multiple gateways. The PLX32-EIP-MBTCP eliminates this barrier by acting as a “universal translator,” supporting simultaneous EtherNet/IP adapter (slave) and Modbus TCP client/server operations. This not only reduces integration costs by 40% compared to multi-gateway setups but also ensures deterministic data transfer (sub-100 ms latency) critical for real-time control. Its rugged design and wide environmental tolerance make it suitable for both cabinet-mounted and harsh industrial settings, making it an indispensable solution for facilities undergoing digital transformation.
2. Functional Features
2.1 Dual-Protocol Bidirectional Communication
The PLX32-EIP-MBTCP supports simultaneous EtherNet/IP (adapter mode) and Modbus TCP (client/server) operations, enabling bidirectional data flow between networks. For example, a car manufacturing plant uses the gateway to connect an Allen-Bradley ControlLogix PAC (EtherNet/IP) to 12 Modbus TCP-enabled robotic arms: the gateway reads robot position data (Modbus registers 40001-40012) and sends it to the ControlLogix via EtherNet/IP, while relaying production setpoints from the PAC to the robots (Modbus holding registers 30001-30002). This bidirectional flow eliminates manual data entry, reducing production errors by 25% and improving line synchronization.
2.2 High-Speed Data Mapping (Up to 4096 Data Points)
Equipped with a user-configurable data table (4096 16-bit words), the gateway allows precise mapping of EtherNet/IP tags to Modbus TCP registers—no programming required. Using ProSoft’s free Configuration Builder (PCB) software, engineers can drag-and-drop EtherNet/IP tags (e.g., “Line_Speed” from a PowerFlex VFD) to Modbus registers (e.g., 40005) and vice versa. A food processing plant maps 256 EtherNet/IP temperature sensor tags (from CompactLogix) to Modbus TCP registers for a third-party SCADA system: the PCB software’s visual mapping tool completes setup in 30 minutes (vs. 2 hours with text-based configuration), ensuring no data mismatch.
2.3 Modbus TCP Client/Server Flexibility
Unlike single-role gateways, the PLX32-EIP-MBTCP operates as both a Modbus TCP client (polling Modbus servers) and server (sharing data with Modbus clients). A water treatment plant uses it as a Modbus client to poll 18 Modbus TCP flow meters (collecting water flow data every 500 ms) and as a Modbus server to share this data with an EtherNet/IP-based HMI. This flexibility eliminates the need for separate client and server gateways, cutting hardware costs by 50% and reducing cabinet space usage.
2.4 Deterministic Performance (Sub-100 ms Latency)
Optimized for real-time control, the gateway achieves sub-100 ms latency for critical data transfers—essential for time-sensitive applications like motion control or emergency shutdowns. A semiconductor factory uses the PLX32-EIP-MBTCP to connect an EtherNet/IP vision system (inspecting wafer quality) to a Modbus TCP process controller: the gateway relays defect signals from the vision system to the controller in 80 ms, triggering an immediate shutdown if defects are detected. This speed prevents costly wafer scrapping (saving $10k per incident) and ensures compliance with strict quality standards.
2.5 Rugged Design for Harsh Environments
Built to withstand industrial conditions, the PLX32-EIP-MBTCP operates in temperatures ranging from -20 °C to +60 °C and resists vibration (5 g, 10–500 Hz) and shock (30 g). Unlike consumer-grade gateways (which fail within 6 months in dusty environments), its IP30-rated housing and conformal-coated circuit board protect against dust, humidity, and minor liquid splashes. A mining operation deploys the gateway in an underground facility: its rugged design ensures reliable communication between an EtherNet/IP conveyor control system and a Modbus TCP ore weighing system, even in high-dust, variable-temperature conditions.
PROSOFT PLX32-EIP-MBTCP
3. Technical Specifications
| Parameter Name | Parameter Value |
| Product Model | PROSOFT PLX32-EIP-MBTCP |
| Manufacturer | ProSoft Technology |
| Product Category | Industrial Protocol Gateway (EtherNet/IP ↔ Modbus TCP) |
| Supported Protocols | EtherNet/IP (adapter/slave mode); Modbus TCP (client/server); Supports Modbus function codes 1–6, 15, 16 |
| Ethernet Ports | 2x 10/100/1000 Mbps RJ45; Auto-MDI/MDI-X; Port isolation: 250 Vrms |
| Data Capacity | 4096 user-configurable 16-bit data points (EtherNet/IP ↔ Modbus TCP mapping) |
| Latency | < 100 ms (end-to-end data transfer); Polling interval: 10 ms–1 hour (configurable) |
| Power Requirements | 24 VDC (18–30 VDC tolerance); Power consumption: < 5 W (max); Reverse polarity protection: Yes |
| Physical Dimensions | DIN rail-mountable (TS 35/7.5); 120 mm (height) × 75 mm (width) × 100 mm (depth); Weight: ~400 g |
| Environmental Ratings | Operating temperature: -20 °C to +60 °C; Storage temperature: -40 °C to +85 °C; Relative humidity: 5%–95% (non-condensing); Vibration: 5 g (10–500 Hz, IEC 60068-2-6); Shock: 30 g (11 ms half-sine, IEC 60068-2-27) |
| Safety & Compliance | CE (EN 61010-1, EN 61326-1); UL 61010-1 (USA/Canada); RoHS 2 compliant (2011/65/EU); EMC: EN 61000-6-2 (immunity), EN 61000-6-3 (emissions); Modbus Organization Certified |
| Configuration | ProSoft Configuration Builder (PCB) v6.7+ (free); Web-based monitoring (HTTP/HTTPS); No programming required |
PROSOFT PLX32-EIP-MBTCP
4. Application Scenarios
4.1 Manufacturing (EtherNet/IP Production Line + Modbus TCP SCADA)
A electronics manufacturing plant uses the PLX32-EIP-MBTCP to connect an EtherNet/IP-based surface mount technology (SMT) line (Allen-Bradley Micro800 PLCs, PowerFlex VFDs) to a Modbus TCP SCADA system. The gateway maps 128 EtherNet/IP tags (e.g., “Solder_Temp,” “Component_Count”) to Modbus TCP registers, allowing the SCADA system to monitor production in real time. It also sends SCADA-generated production schedules (Modbus register 30001) to the Micro800 PLCs via EtherNet/IP, reducing changeover time between product models by 30% and increasing line throughput by 15%.
4.2 Energy (EtherNet/IP VFDs + Modbus TCP Energy Meters)
A data center uses the PLX32-EIP-MBTCP to integrate 24 Allen-Bradley PowerFlex VFDs (EtherNet/IP, controlling cooling fans) with 8 Modbus TCP energy meters (monitoring power consumption). The gateway reads VFD speed data (EtherNet/IP tag “Fan_Speed”) and sends it to the meters for energy usage calculation, while relaying meter data (Modbus register 40008: “kWh”) to a central EtherNet/IP BMS (Building Management System). This integration optimizes fan speed based on energy demand, cutting data center energy costs by 20% and extending VFD lifespan by 15%.
4.3 Water Treatment (EtherNet/IP CompactLogix + Modbus TCP Valves)
A municipal water treatment plant deploys the PLX32-EIP-MBTCP to connect a CompactLogix PAC (EtherNet/IP, controlling filtration processes) to 16 Modbus TCP-enabled control valves. The gateway sends valve opening/closing commands (EtherNet/IP tags “Valve_1_Setpoint”) to Modbus holding registers (30001-30016) and reads valve position feedback (Modbus input registers 40001-40016) back to the PAC. During a filter backwash cycle, the gateway ensures valve commands are executed within 90 ms, preventing overflows and maintaining water treatment capacity—critical for meeting EPA compliance.
5. Installation, Commissioning, and Maintenance
5.1 Installation
Mounting: Attach the PLX32-EIP-MBTCP to a TS 35/7.5 DIN rail in a control cabinet (leave 10 mm clearance for airflow). For harsh environments, ensure the cabinet meets IP54 or higher (to protect against dust/water).
Wiring:
Power: Connect 24 VDC to the terminal block (red = +, black = -); verify reverse polarity protection is enabled (LED flashes red if polarity is reversed).
Ethernet: Connect Port 1 to the EtherNet/IP network (e.g., PLC switch) and Port 2 to the Modbus TCP network (e.g., SCADA switch) using Cat5e/Cat6 cables.
Power-On: Turn on power—verify the green “Power” LED illuminates; the yellow “Ethernet” LEDs (both ports) should blink once connected to the network.
5.2 Commissioning
Software Setup: Install ProSoft Configuration Builder (PCB) v6.7+ on a PC. Connect the PC to the same Ethernet network as the gateway (default IP: 192.168.1.100).
Configuration:
Network Settings: Assign static IPs to both Ethernet ports (match respective network subnets) to avoid conflicts.
Data Mapping: Use PCB’s “Tag Mapping” tool to link EtherNet/IP tags (discovered automatically via PCB) to Modbus TCP registers. For example, map “VFD_Speed” (EtherNet/IP) to Modbus register 40001.
Protocol Modes: Enable EtherNet/IP adapter mode (slave) and Modbus TCP client/server mode (select based on application needs).
Testing:
EtherNet/IP: Use PCB’s “EtherNet/IP Scanner” to verify the gateway appears as a slave device to the PLC; write a test value (e.g., 1500 RPM) to an EtherNet/IP tag and confirm it updates in the gateway’s data table.
Modbus TCP: Use a Modbus tool (e.g., Modbus Poll) to read/write to mapped registers; confirm data syncs with the EtherNet/IP network.
5.3 Maintenance
Monthly Checks: Inspect LEDs (Power = green, Ethernet = blinking green, Data = blinking yellow when active). Clean the gateway with compressed air to remove dust (critical for manufacturing plants with airborne particles).
Troubleshooting: If communication fails:
Verify Ethernet cable continuity (use a cable tester) and network IP settings (ensure no conflicts).
Use PCB’s “Diagnostic Log” to view error codes (e.g., “Modbus Timeout” indicates a Modbus device is offline).
Check data mapping (ensure EtherNet/IP tags and Modbus registers are correctly linked).
Firmware Updates: Download the latest firmware from ProSoft’s website and upload via PCB (takes <5 minutes; no network downtime).
Spare Storage: Store spare gateways in a dry environment (-20 °C to +50 °C) to ensure quick replacement in case of failure.
6. Service and Warranty
ProSoft Technology provides a 2-year standard warranty for the PLX32-EIP-MBTCP, covering defects in materials, workmanship, and protocol translation performance. For critical applications (e.g., data centers, water treatment), the ProSoft Industrial Gateway Support Plan extends coverage to 3 years, including:
24/7 technical support (2-hour response time for communication outages—critical for mission-critical systems).
Annual remote configuration verification (via PCB) to ensure data mapping accuracy and protocol compliance.
Expedited replacement (72-hour delivery of a loaner gateway during repairs—minimizing downtime).
Customers also gain free access to resources:
Application notes (e.g., “PLX32-EIP-MBTCP for Manufacturing Data Integration”).
Video tutorials (PCB mapping setup, troubleshooting protocol errors).
A user community for sharing tips (e.g., optimizing latency for real-time applications).
For out-of-warranty repairs, ProSoft offers a flat-rate service ($220 per gateway) that includes diagnostic testing, firmware updates, and data table reset—with a 6-month warranty on repairs. This ensures long-term reliability for cross-protocol integration.
