What causes Siemens SINUMERIK alarm 100650?

Required machine data or parameter not configured for the requested function. Option bit not set in SINUMERIK to enable the required functionality. Program references a function or axis that has not been configured. Machine commissioning incomplete — required setup step was not performed. Configuration data cleared or lost due to a parameter reset or hardware change.

How do I fix Siemens SINUMERIK alarm 100650?

1. Read the full alarm message to identify what is missing (axis name, parameter number, function name). 2. Consult the SINUMERIK alarm manual for alarm 100650 for the specific configuration requirement. 3. Check the relevant machine data group and set the required parameter. 4. If a specific option is required, verify it is licensed and enabled in the SINUMERIK option settings. 5. Power cycle after making configuration changes to apply the new settings.

axismd.ai

Siemens SINUMERIK Controller

PLC · Intermediate · 30-120 minutes

Alarm 100650

Siemens 840D 100650 - No NC/PLC found! NC/PLC being simulated!

SINUMERIK alarm 100650 indicates the NCK (Numerical Control Kernel) and/or PLC cannot be found or properly initialized, forcing the system into simulation mode. This typically occurs during system startup when hardware communication fails or when running in virtual/simulation environments.

Siemens SINUMERIKPLCIntermediate30-120 minutes

100650

Siemens 840D 100650 - No NC/PLC found! NC/PLC being simulated!

No NC/PLC found! NC/PLC being simulated!

Root Cause Summary

SINUMERIK alarm 100650 indicates the NCK (Numerical Control Kernel) and/or PLC cannot be found or properly initialized, forcing the system into simulation mode. This typically occurs during system startup when hardware communication fails or when running in virtual/simulation environments.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Check NCK Power Supply
Verify 24VDC power supply to NCK module and check LED status indicators on NCK unit for proper operation.
Ensure proper lockout/tagout procedures before checking electrical connections.
2
Verify DRIVE-CLiQ Communication
Check DRIVE-CLiQ cable connections between NCU and NCK, inspect for damaged cables or loose connections at X101/X102 interfaces.
Use STARTER software to diagnose DRIVE-CLiQ topology and communication status.
3
Check NCK Module Status
Access HMI Diagnostics > Hardware > NCK to verify module recognition and status in SINUMERIK system configuration.
Compare detected hardware with configured hardware in machine data MD10000 (NCK_MM_SYSTEM_CONFIG).
4
Perform NCK Reset
Execute NCK cold restart via HMI Commissioning > System > NCK > Reset NCK or power cycle the complete system.
Save all programs and data before performing NCK reset as unsaved changes will be lost.

DIY Feasiblehigh confidence

Call a technician if:

·NCK hardware module replacement needed
·Complete software reinstallation required
·DRIVE-CLiQ topology errors persist
·Safety system integration issues

Prevention

Regular system backups including NCK and PLC programs
Monitor DRIVE-CLiQ cable condition during preventive maintenance
Keep system software versions synchronized during updates
Document hardware configuration changes in machine data

Common Mistakes

Disabling simulation mode without verifying hardware connection
Performing NCK reset without backing up programs
Ignoring DRIVE-CLiQ communication errors
Mixing incompatible software versions during updates

Related Alarms

100651 100652 380001 380002 300500

Seeing Multiple Alarms?

Seeing another alarm with this one? Enter the code.

Get machine-aware diagnosis

AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.

Start free

Was this guide helpful?

Always verify with your machine manual or a certified technician before performing service procedures.