Siemens V90 Drive Fault Codes:
| Fault Code and Meaning | Cause and Remedy |
|---|---|
| F1000 Internal software error | Cause: An internal software error has occurred. Remedy:
|
| F1001 FloatingPoint exception | Cause: An exception occurred during an operation with the FloatingPoint data type. Remedy:
|
| F1002 Internal software error | Cause: An internal software error has occurred. Remedy:
|
| F1003 Acknowledgement delay when accessing the memory | Cause: A memory area was accessed that does not return a “READY”. Remedy:
|
| F1015 Internal software error | Cause: An internal software error has occurred. Remedy:
|
| F1018 Booting has been interrupted several times | Cause: Module booting was interrupted several times. As a consequence, the module boots with the factory setting. Possible reasons for booting being interrupted:
After this fault is output, then the module is booted with the factory settings. Remedy:
Examples:
Note: If the fault situation is repeated, then this fault is again output after several interrupted boots. |
| F1030 Sign-of-life failure for master control | Cause: For active PC master control, no sign-of-life was received within the monitoring time. Remedy: Contact the Hotline. |
| F1611 SI CU: Defect detected | Cause: The drive-integrated “Safety Integrated” (SI) function on the Control Unit (CU) has detected an error and initiated an STO. Remedy:
|
| F7011 Motor overtemperature | Cause:
Remedy:
|
| F7085 Open-loop/closed-loop control parameters changed | Cause: Open-loop/closed-loop control parameters have had to be changed for the following reasons:
Remedy: It is not necessary to change the parameters as they have already been correctly limited. |
| F7403 Lower DC link voltage threshold reached | Cause: The DC link voltage monitoring is active and the lower DC link voltage threshold was reached in the “Operation” state. Remedy:
|
| F7404 Upper DC link voltage threshold reached | Cause: The DC link voltage monitoring is active and the upper DC link voltage threshold was reached in the “Operation” state. Remedy:
|
| F7410 Current controller output limited | Cause: The condition “I_act = 0 and Uq_set_1 longer than 16 ms at its limit” is present and can be caused by the following:
Remedy:
|
| F7412 Commutation angle incorrect (motor model) | Cause: An incorrect commutation angle was detected that can result in a positive coupling in the speed controller. Possible causes:
Remedy:
|
| F7430 Changeover to open-loop torque controlled operation not possible | Cause: For encoderless operation, the converter cannot change over to closed-loop torque-controlled operation. Remedy:
|
| F7431 Changeover to encoderless operation not possible | Cause: For closed-loop torque control, the converter cannot change over to encoderless operation. Remedy:
|
| F7442 LR: Multiturn does not match the modulo range | Cause: The ratio between the multiturn resolution and the modulo range (p29246) is not an integer number. This results in the adjustment being set back, as the position actual value cannot be reproduced after power-off/power-on. Remedy: Make the ratio between the multiturn resolution and the modulo range an integer number. The ratio v is calculated as follows: v = (4096 * p29247 * p29248) / (p29249 * p29246) |
| F7443 Reference point coordinate not in the permissible range | Cause: The reference point coordinate received when adjusting the encoder via connector input p2599 lies outside the half of the encoder range and cannot be set as actual axis position. Remedy: Set the reference point coordinate to a lower value than specified in the fault value. See also: p2599 (EPOS reference point coordinate value). For a motor with an absolute encoder, the maximum permissible encoder range is calculated by the formula (4096 * p29247)/2. |
| F7450 Standstill monitoring has responded | Cause: After the standstill monitoring time expired, the drive left the standstill window.
Remedy: Check the causes and resolve. |
| F7452 Following error too high | Cause: The difference between the position setpoint position actual value (following error dynamic model) is greater than the tolerance.
Remedy: Check the causes and resolve. |
| F7453 Position actual value preprocessing error | Cause: An error has occurred during the position actual value preprocessing. Remedy: Check the encoder for the position actual value preprocessing. |
| F7458 EPOS: Reference cam not found | Cause: After starting the search for reference, the axis moved through the maximum permissible distance to search for the reference cam without actually finding the reference cam. Remedy:
See also: p2606 (EPOS search for reference cam maximum distance) |
| F7459 Zero mark not detected | Cause: After leaving the reference cam, the axis has traversed the maximum permissible distance (p2609) between the reference cam and the zero mark without finding the zero mark. Remedy:
|
| F7460 EPOS: End of reference cam not found | Cause: During the search for reference, when the axis reached the zero mark it also reached the end of the traversing range without detecting an edge at the binector input “reference cam”. Maximum traversing range: -2147483648 [LU] … -2147483647 [LU] Remedy:
|
| F7475 EPOS: Target position < start of traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| F7476 EPOS: Target position > end of the traversing range | Cause: The target position for relative traversing lies outside the traversing range. Remedy: Correct the target position. |
| F7481 EPOS: Axis position < software limit switch minus | Cause: The actual position of the axis is less than the position of the software limit switch minus. Remedy:
|
| F7482 EPOS: Axis position > software limit switch plus | Cause: The actual position of the axis is greater than the position of the software limit switch plus. Remedy:
|
| F7490 Enable signal withdrawn while traversing | Cause:
Remedy:
|
| F7491 STOP cam minus reached | Cause: The STOP cam minus was reached. For a positive traversing direction, the STOP cam minus was reached, i.e. the wiring of the STOP cam is incorrect. Remedy:
|
| F7492 STOP cam plus reached | Cause: The STOP cam plus was reached. For a negative traversing direction, the STOP cam plus was reached, i.e. the wiring of the STOP cam is incorrect. Remedy:
|
| F7493 LR: Overflow of the value range for position actual value | Cause: The value range (-2147483648 … 2147483647) for the position actual value representation was exceeded. When the overflow occurs, the “referenced” or “adjustment absolute measuring system” status is reset.
Remedy: If required, reduce the traversing range or position resolution p29247. Note for case = 3: If the value for the maximum possible absolute position (LU) is greater than 4294967296, then it is not possible to make an adjustment due to an overflow. For rotary encoders, the maximum possible absolute position (LU) is calculated as follows: Motor encoder without position tracking:
|
| F7599 Encoder 1: Adjustment not possible | Cause: The maximum encoder value times the factor to convert the absolute position from increments to length units (LU) has exceeded the value range (-2147483648 … 2147483647) for displaying the position actual value. Remedy: If the value for the maximum possible absolute position (LU) is greater than 4294967296, then it is not possible to make an adjustment due to an overflow. For rotary encoders, the maximum possible absolute position (LU) is calculated as follows: Motor encoder without position tracking:
|
| F7801 Motor overcurrent | Cause: The permissible motor limit current was exceeded.
Remedy:
|
| F7802 Infeed or power unit not ready | Cause: After an internal power-on command, the infeed or drive does not signal ready because of one of the following reasons:
Remedy:
|
| F7815 Power unit has been changed | Cause: The code number of the actual power unit does not match the saved number. Remedy: Connect the original power unit and power up the Control Unit again (POWER ON). |
| F7900 Motor blocked/speed controller at its limit | Cause: The servo motor has been operating at the torque limit longer than 1s and below the speed threshold of 120 rpm. This signal can also be initiated if the speed actual value is oscillating and the speed controller output repeatedly goes to its limit. Remedy:
|
| F7901 Motor overspeed | Cause: The maximumly permissible speed has been exceeded. Remedy: Check and correct the maximum speed (p1082). |
| F7995 Motor identification failure | Cause: For incremental motor, needs pole position identification when first SON. If motor already in run (i.e. by external force) position identification may failure. Remedy: Stop motor before SON. |
| F30001 Power unit: Overcurrent | Cause: The power unit has detected an overcurrent condition.
Remedy:
|
| F30002 DC link voltage, overvoltage | Cause: The power unit has detected overvoltage in the DC link.
Remedy:
|
| F30003 DC link voltage, undervoltage | Cause: The power unit has detected an undervoltage condition in the DC link.
Remedy:
|
| F30004 Drive heat sink overtemperature | Cause: The temperature of the power unit heat sink has exceeded the permissible limit value.
Remedy:
|
| F30005 Power unit: Overload I²t | Cause: The power unit was overloaded.
Remedy:
|
| F30011 Line phase failure in main circuit | Cause: At the power unit, the DC link voltage ripple has exceeded the permissible limit value. Possible causes:
Remedy:
|
| F30015 Phase failure motor cable | Cause: A phase failure in the motor feeder cable was detected. The signal can also be output in the following case: The motor is correctly connected, however the closed-speed control is instable and therefore an oscillating torque is generated. Remedy:
|
| F30021 Ground fault | Cause: Power unit has detected a ground fault.
Remedy:
|
| F30027 Precharging DC link time monitoring | Cause: The power unit DC link was not able to be pre-charged within the expected time.
Remedy: Check the line supply voltage at the input terminals. |
| F30036 Internal overtemperature | Cause: The temperature inside the drive converter has exceeded the permissible temperature limit. • Insufficient cooling, fan failure. • Overload. • Surrounding temperature too high. Remedy:
Notice: This fault can only be acknowledged once the permissible temperature limit minus 5 K has been fallen below. |
| F30050 24 V supply overvoltage | Cause: The voltage monitor signals an overvoltage fault on the module. Remedy:
|
| F31100 Zero mark distance error | 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. Remedy:
|
| F31110 Serial communications error | Cause: Serial communication protocol transfer error between the encoder and evaluation module. Remedy:
|
| F31112 Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
| F31117 Inversion error signals A/B/R | 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. Remedy:
|
| F31130 Zero mark and position error from the coarse synchronization | 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. Remedy:
|
| F31150 Initialization error | Cause: Encoder functionality is not operating correctly. Remedy:
|
| F52903 Fault inconsistence between fault status and fault buffer | Cause: Fault status and fault number buffer are inconsistent. Remedy:
|
| F52904 Control mode change | Cause: When the control mode is changed, the drive must be saved and restarted. Remedy:
|
| F52911 Positive torque limitation value error | Cause: One of positive torque limitation values (P29050) becomes less than 0. Remedy:
|
| F52912 Negative torque limitation value error | Cause: One of negative torque limitation values (P29051) becomes greater than 0. Remedy:
|
| F52931 Gear box limit | Cause: The electronic gear ratio (p29012[x] / p29013[x]) exceeds the range from 0.02 to 200. Remedy:
|
| F52980 Absolute encoder motor changed | Cause: The servo motor with absolute encoder is changed. Actual motor ID is different from commissioned motor ID. Remedy:
|
| F52981 Absolute encoder motor mismatched | Cause: Connected absolute encoder motor cannot be operated. The servo drive in use does not support the Motor ID. Remedy:
|
| F52983 No encoder detected | Cause: The servo drive in use does not support encoderless operation. Remedy:
|
| F52984 Incremental encoder motor not configured | Cause: • Commissioning of the servo motor has failed. • The incremental encoder motor is connected but fails to commission. Remedy:
|
| F52985 Absolute encoder motor wrong | Cause: • Motor ID is downloaded wrong during manufacture. • The software of the servo drive does not support the Motor ID. Remedy:
|
| F52987 Absolute encoder replaced | Cause: Incorrect absolute encoder data. Remedy:
|
| A1009 Control module overtemperature | Cause: The temperature of the control module (Control Unit) has exceeded the specified limit value. Remedy:
Note: The alarm automatically disappears after the limit value has been undershot. |
| A1019 Writing to the removable data medium unsuccessful | Cause: The write access to the removable data medium was unsuccessful. Remedy:
|
| A1032 All parameters must be saved | Cause: The parameters of an individual drive object were saved, although there is still no backup of all drive system parameters. The saved object-specific parameters are not loaded the next time that the system powers up. For the system to successfully power up, all of the parameters must have been completely backed up. Remedy:
|
| A1045 Configuring data invalid | Cause: An error was detected when evaluating the parameter files saved in the non-volatile memory. Because of this, under certain circumstances, several of the saved parameter values were not able to be accepted. Remedy:
|
| A1920 Drive Bus: Receive setpoints after To | Cause: Output data of Drive Bus master (setpoints) received at the incorrect instant in time within the Drive Bus clock cycle. Remedy:
Note: To: Time of setpoint acceptance Tdx: Data exchange time |
| A1932 Drive Bus clock cycle synchronization missing for DSC | Cause: There is no clock synchronization or clock synchronous sign of life and DSC is selected. Note: DSC: Dynamic Servo Control Remedy: Set clock synchronization across the bus configuration and transfer clock synchronous sign-of-life. |
| A5000 Drive heat sink overtemperature | Cause: The alarm threshold for overtemperature at the inverter heat sink has been reached. If the temperature of the heat sink increases by an additional 5 K, then fault F30004 is initiated. Remedy: Check the following:
|
| A7012 Motor temperature model 1/3 overtemperature | Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded. Remedy:
|
| A7441 LR: Save the position offset of the absolute encoder adjustment | Cause: The status of the absolute encoder adjustment has changed. In order to permanently save the determined position offset (p2525) it must be saved. Remedy: Not necessary. This alarm automatically disappears after the offset has been saved. |
| A7456 EPOS: Setpoint velocity limited | Cause: The actual setpoint velocity is greater than the parameterized maximum velocity and is therefore limited. Remedy: Decrease the actual setpoint velocity. |
| A7461 EPOS: Reference point not set | Cause: When starting a traversing block/direct setpoint input, a reference point is not set. Remedy: Reference the system (search for reference, flying referencing, set reference point). |
| A7469 EPOS: Traversing block < target position < software limit switch minus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch minus. Remedy:
|
| A7470 EPOS: Traversing block > target position > software limit switch plus | Cause: In the traversing block the specified absolute target position lies outside the range limited by the software limit switch plus. Remedy:
|
| A7471 EPOS: Traversing block target position outside the modulo range | Cause: In the traversing block the target position lies outside the modulo range. Remedy:
|
| A7472 EPOS: Traversing block ABS_POS/ABS_NEG not possible | Cause: In the traversing block the positioning mode ABS_POS or ABS_NEG were parameterized with the modulo correction not activated. Remedy: Correct the traversing block. |
| A7473 EPOS: Beginning of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the positive direction. |
| A7474 EPOS: End of traversing range reached | Cause: When traversing, the axis has moved to the traversing range limit. Remedy: Move away in the negative direction. |
| A7477 EPOS: Target position < software limit switch minus | Cause: In the actual traversing operation, the target position is less than the software limit switch minus. Remedy:
|
| A7478 EPOS: Target position > software limit switch plus | Cause: In the actual traversing operation, the target position is greater than the software limit switch plus. Remedy:
|
| A7479 EPOS: Software limit switch minus reached | Cause: The axis is at the position of the software limit switch minus. An active traversing block was interrupted. Remedy:
|
| A7480 EPOS: Software limit switch plus reached | Cause: The axis is at the position of the software limit switch plus. An active traversing block was interrupted. Remedy:
|
| A7496 SON enable missing | Cause: In the PTI mode or a compound mode with PTI, the drive is in the servo off state. Remedy: Enable servo on for the drive. |
| A7576 Encoderless operation due to a fault active | Cause: Encoderless operation is active due to a fault. Remedy:
|
| A7585 P-TRG or CLR active | Cause: In the PTI mode or a compound mode with PTI, the P-TRG or CLR function is activated. Remedy: In the PTI mode, deactivate the P-TRG or CLR function; in the compound mode with PTI, do not switch to other modes. |
| A7965 Save required | Cause: The angular commutation offset was re-defined and has still not been saved. In order to permanently accept the new value, it must be saved in a non-volatile fashion. Remedy: This alarm automatically disappears after the data has been saved. |
| A7971 Angular commutation offset determination activated | Cause: The automatic determination of the angular commutation offset (encoder adjustment) is activated. The automatic determination is carried out at the next power-on command. Remedy: The alarm automatically disappears after determination. |
| A7991 Motor data identification activated | Cause: The motor data ident. routine is activated. The motor data identification routine is carried out at the next power-on command. Remedy: The alarm automatically disappears after the motor data identification routine has been successfully completed. If a POWER ON or a warm restart is performed with motor data identification selected, the motor data identification request will be lost. If motor data identification is required, it will need to be selected again manually following ramp-up. |
| A30016 Load supply switched off | Cause: The DC link voltage is too low. Remedy:
|
| A30031 Hardware current limiting in phase U | Cause: Hardware current limit for phase U responded. The pulsing in this phase is inhibited for one pulse period. Possible causes:
Note: Alarm A30031 is always output if, for a Power Module, the hardware current limiting of phase U, V or W responds. Remedy: Check the motor data. As an alternative, run a motor data identification.
|
| A31411 Absolute encoder signals internal alarms | Cause: The absolute encoder fault word includes alarm bits that have been set. Remedy: Replace the encoder. |
| A31412 Error bit set in the serial protocol | Cause: The encoder sends a set error bit via the serial protocol. Remedy:
|
| A52900 Failure during data copying | Cause:
Remedy:
|
| A52901 Braking resistor reaches alarm threshold | Cause: The heat capacity reaches the threshold (p29005) of the braking resistor capacity. Remedy:
|
| A52902 Emergency missing | Cause: Implement servo on when the emergency input (EMGS) is switched off. Remedy: Switch on the emergency input (EMGS) and then implement servo on. |
| A52932 PTO max limit | Cause:
Remedy: Change PTO ratio. |