SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020) - page 20

 

  Index      Manuals     SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020)

 

Search            copyright infringement  

 

   

 

    

 

Content      ..     45      46      47      48     ..

 

 

 

SINUMERIK 840D sl, SINAMICS S120. Alarms. Diagnostics Manual (2020) - page 20

 

 

SINAMICS alarms
Cause:
The encoder signals a set error bit via the serial protocol.
Fault value (r0949, interpret binary):
Bit 0: Fault bit in the position protocol.
Remedy:
For fault value, bit 0 = 1:
In the case of an EnDat encoder, F31111 may provide further details.
233115
<location>Encoder 3: Signal level track A or B too low
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
A track: %1, B-track: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Cause:
The signal level (root from A^2 + B^2) of the encoder falls below the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 170 mV (input frequency <= 256 kHz) or < 120 mV (input frequency > 256 kHz).
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note for Sensor Modules for resolvers (e.g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold is < 1070 mV.
A signal level of 2900 mV peak value corresponds to the numerical value 6666 hex = 26214 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy:
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
The following applies to measuring systems without their own bearing system:
- adjust the scanning head and check the bearing system of the measuring wheel.
The following applies for measuring systems with their own bearing system:
- ensure that the encoder housing is not subject to any axial force.
233116
<location>Encoder 3: Signal level track A or B too low
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
A track: %1, B-track: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
1320
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The signal level of the rectified encoder signals A and B of the encoder fall below the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 130 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy:
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
233117
<location>Encoder 3: Inversion error signals A/B/R
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For a square-wave encoder (bipolar, double ended) signals A*, B* and R* are not inverted with respect to signals A, B and
R.
Fault value (r0949, interpret binary):
Bits 0 ... 15: Only for internal Siemens troubleshooting.
Bit 16: Error track A.
Bit 17: Error track B.
Bit 18: Error track R.
Note:
For SMC30 (only Article No. 6SL3055-0AA00-5CA0 and 6SL3055-0AA00-5CA1), CUA32 and CU310-2, the following applies:
A square-wave encoder without track R is used and track monitoring (p0405.2 = 1) is activated.
Remedy:
- check the encoder/cable.
- Does the encoder supply signals and the associated inverted signals?
Note:
For SMC30 (only Article Number 6SL3055-0AA00-5CA0 and 6SL3055-0AA00-5CA1), the following applies:
- check the setting of p0405 (p0405.2 = 1 is only possible if the encoder is connected at X520).
For a square-wave encoder without track R, the following jumpers must be set for the connection at X520 (SMC30), X220
(CUA32) or X23 (CU310-2):
- pin 10 (reference signal R) <--> pin 7 (encoder power supply, ground)
- pin 11 (reference signal R inverted) <--> pin 4 (encoder power supply)
233118
<location>Encoder 3: Speed change not plausible
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1321
SINAMICS alarms
Cause:
For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles.
The change to the averaged speed actual value - if applicable - is monitored in the current controller sampling time.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492
Remedy:
- check the tachometer feeder cable for interruptions.
- check the grounding of the tachometer shielding.
- if required, increase the maximum speed difference per sampling cycle (p0492).
233120
<location>Encoder 3: Encoder power supply fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Cause:
An encoder power supply fault was detected.
Fault value (r0949, interpret binary):
Bit 0: Undervoltage condition on the sense line.
Bit 1: Overcurrent condition for the encoder power supply.
Bit 2: Overcurrent condition for encoder power supply on cable resolver excitation negative.
Bit 3: Overcurrent condition for encoder power supply on cable resolver excitation positive.
Bit 4: The 24 V power supply through the Power Module (PM) is overloaded.
Bit 5: Overcurrent at the EnDat connection of the converter.
Bit 6: Overvoltage at the EnDat connection of the converter.
Bit 7: Hardware fault at the EnDat connection of the converter.
Note:
If the encoder cables 6FX2002-2EQ00-
and 6FX2002-2CH00-
are interchanged, this can result in the encoder being
destroyed because the pins of the operating voltage are reversed.
Remedy:
For fault value, bit 0 = 1:
- correct encoder cable connected?
- check the plug connections of the encoder cable.
- SMC30: Check the parameterization (p0404.22).
For fault value, bit 1 = 1:
- correct encoder cable connected?
- replace the encoder or encoder cable.
For fault value, bit 2 = 1:
- correct encoder cable connected?
- replace the encoder or encoder cable.
For fault value, bit 3 = 1:
- correct encoder cable connected?
- replace the encoder or encoder cable.
For fault value, bit 5 = 1:
- Measuring unit correctly connected at the converter?
- Replace the measuring unit or the cable to the measuring unit.
For fault value, bit 6, 7 = 1:
- Replace the defective EnDat 2.2 converter.
233121
<location>Encoder 3: Determined commutation position incorrect
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Alarms
1322
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Cause:
A commutation position actual value sensing error was detected.
Remedy:
Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
233122
<location>Encoder 3: Sensor Module hardware fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1
Acknowledge:
IMMEDIATELY
Cause:
An internal Sensor Module hardware fault was detected.
Fault value (r0949, interpret decimal):
1: Reference voltage error.
2: Internal undervoltage.
3: Internal overvoltage.
Remedy:
Replace the motor with DRIVE-CLiQ or the appropriate Sensor Module.
233123
<location>Encoder 3: Signal level A/B outside tolerance
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The unipolar level (AP/AN or BP/BN) for encoder 3 is outside the permissible tolerance.
Fault value (r0949, interpret binary):
Bit 0 = 1: Either AP or AN outside the tolerance.
Bit 16 = 1: Either BP or BN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy:
- make sure that the encoder cables and shielding are installed in an EMC-compliant manner.
- check the plug connections and contacts of the encoder cable.
- check the short-circuit of a signal cable with mass or the operating voltage.
- replace the encoder cable.
233125
<location>Encoder 3: Signal level track A or B too high
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
A track: %1, B-track: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1323
SINAMICS alarms
Cause:
The signal level (root from A^2 + B^2) of the encoder exceeds the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track B (16 bits with sign).
xxxx = Signal level, track A (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note for Sensor Modules for resolvers (e.g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms).
The response threshold is > 3582 mV.
A signal level of 2900 mV peak value corresponds to the numerical value 6666 hex = 26214 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy:
- check that the encoder cables and shielding are routed in compliance with EMC.
- replace the encoder or encoder cable.
233126
<location>Encoder 3: Signal level track A or B too high
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Amplitude: %1, Angle: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Cause:
The signal level (|A| + |B|) of the encoder exceeds the permissible limit value.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Angle
xxxx = amplitude, i.e. root of A^2 + B^2 (16 bits without sign)
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold for (|A| + |B|) is > 1120 mV or the root of (A^2 + B^2) > 955 mV.
A signal level of 500 mV peak value corresponds to the numerical value of 299A hex = 10650 dec.
The angle 0 ... FFFF hex corresponds to 0 ... 360 degrees of the fine position. Zero degrees is present at the negative zero
crossover of track B.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Remedy:
- check that the encoder cables and shielding are routed in compliance with EMC.
- replace the encoder or encoder cable.
233129
<location>Encoder 3: Position difference hall sensor/track C/D and A/B too large
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
1324
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than
+/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
After the fine synchronization using one reference mark or 2 reference marks for distance-coded encoders, this fault is no
longer initiated, but instead, Alarm A33429.
Fault value (r0949, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy:
- track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
233130
<location>Encoder 3: Zero mark and position error from the coarse synchronization
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Angular deviation, electrical: %1, angle, mechanical: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Cause:
After initializing the pole position using track C/D, Hall signals or pole position identification routine, the zero mark was
detected outside the permissible range. For distance-coded encoders, the test is carried out after passing 2 zero marks. Fine
synchronization was not carried out.
When initializing via track C/D (p0404) then it is checked whether the zero mark occurs in an angular range of +/-18 °
mechanical.
When initializing via Hall sensors (p0404) or pole position identification (p1982) it is checked whether the zero mark occurs
in an angular range of +/-60 ° electrical.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
yyyy: Determined mechanical zero mark position (can only be used for track C/D).
xxxx: Deviation of the zero mark from the expected position as electrical angle.
Scaling: 32768 dec = 180 °
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- if the Hall sensor is used as an equivalent for track C/D, check the connection.
- check the connection of track C or D.
- replace the encoder or encoder cable.
233131
<location>Encoder 3: Position deviation incremental/absolute too high
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1325
SINAMICS alarms
Cause:
Absolute encoder:
When cyclically reading the absolute position, an excessively high difference to the incremental position was detected. The
absolute position that was read is rejected.
Limit value for the deviation:
- EnDat encoder: Is supplied from the encoder and is a minimum of 2 quadrants (e.g. EQI 1325 > 2 quadrants, EQN 1325
> 50 quadrants).
- other encoders: 15 pulses = 60 quadrants.
Incremental encoder:
When the zero pulse is passed, a deviation in the incremental position was detected.
For equidistant zero marks, the following applies:
- the first zero mark passed supplies the reference point for all subsequent checks. The other zero marks must have n times
the distance referred to the first zero mark.
For distance-coded zero marks, the following applies:
- the first zero mark pair supplies the reference point for all subsequent checks. The other zero mark pairs must have the
expected distance to the first zero mark pair.
Fault value (r0949, interpret decimal):
Deviation in quadrants (1 pulse = 4 quadrants).
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check whether the coding disk is dirty or there are strong ambient magnetic fields.
- adapt the parameter for the clearance between zero marks (p0425).
- if message output above speed threshold, reduce filter time if necessary (p0438).
233135
<location>Encoder 3: Fault when determining the position (singleturn)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
1326
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The encoder has identified a position determination fault (singleturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy:
- determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
233136
<location>Encoder 3: Fault when determining the position (multiturn)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1327
SINAMICS alarms
Cause:
The encoder has identified a position determination fault (multiturn) and supplies status information bit by bit in an internal
status/fault word.
Some of these bits cause this fault to be triggered. Other bits are status displays. The status/fault word is displayed in the
fault value.
Note regarding the bit designation:
The first designation is valid for DRIVE-CLiQ encoders, the second for EnDat 2.2 encoders.
Fault value (r0949, interpret binary):
Bit 0: F1 (safety status display).
Bit 1: F2 (safety status display).
Bit 2: Reserved (lighting).
Bit 3: Reserved (signal amplitude).
Bit 4: Reserved (position value).
Bit 5: Reserved (overvoltage).
Bit 6: Reserved (undervoltage)/hardware fault EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 7: Reserved (overcurrent)/EnDat encoder withdrawn when not in the parked state (--> F3x110, x = 1, 2, 3).
Bit 8: Reserved (battery)/overcurrent EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 9: Reserved/overvoltage EnDat supply (--> F3x110, x = 1, 2, 3).
Bit 11: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 12: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 13: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 14: Reserved/internal communication error (--> F3x110, x = 1, 2, 3).
Bit 15: Internal communication error (--> F3x110, x = 1, 2, 3).
Bit 16: Lighting (--> F3x135, x = 1, 2, 3).
Bit 17: Signal amplitude (--> F3x135, x = 1, 2, 3).
Bit 18: Singleturn position 1 (--> F3x135, x = 1, 2, 3).
Bit 19: Overvoltage (--> F3x135, x = 1, 2, 3).
Bit 20: Undervoltage (--> F3x135, x = 1, 2, 3).
Bit 21: Overcurrent (--> F3x135, x = 1, 2, 3).
Bit 22: Temperature exceeded (--> F3x405, x = 1, 2, 3).
Bit 23: Singleturn position 2 (safety status display).
Bit 24: Singleturn system (--> F3x135, x = 1, 2, 3).
Bit 25: Singleturn power down (--> F3x135, x = 1, 2, 3)
Bit 26: Multiturn position 1 (--> F3x136, x = 1, 2, 3).
Bit 27: Multiturn position 2 (--> F3x136, x = 1, 2, 3).
Bit 28: Multiturn system (--> F3x136, x = 1, 2, 3).
Bit 29: Multiturn power down (--> F3x136, x = 1, 2, 3).
Bit 30: Multiturn overflow/underflow (--> F3x136, x = 1, 2, 3).
Bit 31: Multiturn battery (reserved).
Remedy:
- determine the detailed cause of the fault using the fault value.
- replace the encoder if necessary.
Note:
An EnDat 2.2 encoder may only be removed and inserted in the "Park" state.
If an EnDat 2.2 encoder was removed when not in the "Park" state, then after inserting the encoder, a POWER ON (switch-
off/switch-on) is necessary to acknowledge the fault.
233137
<location>Encoder 3: Fault when determining the position (singleturn)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
1328
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A position determination fault has occurred in the DRIVE-CLiQ encoder.
Fault value (r0949, interpret binary):
yyxxxxxx hex: yy = encoder version, xxxxxx = bit coding of the fault cause
----------
For yy = 8 (0000 1000 bin), the following applies:
Bit 1: Signal monitoring (sin/cos).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 16: LED monitoring.
Bit 17: Fault when determining the position (multiturn).
Bit 18: Single-step capability monitoring singleturn from the Safety channel.
Bit 19: ECRC, configuration error in the safety channel.
Bit 23: Temperature outside the limit values.
----------
For yy = 11 (0000 1011 bin), the following applies:
Bit 0: Position word 1 difference between rotation counter and software counter (XC_ERR).
Bit 1: Position word 1 track error of the incremental signals (LIS_ERR).
Bit 2: Position word 1 error when aligning between incremental track signals and absolute value (ST_ERR).
Bit 3: Maximum permissible temperature exceeded (TEMP_ERR).
Bit 4: Power supply overvoltage (MON_OVR_VOLT).
Bit 5: Power supply overcurrent (MON_OVR_CUR).
Bit 6: Power supply undervoltage (MON_UND_VOLT).
Bit 7: Rotation error counter (MT_ERR).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 11: Position word 1 status bit: singleturn position OK (ADC_ready).
Bit 12: Position word 1 status bit: rotation counter OK (MT_ready).
Bit 13: Position word 1 memory error (MEM_ERR).
Bit 14: Position word 1 absolute position error (MLS_ERR).
Bit 15: position word 1 LED error, lighting unit error (LED_ERR).
Bit 18: Position word 2 error when aligning between incremental track signals and absolute value (ST_ERR).
Bit 21: Position word 2 memory error (MEM_ERR).
Bit 22: Position word 2 absolute position error (MLS_ERR).
Bit 23: position word 2 LED error, lighting unit error (LED_ERR).
----------
For yy = 12 (0000 1100 bin), the following applies:
Bit 8: encoder fault.
Bit 10: error in the internal position data transport.
----------
For yy = 14 (0000 1110 bin), the following applies:
Bit 0: Position word 1 temperature outside limit value.
Bit 1: Position word 1 position determination error (multiturn).
Bit 2: Position word 1 FPGA error.
Bit 3: Position word 1 velocity error.
Bit 4: Position word 1 communication error between FPGAs/error in the incremental signal.
Bit 5: Position word 1 timeout absolute value/error when determining the position (singleturn).
Bit 6: Position word 1 internal hardware fault (clock/power monitor IC/power).
Bit 7: Position word 1 internal error (FPGA communication/FPGA parameterization/self-test/software).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 16: Position word 2 temperature outside limit value.
Bit 17: Position word 2 position determination error (multiturn).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1329
SINAMICS alarms
Bit 18: Position word 2 FPGA error.
Bit 19: Position word 2 velocity error.
Bit 20: Position word 2 communication error between FPGAs.
Bit 21: Position word 2 position determination error (singleturn).
Bit 22: Position word 2 internal hardware fault (clock/power monitor IC/power).
Bit 23: Position word 2 internal error (self-test/software).
----------
Note:
For an encoder version that is not described here, please contact the encoder manufacturer for more detailed information
on the bit coding.
Remedy:
- determine the detailed cause of the fault using the fault value.
- if required, replace the DRIVE-CLiQ encoder.
233138
<location>Encoder 3: Fault when determining the position (multiturn)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
1330
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A position determination fault has occurred in the DRIVE-CLiQ encoder.
Fault value (r0949, interpret binary):
yyxxxxxx hex: yy = encoder version, xxxxxx = bit coding of the fault cause
----------
For yy = 8 (0000 1000 bin), the following applies:
Bit 1: Signal monitoring (sin/cos).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 16: LED monitoring.
Bit 17: Fault when determining the position (multiturn).
Bit 19: ECRC, configuration error in the safety channel.
Bit 23: Temperature outside the limit values.
----------
For yy = 11 (0000 1011 bin), the following applies:
Bit 0: Position word 1 difference between rotation counter and software counter (XC_ERR).
Bit 1: Position word 1 track error of the incremental signals (LIS_ERR).
Bit 2: Position word 1 error when aligning between incremental track signals and absolute value (ST_ERR).
Bit 3: Maximum permissible temperature exceeded (TEMP_ERR).
Bit 4: Power supply overvoltage (MON_OVR_VOLT).
Bit 5: Power supply overcurrent (MON_OVR_CUR).
Bit 6: Power supply undervoltage (MON_UND_VOLT).
Bit 7: Rotation error counter (MT_ERR).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 11: Position word 1 status bit: singleturn position OK (ADC_ready).
Bit 12: Position word 1 status bit: rotation counter OK (MT_ready).
Bit 13: Position word 1 memory error (MEM_ERR).
Bit 14: Position word 1 absolute position error (MLS_ERR).
Bit 15: position word 1 LED error, lighting unit error (LED_ERR).
Bit 18: Position word 2 error when aligning between incremental track signals and absolute value (ST_ERR).
Bit 21: Position word 2 memory error (MEM_ERR).
Bit 22: Position word 2 absolute position error (MLS_ERR).
Bit 23: position word 2 LED error, lighting unit error (LED_ERR).
----------
For yy = 14 (0000 1110 bin), the following applies:
Bit 0: Position word 1 temperature outside limit value.
Bit 1: Position word 1 position determination error (multiturn).
Bit 2: Position word 1 FPGA error.
Bit 3: Position word 1 velocity error.
Bit 4: Position word 1 communication error between FPGAs/error in the incremental signal.
Bit 5: Position word 1 timeout absolute value/error when determining the position (singleturn).
Bit 6: Position word 1 internal hardware fault (clock/power monitor IC/power).
Bit 7: Position word 1 internal error (FPGA communication/FPGA parameterization/self-test/software).
Bit 8: F1 (safety status display) error position word 1.
Bit 9: F2 (safety status display) error position word 2.
Bit 16: Position word 2 temperature outside limit value.
Bit 17: Position word 2 position determination error (multiturn).
Bit 18: Position word 2 FPGA error.
Bit 19: Position word 2 velocity error.
Bit 20: Position word 2 communication error between FPGAs.
Bit 21: Position word 2 position determination error (singleturn).
Bit 22: Position word 2 internal hardware fault (clock/power monitor IC/power).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1331
SINAMICS alarms
Bit 23: Position word 2 internal error (self-test/software).
----------
Note:
For an encoder version that is not described here, please contact the encoder manufacturer for more detailed information
on the bit coding.
Remedy:
- determine the detailed cause of the fault using the fault value.
- if required, replace the DRIVE-CLiQ encoder.
233142
<location>Encoder 3: Battery voltage fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
When switched-off, the encoder uses a battery to back up the multiturn information. The battery voltage is no longer
sufficient to check the multiturn information.
Remedy:
Replace battery.
233150
<location>Encoder 3: Initialization error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Cause:
Encoder functionality selected in p0404 cannot be executed.
Fault value (r0949, interpret hexadecimal):
Encoder malfunction.
The bit assignment corresponds to that of p0404 (e.g. bit 5 set: Error track C/D).
Remedy:
- check that p0404 is correctly set.
- check the encoder type used (incremental/absolute) and for SMCxx, the encoder cable.
- if relevant, note additional fault messages that describe the fault in detail.
233151
<location>Encoder 3: Encoder speed for initialization AB too high
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Cause:
The encoder speed is too high while initializing the Sensor Module.
Remedy:
Reduce the speed of the encoder accordingly during initialization.
If necessary, deactivate monitoring (p0437.29).
See also: p0437
233152
<location>Encoder 3: Max. signal frequency (track A/B) exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Alarms
1332
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
PULSE INHIBIT
Cause:
The maximum signal frequency of the encoder evaluation has been exceeded.
Fault value (r0949, interpret decimal):
Actual input frequency in Hz.
See also: p0408
Remedy:
- reduce the speed.
- Use an encoder with a lower pulse number (p0408).
233153
<location>Encoder 3: Identification error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
An error has occurred when identifying the encoder (waiting) p0400 = 10100.
The connected encoder was not able to be identified.
Fault value (r0949, interpret binary):
Bit 0: Data length incorrect.
See also: p0400 (Encoder type selection)
Remedy:
Manually configure the encoder according to the data sheet.
233160
<location>Encoder 3: Analog sensor channel A failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE)
Vector: OFF1 (IASC/DCBRK, NONE)
Hla: OFF1 (NONE)
Acknowledge:
PULSE INHIBIT
Cause:
The input voltage of the analog sensor is outside the permissible limits.
Fault value (r0949, interpret decimal):
1: Input voltage outside detectable measuring range.
2: Input voltage outside the measuring range set in (p4673).
3: The absolute value of the input voltage has exceeded the range limit (p4676).
Remedy:
For fault value = 1:
- check the output voltage of the analog sensor.
For fault value = 2:
- check the voltage setting for each encoder period (p4673).
For fault value = 3:
- check the range limit setting and increase it if necessary (p4676).
233161
<location>Encoder 3: Analog sensor channel B failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE)
Vector: OFF1 (IASC/DCBRK, NONE)
Hla: OFF1 (NONE)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1333
SINAMICS alarms
Cause:
The input voltage of the analog sensor is outside the permissible limits.
Fault value (r0949, interpret decimal):
1: Input voltage outside detectable measuring range.
2: Input voltage outside the selected measuring range (p4675).
3: The absolute value of the input voltage has exceeded the range limit (p4676).
Remedy:
For fault value = 1:
- check the output voltage of the analog sensor.
For fault value = 2:
- check the voltage setting for each encoder period (p4675).
For fault value = 3:
- check the range limit setting and increase it if necessary (p4676).
233163
<location>Encoder 3: Analog sensor position value exceeds limit value
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE)
Vector: OFF1 (IASC/DCBRK, NONE)
Hla: OFF1 (NONE)
Acknowledge:
PULSE INHIBIT
Cause:
The position value has exceeded the permissible range of -0.5 ... +0.5.
Fault value (r0949, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy:
For fault value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For fault value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
233400
<location>Encoder 3: Zero mark distance error (alarm threshold exceeded)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The measured zero mark distance does not correspond to the parameterized zero mark distance.
For distance-coded encoders, the zero mark distance is determined from zero marks detected pairs. This means that if a zero
mark is missing, depending on the pair generation, this cannot result in a fault and also has no effect in the system.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder).
Alarm value (r2124, interpret decimal):
Last measured zero mark distance in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
233401
<location>Encoder 3: Zero mark failed (alarm threshold exceeded)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Alarms
1334
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
The 1.5x parameterized zero mark distance was exceeded without a zero mark being detected.
The zero mark distance for the zero mark monitoring is set in p0425 (rotary encoder) or p0424 (linear encoder).
Alarm value (r2124, interpret decimal):
Number of increments after POWER ON or since the last zero mark that was detected (4 increments = 1 encoder pulse).
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the clearance between zero marks (p0425).
- replace the encoder or encoder cable.
233405
<location>Encoder 3: Temperature in the encoder evaluation exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
temperature: [0.1 degrees C] %1, temperature sensor number: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
An inadmissibly high temperature was detected in the encoder electronics or the encoder evaluation.
Fault value (r0949, interpret hexadecimal):
yyxxxx hex: yy = temperature sensor number, xxxx = measured module temperature in 0.1 °C.
Remedy:
Reduce the ambient temperature for the DRIVE-CLiQ connection of the motor.
233407
<location>Encoder 3: Function limit reached
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The encoder has reached one of its function limits. A service is recommended.
Alarm value (r2124, interpret decimal):
1: Incremental signals
3: Absolute track
4: Code connection
Remedy:
Perform service. Replace the encoder if necessary.
Note:
The actual functional reserve of an encoder can be displayed via r4651.
See also: p4650 (Encoder functional reserve component number), r4651 (Encoder functional reserve)
233410
<location>Encoder 3: Communication error (encoder and Sensor Module)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1335
SINAMICS alarms
Cause:
Serial communication protocol transfer error between the encoder and evaluation module.
Alarm value (r2124, interpret binary):
Bit 0: Alarm bit in the position protocol.
Bit 1: Incorrect quiescent level on the data line.
Bit 2: Encoder does not respond (does not supply a start bit within 50 ms).
Bit 3: CRC error: The checksum in the protocol from the encoder does not match the data.
Bit 4: Encoder acknowledgment error: The encoder incorrectly understood the task (request) or cannot execute it.
Bit 5: Internal error in the serial driver: An illegal mode command was requested.
Bit 6: Timeout when cyclically reading.
Bit 8: Protocol is too long (e.g. > 64 bits).
Bit 9: Receive buffer overflow.
Bit 10: Frame error when reading twice.
Bit 11: Parity error.
Bit 12: Data line signal level error during the monoflop time.
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace encoder.
233411
<location>Encoder 3: Encoder signals an internal alarm (detailed information)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin, additional information: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
The absolute encoder fault word includes alarm bits that have been set.
Alarm value (r2124, interpret binary):
yyyyxxxx hex: yyyy = supplementary information, xxxx = fault cause
yyyy = 0:
Bit 0: Frequency exceeded (speed too high).
Bit 1: Temperature exceeded.
Bit 2: Control reserve, lighting system exceeded.
Bit 3: Battery discharged.
Bit 4: Reference point passed.
yyyy = 1:
Bit 0: Signal amplitude outside the control range.
Bit 1: Error multiturn interface
Bit 2: Internal data error (singleturn/multiturn not with single steps).
Bit 3: Error EEPROM interface.
Bit 4: SAR converter error.
Bit 5: Fault for the register data transfer.
Bit 6: Internal error identified at the error pin (nErr).
Bit 7: Temperature threshold exceeded or fallen below.
Remedy:
Replace encoder.
233412
<location>Encoder 3: Encoder signals an internal alarm
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
1336
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The encoder signals an internal alarm via serial protocol.
Alarm value (r2124, interpret binary):
Bit 0: Fault bit in the position protocol.
Bit 1: Alarm bit in the position protocol.
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace encoder.
233414
<location>Encoder 3: Signal level track C or D out of tolerance
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
C track: %1, D track: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
The signal level (C^2 + D^2) of track C or D of the encoder or from the Hall signals, is not within the tolerance bandwidth.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Signal level, track D (16 bits with sign).
xxxx = Signal level, track C (16 bits with sign).
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response thresholds are < 230 mV (observe the frequency response of the encoder) and > 750 mV.
A signal level of 500 mV peak value corresponds to the numerical value 5333 hex = 21299 dec.
Note:
If the amplitude is not within the tolerance bandwidth, then it cannot be used to initialize the start position.
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- check the Hall sensor box.
233415
<location>Encoder 3: Signal level track A or B outside tolerance (alarm)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Amplitude: %1, Angle: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
The signal level (root from A^2 + B^2) of the encoder is outside the permissible tolerance.
Alarm value (r2124, interpret hexadecimal):
yyyyxxxx hex:
yyyy = Angle
xxxx = amplitude, i.e. root of A^2 + B^2 (16 bits without sign)
The nominal signal level of the encoder must lie in the range 375 mV to 600 mV (500 mV -25/+20 %).
The response threshold is < 230 mV (observe the frequency response of the encoder).
A signal level of 500 mV peak value corresponds to the numerical value 299A hex = 10650 dec.
The angle 0 ... FFFF hex corresponds to 0 ... 360 degrees of the fine position. Zero degrees is present at the negative zero
crossover of track B.
Note for Sensor Modules for resolvers (e.g. SMC10):
The nominal signal level is at 2900 mV (2.0 Vrms). The response threshold is < 1414 mV (1.0 Vrms).
A signal level of 2900 mV peak value corresponds to the numerical value 3333 hex = 13107 dec.
Note:
The analog values of the amplitude error are not measured at the same time with the hardware fault output by the Sensor
Module.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1337
SINAMICS alarms
Remedy:
- check the speed range, frequency characteristic (amplitude characteristic) of the measuring equipment is not sufficient for
the speed range.
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check the Sensor Module (e.g. contacts).
- if the coding disk is soiled or the lighting aged, replace the encoder.
233418
<location>Encoder 3: Speed change not plausible (alarm)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
For an HTL/TTL encoder, the speed change has exceeded the value in p0492 over several sampling cycles.
The change to the averaged speed actual value - if applicable - is monitored in the current controller sampling time.
Alarm value (r2124, interpret decimal):
Only for internal Siemens troubleshooting.
See also: p0492
Remedy:
- check the tachometer feeder cable for interruptions.
- check the grounding of the tachometer shielding.
- if required, increase the setting of p0492.
233419
<location>Encoder 3: Track A or B outside tolerance
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The amplitude/phase/offset correction for track A or B is at the limit.
Amplitude error correction: Amplitude B / Amplitude A = 0.78 ... 1.27
Phase: <84 degrees or >96 degrees
SMC20: Offset correction: +/-140 mV
SMC10: Offset correction: +/-650 mV
Alarm value (r2124, interpret hexadecimal):
xxxx1: Minimum of the offset correction, track B
xxxx2: Maximum of the offset correction, track B
xxx1x: Minimum of the offset correction, track A
xxx2x: Maximum of the offset correction, track A
xx1xx: Minimum of the amplitude correction, track B/A
xx2xx: Maximum of the amplitude correction, track B/A
x1xxx: Minimum of the phase error correction
x2xxx: Maximum of the phase error correction
1xxxx: Minimum of the cubic correction
2xxxx: Maximum of the cubic correction
Remedy:
- check mechanical mounting tolerances for encoders without their own bearings (e.g. toothed-wheel encoders).
- check the plug connections (also the transition resistance).
- check the encoder signals.
- replace the encoder or encoder cable.
233421
<location>Encoder 3: Determined commutation position incorrect (alarm)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Alarms
1338
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
A commutation position actual value sensing error was detected.
Alarm value (r2124, interpret decimal):
3: The absolute position of the serial protocol and track A/B differ by half an encoder pulse. The absolute position must have
its zero position in the quadrants in which both tracks are negative. In the case of a fault, the position can be incorrect by
one encoder pulse.
Remedy:
For alarm value = 3:
- For a standard encoder with cable, contact the manufacturer where relevant.
- correct the assignment of the tracks to the position value that is serially transferred. To do this, the two tracks must be
connected, inverted, at the Sensor Module (interchange A with A* and B with B*) or, for a programmable encoder, check
the zero offset of the position.
233422
<location>Encoder 3: Pulses per revolution square-wave encoder outside tolerance
bandwidth
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The measured zero mark distance does not correspond to the parameterized zero mark distance.
This alarm is triggered with active square-wave encoder PPR correction and re-parameterized fault 31131 if the accumulator
contains larger values than p4683 or p4684.
The zero mark distance for zero mark monitoring is set in p0425 (rotary encoder).
Alarm value (r2124, interpret decimal):
accumulated differential pulses in encoder pulses.
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- check the encoder type (encoder with equidistant zero marks).
- adapt the parameter for the distance between zero marks (p0424, p0425).
- replace the encoder or encoder cable.
233429
<location>Encoder 3: Position difference hall sensor/track C/D and A/B too large
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The error for track C/D is greater than +/-15 ° mechanical or +/-60 ° electrical or the error for the Hall signals is greater than
+/-60 ° electrical.
One period of track C/D corresponds to 360 ° mechanical.
One period of the Hall signal corresponds to 360 ° electrical.
The monitoring responds if, for example, Hall sensors are connected as equivalent for the C/D tracks with the incorrect
rotational sense or supply values that are not accurate enough.
Alarm value (r2124, interpret decimal):
For track C/D, the following applies:
Measured deviation as mechanical angle (16 bits with sign, 182 dec corresponds to 1 °).
For Hall signals, the following applies:
Measured deviation as electrical angle (16 bits with sign, 182 dec corresponds to 1 °).
Remedy:
- track C or D not connected.
- correct the direction of rotation of the Hall sensor possibly connected as equivalent for track C/D.
- check that the encoder cables are routed in compliance with EMC.
- check the adjustment of the Hall sensor.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1339
SINAMICS alarms
233431
<location>Encoder 3: Position deviation incremental/absolute too high (alarm)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
When the zero pulse is passed, a deviation in the incremental position was detected.
For equidistant zero marks, the following applies:
- the first zero mark passed supplies the reference point for all subsequent checks. The other zero marks must have n times
the distance referred to the first zero mark.
For distance-coded zero marks, the following applies:
- the first zero mark pair supplies the reference point for all subsequent checks. The other zero mark pairs must have the
expected distance to the first zero mark pair.
Alarm value (r2124, interpret decimal):
Deviation in quadrants (1 pulse = 4 quadrants).
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- Clean coding disk or remove strong magnetic fields.
233432
<location>Encoder 3: Rotor position adaptation corrects deviation
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
On track A/B, pulses have been lost or too many have been counted. These pulses are presently being corrected.
Alarm value (r2124, interpret decimal):
Last measured deviation of zero mark in increments (4 increments = 1 encoder pulse).
The sign designates the direction of motion when detecting the zero mark distance.
Remedy:
- check that the encoder cables are routed in compliance with EMC.
- check the plug connections.
- replace the encoder or encoder cable.
- check encoder limit frequency.
- adapt the parameter for the distance between zero marks (p0424, p0425).
233442
<location>Encoder 3: Battery voltage alarm threshold reached
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
When switched-off, the encoder uses a battery to back up the multiturn information. The multiturn information can no
longer be buffered if the battery voltage drops even further.
Remedy:
Replace battery.
233443
<location>Encoder 3: Signal level track C/D outside tolerance (alarm)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Alarms
1340
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The unipolar level (CP/CN or DP/DN) for encoder 3 is outside the permissible tolerance.
Alarm value (r2124, interpret binary):
Bit 0 = 1: Either CP or CN outside the tolerance.
Bit 16 = 1: Either DP or DN outside the tolerance.
The unipolar nominal signal level of the encoder must lie in the range 2500 mV +/- 500 mV.
The response thresholds are < 1700 mV and > 3300 mV.
Note:
The signal level is not evaluated unless the following conditions are satisfied:
- Sensor Module properties available (r0459.31 = 1).
- monitoring active (p0437.31 = 1).
Remedy:
- check that the encoder cables and shielding are routed in compliance with EMC.
- check the plug connections and contacts of the encoder cable.
- are the C/D tracks connected correctly (have the signal cables CP and CN or DP and DN been interchanged)?
- replace the encoder cable.
233460
<location>Encoder 3: Analog sensor channel A failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The input voltage of the analog sensor is outside the permissible limits.
Alarm value (r2124, interpret decimal):
1: Input voltage outside detectable measuring range.
2: Input voltage outside measuring range set in p4673.
3: The absolute value of the input voltage has exceeded the range limit (p4676).
Remedy:
For alarm value = 1:
- check the output voltage of the analog sensor.
For alarm value = 2:
- check the voltage setting for each encoder period (p4673).
For alarm value = 3:
- check the range limit setting and increase it if necessary (p4676).
233461
<location>Encoder 3: Analog sensor channel B failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The input voltage of the analog sensor is outside the permissible limits.
Alarm value (r2124, interpret decimal):
1: Input voltage outside detectable measuring range.
2: Input voltage outside the selected measuring range (p4675).
3: The absolute value of the input voltage has exceeded the range limit (p4676).
Remedy:
For alarm value = 1:
- check the output voltage of the analog sensor.
For alarm value = 2:
- check the voltage setting for each encoder period (p4675).
For alarm value = 3:
- check the range limit setting and increase it if necessary (p4676).
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1341
SINAMICS alarms
233462
<location>Encoder 3: Analog sensor no channel active
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Channel A and B are not activated for the analog sensor.
Remedy:
- activate channel A and/or channel B (p4670).
- check the encoder configuration (p0404.17).
See also: p4670 (Analog sensor configuration)
233463
<location>Encoder 3: Analog sensor position value exceeds limit value
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The position value has exceeded the permissible range of -0.5 ... +0.5.
Alarm value (r2124, interpret decimal):
1: Position value from the LVDT sensor.
2: Position value from the encoder characteristic.
Remedy:
For alarm value = 1:
- check the LVDT ratio (p4678).
- check the reference signal connection at track B.
For alarm value = 2:
- check the coefficients of the characteristic (p4663 ... p4666).
233470
<location>Encoder 3: Encoder signals an internal error (X521.7)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
For the Sensor Module Cabinet 30 (SMC30), a dirty encoder is signaled via a 0 signal at terminal X521.7.
Remedy:
- check the plug connections.
- replace the encoder or encoder cable.
233500
<location>Encoder 3: Position tracking traversing range exceeded
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For a configured linear axis without modulo correction, the drive/encoder has exceeded the maximum possible traversing
range. The value should be read in p0412 and interpreted as the number of motor revolutions.
For p0411.0 = 1, the maximum traversing range for the configured linear axis is defined to be 64x (+/- 32x) of p0421.
For p0411.3 = 1, the maximum traversing range for the configured linear axis is preset (default value) to the highest possible
value and is +/-p0412/2 (rounded off to complete revolutions). The highest possible value depends on the pulse number
(p0408) and the fine resolution (p0419).
Remedy:
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.
Alarms
1342
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
233501
<location>Encoder 3: Position tracking encoder position outside tolerance window
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
When switched off, the drive/encoder was moved through a distance greater than was parameterized in the tolerance
window. It is possible that there is no longer any reference between the mechanical system and encoder.
Fault value (r0949, interpret decimal):
Deviation (difference) to the last encoder position in increments of the absolute value.
The sign designates the traversing direction.
Note:
The deviation (difference) found is also displayed in r0477.
See also: p0413, r0477
Remedy:
Reset the position tracking as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and, if necessary, the absolute encoder adjusted (p2507).
See also: p0010, p2507
233502
<location>Encoder 3: Encoder with measuring gear without valid signals
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The encoder with measuring gear no longer provides any valid signals.
Remedy:
It must be ensured that all of the encoders, with mounted measuring gear, provide valid actual values in operation.
233503
<location>Encoder 3: Position tracking cannot be reset
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The position tracking for the measuring gear cannot be reset.
Remedy:
The fault should be resolved as follows:
- select encoder commissioning (p0010 = 4).
- reset the position tracking as follows (p0411.2 = 1).
- deselect encoder commissioning (p0010 = 0).
The fault should then be acknowledged and the absolute encoder adjusted.
233700
<location>Encoder 3: Effectivity test does not supply the expected value
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Cause:
The DRIVE-CLiQ encoder fault word supplies fault bits that have been set.
Alarm value (r2124, interpret binary):
Bit x = 1: Effectivity test x unsuccessful.
Remedy:
Replace encoder.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1343
SINAMICS alarms
233800
<location>Encoder 3: Group signal
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
NONE
Cause:
The motor encoder has detected at least one fault.
Remedy:
Evaluate the other messages that are presently available.
233801
<location>Encoder 3 DRIVE-CLiQ: Sign-of-life missing
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved.
Fault cause:
10 (= 0A hex):
The sign-of-life bit in the receive telegram is not set.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the electrical cabinet design and cable routing for EMC compliance
- replace the component involved.
233802
<location>Encoder 3: Time slice overflow
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A time slice overflow has occurred in encoder 3.
Fault value (r0949, interpret hexadecimal):
yx hex: y = function involved (Siemens-internal fault diagnostics), x = time slice involved
x = 9:
Time slice overflow of the fast (current controller clock cycle) time slice.
x = A:
Time slice overflow of the average time slice.
x = C:
Time slice overflow of the slow time slice.
yx = 3E7:
Timeout when waiting for SYNO (e.g. unexpected return to non-cyclic operation).
Remedy:
Increase the current controller sampling time
Note:
For a current controller sampling time = 31.25 µs, use an SMx20 with Article No. 6SL3055-0AA00-5xA3.
Alarms
1344
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
233804
<location>Encoder 3: Sensor Module checksum error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
POWER ON (IMMEDIATELY)
Cause:
A checksum error has occurred when reading-out the program memory on the Sensor Module.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
yyyy: Memory area involved.
xxxx: Difference between the checksum at POWER ON and the actual checksum.
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- upgrade firmware to later version (>= V2.6 HF3, >= V4.3 SP2, >= V4.4).
- check whether the permissible ambient temperature for the component is maintained.
- replace the Sensor Module.
233805
<location>Encoder 3: EEPROM checksum error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
Data in the EEPROM corrupted .
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.
Remedy:
Replace the module.
233806
<location>Encoder 3: Initialization error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1345
SINAMICS alarms
Cause:
The encoder was not successfully initialized.
Fault value (r0949, interpret binary):
Bit 0, 1: Encoder initialization with the motor rotating has failed (deviation involving coarse and fine position in encoder
pulses/4).
Bit 2: Mid-voltage matching for track A unsuccessful.
Bit 3: Mid-voltage matching for track B unsuccessful.
Bit 4: Mid-voltage matching for acceleration input unsuccessful.
Bit 5: Mid-voltage matching for track safety A unsuccessful.
Bit 6: Mid-voltage matching for track safety B unsuccessful.
Bit 7: Mid-voltage matching for track C unsuccessful.
Bit 8: Mid-voltage matching for track D unsuccessful.
Bit 9: Mid-voltage matching for track R unsuccessful.
Bit 10: The difference in mid-voltages between A and B is too great (> 0.5 V)
Bit 11: The difference in mid-voltages between C and D is too great (> 0.5 V)
Bit 12: The difference in mid-voltages between safety A and safety B is too great (> 0.5 V)
Bit 13: The difference in mid-voltages between A and safety B is too great (> 0.5 V)
Bit 14: The difference in mid-voltages between B and safety A is too great (> 0.5 V)
Bit 15: The standard deviation of the calculated mid-voltages is too great (> 0.3 V)
Bit 16: Internal fault - fault when reading a register (CAFE)
Bit 17: Internal fault - fault when writing a register (CAFE)
Bit 18: Internal fault: No mid-voltage matching available
Bit 19: Internal error - ADC access error.
Bit 20: Internal error - no zero crossover found.
Bit 28: Error while initializing the EnDat 2.2 measuring unit.
Bit 29: Error when reading out the data from the EnDat 2.2 measuring unit.
Bit 30: EEPROM checksum of the EnDat 2.2 measuring unit incorrect.
Bit 31: Data of the EnDat 2.2 measuring unit inconsistent.
Note:
Bit 0, 1: Up to 6SL3055-0AA00-5*A0
Bits 2 ... 20: 6SL3055-0AA00-5*A1 and higher
Remedy:
Acknowledge fault.
If the fault cannot be acknowledged:
Bits 2 ... 9: Check encoder power supply.
Bits 2 ... 14: Check the corresponding cable.
Bit 15 with no other bits: Check track R, check settings in p0404.
Bit 28: Check the cable between the EnDat 2.2 converter and the measuring unit.
Bit 29 ... 31: Replace the defective measuring unit.
233811
<location>Encoder 3: Encoder serial number changed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The encoder serial number has changed. The change is only checked for encoders with serial number (e.g. EnDat encoders).
- the encoder was replaced.
Note:
With closed-loop position control, the serial number is accepted when starting the adjustment (p2507 = 2).
When the encoder is adjusted (p2507 = 3), the serial number is checked for changes and if required, the adjustment is reset
(p2507 = 1).
Proceed as follows to hide serial number monitoring:
- set the following serial numbers for the corresponding Encoder Data Set: p0441= FF, p0442 = 0, p0443 = 0, p0444 = 0,
p0445 = 0.
Alarms
1346
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Mechanically adjust the encoder. Accept the new serial number with p0440 = 1.
233812
<location>Encoder 3: Requested cycle or RX-/TX timing not supported
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Cause:
A cycle requested from the Control Unit or RX/TX timing is not supported.
Fault value (r0949, interpret decimal):
0: Application cycle is not supported.
1: DRIVE-CLiQ cycle is not supported.
2: Distance between RX and TX instants in time too low.
3: TX instant in time too early.
Remedy:
Carry out a POWER ON (switch-off/switch-on) for all components.
233813
<location>Encoder 3: Hardware logic unit failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
PULSE INHIBIT
Cause:
The logic unit of the DRIVE-CLiQ encoder has failed.
Fault value (r0949, interpret binary):
Bit 0: ALU watchdog has responded.
Bit 1: ALU has detected a sign-of-life error.
Remedy:
When the error reoccurs, replace the encoder.
233820
<location>Encoder 3 DRIVE-CLiQ: Telegram error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1347
SINAMICS alarms
Cause:
A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the component in the telegram and in the receive list do not match.
7 (= 07 hex):
A SYNC telegram is expected - but the received telegram is not a SYNC telegram.
8 (= 08 hex):
No SYNC telegram is expected - but the received telegram is one.
9 (= 09 hex):
The error bit in the receive telegram is set.
16 (= 10 hex):
The receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
233835
<location>Encoder 3 DRIVE-CLiQ: Cyclic data transfer error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder concerned. The nodes do not send
and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON.
- replace the component involved.
Alarms
1348
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
233836
<location>Encoder 3 DRIVE-CLiQ: Send error for DRIVE-CLiQ data
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved. Data were not able to be
sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
233837
<location>Encoder 3 DRIVE-CLiQ: Component fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
233845
<location>Encoder 3 DRIVE-CLiQ: Cyclic data transfer error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1349
SINAMICS alarms
Cause:
A DRIVE-CLiQ communication error has occurred from the Control Unit to the encoder involved.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON (switch-off/switch-on).
233850
<location>Encoder 3: Encoder evaluation internal software error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
POWER ON
Cause:
An internal software error has occurred in the Sensor Module of encoder 3.
Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
10000: OEM memory of the EnDat encoder contains data that cannot be interpreted.
11000 ... 11499: Descriptive data from EEPROM incorrect.
11500 ... 11899: Calibration data from EEPROM incorrect.
11900 ... 11999: Configuration data from EEPROM incorrect.
12000 ... 12008: communication with analog/digital converter faulted.
16000: DRIVE-CLiQ encoder initialization application error.
16001: DRIVE-CLiQ encoder initialization ALU error.
16002: DRIVE-CLiQ encoder HISI / SISI initialization error.
16003: DRIVE-CLiQ encoder safety initialization error.
16004: DRIVE-CLiQ encoder internal system error.
Remedy:
- replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
233851
<location>Encoder 3 DRIVE-CLiQ (CU): Sign-of-life missing
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault cause:
10 (= 0A hex):
The sign-of-life bit in the receive telegram is not set.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- Upgrade the firmware of the component involved.
- carry out a POWER ON (switch-off/switch-on) for the component involved.
Alarms
1350
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
233860
<location>Encoder 3 DRIVE-CLiQ (CU): Telegram error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage
has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
233875
<location>Encoder 3: power supply voltage failed
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1351
SINAMICS alarms
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage
has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
233885
<location>Encoder 3 DRIVE-CLiQ (CU): Cyclic data transfer error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
The nodes do not send and receive in synchronism.
Fault cause:
26 (= 1A hex):
Sign-of-life bit in the receive telegram not set and the receive telegram is too early.
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
98 (= 62 hex):
Error at the transition to cyclic operation.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the power supply voltage of the component involved.
- carry out a POWER ON (switch-off/switch-on).
- replace the component involved.
233886
<location>Encoder 3 DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
1352
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
233887
<location>Encoder 3 DRIVE-CLiQ (CU): Component fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
Fault detected on the DRIVE-CLiQ component involved (Sensor Module for encoder 3). Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
96 (= 60 hex):
Response received too late during runtime measurement.
97 (= 61 hex):
Time taken to exchange characteristic data too long.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
233895
<location>Encoder 3 DRIVE-CLiQ (CU): Alternating cyclic data transfer error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3)
Hla: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1353
SINAMICS alarms
Cause:
A DRIVE-CLiQ communication error has occurred from the Sensor Module (encoder 3) involved to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
233896
<location>Encoder 3 DRIVE-CLiQ (CU): Inconsistent component properties
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Component number: %1
Reaction:
Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
The properties of the DRIVE-CLiQ component (Sensor Module for encoder 3), specified by the fault value, have changed in
an incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or
DRIVE-CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.
Remedy:
- carry out a POWER ON.
- when a component is replaced, the same component type and if possible the same firmware version should be used.
- when a cable is replaced, only cables whose length is the same as or as close as possible to the length of the original cables
should be used (ensure compliance with the maximum cable length).
233899
<location>Encoder 3: Unknown fault
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
New message: %1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A fault occurred on the Sensor Module for encoder 3 that cannot be interpreted by the Control Unit firmware.
This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more recent description of the Control Unit.
Remedy:
- replace the firmware on the Sensor Module by an older firmware version (r0148).
- upgrade the firmware on the Control Unit (r0018).
233902
<location>Encoder 3: SPI-BUS error occurred
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Error when operating the internal SPI bus.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Alarms
1354
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
233903
<location>Encoder 3: I2C-BUS error occurred
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
Error when operating the internal I2C bus.
Alarm value (r2124, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
- replace the Sensor Module.
- if required, upgrade the firmware in the Sensor Module.
- contact Technical Support.
233905
<location>Encoder 3: Encoder parameterization error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Parameter: %1, supplementary information: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1355
SINAMICS alarms
Cause:
An error was identified in the encoder parameterization.
It is possible that the parameterized encoder type does not match the connected encoder.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
Fault value (r0949, interpret decimal):
yyyyxxxx dec: yyyy = supplementary information, xxxx = parameter
xxxx = 421:
For an EnDat/SSI encoder, the absolute position in the protocol must be less than or equal to 30 bits.
yyyy = 0:
No additional information available.
yyyy = 1:
The component does not support HTL level (p0405.1 = 0) combined with track monitoring A/B <> -A/B (p0405.2 = 1).
yyyy = 2:
A code number for an identified encoder has been entered into p0400, however, no identification was carried out. Please
start a new encoder identification.
yyyy = 3:
A code number for an identified encoder has been entered into p0400, however, no identification was carried out. Please
select a listed encoder in p0400 with a code number < 10000.
yyyy = 4:
This component does not support SSI encoders (p0404.9 = 1) without track A/B.
yyyy = 5:
For SQW encoder, value in p4686 greater than in p0425.
yyyy = 6:
DRIVE-CLiQ encoder cannot be used with this firmware version.
yyyy = 7:
For an SQW encoder, the XIST1 correction (p0437.2) is only permitted for equidistant zero marks.
yyyy = 8:
The motor pole pair width is not supported by the linear scale being used.
yyyy = 9:
The length of the position in the EnDat protocol may be a maximum of 32 bits.
yyyy = 10:
The connected encoder is not supported.
yyyy = 11:
The hardware does not support track monitoring.
Remedy:
- check whether the connected encoder type matches the encoder that has been parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
- re parameter number = 314:
- check the pole pair number and measuring gear ratio. The quotient of the "pole pair number" divided by the "measuring
gear ratio" must be less than or equal to 1000 ((r0313 * p0433) / p0432 <= 1000).
233912
<location>Encoder 3: Device combination is not permissible
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE)
Vector: OFF1 (IASC/DCBRK, NONE)
Hla: OFF1 (NONE)
Acknowledge:
PULSE INHIBIT
Alarms
1356
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The selected device combination is not supported.
Fault value (r0949, interpret decimal):
1003:
The connected measuring unit cannot be operated with the EnDat 2.2 converter. For instance, the measuring unit has a
pulse number/resolution of 2^n.
1005:
The type of measuring unit (incremental) is not supported by the EnDat 2.2 converter.
1006:
The maximum duration of the EnDat transfer (31.25 µs) was exceeded.
2001:
The set combination of current controller cycle, DP cycle and Safety cycle is not supported by the EnDat 2.2 converter.
2002:
The resolution of the linear measuring unit does not match the pole pair width of the linear motor
Pole pair width, minimum = p0422 * 2^20
Remedy:
For fault value = 1003, 1005, 1006:
- Use a measuring unit that is permissible.
For fault value = 2001:
- set a permissible cycle combination (if required, use standard settings).
For fault value = 2002:
- Use a measuring unit with a lower resolution (p0422).
233915
<location>Encoder 3: Encoder configuration error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The configuration for encoder 3 is incorrect.
Alarm value (r2124, interpret decimal):
1:
Re-parameterization between fault/alarm is not permissible.
2:
The cyclic DQ receive telegram is too long and is limited.
3:
The cyclic DQ send telegram is too long and is limited.
419:
When the fine resolution Gx_XIST2 is configured, the encoder identifies a maximum possible absolute position actual value
(r0483) that can no longer be represented within 32 bits.
Remedy:
For alarm value = 1:
No re-parameterization between fault/alarm.
For alarm value = 419:
Reduce the fine resolution (p0419) or deactivate the monitoring (p0437.25), if the complete multiturn range is not required.
233916
<location>Encoder 3: Encoder parameterization error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Parameter: %1, supplementary information: %2
Reaction:
Servo: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Vector: OFF1 (IASC/DCBRK, NONE, OFF2, OFF3, STOP2)
Hla: OFF1 (NONE, OFF2, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1357
SINAMICS alarms
Cause:
An encoder parameter was detected as being incorrect.
It is possible that the parameterized encoder type does not match the connected encoder.
The parameter involved can be determined as follows:
- determine the parameter number using the fault value (r0949).
- determine the parameter index (p0187).
Fault value (r0949, interpret decimal):
Parameter number.
Remedy:
- check whether the connected encoder type matches the encoder that has been parameterized.
- correct the parameter specified by the fault value (r0949) and p0187.
233920
<location>Encoder 3: Temperature sensor fault (motor)
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
Fault cause: %1, channel number: %2
Reaction:
NONE
Acknowledge:
NONE
Cause:
The motor detected a fault when evaluating the temperature sensor.
Fault cause:
1 (= 01 hex):
Wire breakage or sensor not connected.
KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm
2 (= 02 hex):
Measured resistance too low.
PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 603 Ohm
Additional values:
Only for internal Siemens troubleshooting.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = channel number, xx = error cause
Remedy:
- check that the encoder cable is the correct type and is correctly connected.
- check the temperature sensor selection in p0600 to p0603.
- replace the Sensor Module (hardware defect or incorrect calibration data).
233930
<location>Encoder 3: Data logger has saved data
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
For the activated function "Data logger" (p0437.0 = 1) a fault has occurred with the Sensor Module. This alarm indicates that
the diagnostics data corresponding to the fault was saved on the memory card.
The diagnostics data is saved in the following folder:
/USER/SINAMICS/DATA/SMTRC00.BIN
/USER/SINAMICS/DATA/SMTRC07.BIN
/USER/SINAMICS/DATA/SMTRCIDX.TXT
The following information is contained in the TXT file:
- Display of the last written BIN file.
- Number of write operations that are still possible (from 10000 downwards).
Note:
Only Siemens can evaluate the BIN files.
Alarms
1358
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Not necessary.
This alarm is automatically withdrawn.
The data logger is ready to record the next fault case.
233940
<location>Encoder 3: Spindle sensor S1 voltage incorrect
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The voltage of analog sensor S1 is outside the permissible range.
Alarm value (r2124, interpret decimal):
Signal level from sensor S1.
Note:
A signal level of 500 mV corresponds to the numerical value 500 dec.
Remedy:
- check the clamped tool.
- check the tolerance and if required, adapt (p5040).
- check the thresholds and if required, adapt (p5041).
- check analog sensor S1 and connections.
See also: p5040 (Spindle voltage threshold values tolerance), p5041 (Spindle voltage threshold values)
233950
<location>Encoder 3: Internal software error
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF1 (OFF2)
Acknowledge:
POWER ON
Cause:
An internal software error has occurred.
Fault value (r0949, interpret decimal):
Information about the fault source.
Only for internal Siemens troubleshooting.
Remedy:
- if necessary, upgrade the firmware in the Sensor Module to a later version.
- contact Technical Support.
233999
<location>Encoder 3: Unknown alarm
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
New message: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A alarm has occurred on the Sensor Module for encoder 3 that cannot be interpreted by the Control Unit firmware.
This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
Alarm value (r2124, interpret decimal):
Alarm number.
Note:
If required, the significance of this new alarm can be read about in a more recent description of the Control Unit.
Remedy:
- replace the firmware on the Sensor Module by an older firmware version (r0148).
- upgrade the firmware on the Control Unit (r0018).
234207
<location>VSM: Temperature fault threshold exceeded
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1359
SINAMICS alarms
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3668).
Note:
This fault can only be output if the temperature evaluation was activated (p3665 > 0).
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
See also: r3666, p3668
Remedy:
- check the fan.
- reduce the power.
234207
<location>VSM: Temperature fault threshold exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3668).
Note:
This fault can only be output if the temperature evaluation was activated (p3665 > 0).
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
See also: r3666, p3668
Remedy:
- check the fan.
- reduce the power.
- check the temperature sensor type setting (p3665).
- infeed: check the line filter type setting (p0220).
See also: p3665 (VSM temperature evaluation sensor type)
234211
<location>VSM: Temperature alarm threshold exceeded
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3667).
Alarm value (r2124, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
See also: r3666, p3667
Remedy:
- check the fan.
- reduce the power.
234211
<location>VSM: Temperature alarm threshold exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The temperature (r3666) measured using the Voltage Sensing Module (VSM) has exceeded the threshold value (p3667).
Alarm value (r2124, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
See also: r3666, p3667
Alarms
1360
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the fan.
- reduce the power.
- check the temperature sensor type setting (p3665).
- infeed: check the line filter type setting (p0220).
See also: p3665 (VSM temperature evaluation sensor type)
234800
<location>VSM: Group signal
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
NONE
Cause:
The Voltage Sensing Module (VSM) has detected at least one fault.
Remedy:
Evaluates other actual messages.
234801
<location>VSM DRIVE-CLiQ: Sign-of-life missing
Drive object:
VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM).
Fault cause:
10 (= 0A hex):
The sign-of-life bit in the receive telegram is not set.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the DRIVE-CLiQ connection.
- replace the component involved.
234801
<location>VSM DRIVE-CLiQ: Sign-of-life missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
Component number: %1, fault cause: %2
Reaction:
OFF2 (NONE, OFF1)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM).
Fault cause:
10 (= 0A hex):
The sign-of-life bit in the receive telegram is not set.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the DRIVE-CLiQ connection.
- replace the Voltage Sensing Module (VSM).
234802
<location>VSM: Time slice overflow
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1361
SINAMICS alarms
Acknowledge:
IMMEDIATELY
Cause:
A time slice overflow has occurred on the Voltage Sensing Module.
Remedy:
Replace the Voltage Sensing Module.
234803
<location>VSM: Memory test
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
An error has occurred during the memory test on the Voltage Sensing Module.
Remedy:
- check whether the permissible ambient temperature for the Voltage Sensing Module is being maintained.
- replace the Voltage Sensing Module.
234804
<location>VSM: CRC
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
A checksum error has occurred when reading-out the program memory on the Voltage Sensing Module (VSM).
Remedy:
- check whether the permissible ambient temperature for the component is maintained.
- replace the Voltage Sensing Module.
234805
<location>VSM: EEPROM checksum error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
Internal parameter data is corrupted.
Fault value (r0949, interpret hexadecimal):
01: EEPROM access error.
02: Too many blocks in the EEPROM.
Remedy:
- check whether the permissible ambient temperature for the component is maintained.
- replace the Voltage Sensing Module (VSM).
234806
<location>VSM: Initialization
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY
Cause:
For the Voltage Sensing Module (VSM), a fault has occurred while initializing.
Remedy:
Replace the Voltage Sensing Module.
234807
<location>VSM: Sequence control time monitoring
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Alarms
1362
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Reaction:
NONE
Acknowledge:
NONE
Cause:
Error, timeout in the sequence control on the Voltage Sensing Module (VSM).
Remedy:
Replace the Voltage Sensing Module.
234820
<location>VSM DRIVE-CLiQ: Telegram error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the component in the telegram and in the receive list do not match.
7 (= 07 hex):
A SYNC telegram is expected - but the received telegram is not a SYNC telegram.
8 (= 08 hex):
No SYNC telegram is expected - but the received telegram is one.
9 (= 09 hex):
The error bit in the receive telegram is set.
16 (= 10 hex):
The receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
234835
<location>VSM DRIVE-CLiQ: Cyclic data transfer error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1363
SINAMICS alarms
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module involved. The nodes
do not send and receive in synchronism.
Fault cause:
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON.
- replace the component involved.
234836
<location>VSM DRIVE-CLiQ: Send error for DRIVE-CLiQ data
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module. Data were not able
to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
234837
<location>VSM DRIVE-CLiQ: Component fault
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
Fault detected on the DRIVE-CLiQ component concerned. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Alarms
1364
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
234845
<location>VSM DRIVE-CLiQ: Cyclic data transfer error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Vector: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Control Unit to the Voltage Sensing Module (VSM).
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
234850
<location>VSM: Internal software error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF1 (NONE, OFF2)
Vector: OFF1 (NONE, OFF2, OFF3)
Acknowledge:
POWER ON
Cause:
An internal software error in the Voltage Sensing Module (VSM) has occurred.
Fault value (r0949, interpret decimal):
1: Background time slice is blocked.
2: Checksum over the code memory is not OK.
Remedy:
- replace the Voltage Sensing Module (VSM).
- if required, upgrade the firmware in the Voltage Sensing Module.
- contact Technical Support.
234851
<location>VSM DRIVE-CLiQ (CU): Sign-of-life missing
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1365
SINAMICS alarms
Cause:
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
The DRIVE-CLiQ component did not set the sign-of-life to the Control Unit.
Fault cause:
10 (= 0A hex):
The sign-of-life bit in the receive telegram is not set.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Upgrade the firmware of the component involved.
234860
<location>VSM DRIVE-CLiQ (CU): Telegram error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
1366
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
Fault cause:
1 (= 01 hex):
Checksum error (CRC error).
2 (= 02 hex):
Telegram is shorter than specified in the length byte or in the receive list.
3 (= 03 hex):
Telegram is longer than specified in the length byte or in the receive list.
4 (= 04 hex):
The length of the receive telegram does not match the receive list.
5 (= 05 hex):
The type of the receive telegram does not match the receive list.
6 (= 06 hex):
The address of the power unit in the telegram and in the receive list do not match.
9 (= 09 hex):
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage
has failed.
16 (= 10 hex):
The receive telegram is too early.
17 (= 11 hex):
CRC error and the receive telegram is too early.
18 (= 12 hex):
The telegram is shorter than that specified in the length byte or in the receive list and the receive telegram is too early.
19 (= 13 hex):
The telegram is longer than that specified in the length byte or in the receive list and the receive telegram is too early.
20 (= 14 hex):
The length of the receive telegram does not match the receive list and the receive telegram is too early.
21 (= 15 hex):
The type of the receive telegram does not match the receive list and the receive telegram is too early.
22 (= 16 hex):
The address of the power unit in the telegram and in the receive list does not match and the receive telegram is too early.
25 (= 19 hex):
The error bit in the receive telegram is set and the receive telegram is too early.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the electrical cabinet design and cable routing for EMC compliance
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
234875
<location>VSM: power supply voltage failed
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
OFF2
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1367
SINAMICS alarms
Cause:
The DRIVE-CLiQ communication from the DRIVE-CLiQ component involved to the Control Unit signals that the supply voltage
has failed.
Fault cause:
9 (= 09 hex):
The power supply voltage for the components has failed.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- carry out a POWER ON (switch-off/switch-on).
- check the power supply voltage wiring for the DRIVE-CLiQ component (interrupted cable, contacts, ...).
- check the dimensioning of the power supply for the DRIVE-CLiQ component.
234885
<location>VSM DRIVE-CLiQ (CU): Cyclic data transfer error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
The nodes do not send and receive in synchronism.
Fault cause:
26 (= 1A hex):
Sign-of-life bit in the receive telegram not set and the receive telegram is too early.
33 (= 21 hex):
The cyclic telegram has not been received.
34 (= 22 hex):
Timeout in the telegram receive list.
64 (= 40 hex):
Timeout in the telegram send list.
98 (= 62 hex):
Error at the transition to cyclic operation.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the power supply voltage of the component involved.
- carry out a POWER ON.
- replace the component involved.
234886
<location>VSM DRIVE-CLiQ (CU): Error when sending DRIVE-CLiQ data
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
1368
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
Data were not able to be sent.
Fault cause:
65 (= 41 hex):
Telegram type does not match send list.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
234887
<location>VSM DRIVE-CLiQ (CU): Component fault
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Cause:
Fault detected on the DRIVE-CLiQ component (Voltage Sensing Module) involved. Faulty hardware cannot be excluded.
Fault cause:
32 (= 20 hex):
Error in the telegram header.
35 (= 23 hex):
Receive error: The telegram buffer memory contains an error.
66 (= 42 hex):
Send error: The telegram buffer memory contains an error.
67 (= 43 hex):
Send error: The telegram buffer memory contains an error.
96 (= 60 hex):
Response received too late during runtime measurement.
97 (= 61 hex):
Time taken to exchange characteristic data too long.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
- check the DRIVE-CLiQ wiring (interrupted cable, contacts, ...).
- check the electrical cabinet design and cable routing for EMC compliance
- if required, use another DRIVE-CLiQ socket (p9904).
- replace the component involved.
234895
<location>VSM DRIVE-CLiQ (CU): Alternating cyclic data transfer error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1, fault cause: %2
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2)
Hla: NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1369
SINAMICS alarms
Cause:
A DRIVE-CLiQ communications error has occurred from the Voltage Sensing Module involved (VSM) to the Control Unit.
Fault cause:
11 (= 0B hex):
Synchronization error during alternating cyclic data transfer.
Note regarding the message value:
The individual information is coded as follows in the message value (r0949/r2124):
0000yyxx hex: yy = component number, xx = error cause
Remedy:
Carry out a POWER ON.
234896
<location>VSM DRIVE-CLiQ (CU): Inconsistent component properties
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, CU_LINK, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC,
TM120, TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
Component number: %1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Vector: OFF2 (IASC/DCBRK, NONE, OFF1, OFF3, STOP2)
Hla: OFF2 (NONE, OFF1, OFF3, STOP2)
Acknowledge:
IMMEDIATELY
Cause:
The properties of the DRIVE-CLiQ component (Voltage Sensing Module), specified by the fault value, have changed in an
incompatible fashion with respect to the properties when booted. One cause can be, e.g. that a DRIVE-CLiQ cable or DRIVE-
CLiQ component has been replaced.
Fault value (r0949, interpret decimal):
Component number.
Remedy:
- carry out a POWER ON.
- when a component is replaced, the same component type and if possible the same firmware version should be used.
- when a cable is replaced, only cables whose length is the same as or as close as possible to the length of the original cables
should be used (ensure compliance with the maximum cable length).
234899
<location>VSM: Unknown fault
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
New message: %1
Reaction:
Infeed: NONE (OFF1, OFF2)
Vector: NONE (OFF1, OFF2, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A fault occurred on the Voltage Sensing Module that cannot be interpreted by the Control Unit firmware.
This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
Fault value (r0949, interpret decimal):
Fault number.
Note:
If required, the significance of this new fault can be read about in a more recent description of the Control Unit.
Remedy:
- replace the firmware on the Voltage Sensing Module by an older firmware version (r0158).
- upgrade the firmware on the Control Unit (r0018).
234903
<location>VSM: I2C bus error occurred
Drive object:
VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
An error has occurred when accessing the module-internal I2C bus.
Remedy:
Replace the Terminal Module.
Alarms
1370
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
234903
<location>VSM: I2C bus error occurred
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
An error has occurred when accessing the module-internal I2C bus.
Remedy:
Replace the Voltage Sensing Module (VSM).
234904
<location>VSM: EEPROM
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
An error has occurred accessing the non-volatile memory on the Terminal Module.
Remedy:
Replace the Voltage Sensing Module (VSM).
234905
<location>VSM: Parameter access
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The Control Unit attempted to write an illegal parameter value to the Voltage Sensing Module (VSM).
Remedy:
- check whether the firmware version of the VSM (r0158) matches the firmware version of Control Unit (r0018).
- if required, replace the Voltage Sensing Module.
Note:
The firmware versions that match each other are in the readme.txt file on the memory card.
234920
<location>VSM: overtemperature or temperature sensor fault
Drive object:
VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
When evaluating the temperature sensor, a resistance value outside the permissible range was detected.
Fault value (r0949, interpret decimal):
1: overtemperature, wire breakage or sensor not connected.
KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm
2: Measured resistance too low.
PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 723 Ohm
Remedy:
- make sure that the sensor is connected correctly.
- replace the sensor.
- allow to cool down and then check the ambient conditions, load cycle and cooling (fan fuse).
234920
<location>VSM: overtemperature or temperature sensor fault
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840
Message value:
%1
Reaction:
NONE (OFF1, OFF2)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1371
SINAMICS alarms
Cause:
When evaluating the temperature sensor, a resistance value outside the permissible range was detected.
Fault value (r0949, interpret decimal):
1: overtemperature, wire breakage or sensor not connected.
KTY: R > 1630 Ohm, PT1000: R > 1720 Ohm
2: Measured resistance too low.
PTC: R < 20 Ohm, KTY: R < 50 Ohm, PT1000: R < 723 Ohm
Remedy:
- make sure that the sensor is connected correctly.
- replace the sensor.
- allow to cool down and then check the ambient conditions, load cycle and cooling (fan fuse).
- check the temperature sensor type setting (p3665).
- infeed: check the line filter type setting (p0220).
234950
<location>VSM: Internal software error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
OFF2
Acknowledge:
POWER ON
Cause:
An internal software error in the Voltage Sensing Module (VSM) has occurred.
Fault value (r0949, interpret decimal):
Information about the fault source.
Only for internal Siemens troubleshooting.
Remedy:
- if necessary, upgrade the firmware in the Voltage Sensing Module to a later version.
- contact Technical Support.
234999
<location>VSM: Unknown alarm
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, R_INF, S_INF, S_INF_840, VECTOR, VECTOR_AC
Message value:
New message: %1
Reaction:
NONE
Acknowledge:
NONE
Cause:
A fault occurred on the Voltage Sensing Module (VSM) an alarm has occurred that cannot be interpreted by the Control Unit
firmware.
This can occur if the firmware on this component is more recent than the firmware on the Control Unit.
Alarm value (r2124, interpret decimal):
Alarm number.
Note:
If required, the significance of this new alarm can be read about in a more recent description of the Control Unit.
Remedy:
- replace the firmware on the Voltage Sensing Module by an older firmware version (r0148).
- upgrade the firmware on the Control Unit (r0018).
235000
<location>TM54F: Sampling time invalid
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
POWER ON
Cause:
The set sampling time is invalid.
- not a multiple integer of the DP clock cycle.
Fault value (r0949, floating point):
Recommended valid sampling time.
Alarms
1372
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
Adapt the sampling time (e.g. set the recommended valid sampling time).
See also: p10000 (SI TM54F communication clock cycle)
235001
<location>TM54F: Parameter value invalid
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
The functionality of Safety Basic Functions via TM54F is used.
TM54F has been incorrectly parameterized (incorrect parameter assignment).
Only the following signals may be parameterized:
- STO active
- SS1 active
- internal event
- safe state
Possible causes:
- p10024 ... p10038 not set to 0 or 255.
- p10039, p10042 ... p10045 use signals from Safety Extended Functions.
Fault value (r0949, interpret binary):
Bits 0 ... 3 specifies for which drive group an illegal F-DI was parameterized:
Bit 0 = 1: drive group 1 error
Bit 1 = 1: drive group 2 error
Bit 2 = 1: drive group 3 error
Bit 3 = 1: drive group 4 error
Bits 4 ... 7 specifies for which F-DOs incorrect links were specified:
Bit 4 = 1: F-DO 0 error (p10042)
Bit 5 = 1: F-DO 1 error (p10043)
Bit 6 = 1: F-DO 2 error (p10044)
Bit 7 = 1: F-DO 3 error (p10045)
Remedy:
- check the setting of the failsafe digital inputs (F-DI) for the Safety Extended Functions - and set to a value of 0 or 255
(p10024 ... p10039).
- check the setting of the signal sources for the failsafe digital outputs (F-DO) and if necessary, correct (p10042 ... p10045).
Note:
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
235002
<location>TM54F: Commissioning not possible
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
The commissioning mode activation was rejected because at least one drive belonging to the TM54F is enabled for
operation.
Fault value (r0949, interpret decimal):
Drive object number of the first drive found without pulse suppression/power inhibit.
Remedy:
Withdraw the operating enable for the drive specified in the fault value.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1373
SINAMICS alarms
235003
<location>TM54F: Acknowledgment on the Control Unit is required
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
A fault on the Terminal Module 54F (TM54) was acknowledged using the safe acknowledgment (p10006).
An additional acknowledgment is also required at the Control Unit.
Remedy:
- acknowledge all faults on the Control Unit (BI: p2102).
or
- acknowledge all faults on the drive object TM54F (BI: p2103, p2104 or p2105).
Note:
A fault acknowledgment is triggered with a 0/1 signal.
235004
<location>TM54F: communication cycle invalid
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
- the communication cycle specified in p10000[x] does not correspond with the monitoring cycle of the drive object, which
was specified in p10010[x].
As long as this fault is present, Failsafe Values are activated in TM54F. All the drives are not enabled.
Fault value (r0949, interpret binary):
If a bit is set in the range bit 0 ... 5, then the following applies:
The communication cycle specified in p10000[x] does not correspond with the monitoring cycle of the drive object which
was specified in p10010[x]. (if only p10000[0] used, then this value must be identical with all monitoring cycles of the drive
objects used in p10010[0...5].)
Bit 0 = 1: p10000[0] does not correspond with the monitoring cycle of p10010[0]
Bit 1 = 1: p10000[1] does not correspond with the monitoring cycle of p10010[1]
Bit 5 = 1: p10000[5] does not correspond with the monitoring cycle of p10010[5]
If a bit is set in the range bit 16 ... 21, then the following applies:
Bit 16 = 1: p10000[0] has been selected too low.
Bit 17 = 1: p10000[1] has been selected too low.
Bit 21 = 1: p10000[5] has been selected too low.
When using an axis with Basic Safety Functions with TM54F, then the monitoring cycle should be greater than 500us + 8 *
current controller clock cycles of the drive.
Note:
This error is also signaled if a drive controlled with TM54F is parameterized so that the basic functions are controlled via
TM54F - and simultaneously the extended safety functions or ncSI have been parameterized.
The following applies for fault value = 0:
- since the firmware update of the TM54F it has not been switched off.
- the firmware of the connected TM54F is too old.
See also: p10010 (SI TM54F drive object assignment)
Alarms
1374
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Remedy:
For a fault value in the range from bit 0 ... 5:
- first check that all drives, which are entered in p10010, have either Extended Safety Functions or Basic Functions via TM54F.
- Execute the copy function for TM54F(p9700 = 87).
- adapt the checksums for TM54F(p9701 = 172).
- copy RAM to ROM.
- carry out a POWER ON.
For a fault value in the range from bit 16 ... 21:
Increase the current controller sampling time of the corresponding drive, in order to avoid faults in operation.
- Execute the copy function for TM54F(p9700 = 87).
- adapt the checksums for TM54F(p9701 = 172).
- copy RAM to ROM.
- carry out a POWER ON.
235005
<location>TM54F:parallel connection not supported
Drive object:
HLA, HLA_840, SERVO, SERVO_840, SERVO_AC, VECTOR
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
POWER ON
Cause:
The TM54F function with Basic Safety Functions is used. This function is not supported when power units are connected in
parallel.
All drives of the TM54F assume Failsafe Values, and are not enabled.
See also: p10010 (SI TM54F drive object assignment)
Remedy:
- deactivate parallel connection or TM54F with Basic Safety Functions.
- copy RAM to ROM.
- carry out a POWER ON (switch-off/switch-on).
235006
<location>TM54F: drive groups invalid
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
POWER ON
Cause:
The functionality of the basic functions via TM54F is used.
Drive groups have been incorrectly parameterized (incorrect parameter assignment).
Fault value (r0949, interpret binary):
The value specifies in which drive group Basic Safety drives are mixed with Extended Safety drives.
Bit 0 = 1: drive group 1 error
Bit 1 = 1: drive group 2 error
Bit 2 = 1: drive group 3 error
Bit 3 = 1: drive group 4 error
As long as this fault is present, Failsafe Values are activated in TM54F. All the drives are not enabled.
Note:
-this error is also signaled if a drive controlled with TM54F is parameterized so that the basic functions are controlled via
TM54F and simultaneously extended safety functions or ncSI have been parameterized.
Remedy:
Corresponding to the fault value, p10011 should be checked to ensure that no Basic Safety drives are mixed with Extended
Safety drives in a drive group.
235009
<location>TM54F: Safety commissioning drive incomplete
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, VECTOR, VECTOR_AC
Message value:
%1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1375
SINAMICS alarms
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
For Terminal Module 54F (TM54F), a drive object was assigned (p10010), for which no safety functions or faulty safety
functions are parameterized (p9501, p9601).
Fault value (r0949, interpret bitwise binary):
Bit 0 = 1: drive 1 error
Bit 1 = 1: drive 2 error
Bit 2 = 1: drive 3 error
Bit 3 = 1: drive 4 error
Bit 4 = 1: drive 5 error
Bit 5 = 1: drive 6 error
Remedy:
- carry out the safety commissioning of the drive involved and enable the safety functions for TM54F.
- commission the TM54F - and just set p9700 = 87d and p9701 = 172d.
235011
<location>TM54F: Drive object number assignment illegal
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A drive object number was assigned twice. Each drive object number can be assigned only once.
Remedy:
Correct the assignment of the drive object numbers.
See also: p10010 (SI TM54F drive object assignment)
235012
<location>TM54F: Test stop for failsafe digital inputs/outputs
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The forced checking procedure (test stop) for the failsafe digital inputs/outputs (F-DI/F-DO) is currently in progress.
Remedy:
The alarm is automatically withdraw after successfully ending or canceling (when a fault condition occurs) the test stop.
Note:
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
235013
<location>TM54F: Test stop error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
1376
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
A fault has been detected during the forced checking procedure (test stop) of the failsafe digital inputs/outputs on the
TM54F. Failsafe control signals (Failsafe Values) are transferred to the safety functions.
Fault value (r0949, interpret hexadecimal):
aaaabbcc hex:
aaaa: DO or F-DI (dependent on test step cc), where the expected state was not assumed (bit 0 = F-DI 0 or F-DO 0, bit 1 =
F-DI 1 or F-DO 1, etc.).
bb: Fault cause
bb = 01 hex: Internal fault.
bb = 02 hex: Fault when comparing the switching signals of the two channels (F-DI or DI).
bb = 03 hex: Internal fault.
bb = 04 hex: Fault when comparing the switching signals of the two channels (Diag-DO).
cc: State of the test stop in which the fault has occurred.
The display format is as follows:
Slave fault state: (test actions)(test actions) | corresponding step for the master: (test actions)(test actions) | Description
00 hex: (L1+OFF)(L2+ON) | 0A hex: ( )( ) | Synchronization / switching step
0A hex: (L1+OFF)(L2+ON) | 15 hex: ( )( ) | Wait step
15 hex: (L1+OFF)(L2+OFF) | 20 hex:( )( ) | 1.) F-DI 0 ... 4 check for 0 V 2.) Switch step to new level
20 hex: (L1+OFF)(L2+OFF) | 2B hex: ( )( ) | Wait step
2B hex: (L1+ON)(L2+ON) | 36 hex: ( )( ) | 1.) F-DI 5 ... 9 check for 0 V 2.) Switch step to new level
36 hex: (DO OFF)( ) | 41 hex: (DO OFF)( ) | Wait step / switching step
41 hex: (DO OFF)( ) | 4C hex: (DO OFF)( ) | Wait step
4C hex: (DO ON)( ) | 57 hex: (DO ON)( ) | 1.) Check diag-DO or diag-DI 2.) Switch step to new level
57 hex: (DO ON)( ) | 62 hex: (DO ON)( ) | Wait step
62 hex: (DO OFF)( ) | 6D hex: (DO ON)( ) | 1.) Check diag-DO or diag-DI 2.) Switch step
6D hex: (DO OFF)( ) | 78 hex: (DO ON)( ) | Wait step
78 hex: (DO ON)( ) | 83 hex: (DO OFF)( ) | 1.) Check diag-DO or diag-DI 2.) Switch step
83 hex: (DO ON)( ) | 8E hex: (DO OFF)( ) | Wait step
8E hex: (DO OFF)( ) | 99 hex: (DO OFF)( ) | 1.) Check diag-DO or diag-DI 2.) Switch step
99 hex: (DO OFF)( ) | A4 hex: (DO OFF)( ) | Wait step
A4 hex: (DO OFF)( ) | AF hex: (DO OFF)( ) | Check Diag-DO or Diag-DI
AF hex: (DO original state)() | C5 hex: (DO original state)() | Switching step
C5 hex: End of test
The expected states to be checked depend on the parameterized test mode (p10047).
The following expected states are tested in the test steps when testing the F-DOs:
The display format is as follows:
Test step (SL MA): Expected Diag-DO mode 1 | Expected DI 20 ... 23 mode 2 | Expected DI 20 ... 23 mode 3
(4C hex 57 hex): Diag-DO = 0 V | DI = 24 V | DI = 24 V
(62 hex 6D hex): Diag-DO = 0 V | DI = 0 V | DI = 0 V
(78 hex 83 hex): Diag-DO = 0 V | DI = 0 V | DI = 24 V
(8E hex 99 hex): Diag-DO = 24 V | DI = 0 V | DI = 24 V
(A4 hex AF hex): Diag-DO = 0 V | DI = 24 V | DI = 24 V
Example:
If an error with fault causes bb = 02 hex or 04 hex occurs in a test stop step, the test action for the fault took place in the
previous test stop step. The expected states are tested in the next step.
Master signals fault value 0001_04AF and slave signals fault value 0001_04A4.
aaaa = 1 --> F-DO 0 is involved.
bb = 04 hex --> the test of the Diag-DO was unsuccessful.
cc = The expected states were tested in test stop step AF on the master and A4 on the slave.
The expected state Diag-DO = 0 V was checked in the table, i.e. Diag-DO was at 0 V instead of the expected 24 V. The
associated test action took place in the previous step (99 hex DO OFF, A4 hex DO OFF). Both DOs were switched to OFF.
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1377
SINAMICS alarms
Remedy:
Check the wiring of the F-DIs and F-DOs and restart the test stop.
Note:
The fault is withdrawn if the test stop is successfully completed.
For fault value = CCCCCCCC hex, DDDDDDDD hex, EEEEEEEE hex the following applies:
These fault values occur together with fault F35152.
Possible countermeasure:
- check all parameters for the test stop.
- you should also check whether the firmware version of the TM54F matches that of the Control Unit.
- check p10001, p10017, p10046 and p10047.
A POWER ON must be carried out after correcting the parameters.
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
235014
<location>TM54F: Test stop for failsafe digital inputs/outputs
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
The time set in p10003 for the forced checking procedure (test stop) for the digital inputs/outputs has been exceeded. A new
forced checking procedure is required.
After the next time the forced checking procedure is selected, the message is withdrawn and the monitoring time is reset.
Note:
- this message does not result in a safety stop response.
- the test must be performed within a defined, maximum time interval (p10003, maximum of 8760 hours) in order to
comply with the requirements as laid down in the standards for timely fault detection and the conditions to calculate the
failure rates of safety functions (PFH value). Operation beyond this maximum time period is permissible if it can be ensured
that the forced checking procedure is performed before persons enter the hazardous area and who are depending on the
safety functions correctly functioning.
See also: p10003
Remedy:
Carry out the forced checking procedure for the digital inputs/outputs.
The signal source to select the forced checking procedure is set via binector input p10007.
See also: p10007
235015
<location>TM54F: Motor/Hydraulic Module replaced or configuration inconsistent
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
NONE
Alarms
1378
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
Cyclic communication of at least one drive with the Terminal Module 54F (TM54F) is not active.
Possible causes:
- at least one Motor Module/Hydraulic Module was replaced (e.g. hardware was replaced).
- the parameterization of theTM54F (p10010) is inconsistent with the number of drives, which have drive-based motion
monitoring functions activated with TM54F.
- for the signaled drive, it is not permissible that the "Safe motion monitoring without selection" (p9601.5 = 1) is
parameterized.
- And activated drive has no communication via DRIVE-CLiQ.
- p10010 of the TM54F master module is not the same as p10010 of the TM54F slave module (in this case, F35051 is also
output).
- in p10010 of the TM54F master or slave module, the number of a drive object was entered several times.
- the control of the Basis Functions via TM54F was parameterized, and simultaneously the Extended Safety Functions or ncSI
were parameterized.
Alarm value (r2124, interpret binary):
yyyy yyyy xxxx xxxx bin
xxxx xxxx bin: inconsistent configuration
Bit 0 = 1: No communication with drive 1.
Bit 5 = 1: No communication with drive 6.
yyyy yyyy bin: Motor Module/Hydraulic Module replaced or a DRIVE-CLiQ cable of a Motor/Hydraulic Module not inserted.
Bit 8 = 1: Motor Module/Hydraulic Module from drive 1 was replaced or does not communicate.
Bit 13 = 1: Motor Module/Hydraulic Module from drive 6 was replaced or does not communicate.
Note:
When this alarm is active, none of the drives listed in the alarm value, which have drive-based motion monitoring functions
operating with TM54F, are enabled.
For alarm value = 0:
The number of drive objects specified in p10010 is not equal to the number of drives that have drive-based motion
monitoring functions that have been enabled.
See also: p10010 (SI TM54F drive object assignment)
Remedy:
For all drive objects specified in p10010, check whether the drive-based motion monitoring functions with TM54F are
enabled (p9601).
Check as to whether F35051 is also output and remove the cause.
Check whether each drive object number is listed only once in the indices of p10010.
Note:
If a drive was deactivated and activated without first having established the DRIVE-CLiQ connection, then this alarm is also
output.
When replacing a Motor Module/Hydraulic Module, carry out the following steps:
- start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
- acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
For SINUMERIK, the following applies:
HMI supports the replacement of components with Safety functions (operating area "Diagnostics" --> Softkey "Alarm list" --
> Softkey "Confirm SI HW" etc.).
The precise procedure is given in the following document:
SINUMERIK Function Manual Safety Integrated
235016
<location>TM54F: Net data communication with drive not established
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1379
SINAMICS alarms
Acknowledge:
NONE
Cause:
The cyclic net data communication within the Terminal Module 54F (TM54F) is still not active for at least one drive.
Note:
This message is output after the TM54F master and TM54F slave have booted and is automatically withdrawn as soon as
communications have been established.
Remedy:
When replacing a Motor Module/Hydraulic Module, carry out the following steps:
- start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
- acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
The following always applies:
- for all drive objects specified in p10010, check whether the drive-based motion monitoring functions with TM54F are
enabled (p9601).
- check whether fault F35150 is present and if required, remove the cause of this fault.
Note:
The communication status of the individual drives is indicated in r10055. The corresponding drive objects can be identified
together with p10010.
See also: r10055 (SI TM54F communication status drive-specific)
235040
<location>TM54F: 24 V undervoltage
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
Fault cause: %1 bin
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
For the 24 V power supply for the Terminal Module 54F (TM54F) an undervoltage condition was detected.
As fault response failsafe input terminal signals are transferred to the motion monitoring functions.
Fault value (r0949, interpret binary):
Bit 0 = 1: Power supply undervoltage at connection X524.
Bit 1 = 1: Power supply undervoltage at connection X514.
Remedy:
- check the 24 V DC power supply for the TM54F.
- carry out safe acknowledgment (p10006).
235043
<location>TM54F: 24 V overvoltage
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
For the 24 V power supply for the Terminal Module 54F (TM54F) an overvoltage condition was detected.
As fault response failsafe input terminal signals are transferred to the motion monitoring functions.
Remedy:
- check the 24 V DC power supply for the TM54F.
- carry out safe acknowledgment (p10006).
235051
<location>TM54F: Defect in a monitoring channel
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Alarms
1380
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The Terminal Module 54F (TM54F) has identified an error in the data cross check between the two control channels.
This can be the result of incorrect parameterization. However, a fault may have occurred, which was identified by the Safety
Integrated software (e.g. defective hardware).
Perform the steps listed under "Remedy" in order to rule out any defective hardware.
As fault response failsafe input terminal signals are transferred to the motion monitoring functions.
Fault value (r0949, interpret hexadecimal):
aaaabbcc hex
aaaa: A value greater than zero indicates an internal software error.
bb: Data to be cross-compared that resulted in the error.
If specified, check the specified parameters to ensure that they are the same for both the TM54F master and TM54F slave.
bb = 00 hex: p10000[0]
bb = 01 hex: p10001
bb = 02 hex: p10002
bb = 03 hex: p10006
bb = 04 hex: p10008
bb = 05 hex: p10010
bb = 06 hex: p10011
bb = 07 hex: p10020
bb = 08 hex: p10021
bb = 09 hex: p10022
bb = 0A hex: p10023
bb = 0B hex: p10024
bb = 0C hex: p10025
bb = 0D hex: p10026
bb = 0E hex: p10027
bb = 0F hex: p10028
bb = 10 hex: p10036
bb = 11 hex: p10037
bb = 12 hex: p10038
bb = 13 hex: p10039
bb = 14 hex: p10040
bb = 15 hex: p10041
bb = 16 hex: p10042
bb = 17 hex: p10043
bb = 18 hex: p10044
bb = 19 hex: p10045
bb = 1A hex: p10046
bb = 1B hex: p10041
bb = 1C hex: p10046
bb = 1D ... 1F hex: p10017, p10002, p10000
bb = 20 ... 2A hex: p10040, p10046, p10047
bb = 2B hex: error in the data for test stop initialization
bb = 2C hex: error in the data for initializing the input/output calculation
bb = 2D ... 45 hex: error in the data for the output calculation p10042 ... p10045
bb = 46 ... 63 hex: error in the data for the calculation of drive group 1
bb = 64 ... 81 hex: error in the data for the calculation of drive group 2
bb = 82 ... 9F hex: error in the data for the calculation of drive group 3
bb = A0 ... BD hex: error in the data for the calculation of the drive group 4
bb = BE hex: debounce time of the failsafe inputs (F-DI) p10017
bb = BF hex: debounce time of the single-channel inputs (DI) p10017
bb = C0 hex: debounce time of the Diag inputs p10017
bb = C1 hex: error in the internal data for p10030 SDI positive
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1381
SINAMICS alarms
bb = C2 hex: error in the internal data for p10031 SDI negative
bb = C3 ... CA hex: error in the data to calculate the drive groups p10030 ... p10031
bb = CB hex: p10032
bb = CC hex: p10033
bb = CD hex: p10009
bb = CE ... CF error in the data for drive group 1 SLP parameter p10032 ... p10033
bb = D0 ... D1 error in the data for drive group 2 SLP parameter p10032 ... p10033
bb = D2 ... D3 error in the data for drive group 3 SLP parameter p10032 ... p10033
bb = D4 ... D5 error in the data for drive group 4 SLP parameter p10032 ... p10033
bb = D6 error in the data for initializing the retract function
bb = D7 error in the data for the retract function SLP
bb = D8 error in parameter p10000[1...5]
bb = D9 ... E3 error in the internal data of the axis communication
bb = E4 ... F2 error in the internal data of the discrepancy check
cc: indicates the index of the data to be cross-compared that resulted in the error.
Remedy:
Carry out the following steps on the TM54F:
- check the specified parameters for incorrect parameterization.
- activate the safety commissioning mode (p0010 = 95).
- start the copy function for SI parameters (p9700 = 57 hex).
- acknowledge complete data change (p9701 = AC hex).
- exit the safety commissioning mode (p0010 = 0).
- save all parameters (p0977 = 1).
- carry out safe acknowledgment (p10006).
For an internal software error (aaaa > 0):
- For TM54F, upgrade the firmware to a later version.
- contact Technical Support.
- replace the TM54F.
235052
<location>TM54F: Internal hardware error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
An internal software/hardware error has been detected on the Terminal Module 54F (TM54F).
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade TM54F firmware to more recent version.
- contact Technical Support.
- replace the TM54F.
235053
<location>TM54F: Temperature fault threshold exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Alarms
1382
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this
fault.
As fault response failsafe input terminal signals are transferred to the motion monitoring functions.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Remedy:
- allow the TM54F to cool down.
- carry out safe acknowledgment (p10006).
235054
<location>TM54F: Temperature alarm threshold exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
The temperature measured using the temperature sensing on the TM54F has exceeded the threshold value to initiate this
alarm.
Remedy:
- allow the TM54F to cool down.
- carry out safe acknowledgment (p10006).
235075
<location>TM54F: Error during internal communication
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
An internal communications error has occurred in the Terminal Module 54F (TM54F).
This message is also output in the following cases:
- parameter p10000 (TM54F master) is not set the same as p10000 (TM54F slave).
- parameter p10010 (TM54F master) is not set the same as p10010 (TM54F slave).
Alarm value (r2124, interpret decimal):
Only for internal Siemens diagnostics.
Remedy:
For p10010/p10000 from the TM54F master not equal to the TM54F slave:
- start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
- acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
For internal communication errors:
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade the software on the TM54F.
- contact Technical Support.
- replace the TM54F.
235080
<location>TM54F: Checksum error safety parameters
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1383
SINAMICS alarms
Cause:
The calculated checksum entered in r10004 over the safety-relevant parameters does not match the reference checksum
saved in p10005 at the last machine acceptance.
Fault value (r0949, interpret binary):
Bit 0 = 1: Checksum error for functional SI parameters.
Bit 1 = 1: Checksum error for SI parameters for component assignment.
Remedy:
- check the safety-relevant parameters and if required, correct.
- set the reference checksum to the actual checksum.
- acknowledge the hardware replacement.
- carry out a POWER ON (switch-off/switch-on).
- carry out an acceptance test.
235081
<location>TM54F: Static (steady state) 1 signal at the F-DI for safe acknowledgment
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
-
Reaction:
NONE
Acknowledge:
NONE
Cause:
A logical 1 signal is present at the F-DI configured in p10006 for more than 10 seconds.
If, at the F-DI no acknowledgment was performed for safe acknowledgment, then a steady-state logical and 0 signal must
be present. This avoids unintentional safety-relevant acknowledgment (or the "Internal Event Acknowledge" signal) if a wire
breaks or one of the two digital inputs bounces.
Remedy:
Set the failsafe digital input (F-DI) to a logical 0 signal (p10006).
Note:
F-DI: Failsafe Digital Input
235150
<location>TM54F: Communication error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
A communication error between the TM54F master and Control Unit or between the TM54F slave and the Motor Module/
Hydraulic Module was detected.
Fault value (r0949, interpret hexadecimal):
Only for internal Siemens troubleshooting.
Remedy:
When replacing a Motor Module/Hydraulic Module, carry out the following steps:
- start the copy function for the node identifier on the TM54F (p9700 = 1D hex).
- acknowledge the hardware CRC on the TM54F (p9701 = EC hex).
- save all parameters (p0977 = 1).
- carry out a POWER ON (switch-off/switch-on) for all components.
The following always applies:
- check the electrical cabinet design and cable routing for EMC compliance
- upgrade the software on the TM54F.
- contact Technical Support.
- replace the TM54F.
235151
<location>TM54F: Discrepancy error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Alarms
1384
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Acknowledge:
IMMEDIATELY
Cause:
The safe input terminals or output terminals have a different state for longer than the time parameterized in p10002 - or too
many switching operations were carried out within a monitoring cycle p10002.
Fault value (r0949, interpret hexadecimal):
yyyyxxxx hex
xxxx: The safety-relevant input terminals F-DI indicate a discrepancy.
Bit 0: Discrepancy for F-DI 0
Bit 9: Discrepancy for F-DI 9
yyyy: The safety-relevant output terminals F-DO indicate a discrepancy.
Bit 0: Discrepancy for F-DO 0
Bit 3: Discrepancy for F-DO 3
Note:
If several discrepancy errors occur consecutively, then this fault is only signaled for the first error that occurs.
The following options are available to analyze all of the discrepancy errors:
- using the commissioning tool, evaluate the input states and output states of the TM54F. All discrepancy errors are displayed
here.
- compare parameters p10051 and p10052 from the TM54F master and TM54F slave for discrepancy.
Remedy:
Check the wiring of the corresponding F-DI (contact problems).
If the wiring is correct, and for example there is no wire breakage, then a check must be made as to whether the switching
frequency at F-DI is too high and must therefore be reduced (switching pulses must have a longer time between them).
The time interval between each signal edge at an F-DI must be at least equal to the discrepancy time before the input is
switched again.
Discrepancy errors in the failsafe digital inputs (F-DI) can only be completely acknowledged if, after the cause of the error
was resolved, safe acknowledgment was carried out (see p10006). As long as safety acknowledgment was not carried out,
the corresponding F-DI stays in the safe state internally.
Sets the discrepancy time for fast switching operations at the F-DIs:
For fast switching operations at the failsafe digital inputs (F-DI), it may be necessary to adapt the discrepancy time to the
switching frequency:
- the period of a cyclic switching pulse must be less than half of the discrepancy time (if necessary, round down).
- the time between two switching pulses should be longer than the discrepancy time (if necessary, round up).
- the discrepancy time must be at least r10003 (it must always be rounded-down or rounded-up to an integer multiple of
the SI sampling time r10003). If a debounce time has been parameterized (p10017 > 0), then the shortest possible
discrepancy time is directly specified using the debounce time.
- the period of a cyclic switching pulse must be less than half of the discrepancy time p10017 (if necessary, round down).
- the time between two fast switching pulses should be longer than the discrepancy time+p10017 (if necessary, round up).
- the discrepancy time must be at least r10003.
The debounce time must always be set less than the discrepancy time.
Example:
If the SI sampling cycle is 12 ms and the switching frequency is 110 ms (p10017 = 0), the maximum discrepancy time which
can be set is as follows:
p10002 <= 110/2 ms - 12 ms = 43 ms --> rounded-off, the following is obtained p10002 <= 36 ms
Since the discrepancy time can only be accepted as a whole SI sampling time, the value will need to be rounded up or down
to a whole SI sampling time value if it is not an exact integer multiple of an SI sampling time.
Basic secondary condition to set the discrepancy time:
The discrepancy time of the F-DIs must always be longer than the longest SI sampling time of all drives that use Safety
Integrated with TM54F (p9780/p9500).
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
235152
<location>TM54F: Internal software error
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM41,
TM54F_MA, TM54F_SL, VECTOR, VECTOR_AC
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1385
SINAMICS alarms
Message value:
%1
Reaction:
NONE
Acknowledge:
IMMEDIATELY
Cause:
An internal software error has occurred in the Terminal Module 54F (TM54F).
The failsafe digital inputs and digital outputs (F-DI, F-DO) on the TM54F have been set to the safe state.
Fault value (r0949, interpret decimal):
Only for internal Siemens troubleshooting.
Note:
F-DI: Failsafe Digital Input
F-DO: Failsafe Digital Output
Remedy:
Check that the firmware version of the TM54F matches the Control Unit's firmware version.
The automatic firmware update must be activated in the project.
Note:
This signal will also appear, for example, in conjunction with fault F35013. In this case, check all the parameters for the test
stop on the TM54F (p10001, p10003, p10007, p10041, p10046, p10047). In this case, a POWER ON is required after the
parameters have been corrected.
235200
<location>TM: Calibration data
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM120,
TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
NONE
Acknowledge:
NONE
Cause:
An error was detected in the calibration data of the Terminal Module.
Alarm value (r2124, interpret decimal):
ddcbaa dec: dd = component number, c = AI/AO, b = fault type, aa = number
c = 0: analog input (AI)
c = 1: analog output (AO)
b = 0: No calibration data available.
b = 1: Offset too high (> 100 mV).
Remedy:
- carry out a POWER ON (switch-off/switch-on) for all components.
- replace the component if necessary.
235207
<location>TM: Temperature fault/alarm threshold channel 0 exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM120,
TM15, TM150, TM15DI_DO, TM17, TM31, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (NONE, OFF1, OFF3)
Vector: OFF2 (NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Alarms
1386
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
SINAMICS alarms
Cause:
For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is
fulfilled:
- alarm threshold has been exceeded longer than that set in the timer (p4102[0], p4103[0]).
or
- fault threshold exceeded (p4102[1]).
Note:
For sensor type "PTC thermistor" and "Bimetallic NC contact" (p4100[0] = 1, 4), the following applies:
- if r4101[0] > 1650 ohms, the temperature r4105[0] = 250 °C
- if r4101[0] <= 1650 ohms, the temperature r4105[0] = -50 °C
The temperature actual value is displayed via connector output r4105[0] and can be interconnected.
Notice:
This fault only causes the drive to shut down if there is at least one BICO interconnection between the drive and the Terminal
Module.
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
Remedy:
- allow the temperature sensor to cool down to below p4102[1] - hysteresis (5 K, for TM150, can be set using p4118[0]).
- if required, set the fault response to NONE (p2100, p2101).
See also: p4102
235208
<location>TM: Temperature fault/alarm threshold channel 1 exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM120,
TM150, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (NONE, OFF1, OFF3)
Vector: OFF2 (NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is
fulfilled:
- alarm threshold has been exceeded longer than that set in the timer (p4102[2], p4103[1]).
or
- fault threshold exceeded (p4102[3]).
Note:
For sensor type "PTC thermistor" and "Bimetallic NC contact" (p4100[1] = 1, 4), the following applies:
- if r4101[1] > 1650 ohms, the temperature r4105[1] = 250 °C
- if r4101[1] <= 1650 ohms, the temperature r4105[1] = -50 °C
The temperature actual value is displayed via connector output r4105[1] and can be interconnected.
Notice:
This fault only causes the drive to shut down if there is at least one BICO interconnection between the drive and the Terminal
Module.
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
Remedy:
- allow the temperature sensor to cool down to below p4102[3] - hysteresis (5 K, for TM150, can be set using p4118[1]).
- if required, set the fault response to NONE (p2100, p2101).
See also: p4102
235209
<location>TM: Temperature fault/alarm threshold channel 2 exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM120,
TM150, TM41, VECTOR, VECTOR_AC
Message value:
%1
Alarms
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4
1387
SINAMICS alarms
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (NONE, OFF1, OFF3)
Vector: OFF2 (NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is
fulfilled:
- alarm threshold has been exceeded longer than that set in the timer (p4102[4], p4103[2]).
or
- fault threshold exceeded (p4102[5]).
Note:
For sensor type "PTC thermistor" and "Bimetallic NC contact" (p4100[2] = 1, 4), the following applies:
- if r4101[2] > 1650 ohms, the temperature r4105[2] = 250 °C
- if r4101[2] <= 1650 ohms, the temperature r4105[2] = -50 °C
The temperature actual value is displayed via connector output r4105[2] and can be interconnected.
Notice:
This fault only causes the drive to shut down if there is at least one BICO interconnection between the drive and the Terminal
Module.
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
Remedy:
- allow the temperature sensor to cool down to below p4102[5] - hysteresis (5 K, for TM150, can be set using p4118[2]).
- if required, set the fault response to NONE (p2100, p2101).
See also: p4102
235210
<location>TM: Temperature fault/alarm threshold channel 3 exceeded
Drive object:
A_INF, A_INF_840, B_INF, B_INF_840, HLA, HLA_840, R_INF, S_INF, S_INF_840, SERVO, SERVO_840, SERVO_AC, TM120,
TM150, TM41, VECTOR, VECTOR_AC
Message value:
%1
Reaction:
Infeed: OFF2 (NONE, OFF1)
Servo: OFF2 (NONE, OFF1, OFF3)
Vector: OFF2 (NONE, OFF1, OFF3)
Hla: OFF2 (NONE, OFF1, OFF3)
Acknowledge:
IMMEDIATELY (POWER ON)
Cause:
For the temperature evaluation via the Terminal Module (TM), at least one of the following conditions to initiate this fault is
fulfilled:
- alarm threshold has been exceeded longer than that set in the timer (p4102[6], p4103[3]).
or
- fault threshold exceeded (p4102[7]).
Note:
For sensor type "PTC thermistor" and "Bimetallic NC contact" (p4100[3] = 1, 4), the following applies:
- if r4101[3] > 1650 ohms, the temperature r4105[3] = 250 °C
- if r4101[3] <= 1650 ohms, the temperature r4105[3] = -50 °C
The temperature actual value is displayed via connector output r4105[3] and can be interconnected.
Notice:
This fault only causes the drive to shut down if there is at least one BICO interconnection between the drive and the Terminal
Module.
Fault value (r0949, interpret decimal):
Temperature actual value at the time of initiation [0.1 °C].
Remedy:
- allow the temperature sensor to cool down to below p4102[7] - hysteresis (5 K, for TM150, can be set using p4118[3]).
- if required, set the fault response to NONE (p2100, p2101).
See also: p4102
Alarms
1388
Diagnostics Manual, 10/2020, 6FC5398-6BP40-6BA4

 

 

 

 

 

 

 

Content      ..     45      46      47      48     ..