Resolving Siemens PC Adapter Error 13:4542 on S7-300/400 Systems

Problem Description: Error 13:4542 on SIMATIC S7-300/400

When attempting to establish an online connection from a STEP 7 V5.x programming station (SIMATIC Manager) to a SIMATIC S7-300 or S7-400 CPU using the SIMATIC PC Adapter USB A2 (Siemens order number 6GK1571-0BA00-0AA0), the engineering workstation displays the dialog:

The programming device/PC could not be established.
Error 13:4542

The accompanying dialog box offers three diagnostic paths:

1. The cable is plugged in and the drivers are functional.
2. An incorrect node (MPI / PROFIBUS) address was specified under the PG/PC interface assignment.
3. The interface between the PC and the programming device is not correctly configured.

When cable integrity is confirmed, the failure is concentrated in the second and third items. The root cause is rarely a single setting; it is a chain of four independent conditions that must all be true: a valid Windows USB device stack, a properly installed SIMATIC device driver, a correctly assigned PG/PC interface, and a node address that matches a live bus participant on a properly terminated MPI or PROFIBUS segment. Any one of these conditions failing produces error 13:4542 with the same dialog, which is why the message is often misinterpreted as a "cable problem" when it is really a stack problem.

Root Cause Matrix: Why the Adapter Fails to Go Online

Across field service reports on mixed S7-300/S7-400 installations, the failure mode for 13:4542 collapses into six reproducible root causes, in order of frequency:

Genuine Siemens PC Adapter USB A2 vs. Cloned Adapters

Siemens ships the SIMATIC PC Adapter USB A2 under MLFB 6GK1571-0BA00-0AA0. The device converts USB 1.1/2.0 to RS-485 isolated MPI/PROFIBUS/PPI and ships with a SIMATIC-branded 9-pin D-sub connector and termination switch. The firmware on the integrated Siemens ASIC (S7DOS / Softnet dongle replacement) is signed and will not load on third-party silicon.

Clone adapters frequently rebadge the same order number on the housing. Three telltale signs indicate a clone:

1. USB VID/PID mismatch. Genuine adapter enumerates as VID 0x0908 PID 0x0001 or, in newer revisions, the Siemens Softnet PID block. A clone often enumerates as an FTDI FT232 (VID 0x0403 PID 0x6001) or as VID 0x10CF / 0x8101 (VPC3+C). Windows will assign a generic USB-Serial driver, and the S7DOS Helper Service will reject the device because the INF does not match.
2. No bus-parameter broadcast. Genuine adapters transmit a passive bus-parameter message frame (FUN=0x80) every 200 ms, allowing STEP 7 to auto-detect the active profile. Clones that do not implement this frame cause the dialog: "The bus parameters could not be determined automatically. There are no stations on the bus that are sending bus parameter message frames."
3. Hardwired PROFIBUS connector without termination switch. Many clones ship with a non-Siemens 9-pin connector that lacks the integrated termination resistor network and slide switch. Plugging such a connector into a live segment distorts the bus and intermittently kills the entire segment, not just the engineering PC.

Driver Stack Verification on Windows

The PC Adapter USB A2 requires the SIMATIC device driver stack, which is installed with STEP 7 V5.5 / V5.6 (or the standalone PC Adapter driver package). The driver is registered as the S7DOS Helper Service under the Windows Service Control Manager and provides the kernel-mode S7USB driver that maps the adapter to a virtual COM-style device object.

1. Open Device Manager (devmgmt.msc) and expand SIMATIC S7 Device Drivers → SIMATIC PC-Adapter USB. The entry must show a green icon. A yellow bang with code 39 ("Windows cannot load the drivers required for this device") indicates a missing or rejected driver.
2. Open services.msc and confirm S7DOS Helper Service is set to Automatic and is Running. If the service will not start, the driver DLL is unregistered; reinstall with D:\Drivers\PC_Adapter\Setup.exe from the STEP 7 installation media or run the Siemens SIMATIC PC Adapter USB A2 support package from the manufacturer support portal.
3. Check the registry key HKLM\SOFTWARE\Siemens\S7DOS\Devices. A genuine adapter registers a subkey with the matching USB serial number. The absence of this key after a successful plug-in confirms a non-genuine unit.
4. Verify that no third-party USB-Serial driver (FTDI, CP210x, Prolific) is bound to the same VID/PID. A clone can be temporarily forced to enumerate, but STEP 7 will still reject the device because the Softnet/S7DOS handshake fails.

PG/PC Interface Configuration in STEP 7 V5.5

The PG/PC interface is the Windows-level assignment that maps the access point S7ONLINE (used by all STEP 7 online operations) to a physical interface. Misconfiguration is the single most common cause of 13:4542 on otherwise good hardware.

1. Open Start → SIMATIC → STEP 7 → Set PG/PC Interface (or run SIMATIC Manager → Options → Set PG/PC Interface).
2. Select PC Adapter (Auto) as the Interface Parameter Assignment Used. The Auto variant lets the adapter broadcast bus parameters and let STEP 7 select the matching profile (MPI at 187.5 kbps or PROFIBUS at 1.5/3/6/12 Mbps).
3. Click Properties and configure the following tabs:

4. Apply, close, and re-open SIMATIC Manager so the new access-point binding is read by S7ONLINE.

MPI / PROFIBUS Node Address Resolution

Each device on an MPI or PROFIBUS segment must carry a unique node address. The address is set either with rotary switches on the CPU (S7-300), via DIP switches inside the PROFIBUS connector (older hardware), or with the CPU's HW Config → Properties → MPI/DP interface. For a typical S7-300/400 mixed network:

To discover the live address when no documentation is available:

1. In SIMATIC Manager, choose PLC → Accessible Nodes (or Target System → Accessible Nodes). STEP 7 sweeps the address range 0-HSA at the configured baud rate and lists all responding nodes.
2. If the sweep returns nothing, set the PG/PC interface to PC Adapter (MPI) at 187.5 kbps and try again. Most S7-300/400 MPI networks ship at the 187.5 kbps default.
3. If the sweep still returns nothing, switch to PC Adapter (PROFIBUS) at 1.5 Mbps. The same physical wire can carry MPI or PROFIBUS depending on what the CPU port is configured for; the wrong profile selection produces a perfectly silent bus.

Bus Parameter Detection Failure

When STEP 7 returns "The bus parameters could not be determined automatically. There are no stations on the bus that are sending bus parameter message frames", the PC Adapter is online (drivers are loaded) but no device is publishing the periodic bus-parameter frame. This frame is broadcast every 200 ms by:

• Any active PROFIBUS DP master (CPU with DP master interface, CP 342-5, CP 443-5, ET 200S IM, etc.)
• The PC Adapter itself when set to PC Adapter (Auto)
• A passive bus-parameter server, normally the DP master

1. No CPU is powered, or the CPU is in STOP-with-no-DP-master, or the CPU is in startup with OB100 not yet releasing DP.
2. Termination failure: a missing terminator at the far end of the segment allows reflections that corrupt the bus-parameter frame even though the bus is wired.
3. The PC Adapter profile is pinned to a non-default speed (e.g., 12 Mbps) on a 187.5 kbps MPI segment. Force the profile manually to MPI / 187.5 kbps in PG/PC properties and retry.

Physical Layer and Bus Termination

RS-485 MPI and PROFIBUS require termination at both physical ends of the segment. The standard terminator network inside a Siemens 9-pin PROFIBUS connector is:

• 220 Ω between pins 3 (RxD/TxD-P, line B) and 8 (RxD/TxD-N, line A)
• 390 Ω pull-up from pin 8 (line A) to +5V (pin 6, isolated VP)
• 390 Ω pull-down from pin 3 (line B) to GND (pin 5, isolated DGND)

A slide switch on the Siemens connector engages this network. Engage termination only on the two end devices (typically the first and last connector in the daisy chain). Engage it on a middle device and the entire segment collapses.

Step-by-Step Recovery Procedure

Use this sequence in order. Do not skip steps; each one rules out a class of failure before you reach the next.

1. Verify cable identity. Open the housing or look for the Siemens 6GK1571-0BA00-0AA0 label and the S7DOS-approved logo. If the cable is a clone or carries a different order number, replace it before continuing.
2. Reinstall the S7DOS driver. From the STEP 7 installation media, run \Drivers\PC_Adapter\Setup.exe as Administrator. Reboot. Confirm SIMATIC S7 Device Drivers in Device Manager shows SIMATIC PC-Adapter USB with no warnings.
3. Reset PG/PC interface. In Set PG/PC Interface, delete any old PC Adapter entries and re-create PC Adapter (Auto). Assign it to the access point S7ONLINE (the access point STEP 7 uses for all online operations; for routing across networks, also assign it to S7_ROUTE).
4. Run Accessible Nodes. SIMATIC Manager → PLC → Accessible Nodes. If the CPU appears, you are online; the original 13:4542 was a transient mismatch.
5. Discover the live profile. Open PC Adapter (Auto) → Properties → MPI/DP Diagnostics. STEP 7 will list every node it can see, the active baud rate, the HSA, and the bus profile. Use this output to populate the manual settings.
6. Pin the profile. Once you know the active profile (for example, MPI 187.5 kbps with HSA 31), set the PG/PC interface to PC Adapter (MPI) and 187.5 kbps rather than Auto. Pinned profiles are more reliable for daily engineering work because Auto adds a 5-10 s handshake per connection attempt.
7. Verify the target address. If the CPU does not appear in Accessible Nodes but the bus is live, the CPU may be at an address other than 2 (for example, on a project that has been re-addressed). Open PLC → Properties on the offline project to read the configured address, or sweep the bus with STEP 7's broadcast search.
8. Check termination and cable length. Confirm the first and last connector in the segment have termination engaged. Segment length must not exceed the PROFIBUS limit for the active baud rate: 1,200 m at 93.75 kbps, 1,000 m at 187.5 kbps, 400 m at 500 kbps, 200 m at 1.5 Mbps, 100 m at 3-12 Mbps.

Verification and Commissioning

After every change, run the following three-step verification:

1. Online node discovery. SIMATIC Manager → PLC → Accessible Nodes should list the target CPU within 5-10 s with a green checkmark. The MAC and MPI/DP address are shown next to the node.
2. CPU diagnostic buffer read. Open the online project, right-click the CPU → PLC → Diagnostics/Settings → Diagnostic Buffer. The buffer should be free of bus faults. If the buffer shows "DP bus fault" or "MPI bus fault, station failure," the physical layer is still compromised and the CPU cannot handshake even though the PC Adapter can.
3. Project upload integrity check. After uploading, compare the offline System Data blocks (SDB) with what the CPU reports under PLC → Compare Blocks. A successful online/offline match with no error in the diagnostic buffer confirms end-to-end health of the PC Adapter, the bus, and the CPU.

Troubleshooting Matrix: Symptom → Cause → Action

Field-Proven Caveats for Mixed S7-300/400 Networks

Mixed S7-300/400 installations with legacy MPI backbones are common and introduce three additional failure modes that pure S7-400 documentation does not cover:

• Implicit MPI/DP crossover. Many S7-300 CPUs (CPU 31x-2 DP, CPU 31xC) expose a single combined MPI/DP port. The same physical port serves MPI at 187.5 kbps OR PROFIBUS DP at 1.5 Mbps, but not both. If the offline project was set up for DP and the field wiring is MPI (or vice versa), STEP 7 will report success at the application layer and 13:4542 at the transport layer simultaneously. Always read the CPU's interface mode from the diagnostic buffer, not the offline project.
• CPU 31x in RUN with PROFIBUS slave fault. A CPU that has lost its DP slave (cable cut, ET 200S power loss) will still respond to PG requests but will log "Station failure" in the diagnostic buffer. The PG can still upload the project, but any online block view that triggers a re-read of the slave's I/O may hang. Treat 13:4542 here as a slave fault, not a PG fault.
• S7-400 H-system. On an S7-400H redundant pair, only the active CPU's MPI/DP port is online. If the standby CPU's port is probed, STEP 7 will receive a valid frame and then 13:4542 as the standby refuses write operations. Always target the active CPU (H address) for online work, or use the redundant MPI port with a Y-coupler.

Notes on Power and Isolation

The genuine PC Adapter USB A2 provides galvanic isolation between the USB port and the MPI/PROFIBUS segment, rated at 500 V AC isolation per the device datasheet. This is critical when connecting a laptop tied to plant protective earth to a segment tied to a different earth reference; without isolation, ground loops inject noise that causes intermittent 13:4542 errors that look like software faults. Clones frequently omit the isolation transformer and rely on USB ground as the reference, which is one of the reasons they fail in electrically noisy cabinets.

Power draw is 100 mA typical, 200 mA peak from the USB bus, well within the USB 2.0 high-power device limit. Use a powered hub only if the laptop's USB stack is non-compliant (rare on industrial laptops).

Standards and Compatibility References

• PROFIBUS DP is defined by IEC 61158 / IEC 61784. The 9-pin D-sub pinout, RS-485 electrical layer, and bus-parameter frame follow EN 50170.
• Siemens MPI is a Siemens-proprietary subset of PROFIBUS RS-485, addressed at 187.5 kbps default. It is not standardized outside Siemens automation.
• STEP 7 V5.5 supports the PC Adapter USB A2 natively; TIA Portal supports the same hardware via the PC Adapter access point but may require the SIMATIC Automation License Manager to be installed for newer firmware revisions.