Resolving SINA_SPEED Error 8600 and DIAGID 80B1 in TIA Portal V15

Problem Overview

The Siemens SINA_SPEED function block (FB 285 / SINA_SPEED, part of the SINAMICS blocks library) is the standard interface for cyclic speed control of SINAMICS drives (S120, G120, G130, G150, S210) from SIMATIC controllers (S7-1200, S7-1500, ET 200SP) over PROFINET / PROFIdrive. The block hides the underlying DPRD_DAT (read) and DPWR_DAT (write) record calls but inherits their parameter constraints.

When the drive telegram is configured as a free telegram instead of a standard telegram, the user must match the cyclic I/O length manually. A mismatch produces:

• Error code #8600 on the SINA_SPEED output Error (WORD) and Status (WORD) with ErrorId / DIAGID indicating the internal DPRD_DAT call failed.
• DIAGID 80B1 at parameter DIAGID (WORD), which decodes to "length error in record read" in the PROFIdrive diagnostic table.

This article documents the root cause, the exact diagnostic chain, the fix in TIA Portal V15, and how to verify the corrected configuration.

Affected Products and Versions

Standard Telegram Assignments for SINA_XXXX Blocks

The SINAMICS blocks library assumes the following default cyclic telegrams unless explicitly overridden:

If you configure the drive with a different (free) telegram and the controller is wired to that telegram via PROFINET, every cyclic word is still consumed - but the layout no longer matches the block's offsets. This alone does not trigger error 8600; the issue arises from the parameter RECORD length mismatch between PLC and drive.

Root Cause Analysis

Error code 8600 originates inside the DPRD_DAT (read record data) call that SINA_SPEED makes on each OB1 cycle to fetch the cyclic process data from the drive's PROFINET interface. The Siemens documentation states:

"The length of the specific target range at parameter RECORD is shorter than the configured user data length."

Two separate definitions of length must agree:

1. PLC side: the byte length of the ANY pointer passed into RECORD at the DPRD_DAT call inside SINA_SPEED.
2. Drive side: the configured cyclic I/O length (sum of all PZD words) of the telegram selected in the SINAMICS drive (e.g. p0922, p2071, p2079).

If the PLC side is shorter than the drive side, the read fails because the PROFIdrive stack cannot fit the incoming frame into the buffer. The block then sets:

• Error = 1
• Status = 8600 (decimal) = 0x2198
• DIAGID = 80B1 hex = 32945 decimal

DIAGID 80B1 in the SINAMICS diagnostic mapping corresponds to length error in record read / parameter access. It indicates the record index or the record length passed by the PLC does not match the parameter access definition of the drive object.

Diagnostic Chain Inside SINA_SPEED

Internally SINA_SPEED performs, per call:

1. Build the request RECORD ANY pointer at HWIDSTW / HWIDZSW offsets.
2. Call DPRD_DAT(LADDR := HWID, RECORD := pInData, RET_VAL := tmpRet) to read the receive PZD area.
3. Evaluate tmpRet and the BUSY / DONE outputs of DPRD_DAT.
4. Map any non-zero RET_VAL to the block outputs Error, Status, and DIAGID.
5. If tmpRet = W#16#8600, the drive rejects the record because the PLC buffer length (RECORD) is shorter than the configured telegram length (drive parameter p0922 / p2071).

The mapping inside SINA_SPEED for the most common failure modes is:

Prerequisites Before Troubleshooting

1. TIA Portal V15, V15.1, V16, or V17 installed. (V14 ships without the integrated SINA_XXXX block online help; the library must be opened from the standalone PDF.)
2. Siemens SINAMICS blocks library V15 or later installed (e.g. SINAMICS_Blocks_V15.zip).
3. Access to the SINAMICS drive commissioning tool: SINAMICS S120 Commissioning Manual (109475044) or STARTER / Startdrive for G120.
4. The PROFINET device name and IP address of the drive.
5. The current p0922 value of the drive (telegram selection) and the configured PZD layout (p2051 / p2061).

Step-by-Step Resolution

Step 1 - Confirm the error and capture DIAGID

Online, with the PLC in RUN, open the SINA_SPEED instance DB and force a monitor to the following tags:

"iDB".Error      // BOOL  -> must be TRUE
"iDB".Status     // WORD  -> must show 8600 (decimal) / 0x2198
"iDB".DIAGID     // WORD  -> must show 80B1 (hex) / 32945 (decimal)
"iDB".AxisEnabled // BOOL  -> usually FALSE
"iDB".ActVelocity // REAL  -> stays at 0.0

Capture a screenshot of the instance DB. The DIAGID value is the authoritative diagnostic; Status alone is ambiguous because the same decimal value can appear in different SINA_XXXX blocks for different reasons.

Step 2 - Verify the PROFINET telegram on the drive side

In the SINAMICS drive (S120, G120, etc.) check:

p0922 = 999  // free telegram configured (not 1)
// OR
p0922 = 1    // standard telegram 1 - this is what SINA_SPEED expects

Record all PZD assignments:

p2051[0..15]  // transmit (drive -> PLC) PZD word mapping
p2061[0..15]  // receive (PLC -> drive) PZD word mapping

Count the total number of active words. Example for a 6-word free telegram (12 bytes):

Total receive length = 6 words = 12 bytes. Total transmit length = 6 words = 12 bytes.

Step 3 - Verify the PROFINET telegram on the PLC side

In TIA Portal, open Devices & Networks, select the drive's PROFINET interface, and inspect the Device configuration > Module parameters > Telegram configuration. The PROFINET slot must show:

• Same number of input PZD words as the drive's p0922 / p2051 configuration.
• Same number of output PZD words as p2061.

If the slot shows "Standard telegram 1" but the drive is set to "free telegram 999", the PROFINET stack on the drive will still try to send/receive the p0922 layout, and the PLC will read into a buffer sized for telegram 1 (4 words = 8 bytes). The PLC buffer is too short for the drive's real layout - this triggers exactly the 8600 / 80B1 combination.

Step 4 - Adjust either the PLC telegram or the drive telegram so both agree

Choose one of two paths:

Path A - Use the standard telegram (recommended for SINA_SPEED):

1. On the drive, set p0922 = 1 and copy/activate factory defaults (p0010 = 30, p970 = 1).
2. In TIA Portal, change the drive device configuration so the slot uses Standard telegram 1 (PZD-2/2). The IO length becomes 4 words each direction.
3. Recompile and download the project. The SINA_SPEED defaults (4-word layout) now match.

Path B - Keep the free telegram and tell SINA_SPEED the exact length:

1. Keep p0922 = 999 on the drive.
2. In TIA Portal, configure the drive slot with the matching free telegram layout (same word count as the drive).
3. In the SINA_SPEED call, ensure the input ConfigAxis and the data block layout match. SINA_SPEED does not automatically detect the telegram length; it uses the ANY pointer generated at compile time from the PROFINET slot assignment. Therefore the slot length must be identical to the drive-side p0922 layout.
4. Recompile, download, monitor DIAGID - it should now show 0000.

Step 5 - Recompile and download

1. In TIA Portal, mark the PLC and choose Compile > Hardware (rebuild all).
2. Download the hardware configuration to the PLC.
3. Download the program blocks (or do a full download).
4. Cold restart the drive if you changed p0922 (p0009 = 0; p0976 = 1).

Step 6 - Verify the fix

Online, with the PLC in RUN and the drive in cyclic communication:

1. Confirm iDB.Error = FALSE.
2. Confirm iDB.Status = 0000 or 7000 (idle).
3. Confirm iDB.DIAGID = 0000.
4. Confirm iDB.ActVelocity tracks the drive's actual speed (read via STARTER / Startdrive r0063).
5. Toggle iDB.EnableAxis = TRUE (or iDB.Enable depending on block version). Drive should run to iDB.SetVelocity.

Manual Locations for SINA_XXXX Help

• SINAMICS S120 Commissioning Manual (Entry ID 109475044) - includes the canonical description of DPRD_DAT return value 8600 and DIAGID mapping.
• SINAMICS blocks for TIA Portal V15 (Entry ID 109751049) - download archive for V15 library.
• SINA_SPEED function manual (Entry ID 109762715) - block-level help for FB 285 and the DIAGID table.
• PROFIdrive Profile drive technology (Entry ID 109740115) - telegram definitions and PZD conventions.

Common Pitfalls When Migrating From V14 to V15

Extended Diagnostics: Reading Drive-Side Faults

Once error 8600 is cleared, monitor the drive's own fault buffer to ensure no PROFIdrive fault is being silently masked:

r2139.0..15   // current fault code, decimal
r2135.0..15    // last fault code, decimal
r9747.0..15    // PROFIdrive fault code (from telegram)
F30001, F08501 // typical drive-side faults to clear before retry

Clear faults with p3981 = 1 (acknowledge all) and p0952 = 0 after the cause is removed.

Formula: Telegram Length Check

Use this sanity check whenever a free telegram is involved:

RECORD_len_PLC  = N_in * 2          // bytes, N_in = input PZD word count
RECORD_len_drive = N_p2051 * 2       // bytes, N_p2051 = number of populated p2051 entries
DIAGID 80B1  iff  RECORD_len_PLC  <  RECORD_len_drive

Example: drive has 6 words populated in p2051 (12 bytes). PLC slot shows 4 input words (8 bytes). 8 < 12, so 80B1 will fire on the very first read.

When SINA_SPEED Still Returns 8600 After the Fix

1. Confirm the GSD file version matches the drive firmware. Older GSD versions may report a default telegram of 0 words for "free telegram".
2. Confirm the PROFINET topology is RT class 1+ or IRT, not RT class UDP. PROFIdrive telegrams require RT.
3. Check that the IO controller slot for the drive is enabled (slot 0 submodule inserted).
4. Force a cold restart of the drive after any p0922 change so PROFINET re-negotiates the AR.
5. Watch iDB.Status for one full second - SINA_SPEED only updates DIAGID on the cycle where the error is raised. If the drive recovers mid-run, you may catch a stale 80B1.