SIMATIC S5-115 CPU: Replace 232PCLR with 6ES5734-1BD20 Cable

David Krause10 min read
Serial CommunicationSiemensTroubleshooting
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

SIMATIC S5-115 CPU: Replacing the 232PCLR Current Loop Converter with a Siemens 6ES5734-1BD20 Programming Cable

The SIMATIC S5-115 CPU exposes its programming and online diagnostic port (SI1 / PG port) as a 20 mA TTY current loop on a 15-pin sub-D connector. The interface does not natively speak RS-232, RS-422, or USB. To attach a PC, an active converter is required between the PLC's TTY port and the PC's serial (or USB-to-serial) port. Field experience with third-party passive 232PCLR current-loop adapters on S5-115 hardware shows recurring failure modes: blown transmit/receive opto-isolators, intermittent handshaking, and silent loss of communication after a few hours of operation. The replacement path of choice is the Siemens 6ES5734-1BD20 programming cable, which integrates the TTY converter into the cable assembly itself.

Why the 232PCLR keeps failing: The 232PCLR is a generic 20 mA current loop to RS-232 converter. It relies on opto-isolated transmit and receive loops fed from the PLC side, with passive current sourcing from the host. The S5-115 port is sensitive to loop current polarity and to the absence of proper shielding on long cable runs. Field reports consistently indicate that the device works initially, then fails after several hours — a classic signature of thermal stress on the loop-side optocouplers when cable shielding or current limiting is inadequate.

1. Problem Definition and Communication Stack

The S5-115 uses the AS511 protocol on its serial interface (SI1) for programming, online status, and block upload/download. The lower layers are:

Layer Implementation
Physical 20 mA current loop (TTY), passive or active, full-duplex
Connector (PLC side) 15-pin Sub-D (male), Siemens pinout
Protocol AS511 (Siemens proprietary, 9.6 kbps default)
Host software STEP 5 (DOS), PG-2000, or S5W for Windows
Connector (PC side, native) DB-25 male (RS-232)

The TTY loop cannot be connected directly to an RS-232 port. An active converter — either a standalone box (232PCLR, Phoenix Contact PSM-ME-RSRS232/TTY-P) or an integrated cable (Siemens 6ES5734-1BD20, Classic Automation 10203) — is mandatory.

2. Siemens 6ES5734-1BD20 — The Canonical Replacement

The 6ES5734-1BD20 (also written 6ES5 734-1BD20) is the Siemens factory programming cable for the S5 family. It has the TTY converter built into the cable assembly, so no external converter box is required.

Parameter Value
Siemens order number 6ES5734-1BD20
Description SIMATIC S5 734-1 cable from PLC to PC, 15-pin to 25-pin
PLC-side connector DB-15 male (TTY 20 mA current loop)
PC-side connector DB-25 male (RS-232)
Cable length 3.2 m
Converter topology Integrated active TTY ↔ RS-232
Catalog status Discontinued from the A&D Mall; available through Siemens partners and surplus channels
Typical use Programming, online diagnostics, block transfer
Status note: The 6ES5734-1BD20 is no longer listed in the current Siemens A&D catalog. It can still be sourced via Siemens Solution Partners or through third-party industrial surplus distributors. Always verify the part label against the Siemens SIMATIC S5 spare-parts list before commissioning.

3. Third-Party Replacement Cables (Plug-Compatible)

Two drop-in replacements for the 6ES5734-1BD20 are documented in field service:

Vendor Part Number Interface Notes
Classic Automation 10203 DB-15 (TTY) to DB-25 (RS-232) Direct replacement for 6ES5734-1BD20
Classic Automation 10203USB DB-15 (TTY) to USB Same cable plus integrated USB-to-serial
Direct Logic 10203 DB-15 (TTY) to DB-25 (RS-232) Functionally identical drop-in

The 10203USB variant is preferred on modern hardware because no separate USB-to-serial adapter is required and the cable length is bounded. The legacy 10203 (DB-25) variant is appropriate only when paired with a known-good USB-to-serial adapter based on the FTDI FT232 or Prolific PL2303 chipset.

4. Phoenix Contact PSM-ME-RSRS232/TTY-P — Modular Alternative

For environments where the S5 must communicate with a modern operator panel (OP) or touch panel (TP) — rather than a programming PC — Phoenix Contact's PSM-ME-RSRS232/TTY-P converter module is the documented industrial solution. It supports both active and passive TTY operating modes and is DIN-rail mountable.

Parameter Value
Vendor Phoenix Contact
Part number PSM-ME-RSRS232/TTY-P
Function RS-232 ↔ TTY (20 mA) converter
Operating modes Active / passive TTY
Mounting DIN rail
Typical use S5-115 to modern OP/TP, SCADA gateways

5. CP 524 with RS-422 Com Module — When You Need More Than the SI1 Port

If the application requires RS-422 instead of RS-232 or TTY (longer distance, multi-drop, or noise immunity in a plant environment), an alternative is to install a CP 524 communications processor in the S5-115 rack and fit it with the RS-422 Com Module. The CP 524 handles serial protocols independently of the CPU and exposes either RS-232 or RS-422 depending on the inserted Com Module.

Module Function
CP 524 Serial communications processor for S5-115/-135/-150/-155
Com Module (RS-422) Pluggable physical interface for the CP 524
Use case Long-distance, multi-drop, or noisy plant floors where TTY is marginal
Configuration caveat: The CP 524 requires handshake block configuration in STEP 5 (e.g., FB 244 / FB 245 for send/receive). Plan for additional programming effort and verify rack slot compatibility with the CPU-115U variant in service.

6. Adapter Strategy: DB-25 to DB-9 and USB-to-Serial

The 6ES5734-1BD20 and the 10203 variants terminate at a DB-25 male on the PC side. Modern PCs no longer expose DB-9 RS-232 ports, and most no longer have DB-25 either. The bridging strategy is:

  1. DB-25 to DB-9 adapter: A passive gender-moulded adapter on the PC end of the cable, followed by a USB-to-serial adapter on the DB-9. Use only adapters with full shield bonding (the backshell must continue the cable shield through the adapter body).
  2. Direct USB cable: The 10203USB cable integrates both the DB-25-to-USB conversion and the RS-232-to-TTY conversion into one assembly. This is the preferred modern option.
  3. USB-to-serial chipset selection: Choose adapters based on FTDI FT232, Prolific PL2303, or Silicon Labs CP2102/CP2104. Avoid unbranded CH340-based adapters when working with STEP 5 under DOS or older Windows versions; they often lack proper DTR/RTS handshake buffering.

7. Cable Shielding and Length Constraints

The S5-115's TTY port is sensitive to both shield integrity and cable length. Two field-proven constraints apply:

  • Shielding must be continuous end-to-end. A cable that loses shield continuity through a passive DB-25-to-DB-9 adapter (because the adapter's backshell is plastic) introduces common-mode noise on the current loop, which manifests as intermittent communication dropouts after a few hours.
  • Cable runs should not exceed 3 m to 5 m for reliable TTY operation, particularly in panels with VFDs or other switching noise sources. The Siemens 6ES5734-1BD20 ships at 3.2 m for this reason.
Diagnostic clue: If communication works initially, then drops after a thermal cycle, suspect the loop-side optocoupler in the converter rather than the cable. If it drops immediately, suspect wiring, shield continuity, or protocol mismatch in the host software.

8. Host Software Configuration

The PC-side host software must be configured to match the AS511 protocol layer:

Parameter Setting
Baud rate 9 600 bps (default for AS511)
Data bits 8
Parity None
Stop bits 1
Handshake RTS/CTS or XON/XOFF (converter-dependent)
COM port Match the physical COM port exposed by the USB-to-serial driver

For STEP 5 operation, prefer running the host software under native DOS rather than inside a Windows DOS box. The original Siemens drivers were written against direct COM-port access; a virtualized DOS window can mishandle the timing-critical AS511 handshaking and produce spurious timeouts.

9. Step-by-Step Replacement Procedure

  1. Power down the S5-115 rack before touching the SI1 port. Although the TTY loop is current-limited, hot-plugging the loop can damage the optocouplers on the CPU's serial port.
  2. Disconnect and remove the 232PCLR converter and its associated cable from the S5-115 SI1 (DB-15) port.
  3. Inspect the S5-115 DB-15 socket for bent pins, contamination, or signs of overheating. Clean if necessary with isopropyl alcohol; do not use contact cleaners that leave residue.
  4. Connect the 6ES5734-1BD20 (or 10203 / 10203USB) cable's DB-15 end to the S5-115 SI1 port. Tighten the connector screws.
  5. Connect the PC-side end:
    • If using the DB-25 variant: attach a DB-25 to DB-9 adapter (shielded backshell) and then a USB-to-serial adapter based on FTDI/PL2303/CP2102.
    • If using the 10203USB variant: plug the USB end directly into the PC.
  6. Power up the S5-115 rack and confirm the CPU is in RUN or STOP as expected.
  7. Map the COM port: In Windows Device Manager, note the COM port number assigned to the USB-to-serial adapter.
  8. Configure STEP 5 / PG-2000 / S5W to that COM port at 9 600, 8N1.
  9. Initiate an online connection. The host software should report the CPU type (CPU 941, CPU 942, CPU 943, CPU 944, or CPU 945) and the program status.
  10. Verify block transfer by reading a known FB/DB and confirming the checksum or block header matches.

10. Verification and Commissioning Tests

After installing the replacement cable, run the following checks before declaring the workstation operational:

  • Cold-start loop test: Power-cycle the S5-115 rack three times in succession, re-establishing the online connection each time. Verify zero timeouts.
  • Block upload/download test: Upload all FBs and DBs, then download them back. Checksum must match exactly.
  • Force table test: Set and reset a known output via the force table and verify it propagates to the physical output module.
  • Soak test: Leave the connection idle but online for at least 4 hours. The 232PCLR failure mode was thermally triggered after hours of operation; if the replacement has not dropped by then, the failure mode is unlikely to recur.
  • Cable flex test: Gently flex the cable near both connectors during an online session. The connection should not drop; if it does, the connector backshell is not bonding the shield properly.

11. Long-Term Migration Path — S5-115 to S7-1500

If the underlying concern is broader fleet modernization, Siemens documents a serial-coupling path between a SIMATIC S5 and a SIMATIC S7-1500 via the S5's serial port. Refer to the official Siemens application example Serial communication between SIMATIC S5 and SIMATIC S7-1500 for the topology, block configuration, and parameterization. The same 6ES5734-1BD20 / 10203 cable is used on the S5 side, while the S7-1500 connects via its CM (communications module) RS-232 / RS-422 interface. This allows the S5-115 to remain operational while data is forwarded to a modern controller for SCADA or historian purposes.

Migration caveat: The S7-1500 side must be configured with the matching serial protocol block (e.g., PtP communication via Send_P2P / Receive_P2P). Baud rate and framing must match the S5's AS511 settings on the TTY side, with protocol translation handled in the S7-1500 user program. See the Siemens application example referenced above for the exact block parameterization.

12. Troubleshooting Matrix

Symptom Likely Cause Action
No communication at power-up Wrong COM port selected in host software Verify COM port in Device Manager; match to STEP 5 settings
Communication drops after hours Thermal failure of converter optocouplers Replace 232PCLR with 6ES5734-1BD20 or 10203
Intermittent drops during motion VFD noise on shield, unshielded adapter Use shielded backshell adapters or 10203USB
Timeout immediately on connect Protocol mismatch, wrong baud rate, wrong port Set 9 600 / 8N1; confirm SI1 vs CP 524
CPU type reported as unknown Cable polarity reversed or TTY loop open Inspect DB-15 pinout; verify 20 mA loop current
Works on one PC, fails on another USB-to-serial chipset incompatibility Use FTDI/CP2102-based adapter

13. Selection Decision Matrix

Scenario Recommended Solution
Direct PC-to-PLC programming, modern laptop 10203USB
Direct PC-to-PLC programming, legacy PC with DB-9 10203 (DB-25) + DB-25/DB-9 shielded adapter
Need original Siemens documentation 6ES5734-1BD20 (sourced from Siemens partner or surplus)
S5 to modern OP/TP or SCADA gateway Phoenix Contact PSM-ME-RSRS232/TTY-P on DIN rail
Long-distance (> 5 m), noisy plant floor CP 524 with RS-422 Com Module
S5 to S7-1500 migration 10203 / 6ES5734-1BD20 + S7-1500 CM module

Frequently Asked Questions

What is the Siemens replacement for the 232PCLR on a S5-115?

The official replacement is the Siemens 6ES5734-1BD20 programming cable, which integrates the TTY-to-RS-232 converter into the cable. Third-party drop-in equivalents are the Classic Automation 10203 (DB-25) and 10203USB (USB) cables.

Do I still need a separate converter when using the 6ES5734-1BD20?

No. The 6ES5734-1BD20 has the TTY converter built into the cable. You only need a DB-25-to-DB-9 adapter and a USB-to-serial adapter on the PC side, or use the 10203USB variant which integrates both stages.

Is the 6ES5734-1BD20 still available from Siemens?

No, it has been removed from the active A&D catalog. It can still be ordered through Siemens Solution Partners or obtained from industrial surplus distributors. Always verify the part label against the Siemens spare-parts list.

Which USB-to-serial chipset is recommended for STEP 5?

Use FTDI FT232, Prolific PL2303, or Silicon Labs CP2102/CP2104 based adapters. Avoid unbranded CH340-based adapters when running STEP 5 under DOS or older Windows versions, as they often lack reliable DTR/RTS handshake buffering.

Can the S5-115 communicate directly with an S7-1500 over serial?

Yes. Siemens documents the topology in the application example "Serial communication between SIMATIC S5 and SIMATIC S7-1500," using the S5's TTY port (via 6ES5734-1BD20 or equivalent) and an S7-1500 CM RS-232/RS-422 module, with protocol translation handled in the S7-1500 user program.

Back to blog