26105

Access Diagnostics > System Information > Drives on the HMI to display all recognized Profibus slaves. Cross-reference the axis name from alarm parameter %1 with the expected slave address.

If the drive does not appear in this list, the SDB Type-2000 is out of sync with the actual Profibus topology.

In NCK > Machine Data > Axis-specific parameters, locate MD32100 (AXIS_DRIVE_NR) for the affected axis. Verify the slave address matches a valid entry in the Profibus configuration and SDB Type-2000.

Regenerate the SDB Type-2000 via the PLC program or OEM commissioning tool. Ensure all configured drives in the Profibus master are included in the SDB before restarting the NCK.

Do not manually edit SDB Type-2000 without regeneration; use SIMATIC tools (e.g., STEP 7 or TIA Portal) to maintain consistency.

Power-cycle the control or trigger a 'Cold Start' (DFS > Restart > Cold Start) to reload the SDB Type-2000 and re-initialize axis drive discovery.

In NCK > Machine Data, navigate to the affected axis and check MD32100 (AXIS_DRIVE_NR), MD32110 (AXIS_DRIVE_TYPE), and related drive assignment parameters. Document the configured drive reference.

Verify the drive interface exists: For Profibus drives, check Diagnostics > Bus > Profibus. For hardwired drives, verify the terminal assignment in the hardware configuration (PLC I/O mapping).

If the drive is offline or not listed, it may have failed or been removed from the system.

If the drive is present, reload or re-assign the axis machine data. If the drive has been replaced, update MD32100 and any related drive type parameters to match the new hardware address and regenerate the SDB.

Perform a warm restart (DFS > Restart > Warm Start) or power-cycle to trigger axis initialization and drive discovery. Observe diagnostic logs (Trace) for any secondary errors during drive handshake.

Download the current machine data (NCK > Backup > Export) and inspect the axis section for the affected axis. Verify that MD32100 and all related drive parameters contain valid, non-zero values.

If the parameter file was manually edited or recovered from a partial backup, data corruption is likely.

Compare the exported machine data against a known-good backup or commissioning template. If discrepancies are found, restore the correct machine data from a validated source.

If no backup is available, manually reconfigure the axis in NCK > Machine Data, ensuring all drive-related parameters (MD32100, MD32110, etc.) are set according to the OEM documentation and current hardware topology.

Do not guess parameter values; consult the machine manual or OEM support for the correct drive address assignment.

Save the corrected configuration, regenerate the SDB Type-2000, and perform a cold start. Monitor the system log to confirm successful drive enumeration.