SINAMICS S120 PROFIdrive Standard Telegrams: Mapping Reference

SINAMICS S120 PROFIdrive Standard Telegrams: Mapping Reference

The PROFIdrive standard telegrams on a SINAMICS S120 define a fixed, pre-engineered mapping between cyclic PROFIBUS/PROFINET process data words (PZD) and the drive's internal parameters. Selecting a standard telegram in STARTER, Startdrive, or TIA Portal automatically wires the cyclic I/O words to control words (STW), status words (ZSW), setpoints (NSOLL), and actual values (NIST) without manual parameter assignment. This reference consolidates how to locate the bit-level mapping for Control Units, Infeed modules, and Motor Modules, and how to verify the mapping against the firmware that is actually running on the drive.

1. PROFIdrive Telegram Concept on S120

PROFIdrive (IEC 61784-1 CPF 3) standardizes the cyclic process data exchange between a PROFINET/PROFIBUS controller and a drive. The S120 supports a profile version that publishes pre-defined telegrams in the drive's GSD file. When the controller configures telegram 1, for example, the drive internally wires PZD1 to STW1 (output) and PZD1 to ZSW1 (input), PZD2 to NSOLL_A (output) and NIST_A (input), and so on. These are not user-defined mappings; they are bound to the drive's parameter set at firmware build time.

The S120 distinguishes three categories of telegrams:

• Standard telegrams 1–6: speed, position, and basic I/O for single-axis drives
• Standard telegrams 7/9/110: extended setpoints and additional actual values
• Standard telegrams 81/82/83: encoder-only telegrams for S120 with separate encoder interfaces
• Manufacturer-specific telegrams (e.g. 220, 999): free-form BICO wiring for custom PZD layouts

2. Where the Mapping Is Documented

The authoritative bit-level mapping for every standard telegram lives in the SINAMICS S120/S150 List Manual in the function diagrams. The specific section is the PROFIdrive overview that starts at section 2.8 ("Overviews") of the Function Diagrams chapter. The telegrams themselves are drawn on function diagram sheets 2415 and 2422.

Two official sources are required to decode the mapping:

1. The SINAMICS S120 Communication Function Manual (article 109763284) – contains the function diagrams for PROFIdrive standard telegrams and process data on sheet 2415.
2. The SINAMICS S120/S150 List Manual (LH1) – the parameter-level reference; each PZD in the telegram is cross-referenced to a connector (CI/CO) or binector (BI/BO) and from there to a parameter (r/ p).

3. Function Diagram 2415 – PROFIdrive Standard Telegrams

Function diagram 2415 is the master sheet. It draws the cyclic PZD for each standard telegram in tabular form, with:

• Output (controller → drive) PZDs on the right side: STW1, STW2, NSOLL_A, NSOLL_B, G1_STW, G2_STW, etc.
• Input (drive → controller) PZDs on the left side: ZSW1, ZSW2, NIST_A, NIST_B, G1_ZSW, G2_ZSW, etc.
• Each row shows which PZD word the signal occupies and which connector supplies/receives it.

Function diagram 2422 shows the extended telegrams used by S120, including telegram 110, telegram 220 (vendor-specific multi-axis), and the encoder telegrams. The S120-specific differences versus the VIK-NAMUR and SIMODRIVE 611 definitions of the same control word name (e.g. STW1) are visible here, which is critical when copying logic from older commissioning.

4. Standard Telegram Catalog

The following table is the canonical mapping of the most-used standard telegrams on a SINAMICS S120 Motor Module. Inputs and outputs are process data words; word numbering is zero-based for the S7 side. Confirm against function diagram 2415 in the List Manual that matches your firmware.

Signal name abbreviations:

• STW1 / STW2 – Control word 1 and 2 (16 bits each)
• ZSW1 / ZSW2 – Status word 1 and 2 (16 bits each)
• NSOLL_A – Speed setpoint A (16-bit normalized, 4000hex = rated speed)
• NIST_A / NIST_B – Speed actual value A / B
• G1_STW / G1_ZSW – Encoder 1 control/status word
• G1_XIST1 / G1_XIST2 – Encoder 1 position actual 1 / position actual 2
• STW2_ENC / ZSW2_ENC – Encoder control/status word 2

5. STW1 / ZSW1 Bit Map (S120 Profile)

The List Manual publishes three different STW1 / ZSW1 bit maps on function diagram 2422: VIK-NAMUR, SINAMICS, and SIMODRIVE 611. They all use bit 0 as ON/OFF1, but bits 4, 5, 6, 8, 11, 12, 14, 15 differ. The SINAMICS variant is the correct one for S120 Motor Modules with firmware 4.x and 5.x.

6. Locating the Telegram in STARTER

The fastest field-proven method to confirm the actual telegram in use is via the STARTER commissioning tool, which reads the live configuration from the drive's parameter set rather than the printed List Manual.

6.1 Procedure

1. Open the project, go online with the drive, and load the drive into STARTER.
2. Double-click the Communication node in the project tree.
3. Open the PROFIBUS / PROFINET tab. The configured telegram for the Control Unit, Infeed, and each Motor Module is displayed as a row of PZD words.
4. For each PZD word, click the button beside the word. STARTER opens a window that lists the signal name (e.g. STW1), the connector supplying it, the parameter range, and the bit layout. This data is read from the drive firmware, so it always matches the running build.
5. If the row is marked with a red check, the telegram mismatch between project and drive is flagged. Clear it by accepting the drive-side configuration or by reloading the project to the drive.

6.2 Where STARTER Stores the Telegram Selection

7. Reading the Telegram in TIA Portal (S7-1500 / S7-1500T)

When the S120 is connected to an S7-1500 or S7-1500T via PROFINET, the PROFIdrive telegrams are configured directly in TIA Portal. The TIA Portal help system documents the standard telegrams in the same PROFIdrive profile structure used by S120. See the Configuring PROFIdrive telegrams (S7-1500, S7-1500T) reference for the S7-1500T side.

Key steps for the S7-1500T side:

1. Insert the drive from the device catalog (Siemens -> Drives -> SINAMICS S120). The GSD/GSDML exposes the same standard telegrams.
2. Open the device view, drag the required telegram (1, 2, 3, 5, 6, 81, 82, 83, 110) into the slot.
3. Select the IO addresses. The first PZD is mapped to IW/QW of the drive's PN slot. TIA Portal populates the symbol names (STW1, ZSW1, NSOLL_A, NIST_A) automatically from the telegram definition.
4. For S7-1500T axis functions, the technology object (TO) reads the telegram from the device and configures the TO data block (TO_PositioningAxis, TO_SynchronousAxis, etc.) accordingly.

If the S120 telegrams 81, 82, 83 are configured in the S7-1500T axis, the G1_STW / G1_ZSW / G1_XIST1 / G1_XIST2 / G2_STW / G2_ZSW / G2_XIST1 / G2_XIST2 signals are exposed as standard Telegram 81-83 sub-slots. The signals are 16-bit Gx_STW, 16-bit Gx_ZSW, 32-bit Gx_XIST1, and 32-bit Gx_XIST2.

8. Infeed Telegrams (Active Line Module, Basic Line Module, Smart Line Module)

Infeed modules on S120 use a separate telegram set, published on function diagram 2410/2415 of the List Manual:

The SLM_CTL / BLM_CTL bit assignments are not the same as the SINAMICS STW1. The S120 Infeed uses the VIK-NAMUR profile for its control word. Confirm against the List Manual function diagram 2410/2415 in the Infeed section.

9. Verifying the Mapping in the Field

When the cycle between the PLC and the S120 does not behave as expected, run a structured verification to isolate whether the mismatch is in the telegram configuration, the BICO wiring, or the PLC logic.

9.1 STARTER Trace

1. Open the drive, go online, and start the Trace function.
2. Add the connector r2050[0] (PZD receive, first word) and r2050[1] (PZD receive, second word) and the parameter being affected, e.g. r0063 (actual speed) or r0899 (STW1 read back).
3. Trigger from the PLC. Verify the trace of r2050 matches the value the PLC is sending on QW output.

9.2 PLC Side Watch Table

1. Add the cyclic I/O words (e.g. IW 256, IW 258, QW 256, QW 258) to a watch table.
2. Force QW 256 to a known pattern (e.g. 0x047E for "ON + enable + setpoint enable" in SINAMICS STW1) and confirm the drive reacts: r0898 should show the same value, ZSW1 in IW 256 should transition to 0x0631 (ready, enabled, no fault, setpoint reached).

9.3 Drive Parameter r2050 / p2051

r2050[i] – shows the i-th PZD word received from the bus. This is the live process image that the drive actually uses. Comparing r2050 with the PLC's QW output is the definitive way to verify that the telegram is wired correctly.

p2051[i] – defines the connector that the i-th received PZD is wired to. For standard telegrams, p2051 is write-protected. Trying to modify it is the standard symptom of a user attempting to deviate from the standard mapping. If a non-standard mapping is required, switch the telegram to 999 and wire p2051 manually.

10. Common Mismatches and How to Resolve Them

11. Free BICO Telegram (999) vs Standard Telegram

Telegram 999 is the S120's "blank canvas" mode. In this mode, p2051 (receive) and p2061 (send) are writable. Every PZD word is freely wired to a connector. Use 999 when:

• The PLC must exchange a non-standard signal (e.g. raw analog input, torque setpoint, r0899 with custom bits)
• You need to integrate a SINAMICS S120 with a third-party controller that uses the SIMODRIVE 611 or VIK-NAMUR bit layout
• You need an asymmetric layout (e.g. 2 words output, 5 words input)

The trade-off: GSD/GSDML no longer auto-resolves the I/O addresses. The PLC must know the connector layout and use the same BICO definitions in the drive configuration. The SINAMICS S120 Communication Function Manual documents p2051 / p2061 in detail.

12. Working Code Samples

12.1 STW1 Pattern for S7 Logic (Sinamics Telegram 1)

STW1 assembled from PLC flags for an S120 with telegram 1:

// STW1 bits (SINAMICS profile):
// bit 0  - ON / OFF1
// bit 1  - OFF2 (0 = coast)
// bit 2  - OFF3 (0 = quick stop)
// bit 3  - enable operation
// bit 4  - ramp enable
// bit 5  - unfreeze ramp
// bit 6  - setpoint enable
// bit 7  - fault ack (0->1 edge)
// bit 10 - control by PLC
// bit 11 - direction reverse
STW1 := (BOOL_TO_WORD(ON_OFF1)     AND SHL(WORD#1, 0)) OR
        (BOOL_TO_WORD(NOT_OFF2)    AND SHL(WORD#1, 1)) OR
        (BOOL_TO_WORD(NOT_OFF3)    AND SHL(WORD#1, 2)) OR
        (BOOL_TO_WORD(ENABLE_OP)   AND SHL(WORD#1, 3)) OR
        (BOOL_TO_WORD(RAMP_EN)     AND SHL(WORD#1, 4)) OR
        (BOOL_TO_WORD(RAMP_FREEZE) AND SHL(WORD#1, 5)) OR
        (BOOL_TO_WORD(SP_EN)       AND SHL(WORD#1, 6)) OR
        (BOOL_TO_WORD(FAULT_ACK_EDGE) AND SHL(WORD#1, 7)) OR
        (BOOL_TO_WORD(PLC_CTRL)    AND SHL(WORD#1, 10)) OR
        (BOOL_TO_WORD(DIR_REV)     AND SHL(WORD#1, 11));

12.2 Reading ZSW1 Status Flags

// ZSW1 bits (SINAMICS profile):
Ready_to_switch_on := (ZSW1 AND SHL(WORD#1, 0)) <> 0;
Ready_to_operate  := (ZSW1 AND SHL(WORD#1, 1)) <> 0;
Operation_enabled := (ZSW1 AND SHL(WORD#1, 2)) <> 0;
Fault_present     := (ZSW1 AND SHL(WORD#1, 3)) <> 0;
Alarm_present     := (ZSW1 AND SHL(WORD#1, 7)) <> 0;
Setpoint_at_ref   := (ZSW1 AND SHL(WORD#1, 8)) <> 0;
Forw_rot          := (ZSW1 AND SHL(WORD#1, 14)) <> 0;

12.3 NSOLL_A Scaling

NSOLL_A is normalized to 4000hex = 100% of the reference speed defined in p2000. The PLC sends the setpoint as INT. To convert rpm to NSOLL_A:

// p2000 in this example = 3000 rpm
NSOLL_A := DINT_TO_WORD(REAL_TO_DINT(n_setpoint_rpm * 16384.0 / 3000.0));
// Or use the standard PROFIdrive constant: 4000hex = 100% of p2000
NSOLL_A := DINT_TO_WORD(REAL_TO_DINT(n_setpoint_rpm * 4000.0 / 3000.0));

13. Toolbox SINAMICS S120 Function Blocks

Siemens publishes the Toolbox SINAMICS S120 V1.2 with S7 function blocks (FB305, FB310, FB311, FB312, etc.) for the standard telegrams. The blocks encapsulate the bit-level STW1/ZSW1 logic, ramp generation, and fault handling described in section 12. Use these blocks as a reference implementation, but always verify that the FB version matches your drive firmware. Older FBs do not support telegram 110, telegram 81-83, or the SINAMICS profile bit layout on bit 11 / bit 14.

14. Firmware Compatibility Notes

When upgrading firmware, always re-confirm the STW1 / ZSW1 bit map in the new List Manual edition, even if the telegram number is unchanged. The control word / status word definitions are bound to the firmware, not the telegram number.

15. Quick Reference Workflow

To answer "what is in this telegram and what do the bits do":

1. Identify the telegram number on the drive (p0922 in STARTER) and on the PLC side (device configuration).
2. Look up the function diagram 2415 entry for that telegram in the List Manual; note which PZD carries STW1, ZSW1, NSOLL_A, NIST_A, and any encoder / DSC words.
3. For each bit, find the matching column on function diagram 2422 (SINAMICS variant for S120) and read the bit definition. Cross-check against the S7-1500T help on PROFIdrive telegram configuration if the S7-1500T TO is in use.
4. Verify the live values with r2050 (receive) and r2060 (send) in STARTER, and with the PLC watch table on the I/Q addresses.

16. Frequently Asked Questions