S7-200 to S7-1200 Ethernet Communication via Gateway Module
In modern industrial automation, connecting legacy serial-based PLCs to newer Ethernet-enabled controllers is a common challenge. The Siemens S7-200, a workhorse in many factories, relies on RS485 and the PPI protocol, while the S7-1200 uses Profinet over Ethernet. Bridging these two worlds requires a specialized gateway that can translate protocols and physical interfaces without disrupting existing programs.
A dedicated Ethernet module designed for the S7-200 solves this problem by providing a transparent communication channel. It plugs directly into the PPI port and offers an RJ45 Ethernet interface, allowing the S7-200 to appear as a standard TCP/IP node on the network. This approach eliminates the need for complex wiring changes or program modifications on the legacy PLC.
Typical Application Scenario
Consider a production line where older machines are controlled by S7-200 PLCs, and a new section is added with S7-1200 controllers. To achieve centralized monitoring and coordinated control, data must flow between these systems. The gateway module acts as a bridge, enabling the S7-1200 to read process values (temperature, pressure, speed) from the S7-200 and send back commands or setpoints.
This integration is non-invasive: the S7-200 program remains untouched, and the module handles all protocol conversion. The S7-1200 simply communicates via standard Ethernet using the S7 communication protocol (PUT/GET or BSEND/BRCV).
Hardware Connection Setup
Step 1: Connect the gateway module’s DB9 female connector (X1) to the S7-200’s PPI port using a standard programming cable.
Step 2: Connect the module’s Ethernet port to an industrial switch. The S7-1200 also connects to the same switch, forming a local network.
Step 3: Power the module (typically 24V DC) and ensure all link LEDs are active.
The physical wiring is straightforward, but proper IP addressing is critical. The gateway module, S7-1200, and any engineering PC must be in the same subnet (e.g., 192.168.1.x).
Software Configuration in TIA Portal
The S7-1200 side requires configuration in Siemens TIA Portal. No changes are needed in the S7-200 program (Micro/WIN). The gateway module itself is configured via a dedicated PC tool, where you define data exchange rules.
Gateway Module Configuration Steps
- Launch the configuration software and search for the module on the network. Select it and choose “Modify Device Parameters”.
- Create a new client connection: right-click on “Data Exchange” and add a client. Set the remote server IP to the S7-1200’s address (e.g., 192.168.1.178), port 102, and timeout (default 10s).
- Configure TSAP settings. The local TSAP can be any value; the remote TSAP depends on the S7-1200’s slot and rack. Common values are 01 00/01, 02 00/01, etc. (see table below).
- Define data exchange commands: specify source and destination areas. For example, read DB100.DBW0 from S7-1200 and write to DB1.DBW100 in S7-200 (or vice versa). Set transfer size (e.g., 5 words) and timeout (2s).
- Validate the command with the “Check” button and confirm.
| Local TSAP (Gateway) | Remote TSAP (S7-1200) |
|---|---|
| Any | 01 00/01 |
| Any | 02 00/01 |
| Any | 03 00/01 |
S7-1200 TIA Portal Setup
In the TIA Portal project, add the S7-1200 CPU and configure its Ethernet interface with a fixed IP address. No special communication instructions are needed if the gateway module initiates the data transfer. However, if the S7-1200 must actively read/write, use the “PUT” and “GET” instructions (or “TSEND_C”/”TRCV_C” for TCP) in the user program. Ensure that the “Permit access with PUT/GET communication” option is enabled in the CPU properties (under Protection & Security).
Data Exchange Example
A typical command might map S7-200 V-memory to S7-1200 data blocks. For instance:
- Read from S7-200: Local station address 2, DB1 (corresponds to V-area), offset 100, length 10 words → Remote (S7-1200) DB100, offset 0.
- Write to S7-200: Remote DB101, offset 0 → Local DB1, offset 200, length 5 words.
The gateway module continuously exchanges data based on these commands, with cycle times typically under 50 ms for small data blocks.
Benefits and Practical Considerations
No changes to existing S7-200 code or wiring. The module transparently converts PPI to Ethernet.
Multiple S7-200 PLCs can be networked using one module per PLC, all accessible from a central SCADA or S7-1200.
Industrial-grade design with wide temperature range and electrical isolation ensures stable operation in harsh environments.
Troubleshooting Common Issues
If communication fails, check the following:
- Verify IP addresses and subnet masks. Use ping to test basic connectivity.
- Ensure the S7-1200 has PUT/GET access enabled (default is disabled in newer firmware).
- Check TSAP settings: the remote TSAP must match the S7-1200’s slot (usually 0 for CPU) and rack (0). Common values are 01 00 for slot 1, 02 00 for slot 2, etc.
- Confirm that data block numbers and offsets exist in both PLCs and are not optimized (S7-1200 DBs must have “Optimized block access” disabled for absolute addressing).
- Monitor the gateway module’s diagnostic LEDs: a solid link light and flashing activity light indicate normal operation.
Compatibility with HMIs and SCADA
The same gateway module can also connect S7-200 PLCs to Ethernet-based HMIs, such as Siemens Comfort Panels or third-party touchscreens. By assigning the module an IP address, the HMI can directly access S7-200 tags using the S7-200 driver over TCP/IP. This eliminates the need for serial cables and extends the communication distance.
For SCADA systems, the module supports standard OPC servers via the S7 protocol, making it easy to integrate legacy equipment into Industry 4.0 applications.
Note: Always follow proper grounding and shielding practices when installing communication modules in industrial control panels. Use shielded Ethernet cables and ensure the 24V power supply is stable to avoid intermittent faults.
By deploying an Ethernet gateway module, system integrators can extend the life of existing S7-200 installations while seamlessly incorporating modern S7-1200 controllers. This approach saves time and cost compared to full hardware upgrades, and it provides a clear migration path toward fully networked automation systems.
