Overview
The SINAMICS PM250 (CU250S-2DP Vector) drives support a "free telegram" configuration on PROFIBUS that lets you assemble the receive and process data words (PZDs) individually rather than locking the drive to a predefined Siemens standard telegram. When the drive is set to p0922 = 999, the firmware stops interpreting the cyclic payload as a fixed Standard Telegram 1, 2, 3, 4, 5, 6, 7, 9, 110, or 111, and treats the configured PZD set as raw words that the controller can map as needed. The S7-315-2DP master exchanges these PZDs using the SIEM8170.gsd or equivalent GSD for the CU250S-2DP.
For S7-315-2DP commissioning, the central question is what p2071 actually controls, whether it must be set to the length of the status word, and how the Safety Information Channel / Safety Control Channel (SIC/SCC, telegrams 700–706) is positioned in the free PZD layout. The Status Word (ZSW1) is always exactly 1 word (16 bits) when emitted from the drive; the parameter p2071 is not a length field for the status word, it is the start offset of the SIC/SCC telegram inside the free telegram payload. The free telegram still contains a ZSW1 at its standard position unless you re-arrange it via interconnect parameters, but the safety channel occupies a different indexed slot identified by p2071.
Prerequisites
Before commissioning the SINAMICS PM250 with free PROFIBUS telegram and S7-315-2DP, confirm the following:
- SINAMICS PM250 with CU250S-2DP Vector Control Unit (6SL3225-0BE32-2UA0 series or equivalent), firmware ≥ 4.7. Recommended baseline: firmware 4.7 SP3 or 4.8 for full compatibility with STARTER V5.4 and Startdrive V15.1.
- SIMATIC S7-315-2DP (6ES7315-2AG10-0AB0 or later) with STEP 7 V5.5 SP4 / SP5 installed.
- STARTER commissioning tool V5.4 SP1 or higher, with the matching drive ES package installed so the CU250S-2DP appears in the device catalog.
- PROFIBUS DP cable (6XV1830-0EH10 or compatible), PROFIBUS connectors with termination switch, and bus terminators enabled at both physical ends.
- GSD file
SIEM8170.GSE(CU250S-2DP) loaded into the STEP 7 hardware catalog. - PLC program blocks: OB1 (cyclic), OB82 (diagnostic), OB86 (rack failure), and the standard drive function blocks FB2/FB3 (PZD receive/send) or custom data handling.
- Optional: Safety license for SIC/SCC, only if Safety Integrated is required.
PROFIBUS Telegram Model for SINAMICS PM250
SINAMICS drives on PROFIBUS DP-V1/V2 use the PPO (Parameter-Process-Data-Object) or PZD-only model. The CU250S-2DP supports the following PZD layouts:
| Telegram (p0922) | Name | PZD Receive (PLC → Drive) | PZD Send (Drive → PLC) |
|---|---|---|---|
| 1 | Standard Telegram 1 | STW1 + NSOLL (2 words) | ZSW1 + NIST (2 words) |
| 2 | Standard Telegram 2 | STW1 + NSOLL (2 words) | ZSW1 + NIST + IACT (4 words) |
| 3 | Standard Telegram 3 | STW1 + NSOLL (2 words) | ZSW1 + NIST (2 words) + fault |
| 4 | Standard Telegram 4 | STW1 + NSOLL (2 words) | ZSW1 + NIST (2 words) + ZSW2 + ... |
| 5 | Standard Telegram 5 | STW1 + NSOLL (2 words) + additional | ZSW1 + NIST (2 words) + additional |
| 6 | Standard Telegram 6 | STW1 + NSOLL (2 words) + additional | ZSW1 + NIST (2 words) + additional |
| 20 | SIEMENS Telegram 20 | 6 words (vendor specific) | 6 words |
| 352 | SIEMENS Telegram 352 | 6 words | 6 words |
| 999 | Free Telegram | User-defined (1–16 words) | User-defined (1–16 words) |
| 700–706 | SIC/SCC | 1–2 safety words | 1–2 safety words |
When you choose p0922 = 999, STARTER (or the Starter offline configuration) shows a tabular editor where you assign each PZD slot to a connector input (BICO source) on the receive side and to a connector output on the send side. The total length of this free telegram is what is propagated to the S7-315-2DP via the GSD when the drive is inserted in HW Config.
Parameter Map: p0922, p2079, p2070, p2071
The four parameters control the cyclic PZD structure. They are interdependent, and mis-configuring them is the most common cause of F08501 (sign-of-life failure) or F08502 (PZD configuration error) faults.
| Parameter | Description | Typical Value (Free Telegram) | Notes |
|---|---|---|---|
| p0922 | IF1 PROFIdrive PZD telegram selection | 999 | Selects free telegram mode for IF1 (PROFIBUS / PROFINET on CU250S-2) |
| p2079 | IF1 PROFIdrive PZD telegram extension | 999 (only if combined with fixed telegram) | Used to extend a fixed telegram with additional PZDs; not normally required for a fully free telegram |
| p2070 | IF1 PROFIdrive SIC/SCC start offset receive (PLC → Drive) | Total free receive PZD length | Position in the receive telegram where the safety control channel starts |
| p2071 | IF1 PROFIdrive SIC/SCC start offset send (Drive → PLC) | Total free send PZD length | Position in the send telegram where the safety information channel starts |
p2070 and p2071 are preserved at their previous numerical values, but their semantic meaning changes to the offset within the free telegram. The drive does not automatically recalculate them to the new layout. You must re-set p2070 and p2071 to match the intended position of the safety channel in your new free telegram.Step-by-Step: Configuring Free Telegram with p2071
- Open STARTER and connect to CU250S-2DP. Go online, then navigate to Drive → Communication → PROFIBUS. Verify p0922 is currently a fixed value (e.g. 1) or already 999.
- Open the Telegram Configuration. In STARTER, double-click Configuration → Telegram configuration. The dialog lists p0922 and p2079 at the top.
-
Select free telegram. Change
p0922to999. The receive and send PZD tables unlock to allow BICO source/target selection for each word. For example, for a 10-word send telegram you can set: PZD1 = ZSW1, PZD2 = NIST (actual speed), PZD3 = IA (actual current), PZD4 = Udc (DC-link voltage), PZD5–PZD10 = additional connectors you wire via BICO. -
Verify the total PZD count. Count the number of PZDs you have placed in the send (drive → PLC) table. Suppose the layout is 10 words. The SIC/SCC safety words will be appended after these 10 words if Safety Integrated is enabled and configured. In that case,
p2071should be set to10, meaning the safety channel starts at offset 10 (the 11th word). If Safety Integrated is NOT used, leavep2071at its default (typically 0) or do not change it; setting it to a non-zero value when no SIC/SCC telegram is configured has no functional effect because the safety channel is not populated. -
Configure SIC/SCC only if Safety Integrated is active. Navigate to Functions → Safety Integrated. Enable the safety functions (STO, SS1, SBC, SLS as required). The drive will then publish a Telegram 70x. Set
p2071(send direction) andp2070(receive direction) to the offset where the safety words are placed within your free telegram. -
Save and copy RAM to ROM. Click Copy RAM to ROM in STARTER so the configuration survives a power cycle. Then perform a power-on reset or issue
p0977 = 1for parameter save. - Update the STEP 7 HW Config. Open SIMATIC Manager, open the S7-300 station, and double-click the DP master system. Right-click the CU250S-2DP slave, choose Object Properties → Telegram Configuration. STEP 7 reads the telegram length from the GSD. If you changed p0922 to 999 after the slave was inserted, you must re-insert the slave or click Update Catalog so HW Config re-reads the configured PZD length.
-
Map the PZDs to I/O addresses. HW Config will assign peripheral addresses (e.g. PE 256…275 for inputs, PA 256…275 for outputs). Use these in the STEP 7 program via
L PIW 256for the status word, or via FB2 (PZD receive) and FB3 (PZD send) standard blocks. - Download the hardware configuration to the S7-315-2DP. Then run a CPU restart to clear the OB82/OB86 diagnostics.
BICO Source and Target Interconnections for Free Telegram
In free telegram mode, the drive does not automatically route ZSW1, ZSW2, NIST, IA, MIST, UIST, etc., to specific PZD slots. You must wire each PZD slot to a connector. The relevant interconnection parameters are p2050, p2051, p2061, and p2062 (send direction), and p2050 is read for receive. Below is a typical 10-word free send telegram with SIC/SCC at offset 10:
| PZD Slot (Send) | Index | Connector Source | Parameter |
|---|---|---|---|
| 1 | 0 | ZSW1 (r2089[0]) | p2050[0] = r2089[0] |
| 2 | 1 | NIST_A (r0063[0]) | p2050[1] = r0063[0] |
| 3 | 2 | IA (r0027) | p2050[2] = r0027 |
| 4 | 3 | Udc (r0026) | p2050[3] = r0026 |
| 5 | 4 | MIST (r0080) | p2050[4] = r0080 |
| 6 | 5 | PIST (r0082) | p2050[5] = r0082 |
| 7 | 6 | free connector | p2050[6] = user |
| 8 | 7 | free connector | p2050[7] = user |
| 9 | 8 | free connector | p2050[8] = user |
| 10 | 9 | free connector | p2050[9] = user |
| 11 | 10 | SCC (SIC/SCC safety channel send) | p2071 = 10 |
On the receive side, p2051[0] typically defaults to r2090.0 for STW1. For free telegram you can route any PZD slot to any binector input via p2051 and subsequent index parameters.
Status Word and Control Word in Free Telegram
The Control Word (STW1) and Status Word (ZSW1) are mandatory in the first two PZD slots of any PROFIdrive-compliant PZD set when the drive is operated in a standard control mode. In free telegram (p0922 = 999), this default is enforced by the PROFIdrive profile: if the drive detects STW1 / ZSW1 are not in the first two slots, it generates fault F08501 "Sign-of-life failure" or F08502 "PZD configuration error" within 2 × p2047 (sign-of-life monitoring time, default 0.5 s, so within ~1 s).
The user-defined 10 words in the original question (ZSW1 + ZSW2 + current + voltage + ...) is interpreted as: PZD1 = ZSW1, PZD2 = ZSW2 or NIST_A, and PZD3–PZD10 = whatever connectors the application requires. The "10" the user mentioned refers to the total PZD count, not the bit length of the status word. Each status word is exactly 16 bits (1 word) in PROFIdrive.
Verification and Diagnostics
- Check r2050 and r2051 indexing. In STARTER expert list, view r2050[0..9] and r2051[0..9]. Each entry shows the currently active BICO source / target. If a value is 0, the slot is unconnected.
- Check p2070 and p2071 in the expert list. Verify p2071 equals the offset where the safety channel is expected. If the application has no safety channel, p2071 can be left at 0 (default).
- Read r2054 (PZD diagnostics). STARTER's Communication → Telegram diagnostics shows the active telegram (p0922) and the cyclic configuration. It also displays the PROFIBUS PZD count as recognized by the drive.
- Monitor r0046 (missing enable / fault code). If the drive refuses to enter Run mode and r0046 shows F08501 or F08502, the free telegram configuration does not match the S7-315-2DP's PZD length. The most common cause: STEP 7 HW Config still has a different telegram length (e.g. 6 words from Telegram 3) than the drive (10 words). Re-insert the slave with the new GSD PZD count.
- Check PLC online I/O view. In STEP 7, open the drive's PZD inputs (PIW) and outputs (PQW) and verify that the bit pattern in PIW 256 matches the expected ZSW1 bits (e.g. bit 02 = operation enabled, bit 06 = switch-on inhibited, bit 11 = warning active).
- Trigger STO test (if Safety Integrated active). With safety channel present at offset p2071, force the safety request via terminal or via PROFIsafe and verify F01611 (Safety function requested) is logged, the drive outputs are de-energized within p9651 (STO debounce, default 250 ms), and the safety status word reflects the state to the PLC.
- Confirm sign-of-life. The drive sends a 4-bit sign-of-life counter (ZSW1 bits 12–15) which the PLC must echo back in STW1 bits 12–15. Mismatching counters within 2 × p2047 trips F08501.
Troubleshooting Matrix
| Symptom | Fault Code | Likely Cause | Remedy |
|---|---|---|---|
| Drive does not leave Run-Ready state | F08501 | PLC is not toggling sign-of-life bits in STW1 | Verify FB2/FB3 block is running in OB1; check STW1 bits 12–15 are being updated each cycle |
| Drive reports PZD configuration error | F08502 | Free telegram length in drive (p0922 = 999) does not match HW Config PZD length | Re-insert the DP slave from GSD in HW Config; ensure the configured I/O address count matches the BICO wiring |
| ZSW1 always 0x0000 | None | p2050[0] not wired or wired to wrong source | Set p2050[0] = r2089[0] (default for ZSW1) or to r0899 (drive status word) |
| STO does not trigger from PLC | None (drive stays in Run) | SIC/SCC safety channel not populated; p2071 = 0 with no safety telegram | Enable Safety Integrated, configure p2071 to the correct offset, regenerate the free telegram in STARTER |
| PLC diagnostics buffer: "Slave not found" | None | PROFIBUS address conflict (default 6 on PM250) | Set p0918 to a unique address; verify GSD file version matches firmware |
| Drive does not accept the new free telegram | None | After changing p0922, drive requires power cycle or warm restart | Run p0977 = 1, then power cycle the CU; alternatively power up the drive and acknowledge faults |
| Sign-of-life trips after enabling | F08501 | p2047 (sign-of-life time) too short for slow PLC scan | Increase p2047 to 1.0 s and ensure PLC cycle < p2047 |
Interaction with Other SINAMICS Parameters
Several related parameters must be coherent when you activate a free telegram:
- p0918: PROFIBUS node address. Must be unique on the bus; default 6 for PM250.
- p0922: PROFIdrive PZD telegram selection. Set to 999 for free telegram.
- p2047: PROFIBUS sign-of-life monitoring time. Default 0.5 s. Increase to 1.0 s for slow PLC scan times (S7-315-2DP with OB1 cycle > 250 ms).
- p2050[0..15]: BICO source for send PZDs.
- p2051[0..15]: BICO target for receive PZDs.
- p2061[0..15]: Sign-of-life source (only for p0922 = 4 or 220 with sign-of-life enabled).
- p2070: SIC/SCC start offset receive (PLC → Drive).
- p2071: SIC/SCC start offset send (Drive → PLC).
- p2079: PROFIdrive PZD telegram extension. Only relevant when combining a fixed telegram with an extension.
According to the SINAMICS S120 Safety Integrated Function Manual, when the user changes the configuration from a fixed telegram to free (p0922 = 999), the numerical values stored in p2070 and p2071 are preserved from the previous configuration. Because their semantic meaning changes to "offset within the free telegram", you should re-validate them after each telegram change, especially if Safety Integrated telegrams are involved. See the official SINAMICS S120 Safety Integrated Function Manual for the full description.
Edge Cases and Field-Proven Caveats
- Mixing free telegram with PROFIsafe on PROFIBUS. PROFIsafe uses a different mechanism (F-host address, F-source address) and adds a safety slot to PROFINET/PROFIBUS. The SIC/SCC channel is the older safety mechanism, intended for compatibility. If your application uses PROFIsafe, do not use SIC/SCC and p2071 can remain at 0.
- Reversing PZD direction unintentionally. p2050 wires send direction. p2051 wires receive. Swapping them silently compiles the configuration in STARTER but the drive will not pass commissioning because the input/output interpretation is reversed.
- Free telegram size limit. Maximum 16 PZDs (32 bytes) per direction on CU250S-2DP. Exceeding this triggers a configuration error at startup.
- STARTER shows stale telegram after online change. If you edit p0922 online and STARTER does not refresh the Telegram Diagnostics view, click "Update" or close/reopen the Telegram Configuration dialog. This is a UI issue and does not affect the drive.
- STEP 7 keeps the old I/O addresses. After a Telegram change, the I/O addresses in STEP 7 hardware config may shift. Re-validate all PIW/PQW references in the PLC program and recompile.
- StarDrive vs. STARTER behavior. In Startdrive (TIA Portal) for S7-1500/S7-1200, the parameter numbering is the same, but the UI differs. S7-315-2DP is STEP 7 V5.x territory; use STARTER.
Parameter Summary Cheat Sheet
| Parameter | Default | Set Value (Example) | Meaning |
|---|---|---|---|
| p0918 | 6 | 4 (your bus address) | PROFIBUS node address |
| p0922 | 1 | 999 | Free PROFIdrive telegram |
| p2079 | 999 | 999 | Free extension (paired with p0922) |
| p2050[0] | r2089[0] | r2089[0] | ZSW1 source for PZD1 |
| p2050[1..9] | 0 | r0063, r0027, r0026, ... | Additional PZD send connectors |
| p2051[0] | r2090.0 | r2090.0 | STW1 target for PZD1 |
| p2047 | 0.5 s | 1.0 s | Sign-of-life monitoring time |
| p2070 | 0 | 10 (only if SIC/SCC RX active) | SIC/SCC RX start offset |
| p2071 | 0 | 10 (only if SIC/SCC TX active) | SIC/SCC TX start offset |
Verification Checklist Before Going Online
- Drive firmware version compatible with STARTER/Startdrive ES package.
- PROFIBUS address set uniquely (p0918) and matched in HW Config.
- p0922 = 999 saved to ROM and drive restarted.
- p2050[0..n] and p2051[0..n] all wired to valid BICO sources/targets.
- p2070 and p2071 set to the SIC/SCC offset, or left at 0 if no safety channel is used.
- STEP 7 HW Config I/O length matches the free telegram PZD count.
- Sign-of-life bits in STW1 (12–15) are toggled by the PLC each OB1 cycle.
- FB2/FB3 or equivalent blocks are scheduled in OB1 with the correct DB instance.
- All cabling shielded, terminated, and grounded per Siemens PROFIBUS guidelines.
- STARTER online diagnostics show no F08501/F08502 faults after the first commissioning power-up.
FAQ
What is the difference between p2070 and p2071?
p2070 is the start offset of the SIC/SCC safety channel in the receive (PLC → drive) direction, and p2071 is the start offset of the SIC/SCC safety channel in the send (drive → PLC) direction. Both are zero-based indices in the free PROFIdrive telegram, not length fields.
Do I need to set p2071 if I do not use Safety Integrated?
No. If SIC/SCC (telegrams 700–706) is not configured and Safety Integrated is disabled, p2071 has no effect on the cyclic data. Leave it at 0 or its previous value; the drive will not place a safety word at that offset.
Is the status word length configurable?
No. The Status Word (ZSW1) is always 1 word (16 bits). What you configure in a free telegram is the total PZD count, including ZSW1, ZSW2, NIST, IA, Udc, and any other connectors. Setting p2071 to 10 means the safety channel starts at PZD slot 11, not that you are sending 10 status words.
How do I set up the S7-315-2DP to match a 10-word free telegram?
Insert the CU250S-2DP from the GSD into HW Config, set the configured I/O length to 10 words in each direction, download the hardware config to the S7-315-2DP, and map the PIW/PQW addresses to your application. Use FB2/FB3 or direct PIW/PQW loads in OB1 to exchange data, and toggle the sign-of-life bits in STW1 (12–15) every cycle.
What happens to p2071 if I change p0922 from a fixed telegram to 999?
The numerical value of p2071 is preserved, but its meaning changes from "safety channel offset in fixed telegram" to "safety channel offset in free telegram". You must re-validate p2071 to match the new layout; otherwise, the safety channel will be placed at the wrong position or not populated at all.
Which fault indicates a free telegram mismatch with the S7-315-2DP configuration?
F08502 (PZD configuration error) or F08501 (sign-of-life failure). Both are logged in the drive's fault buffer (r0947/r0948) and surface in STARTER's diagnostics. They typically indicate a length mismatch between the drive's BICO-mapped PZD count and the I/O length STEP 7 expects on the slave.