4700

Navigate to Siemens HMI > Diagnosis > Machine Data > MD10500 $MN_DPIO_LOGIC_ADDRESS_IN. Document all configured logical slot addresses and their corresponding physical slot numbers.

Cross-reference the logical address from the alarm message (%1 parameter) against the MD10500 entries. Verify that an entry exists for this address with a valid slot assignment (typically slot 1-8 for PROFIBUS slaves).

Ensure the MD10500 entry uses the correct indexing syntax: MD10500[slot_index] = logical_address

If the address is missing, add a new MD10500 entry with the correct logical address and physical slot pairing. If incorrect, correct the logical address value to match your PROFIBUS GSD configuration.

Save machine data changes and perform a controlled system restart (Siemens HMI > Service > System > Warm Start) to reload the DPIO configuration into the NCK.

Do not perform a power-cycle reset; use warm start to ensure proper MD loading

Access the PROFIBUS master configuration via Siemens automation tool (TIA Portal or STEP 7) and verify that all PROFIBUS slaves referenced in MD10500 are present in the slave list with correct device identifiers and GSD file versions.

Check the PROFIBUS diagnostics on the 840D HMI: Navigate to Diagnosis > Communication > PROFIBUS > Slave Status. Confirm that the slave corresponding to the logical address in the alarm is showing 'Ready' or 'Operational' status, not 'Offline' or 'Error'.

A slave showing 'Offline' indicates a hardware fault, cable issue, or incorrect commissioning

Verify the GSD file used during slave configuration matches the actual slave hardware revision. Re-commission the slave if necessary, ensuring the correct GSD is selected and the slave is powered and electrically connected.

After confirming slave availability and GSD correctness, perform a PROFIBUS reinitialization: Siemens HMI > Service > Communication > PROFIBUS > Reinitialize. Monitor the reinit process for completion.

In the Siemens HMI Machine Data editor, examine the exact syntax of the MD10500 entry in question. Verify the format: MD10500[index] should contain a valid integer logical address (0-127). Check for spaces, special characters, or missing operators.

Common errors: MD10500[8] = 256 (address out of range) or MD10500[slot_1] = address (incorrect index type)

Consult the SINUMERIK 840D documentation (840D_ProgGuide_PROFIBUS.pdf) for the correct MD10500 syntax and valid address range. Correct any syntax errors or out-of-range values in the MD entry.

Delete and re-create the problematic MD10500 entry using the correct syntax and a valid logical address within the documented range. Verify the entry is accepted by the HMI without parse errors.