FaultResolve
Volver a todos los modelos de Siemens
Siemens SINUMERIK 840D CNC

Códigos de error de Siemens SINUMERIK 840D CNC

Referencia completa de códigos de alarma y error para Siemens SINUMERIK 840D CNC. Explore a continuación los 4014 códigos de falla documentados, cada uno con un enlace a una guía detallada de solución de problemas.

Search this section

Search Siemens SINUMERIK 840D CNC

Search all 4014 Siemens SINUMERIK 840D CNC codes without changing pages.

Search all database

Lista completa de alarmas (Page 15 of 21)

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