Resolving SINA_SPEED Errors 80B1 and 8093 on S7-1200 G120

Problem Overview

The SINA_SPEED function block from the Siemens DriveLib library is the standard application block used in TIA Portal to cyclically control SINAMICS drives (notably the G120 family) from a SIMATIC S7-1200 or S7-1500 controller over PROFINET. The block is referenced in the official Siemens application document "Controlling a speed axis with the SINA_SPEED block" (SIOS ID 109485727), and is also used for Technology Modules such as the ET 200SP F-TM StepDrive as described in the F-TM StepDrive SINA_SPEED programming guide.

When commissioning this block on a CPU 1214C DC/DC/DC with a SINAMICS G120 with CU240E-2 PN, two diagnostic IDs are frequently encountered in the field:

• DiagID 80B1 — length of the RECORD source range is shorter than the slave output length.
• DiagID 8093 — the configured hardware identifier (HWID) address does not match a valid PROFINET slot/submodule.

Both errors almost always originate in the way the symbolic I/O addresses of the PROFINET telegram are passed to the SINA_SPEED block, or in the length of the data buffers supplied to DPWR_DAT and DPRD_DAT. This guide walks through root cause analysis, the symbol selection rules, and the verification steps required to clear both faults.

System Topology and Telegram Layout

The reference architecture from the Siemens SIOS document is shown below.

The standard telegram 1 used with the G120 has a fixed payload of 6 process data words in each direction. The mapping is fixed by the G120 firmware and cannot be changed at the controller side without reconfiguring the drive device in TIA Portal / SINAMICS Startdrive.

SINA_SPEED Block Interface

The block ships inside the DriveLib V4.x and later, integrated as a global library in TIA Portal. The interface shown below is taken from the parameter description in the Siemens SIOS document 109485727.

Root Cause Analysis — Error 80B1

DiagID 80B1 is the standard PROFINET diagnostic identifier returned by the DPWR_DAT and DPRD_DAT SFCs. The exact wording of the S7-1200 system error is:

"Length of the RECORD source range is shorter than the slave output length."

Internally SINA_SPEED constructs a RECORD that covers the full 6-word (12-byte) payload of telegram 1. If the user-supplied source range on the data block is smaller than 12 bytes — for example, a P#DBx.DBX0.0 WORD 4 (8 bytes) — the system firmware rejects the write with 80B1.

Common construction mistakes that produce 80B1:

1. Declaring the I/O area as a 4-word array when the G120 is configured for the 6-word standard telegram.
2. Using telegram 2 or telegram 3 on the G120 side while the S7-1200 buffer was sized for telegram 1 (or vice versa).
3. Defining an ANY pointer of BYTE 8 for a free telegram with 10 words (20 bytes).
4. Re-using a residual buffer that was created for a different axis (e.g. a 4-word SINA_SPEED for a V90 instead of the 6-word SINA_SPEED for a G120).

Root Cause Analysis — Error 8093

DiagID 8093 means the symbolic HW identifier supplied at HWIDSTW or HWIDZSW does not match a configured PROFINET submodule of the G120 head module.

The SINA_SPEED block does not communicate with the drive "head module" (the G120 itself, slot 0). It communicates with the PROFINET submodule that owns telegram 1, which is automatically inserted by TIA Portal / SINAMICS Startdrive as slot 1 / submodule 1. The block therefore expects the user to wire the telegram symbol, e.g.:

• "G120_Head"~"Telegram 1"~STW — controller → drive process data
• "G120_Head"~"Telegram 1"~ZSW — drive → controller process data

Wiring the Access Point / head module symbol itself (the default symbol that the user sees first when the device is added) is a very common commissioning mistake. The user originally wired:

• HWIDSTW = "G120_Head"~I — wrong, this is the Access Point / status area of the head module.
• HWIDZSW = "G120_Head"~I — wrong, same root cause.

After correction, both pins point to the PROFINET telegram 1 submodule, the diagID cleared, but the user still observed an 8093 on one of the remaining inputs. This is the second classic variant of the error:

• A leftover or duplicate device from a previous project is still online and is responding to the IO-AR with a different submodule. Remove the duplicate and download the hardware configuration again.
• The HW identifier is the "absolute" address, but the project has been re-compiled and the absolute identifier changed. After any hardware change, recompile and re-download the S7-1200 program so the new HW identifiers are re-resolved.

Step-by-Step Resolution

1 — Verify drive-side telegram configuration

1. Open the G120 in SINAMICS Startdrive inside TIA Portal.
2. In the device view, select the head module → Properties → PROFINET interface → Telegram configuration.
3. Confirm that "Standard telegram 1, PZD-6/6" is enabled and assigned to the cyclic data exchange.
4. Save and compile, then download the drive project. After download, parameter r2075[0] on the CU should report 1 and r2076[0] should report 6.

2 — Wire the correct symbols to SINA_SPEED

1. Open the program block that contains the SINA_SPEED instance DB.
2. Click into the HWIDSTW input. Delete the current reference.
3. Open the project tree → Devices & networks → G120 → Telegram 1 and drag the "STW" entry onto the HWIDSTW input. The variable name now resolves to the PROFINET telegram 1 output area.
4. Repeat for HWIDZSW using the "ZSW" entry of the same Telegram 1 submodule.
5. Compile the S7-1200 program. Any unresolved symbol appears in red and must be fixed before download.

3 — Match the RECORD length to the slave

The SINA_SPEED block itself builds the correct RECORD internally for telegram 1, so once the symbol is correct the data length will follow. If you are using the lower-level DPWR_DAT / DPRD_DAT directly (e.g. with a custom block), the RECORD length must be set as follows:

4 — Recompile and download

1. In the S7-1200 project tree, right-click the device → Compile → Hardware and software (rebuild all).
2. Download the configuration. TIA Portal will report the new HW identifiers if they changed.
3. After download, go online with the S7-1200. Open the SINA_SPEED instance DB and monitor DiagId. The value must return 0 within one PROFINET update cycle (typically 1–4 ms).

Verification

To prove the faults are cleared and the SINA_SPEED block is operating correctly, perform the following checks with the controller online and the drive de-energised (or in "switching on inhibited"):

1. DiagId monitor — DiagId = 16#0000 at all times, and Error = FALSE. If the value latches non-zero, latch it and check the table below.
2. STW echo — Write EnableAxis = TRUE (bit 0 of STW1) and confirm in Startdrive online → r2089[0] that the value 16#047E is present (ready to switch on, with the standard STW1 mask for OFF1 + no coast-down + no quick stop).
3. ZSW reading — The first ZSW1 word read back from the drive should be 16#0E31 or similar (ready, no fault, no warning). Drive must report r899 = 0 in the parameter view.
4. Online & diagnostics — Right-click the G120 in the device view → Online & diagnostics → PROFINET diagnostics. The status of telegram 1 should be "OK" and no AR (Application Relationship) errors should be present.
5. Watch table — Set up a watch table on the telegram 1 inputs and force the first STW word. The value should appear verbatim in the drive's r2050[0].

DiagID Reference Table

The following table summarises the diagID values reported by DPWR_DAT, DPRD_DAT, and therefore by SINA_SPEED. It is the consolidated set the Siemens S7-1200 system manual returns for the I/O access functions.

Frequently Seen Pitfalls

Beyond 80B1 and 8093, the following issues appear repeatedly in the field and are worth verifying as a single checklist before re-powering the drive:

• PROFINET device name — the G120 must be assigned the same PROFINET name as in the TIA Portal project. Use "Assign PROFINET device name" from the Online & diagnostics menu. A mismatch produces no IO-AR, which the S7-1200 reports as 80C3.
• Topology editor vs. port partner — if you use a topology with port 1 of the CPU connected to port 1 of the CU, both must agree. Mismatches do not stop the IO-AR but produce diagnostic interrupts and intermittent 80B2 errors.
• Update time — PROFINET update time on the G120 head module must be at least 1 ms. Setting it to 0.25 ms is supported on a CU240E-2 PN-F only with the latest firmware ≥ V4.7 SP10. The S7-1200 default is 1 ms which is fine.
• Drive object number — AxisNo = 1 for a single-axis G120. For a G120X multi-axis, each drive object has its own number (1, 2, 3, …) and each is mapped to a separate SINA_SPEED instance with the corresponding telegram submodule.
• Setpoint scaling — RefSpeed must equal p2000 of the drive. If p2000 is changed at the drive side, the block must see the new RefSpeed with ConfigAxis pulsed TRUE.
• STW bit polarities — the SINA_SPEED block handles STW1 bit polarities internally. Forcing the user-side EnableAxis TRUE sets bit 0 and the SINA_SPEED library writes the other bits per PROFIdrive profile. The user should not write the entire STW1 manually from outside the block.
• Endianness on the watch table — ZSW1 and NIST_B are little-endian. If you read them as a DWORD in the watch table, byte order matters: 0x31 0x0E 0x00 0x00 is the typical 0x0E31 status for a ready drive.

Diagnostic Workflow Summary

Safety and Operational Notes

Related Documentation

• SIOS 109485727 — SINAMICS G: Controlling a speed axis with the "SINA_SPEED" block
• SINA_SPEED project documentation for S7-1200 with G120 CU240E-2 PN (PDF)
• F-TM StepDrive ST 1x24..48V 5A: Controlling via SINA_SPEED

FAQ