What causes Siemens SINUMERIK alarm 100910?

Part program contains an illegal or unsupported command for the current machine configuration. Parameter or machine data setting incompatible with the commanded operation. Required option or function not enabled on this SINUMERIK control. Incorrect axis assignment or configuration for the commanded function. Software version or compile cycle version mismatch.

How do I fix Siemens SINUMERIK alarm 100910?

1. Note the full alarm message including any parameter values shown (e.g., axis number, block number, channel). 2. Identify the program block or operation that triggered the alarm. 3. Review the SINUMERIK alarm manual for alarm 100910 to identify the specific cause and remedy. 4. Check the relevant machine data parameters referenced in the alarm. 5. If the alarm persists after correcting the program, contact Siemens technical support with the full alarm text and machine data backup.

axismd.ai

Siemens SINUMERIK Controller

Communication · Intermediate · 30-120 minutes

Alarm 100910

Siemens 840D 100910 - Remote diagnostics: Error 00 -int4f_func(CREATE_SRV)-

Alarm 100910 indicates a failure in the remote diagnostics service during the CREATE_SRV function initialization. This is typically related to communication service initialization failures between the NCU and external diagnostic tools, often caused by network configuration issues, firewall blocking, or corrupted VPN/remote access service parameters.

Siemens SINUMERIKCommunicationIntermediate30-120 minutes

100910

Siemens 840D 100910 - Remote diagnostics: Error 00 -int4f_func(CREATE_SRV)-

Remote diagnostics: Error 00 -int4f_func(CREATE_SRV)-

Root Cause Summary

Alarm 100910 indicates a failure in the remote diagnostics service during the CREATE_SRV function initialization. This is typically related to communication service initialization failures between the NCU and external diagnostic tools, often caused by network configuration issues, firewall blocking, or corrupted VPN/remote access service parameters.

Safety

Refer to Siemens documentation
Ensure qualified technician performs repairs

Causes and Fixes

1
Verify NCU network settings: Check IP address, subnet mask, and gateway configuration in HMI under Commissioning > Network settings. Ensure settings match your network infrastructure.
2
Verify that TCP ports 102, 443, and 5900-5910 are open and not blocked by Windows Firewall or corporate firewall on both NCU and connecting PC.
Coordinate with IT department before modifying firewall rules on production networks.
3
Test network connectivity using PING command from HMI diagnostics to the remote diagnostic PC. Check for packet loss or timeout errors.
4
Restart the NCU communication services via HMI: Go to Commissioning > System > Control > select 'Restart Communication'. Wait 2-3 minutes for services to reinitialize.
This will temporarily interrupt all network-based communications including HMI connections.

Service Recommended confidence

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.