Resolving Sinamics G120C PROFIBUS DP Communication with S7-300

David Krause11 min read
ProfibusSiemensTroubleshooting
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

Resolving Sinamics G120C PROFIBUS DP Communication with S7-300

Problem Overview

Engineers commissioning a SINAMICS G120C with a PROFIBUS DP Control Unit (CU240S DP or CU240E DP) against a SIMATIC S7-300 DP master (CPU 31x-2 DP or CP 342-5) frequently report that the drive does not appear in Accessible Nodes, that the cyclic I/O handshake never starts, or that the bus fault LED (BF) on the Control Unit lights steady red even though the GSD file was installed. The drive responds at the BOP/IOP panel but rejects all PLC write attempts to the process data. In every documented case of this symptom the root cause is a mismatch between the HW Config telegram selection, the DIP-set PROFIBUS node address, and the drive's own expert-list parameters (p0922, p2042, p2043).

This reference walks through the diagnostic path, the correct parameter set, and the verification steps that produce a stable cyclic PROFIBUS link between an S7-300 and a SINAMICS G120C.

Affected Components and Firmware

Component Catalog / Order Number Firmware Range Notes
SINAMICS G120C, CU240S DP-F 6SL3244-0BA21-1PA0 V4.4 – V4.7 SP10 Standard PROFIBUS Control Unit
SINAMICS G120C, CU240E DP 6SL3244-0BA21-1PA1 V4.5 – V4.7 Without safety, basic PROFIBUS
SINAMICS G120C PN variants 6SL3244-0BA21-1FA0 PROFINET only, not covered here
CPU 315-2 DP 6ES7315-2AG10-0AB0 Up to V3.3 Integrated DP master port
CPU 317-2 DP 6ES7317-2AK14-0AB0 V3.3 Integrated DP master, faster scan
CP 342-5 6GK7342-5DA02-0XE0 V5.x and V6.x External DP master for non-DP CPUs
Starter (commissioning) 6SL3072-0AA00-0AG0 V4.x – V5.x Or Startdrive V13+
STEP 7 V5.5 + SP2 or later Required for HW Config
Hardware compatibility: The PROFIBUS Control Unit of the G120C must match the GSD file revision installed in STEP 7. Mismatched GSDs (for example a V4.4 GSD against a V4.7 drive) load fine but cause the DP slave to drop out on every PLC stop/run transition.

Root Cause Analysis

Five independent failure modes account for almost every G120C ↔ S7-300 PROFIBUS problem encountered in field commissioning. Diagnose in this order before swapping hardware.

  1. Drive-side fieldbus not enabled. Parameter p2043 (activate fieldbus interface) defaults to 0 on a factory-fresh G120C. The DP port is physically present but logically inert. The PLC sees no answer to its FDL_Diag requests, even though the bus terminator is correct and the cable is good.
  2. Telegram mismatch. The HW Config slot is set to Universal Module (no fixed structure) or to a different telegram than what p0922 requests inside the drive. The PLC opens the connection but every value-word handshake fails the consistency check on the first cycle.
  3. PROFIBUS node address conflict. DIP switches on the CU240 were not changed from default (0), or were set to the same value as another slave on the segment. p2042 in the expert list and the DIP switches must agree; the drive honors whichever was set last via parameter write.
  4. Drive not commissioned. p0010 is still in commissioning state (1, 4, 5, 29, etc.) so the drive has not loaded its application settings. p0099 shows an unknown configuration. The starter project cannot upload, and the PLC handshake cannot start because the drive is in first commissioning state.
  5. Baud-rate auto-negotiation failure. On long segments with low-quality connectors or missing termination, the drive settles at 1.5 Mbaud but the master pushes 12 Mbaud. The BF LED flickers red instead of staying lit.

Prerequisites

  • GSD file for the exact CU variant installed; import via Options → Install GSD File in HW Config. Restart HW Config so the catalog refreshes.
  • Starter (V4.x or V5.x) or Startdrive in TIA Portal V13+ available on the engineering PC with a USB or PROFIBUS-to-Ethernet routing path.
  • PROFIBUS cable terminated at both ends with 220 Ω + 390 Ω resistor network, shield clamped at the connector backshell.
  • Drive and PLC powered up together; the G120C accepts fieldbus configuration only after the basic commissioning (motor data, application class) has been performed.

Step-by-Step Configuration

Step 1 - Set the PROFIBUS node address

The G120C supports PROFIBUS addresses 1 through 126. Address 0 is reserved for temporary wiring checks.

  1. Power down the drive.
  2. Set the DIP switches on the front of the CU240 to the desired address. Switch positions are read left-to-right as binary with the leftmost switch = bit 0 (value 1). For address 5: switches 1 and 3 ON, all others OFF.
  3. Power up. The active address is reported by r2050[0] at the BOP as "5" in the fieldbus status screen.
DIP vs. parameter priority: If the DIP switches are all OFF, the address falls back to p2042 in the expert list. If you later change p2042 from Starter, that value is used as long as the DIP switches remain OFF. Mixing set methods is the most common cause of "the address changed after restart" reports.

Step 2 - Activate the PROFIBUS interface

Navigate from the BOP or via Starter to the parameter list and set:

p2043 = 3

Value 3 means fieldbus interface active, PROFIBUS DP protocol. Without this assignment the drive ignores every telegram and the BF LED stays steady red.

Step 3 - Select the telegram

Telegram PZD Count Direction (PLC → Drive) Direction (Drive → PLC) Use Case
1 (Standard) 2 / 2 STW1, NSOLL_A ZSW1, NIST_A Simple speed control
20 2 / 6 STW1, NSOLL_A ZSW1, NIST_A, IAIST, MIST, PIST, ZSW2 Speed with extended diagnostics
352 6 / 6 STW1, NSOLL_A, M_LIM, M_R, STW2, supplementary ZSW1, NIST_A, IAIST, MIST, PIST, ZSW2 Vector control, free blocks
999 User-config User-mapped via p2051/p2061 User-mapped Custom BICO interconnection

Apply with p0922 = 1 for Standard Telegram 1 or p0922 = 352 for the 6/6 vector telegram. Save with p0971 = 1; the drive reboots once and comes back with the new telegram active.

Step 4 - Configure HW Config in STEP 7

  1. Open the S7 project, insert the G120C from the catalog: PROFIBUS-DP → SINAMICS → SINAMICS G120C → CU240S DP. Do not select the entry under Other field devices → Drives; that entry does not honor p0922.
  2. Assign the PROFIBUS address you set on the DIP switches (here: 5).
  3. Drag the appropriate telegram from the right catalog pane into slot 0 of the slave. For Telegram 1 the catalog label is SINAMICS G120C → Telegram 1 (PZD-2/2).
  4. Double-click the slot and verify the PZD lengths match. STEP 7 will show 2 words input / 2 words output.
  5. Compile and download to the CPU.
Universal Module warning: Selecting Universal Module tells the drive to expect a free-form telegram. In that mode the drive will only run if p0922 = 999 is also set AND the BICO mapping in p2051[0..15] / p2061[0..15] is configured manually. For first-time setup, always start with a fixed Telegram 1 in HW Config.

Step 5 - Commission the drive with Starter

  1. Connect Starter to the drive via the PC connection cable or over PROFIBUS using the CPU as gateway.
  2. Open Accessible Nodes. The drive should appear at the configured PROFIBUS address.
  3. If the drive shows "first commissioning required", run the commissioning wizard: enter motor data from the rating plate, choose application class Standard Drive Control (Speed) for V/f, or Dynamic Drive Control for vector without encoder.
  4. Set p0010 = 0 and confirm the drive leaves commissioning mode (RDY LED green, no warning).
  5. Save with p0971 = 1 or via the toolbar icon. The parameter set is now retained across power cycles.

Step 6 - Establish the cyclic link

From the S7 program:

// Example: write control word 1 (047E hex = OFF1 inhibit, ready)
L  W#16#047E
T  PAW 256      // First PZD out, depends on HW Config base address

// Setpoint speed: 1500 rpm = 4000 hex on NSOLL_A reference
L  W#16#4000
T  PAW 258      // Second PZD out

The drive should respond in the same cycle on the input PAW range with ZSW1 = 0x4331 (operation enabled, no fault) and a feedback speed value. Watch the diagnostic buffer of the CPU for PROFIBUS events.

Verification Checklist

  • BF LED off on the G120C Control Unit. A steady-red BF means telegram mismatch or address conflict; a flickering BF means cable/baud-rate problems.
  • RDY LED green continuously (no orange/yellow indicating first commissioning pending).
  • PROFIBUS monitor in Starter shows the drive as online and the cyclic I/O words update in the IF1 trace window at the configured bus cycle.
  • r2050[0] reports the correct node address (BOP display).
  • STW1 transitions through the correct bit pattern: 047E → 047F (on) → 0x0F7F (acknowledged). A stuck 047E means the drive never received the OFF1 enable.
  • STEP 7 diagnostic buffer: Slave OK for the G120C node, no Station failure entries.
  • Save the project, perform a power cycle, and confirm the link re-establishes without manual intervention.

Troubleshooting Matrix

Symptom Likely Cause First Check Fix
BF steady red, drive not in Accessible Nodes p2043 ≠ 3 BOP: p2043 Set p2043 = 3, save with p0971 = 1
BF steady red, drive visible Telegram mismatch Starter: p0922 vs HW Config slot Align both sides, reboot drive
BF flickering, occasional comm loss Bad cable / termination Terminator resistance, connector shield Replace cable, re-clamp shield, lower baud rate
Address reported as 0 in Starter DIP switches all OFF, p2042 not written p2042 Set DIP switches or p2042 and cycle power
Drive reboots every time PLC transitions RUN→STOP GSD version mismatch GSD date vs drive firmware Import GSD matching the firmware, re-insert in HW Config
RDY yellow, drive ignores PLC commands First commissioning not done r0002 commissioning state Run Starter commissioning wizard, then p0010 = 0
Cyclic I/O starts then drops with F08501 Sign-of-life fault, p2040 too low r0949[0], p2040 Increase p2040 to 200 ms
ZSW1 stuck at 0x031E (no OFF1) STW1 not written or wrong base address Cross-check PAW from PLC program Verify PQW base address matches HW Config slot offset
Firmware mismatch error during upload Different firmware in drive vs Starter project Starter: Online → Target device → Device identification Update Starter project to firmware or downgrade drive firmware

Common Fault Codes Related to PROFIBUS

Fault Value Meaning Recommended Action
F08501 Sign-of-life failure Drive did not receive cyclic data within p2040 ms Increase monitoring time or check PLC scan time
F08502 Telegram selection invalid p0922 mismatch with HW Config Align p0922 with HW Config slot
F08510 Send configuration error Master telegram too long for the slot Reduce PZD count or use free mapping
A08502 Warning, telegram monitoring Brief communication interruption Investigate cabling; clear with p3981 = 0
A50011 Fieldbus link down Physical layer lost Check connectors, baud rate, segment length

Parameter Reference for Quick Setup

Parameter Function Typical Value Access
p0010 Commissioning filter 0 (ready), 1 (quick), 30 (factory reset) BOP / Starter
p0097 Select drive object type 1 (INVERTER) Starter only
p0922 IF1 PROFIdrive telegram selection 1 / 20 / 352 / 999 BOP / Starter
p2030 Fieldbus baud rate (0 = auto) 0 Starter
p2040 Process data monitoring time (ms) 100 (default); 200 for slow scans BOP / Starter
p2042 PROFIBUS node address 1–126 BOP / Starter / DIP
p2043 Activate fieldbus interface 3 (PROFIBUS DP) BOP / Starter
p2047 PROFIBUS additional monitoring time 0 (disabled) Starter
p2051[0..15] CI: process data output words BICO interconnects from control words Starter
p2061[0..15] CI: process data input words BICO interconnects to status words Starter
p0971 Save parameters (RAM to ROM) 1 BOP / Starter

Performance and Timing Notes

  • At a 12 Mbaud PROFIBUS rate and Telegram 1 (2/2 words) the typical bus cycle on the G120C is approximately 1.6 ms with default p2040 = 100 ms monitoring.
  • The PLC scan time must be substantially shorter than p2040. For an S7-300 with a 50 ms OB1 cycle, raise p2040 to 200 ms or shorten the OB1 time.
  • If multiple G120C drives share a segment, use a 9.6 kbaud minimum segment line and keep the total segment length below the value defined by the baud rate (e.g. 100 m at 12 Mbaud).
  • The G120C DP Control Unit does not support isochronous PROFIBUS; for synchronized motion use the PROFINET variant (CU240PN or CU240E PN) and IRT instead.

Safety Considerations

Standard Telegram 1 with STW1 OFF1 (bit 0) follows the STO function category per IEC 61800-5-2 when wired through the safety terminals of the G120C. If the application requires SIL 2 or SIL 3, the CU must be a Failsafe variant (CU240S DP-F, order code 6SL3244-0BA21-1PA0 with the -F suffix in the firmware) and PROFIsafe must be mapped in addition to PROFIdrive. This reference covers the standard PROFIdrive handshake only.

Documentation and Standards

Cross-reference these official Siemens and IEC sources during acceptance testing:

FAQ

Why does my G120C stay offline even though the GSD was installed?

The drive-side PROFIBUS is not enabled. Set parameter p2043 = 3 and save with p0971 = 1. Until this parameter is written, the DP port is physically present but logically silent.

Should I use Universal Module or a fixed telegram?

For a first-time setup, use a fixed Telegram 1 in HW Config (PZD-2/2) and set p0922 = 1 on the drive. Universal Module requires p0922 = 999 and manual BICO mapping of p2051/p2061.

How do I change the PROFIBUS node address after the drive is running?

Edit the DIP switches on the CU240 for a permanent change, or write p2042 from Starter and save with p0971 = 1. Cycle power once for the new address to become active in r2050[0].

Why does my drive report F08501 even though the PLC is in RUN?

The PLC scan time exceeds p2040 (default 100 ms). Either shorten the OB1 time, raise p2040 to 200 ms, or check for diagnostic buffer events indicating telegram timeouts.

Do I need Starter to bring the drive online?

Yes, for the first commissioning the drive application (motor data, application class) must be written and p0010 returned to 0. After that the PLC can handle cyclic operation on its own, and Starter is only used for diagnostics or parameter changes.

Back to blog