4702

Access Siemens SINUMERIK HMI or SCOUT software and navigate to Parameterization > Machine Data > Axis/Spindle > PROFIBUS I/O Configuration. Locate MD10506 ($MN_DPIO_LOGIC_ADDRESS_OUT).

Review the slot index value from the alarm message (%1 parameter). Cross-reference this index against all entries configured in MD10506. Verify that the slot exists and contains a valid logical address mapping.

If the index is beyond the configured array bounds, the entry is missing.

Check the NC program (.mpf or .spf file) and PLC program for references to the missing slot address. Use the Siemens editor to search for PROFIBUS write operations or I/O area calls matching the slot index.

Add the missing logical address entry to MD10506 or update the existing entry with the correct PROFIBUS slave node ID and I/O area offset. After modification, perform a cold restart (POWER OFF > wait 10s > POWER ON) to reload machine data.

Changes to PROFIBUS mapping require system restart; do not attempt online modification during cycle.

In SCOUT or HMI Parameterization, navigate to Profibus Configuration > Slave Devices or PROFIBUS Station List. Verify that the PROFIBUS slave node referenced in MD10506 is present and online (check for green status indicator).

Check the GSD file version associated with the PROFIBUS slave. Access the device properties and confirm the GSD file matches the hardware module version. If outdated, download the latest GSD from the device manufacturer.

Using an outdated GSD can cause module identification failures and address conflicts.

Re-import the GSD file into the SINUMERIK system: Profibus Configuration > Import Device Description > select updated .gsd file. Perform a PROFIBUS network scan to re-enumerate all slave modules and their I/O areas.

After GSD import, regenerate or validate MD10506 entries to ensure all logical addresses now match available slave modules and I/O areas. Restart the control system and retry the operation.

Extract the alarm parameter %1 (slot/I/O area index) from the alarm message log. Cross-check this value against the valid range defined in MD10506. Determine if the index is within bounds (typically 0 to [MD10506 array size - 1]).

Review the NC part program (.mpf/.spf) for hardcoded PROFIBUS I/O calls or PLC calls using DPRD/DPWR instructions. Search for the slot index value and verify it matches an actual configured entry. Look for off-by-one errors or dynamic index calculations that may produce invalid values.

Dynamic index calculations (loops, conditions) are common sources of out-of-range errors; add bounds checking.

Verify the PLC program: In OB1 or relevant function blocks, check for any PROFIBUS I/O area assignments using DBW/DBD access patterns. Ensure the area offset and slot ID match the MD10506 configuration and do not exceed allocated I/O memory.