Description
Product Overview
The ProSoft Technology PLX32-MBTCP-SIE is an industrial communication gateway designed to exchange data between Modbus TCP/IP equipment and Siemens Industrial Ethernet PLCs. It is commonly used when a Schneider Electric programmable automation controller or another Modbus TCP device must share selected data with a Siemens controller without replacing either control platform. The gateway translates data between the two protocol environments, allowing established equipment to participate in a coordinated control architecture. It is a communication interface, not a standalone PLC, so the application still depends on correctly configured data mappings, network settings, and controller logic.
The ProSoft Technology PLX32-MBTCP-SIE provides two independently addressable Ethernet ports so each protocol can operate on a separate subnet. This arrangement can simplify integration where the existing Modbus TCP and Siemens networks use different IP ranges, avoiding the need to renumber connected devices simply to place them on one subnet. The gateway supports read and write data exchange with Siemens S7-200, S7-300, S7-400, S7-1200, and S7-1500 controllers, using data areas such as data blocks, inputs, outputs, flags, counters, and timers. The manufacturer also documents use with Siemens S5 controllers when an appropriate interface is available.
For commissioning and maintenance, the ProSoft Technology PLX32-MBTCP-SIE supports configurable data exchange and can use an optional SD card to store configuration files for recovery. The hardware operates from a 10–36 VDC supply, with a nominal 24 VDC supply, and is rated for ambient temperatures from −25°C to +70°C. Before replacing an installed gateway, verify the configuration file, firmware revision, IP settings for both ports, and PLC data mapping. Two Ethernet ports do not mean the gateway transparently bridges the networks; each port must be assigned to its intended protocol and a separate subnet.
Product Introduction
When a Modbus TCP controller needs to exchange process data with a Siemens PLC, protocol differences and separate IP networks can complicate commissioning. The ProSoft Technology PLX32-MBTCP-SIE provides a dedicated gateway between these systems, using two Ethernet ports to keep the protocol networks on separate subnets.
With support for Siemens S7-200 through S7-1500 families and up to 10,000 16-bit registers, it suits selected data-sharing tasks in industrial control systems. Confirm register mapping, PLC compatibility, and existing network configuration before installation.
Key Technical Specifications
| Parameter | Value |
|---|---|
| Product Model | PLX32-MBTCP-SIE |
| Manufacturer / Brand | ProSoft Technology |
| Product Type | Industrial protocol conversion gateway |
| Product Series | PLX32 |
| Protocol 1 | Modbus TCP/IP |
| Protocol 2 | Siemens Industrial Ethernet |
| Ethernet Ports | 2 independently addressable ports |
| Network Architecture | Each port must use a different subnet |
| Supported Siemens PLCs | S7-200, S7-300, S7-400, S7-1200, S7-1500 |
| Siemens Data Areas | DB, inputs, outputs, flags, counters, timers |
| Maximum Register Capacity | Up to 10,000 16-bit registers |
| Modbus Clients | Up to 10 |
| Modbus Servers | Up to 10 total across documented MBAP and encapsulated connections |
| Siemens Clients | Up to 20 |
| Supply Voltage | 10–36 VDC; 24 VDC nominal |
| Current Consumption | 300 mA at 24 VDC nominal; up to 610 mA over the specified supply range |
| Operating Temperature | −25°C to +70°C |
| Storage Temperature | −40°C to +80°C |
| Relative Humidity | 5–95% RH, non-condensing |
| Dimensions (H × W × D) | 136.7 × 50.5 × 111.3 mm |
| Configuration | ProSoft Configuration Builder software |
| Configuration Backup | Optional SD card |
| Firmware / Hardware Revision | Verify the installed unit |
| Protection Rating | Verify the model documentation and nameplate |
ProSoft Technology, Inc.+3
Integration note: The two Ethernet ports must be assigned to different subnets, and each port communicates using its designated protocol. The gateway is not a transparent Ethernet bridge between the two networks. Confirm the intended data flow and read/write permissions during configuration.
PLX32-MBTCP-SIE
Related Products
The following products provide related protocol-conversion or industrial networking functions. They are alternatives only when their protocol combinations match the application.
- PLX32-EIP-MBTCP — Connects EtherNet/IP systems with Modbus TCP/IP devices; suitable when the source network uses EtherNet/IP rather than Siemens Industrial Ethernet.
- PLX32-EIP-SIE — Connects EtherNet/IP with Siemens Industrial Ethernet; relevant when Allen-Bradley and Siemens systems need data exchange.
- PLX31-EIP-MBS — EtherNet/IP-to-Modbus serial gateway for applications involving serial Modbus equipment; not a direct substitute for a dual-Ethernet gateway.
- PLX31-EIP-ASCII — Connects EtherNet/IP controllers with ASCII devices such as barcode readers and weighing equipment.
- PLX32-MBTCP-SIE — The specified Modbus TCP/IP-to-Siemens Industrial Ethernet gateway; the appropriate model when these are the two required protocols.
- Siemens S7-1200 — PLC family supported for data exchange through the gateway.
- Siemens S7-1500 — PLC family supported for data exchange through the gateway.
- Siemens S7-300 — Legacy PLC family supported for data exchange through the gateway.
- Siemens S7-400 — PLC family used in larger control applications and supported for data exchange through the gateway.
Frequently Asked Questions
What does the ProSoft Technology do?
It exchanges data between Modbus TCP/IP devices and Siemens Industrial Ethernet PLCs. Engineers configure the required data mappings so selected values can be read or written across the two protocol environments.
Which Siemens PLCs are supported?
The documented supported families are S7-200, S7-300, S7-400, S7-1200, and S7-1500. Siemens S5 controllers may also be used with an appropriate interface. Verify the specific CPU, firmware, and data-access requirements before commissioning.
Can I connect both Ethernet ports to the same subnet?
No. The manufacturer specifies that the two independently addressable Ethernet ports must be configured on different subnets. Each port is assigned to its intended protocol network; the gateway does not transparently bridge traffic between them.
Can I hot-swap the while the PLCs are running?
Do not assume live replacement is supported. Replacing the gateway interrupts data exchange through that device and may affect dependent control logic. Review the process consequences, backup the configuration, and follow the site’s approved maintenance procedure before disconnecting power or network cables.
Does the support firmware v3.1?
A firmware version cannot be confirmed as compatible from the model number alone. Check the installed gateway’s hardware and firmware revisions against the relevant ProSoft documentation and configuration software. Back up the current configuration before any firmware change.
How can I replace a failed gateway without rebuilding the configuration?
If the existing configuration was saved, retrieve the approved configuration file and confirm that it matches the replacement unit’s firmware and hardware requirements. The gateway supports configuration backup using an optional SD card. After restoring settings, verify both IP addresses, subnet separation, PLC connections, register mappings, and read/write behavior.
How do I verify authenticity, condition, and warranty?
Check the manufacturer label, full model number, serial number, firmware or hardware revision, Ethernet connectors, and power terminals. Request actual-unit photographs and a functional test report where available. Ask the supplier to specify whether the unit is new, unused surplus, or used, and obtain written warranty terms rather than assuming factory coverage.
Procurement note: Before ordering a replacement, record the current gateway configuration, both Ethernet network settings, firmware revision, and PLC data mappings. A physically compatible unit may still require configuration validation before it can restore reliable data exchange.
