Back to all Siemens models Search all database
Siemens SINUMERIK 840D CNC
Siemens SINUMERIK 840D CNC Error Codes
Complete alarm and error code reference for the Siemens SINUMERIK 840D CNC. Browse all 4014 documented fault codes below, each linking to a detailed troubleshooting guide.
Search this section
Search Siemens SINUMERIK 840D CNC
Search all 4014 Siemens SINUMERIK 840D CNC codes without changing pages.
Complete Alarm List (Page 15 of 21)
Code 201065
<location>Drive: Fault on non-active encoder
View solution Code 201099
<location>Tolerance window of time synchronization exited
View solution Code 201100
<location>CU: Memory card withdrawn
View solution Code 201105
<location>CU: Insufficient memory
View solution Code 201107
<location>CU: Save to CompactFlash card unsuccessful
View solution Code 201110
<location>CU: More than one SINAMICS G on one Control Unit
View solution Code 201111
<location>CU: impermissible mixed operation of drive units
View solution Code 201112
<location>CU: Powe r unit not permissible
View solution Code 201120
<location>Terminal initialization has failed
View solution Code 201122
<location>Frequency at the measuring probe input too high
View solution Code 201150
<location>CU: Number of instances of a drive object type exceeded
View solution Code 201200
<location>CU: Time slice management internal software error
View solution Code 201205
<location>CU: Time slice overflow
View solution Code 201210
<location>CU: Basic clock cycle selection and DRIVE-CLiQ clock cycle do not match
View solution Code 201220
<location>CU: Bas clk cyc too low
View solution Code 201221
<location>CU: Bas clk cyc too low
View solution Code 201223
<location>CU: Sampling time inconsistent
View solution Code 201224
<location>CU: Pulse frequency inconsistent
View solution Code 201250
<location>CU: CU-EEPROM incorrect read-only data
View solution Code 201251
<location>CU: CU-EEPROM incorrect read-write data
View solution Code 201255
<location>CU: Option Board EEPROM read-only data error
View solution Code 201256
<location>CU: Option Board EEPROM read-write data error
View solution Code 201303
<location>DRIVE-CLiQ component does not support the required function
View solution Code 201304
<location>Firmware version of DRI VE-CLiQ component is not up-to-date
View solution Code 201305
<location>Topology: Component number missing
View solution Code 201306
<location>Firmware of the DRIVE-CLiQ component being updated
View solution Code 201314
<location>Topology: Component must not be present
View solution Code 201315
<location>Drive object not ready for operation
View solution Code 201316
<location>Drive object inactive and again ready for operation
View solution Code 201317
<location>De-activated component again present
View solution Code 201318
<location>BICO: De-activated interconnections present
View solution Code 201319
<location>Inserted component not initialized
View solution Code 201320
<location>Topology: Drive object number does not exist in configuration
View solution Code 201321
<location>Topology: Drive object number does not exist in configuration
View solution Code 201322
<location>Topology: Drive object number present twice in configuration
View solution Code 201323
<location>Topology: More than two partial lists created
View solution Code 201324
<location>Topology: Dummy drive object number incorrectly created
View solution Code 201330
<location>Topology: Quick commissioning not possible
View solution Code 201331
<location>Topology: At least one component not assigned to a drive object
View solution Code 201340
<location>Topology: Too many components on one line
View solution Code 201354
<location>Topology: Actual topology indicates an illegal component
View solution Code 201355
<location>Topology: Actual topology changed
View solution Code 201360
<location>Topology: Actual topology is illegal
View solution Code 201361
<location>Topology: Actual to pology contains SINUMERIK and SIMOTION components
View solution Code 201375
<location>Topology: Actual topol ogy, duplicate connection between two components
View solution Code 201380
<location>Topology: Actual topology, defective EEPROM
View solution Code 201381
<location>Topology: Comparison power unit shifted
View solution Code 201382
<location>Topology: Comparison Sensor Module shifted
View solution Code 201383
<location>Topology: Comparison Terminal Module shifted
View solution Code 201384
<location>Topology: Comparison DRIVE-CLiQ Hub Module shifted
View solution Code 201385
<location>Topology: Comparison CX32 shifted
View solution Code 201386
<location>Topology: Comparison DRIVE-CLiQ component shifted
View solution Code 201387
<location>Topology: Comparison option slot component shifted
View solution Code 201388
<location>Topology: Comparison EnDat encoder shifted
View solution Code 201389
<location>Topology: Comparison motor with DRIVE-CLiQ shifted
View solution Code 201416
<location>Topology: Comparison additional component in actual topology
View solution Code 201420
<location>Topology: Comparison a component is different
View solution Code 201421
<location>Topology: Comparison different components
View solution Code 201425
<location>Topology: Comparison serial number of a component is different
View solution Code 201428
<location>Topo: Comparison connection of a component is different
View solution Code 201429
<location>Topology: Comparison connection is different for more than one component
View solution Code 201451
<location>Topology: Target topology is invalid
View solution Code 201470
<location>Topology: Target topology ring-type connection
View solution Code 201475
<location>Topology: Target topology duplicate connection between two components
View solution Code 201481
<location>Topology: Comparison power unit missing in the actual topology
View solution Code 201482
<location>Topology: Comparison Sensor Module missing in the actual topology
View solution Code 201483
<location>Topology: Comparison Terminal Module missing in the actual topology
View solution Code 201484
<location>Topology: Comparison DRIVE-CLiQ Hub Module missing in the actual topology
View solution Code 201485
<location>Topology: Comparison CX32 missing in the actual topology
View solution Code 201486
<location>Topology: Comparison DRIVE-CLiQ components missing in the actual topology
View solution Code 201487
<location>Topology: Comparison opti on slot components missing in the actual topology
View solution Code 201488
<location>Topology: Comparison EnDat encoder missing in the actual topology
View solution Code 201489
<location>Topology: Comparison motor with DRIVE-CLiQ missing in the actual topology
View solution Code 201505
<location>BICO: Interconnection cannot be established
View solution Code 201506
<location>BICO: No standard telegram
View solution Code 201507
<location>BICO: Interconnections to inactive objects present
View solution Code 201508
<location>BICO: Interconnections to inactive objects exceeded
View solution Code 201510
<location>BICO: Signal source is not float type
View solution Code 201511
<location>BICO: Interconnecti on between different normalizations
View solution Code 201512
<location>BICO: No normalization available
View solution Code 201513
<location>BICO: Spanning DO between different normalizations
View solution Code 201514
<location>BICO: Error when writing during a reconnect
View solution Code 201515
<location>BICO: Writing to parameter not permitted as the master control is active
View solution Code 201590
<location>Drive: Motor maintenance interval expired
View solution Code 201600
<location>SI CU: STOP A initiated
View solution Code 201611
<location>SI CU: Defect in a monitoring channel
View solution Code 201612
<location>SI CU: STO inputs for power units connected in parallel different
View solution Code 201620
<location>SI CU: Safe Torque Off active
View solution Code 201621
<location>SI CU: Safe Stop 1 active
View solution Code 201625
<location>SI CU: Sign-of-life error in safety data
View solution Code 201630
<location>SI CU: Brake control error
View solution Code 201649
<location>SI CU: Internal software error
View solution Code 201650
<location>SI CU: Acceptance test required
View solution Code 201651
<location>SI CU: Synchronization safety time slices unsuccessful
View solution Code 201652
<location>SI CU: Illegal monitoring clock cycle
View solution Code 201653
<location>SI CU: PROFIBUS configuration error
View solution Code 201655
<location>SI CU: Align monitoring functions
View solution Code 201656
<location>SI CU: Moto r Module para meter error
View solution Code 201659
<location>SI CU: Write request for parameter rejected
View solution Code 201660
<location>SI CU: Safety-related functions not supported
View solution Code 201663
<location>SI CU: Copying of SI parameters rejected
View solution Code 201664
<location>SI CU: No automatic firmware update
View solution Code 201670
<location>SI Motion: Invalid parameterization Sensor Module
View solution Code 201671
<location>SI Motion: Parameterization encoder error
View solution Code 201672
<location>SI Motion: Motor Module software/hardware incompatible
View solution Code 201673
<location>SI Motion: Sensor Module software/hardware incompatible
View solution Code 201680
<location>SI Motion CU: Checksum error safety monitoring functions
View solution Code 201681
<location>SI Motion CU: Incorrect parameter value
View solution Code 201682
<location>SI Motion CU: Monitoring function not supported
View solution Code 201683
<location>SI Motion CU: SOS/SLS enable missing
View solution Code 201684
<location>SI Motion: Safely limited position limit values interchanged
View solution Code 201685
<location>SI Motion CU: Safely-limited speed limit value too high
View solution Code 201686
<location>SI Motion: Illegal parameterization cam position
View solution Code 201687
<location>SI Motion: Illegal pa rameterization modulo value SCA (SN)
View solution Code 201688
<location>SI Motion CU: Actual value synchronization not permissible
View solution Code 201689
<location>SI Motion: Axis re-configured
View solution Code 201690
<location>SI Motion: Data save problem for the NVRAM
View solution Code 201691
<location>SI Motion: Ti and To unsuitable for DP cycle
View solution Code 201696
<location>SI Motion: Testing of the motion monitoring functions selected when booting
View solution Code 201697
<location>SI Motion: Motion monitoring functions must be tested
View solution Code 201698
<location>SI CU: Commissioning mode active
View solution Code 201699
<location>SI CU: Shutdown path must be tested
View solution Code 201700
<location>SI Motion CU: STOP A initiated
View solution Code 201701
<location>SI Motion CU: STOP B initiated
View solution Code 201706
<location>SI Motion CU: Safe Acceleration Monitor limit exceeded
View solution Code 201707
<location>SI Motion CU: Tolerance for safe operating stop exceeded
View solution Code 201708
<location>SI Motion CU: STOP C initiated
View solution Code 201709
<location>SI Motion CU: STOP D initiated
View solution Code 201710
<location>SI Motion CU: STOP E initiated
View solution Code 201711
<location>SI Motion CU: Defect in a monitoring channel
View solution Code 201714
<location>SI Motion CU: Safely-Limited Speed exceeded
View solution Code 201745
<location>SI Motion CU: Checking braking torque for the brake test
View solution Code 201750
<location>SI Motion CU: Hardware fault safety-relevant encoder
View solution Code 201751
<location>SI Motion CU: eff.test error safe encoder
View solution Code 201796
<location>SI Motion CU: Wait for communication
View solution Code 201798
<location>SI Motion CU: Test stop running
View solution Code 201799
<location>SI Motion CU: Acceptance test mode active
View solution Code 201800
<location>DRIVE-CLiQ: Hardware/configuration error
View solution Code 201802
<location>CU DRIVE-CLiQ: POWE R ON due to basic sampling times
View solution Code 201840
<location>SMI: Component found with changed data
View solution Code 201900
<location>PROFIBUS: Configuration telegram error
View solution Code 201901
<location>PROFIBUS: Parameterizing telegram error
View solution Code 201902
<location>IF1: PB/PN clock cycle synchronous operation parameterization not permissible
View solution Code 201903
<location>COMM INT: Receive configuration data invalid
View solution Code 201910
<location>PROFIBUS: Setpoint timeout
View solution Code 201911
<location>IF1: PB/PN clock cycle synchronous operation clock cycle failure
View solution Code 201912
<location>IF1: PB/PN clock cycle synchronous operation sign-of-life failure
View solution Code 201913
<location>COMM INT: Monitoring time sign-of-life expired
View solution Code 201914
<location>COMM INT: Monitoring time configuration expired
View solution Code 201920
<location>PROFIBUS: Interruption cyclic connection
View solution Code 201921
<location>PROFIBUS: Receive setpoints after To
View solution Code 201930
<location>IF1: PB/PN current controller clock cycle clock cycle synchronous not equal
View solution Code 201931
<location>IF1: PB/PN speed c ontroller clock cycle clock cycle synchronous not equal
View solution Code 201932
<location>IF1: PB/PN clock cycle synchronization missing for DSC
View solution Code 201940
<location>IF1: PB/PN clock cycle synchronism not reached
View solution Code 201941
<location>IF1: PB/PN clock cycle signal missing when establishing bus communication
View solution Code 201943
<location>IF1: PB/PN clock cycle signal error when establishing bus communication
View solution Code 201944
<location>IF1: PB/PN sign-of-life synchronism not reached
View solution Code 201945
<location>PROFIBUS: Connection to the Publisher failed
View solution Code 201946
<location>PROFIBUS: Connection to the Publisher aborted
View solution Code 201950
<location>IF1: PB/PN clock cycle synchronous operation synchronization unsuccessful
View solution Code 201951
<location>CU DRIVE-CLiQ: Synchr onization application clock cycle missing
View solution Code 201952
<location>CU DRIVE-CLiQ: Synchronization of component not supported
View solution Code 201953
<location>CU DRIVE-CLiQ: Synchronization not completed
View solution Code 201954
<location>CU DRIVE-CLiQ: Synchronization unsuccessful
View solution Code 201955
<location>CU DRIVE-CLiQ: Sy nchronization DO not completed
View solution Code 202000
<location>Function generator: Start not possible
View solution Code 202005
<location>Function generator: Drive does not exist
View solution Code 202006
<location>Function generator: No drive specified for connection
View solution Code 202007
<location>Function generator: Drive not SERVO / VECTOR
View solution Code 202008
<location>Function generator: Drive specified a multiple number of times
View solution Code 202009
<location>Function generator: Illegal mode
View solution Code 202010
<location>Function generator: Speed setpoint from the drive is not zero
View solution Code 202011
<location>Function generator: The actual drive speed is not zero
View solution Code 202015
<location>Function generator: Drive enable signals missing
View solution Code 202016
<location>Function generator: Magnetizing running
View solution Code 202020
<location>Function generator: Parameter cannot be changed
View solution Code 202025
<location>Function generator: Period too short
View solution Code 202026
<location>Function generator: Pulse width too high
View solution Code 202030
<location>Function generator: Physical address equals zero
View solution Code 202040
<location>Function generator: Illegal value for offset
View solution Code 202041
<location>Function generator: Illegal value for bandwidth
View solution Code 202047
<location>Function generator: Time slice clock cycle invalid
View solution Code 202050
<location>Trace: Start not possible
View solution Code 202055
<location>Trace: Recording time too short
View solution Code 202056
<location>Trace: Recording cycle too short
View solution Code 202057
<location>Trace: Time slice clock cycle invalid
View solution Code 202058
<location>Trace: Time slice clock cycle for endless trace not valid
View solution Code 202059
<location>Trace: Time slice clock cycle for 2 x 8 recording channels not valid
View solution Code 202060
<location>Trace: Signal to be traced missing
View solution Code 202061
<location>Trace: Invalid signal
View solution Code 202062
<location>Trace: Invalid trigger signal
View solution Code 202063
<location>Trace: Invalid data type
View solution Code 202070
<location>Trace: Parameter cannot be changed
View solution Code 202075
<location>Trace: Pretrigger time too long
View solution Code 202080
<location>Trace: Delete trace because units changed over
View solution Code 202099
<location>Trace: Insufficient Control Unit memory
View solution Code 202100
<location>CU: Computing dead ti me current controller too short
View solution Code 202150
<location>OA: Appli cation cannot be loaded
View solution Code 202151
<location>OA: Internal software error
View solution