Siemens V90 Drive

Fault Code and MeaningCause and Remedy
F1000

Internal software error

Cause:

An internal software error has occurred.



Remedy:


  • Evaluate fault buffer.

  • Carry out a POWER ON (power off/on) for all components.

  • Upgrade firmware to later version.

  • Contact the Hotline.

  • Replace the Control Unit.


F1001

FloatingPoint exception

Cause:

An exception occurred during an operation with the FloatingPoint data type.



Remedy:


  • Carry out a POWER ON (power off/on) for all components.

  • Upgrade firmware to the latest version.

  • Contact the Hotline.


F1002

Internal software error

Cause:

An internal software error has occurred.



Remedy:


  • Carry out a POWER ON (power off/on) for all components.

  • Upgrade firmware to the latest version.

  • Contact the Hotline.


F1003

Acknowledgement delay when accessing the memory

Cause:

A memory area was accessed that does not return a “READY”.



Remedy:


  • Carry out a POWER ON (power off/on) for all components.

  • Contact the Hotline.


F1015

Internal software error

Cause:

An internal software error has occurred.



Remedy:


  • Carry out a POWER ON (power off/on) for all components.

  • Upgrade firmware to the latest version.

  • Contact the Hotline.


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:

  • Power supply interrupted.

  • CPU crashed.

  • Parameterization invalid.


After this fault is output, then the module is booted with the factory settings.



Remedy:


  • Carry out a POWER ON (power off/on). After switching on, the module reboots from the valid parameterization (if available).

  • Restore the valid parameterization.


Examples:

  • Carry out a first commissioning, save, carry out a POWER ON (switch-off/switch-on).

  • Load another valid parameter backup (e.g. from the memory card), save, carry out a POWER ON (switch-off/switch-on).


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:


  • Carry out a POWER ON (power off/on) for all components.

  • Upgrade software.

  • Replace the Control Unit.


F7011

Motor overtemperature

Cause:


  • Motor overloaded.

  • Motor surrounding temperature too high.

  • Wire breakage or sensor not connected.

  • Motor temperature model incorrectly parameterized.





Remedy:


  • Reduce the motor load.

  • Check the surrounding temperature and the motor ventilation.

  • Check the wiring and the connection.

  • Check the motor temperature model parameters.


F7085

Open-loop/closed-loop control parameters changed

Cause:

Open-loop/closed-loop control parameters have had to be changed for the following reasons:

  • As a result of other parameters, they have exceeded the dynamic limits.

  • They cannot be used due to the fact that the hardware detected not having certain features.





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:


  • Check the line supply voltage.

  • Check the infeed.

  • Reduce the lower DC link threshold.

  • Switch out (disable) the DC link voltage monitoring.


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:


  • Check the line supply voltage.

  • Check the infeed module or the brake module.

  • Increase the upper DC link voltage threshold.

  • Switch out (disable) the DC link voltage monitoring.


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:

  • Motor not connected or motor contactor open.

  • No DC link voltage present.

  • Motor Module defective.





Remedy:


  • Connect the motor or check the motor contactor.

  • Check the DC link voltage.

  • Check the Motor Module.


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:

  • The motor encoder is incorrectly adjusted with respect to the magnet position.

  • The motor encoder is damaged.

  • Data to calculate the motor model has been incorrectly set.

  • Pole position identification might have calculated an incorrect value when activated.

  • The motor encoder speed signal is faulted.

  • The control loop is instable due to incorrect parameterization.





Remedy:


  • If the encoder mounting was changed, re-adjust the encoder.

  • Replace the defective motor encoder.

  • Correctly set the motor stator resistance, cable resistance and motor-stator leakage inductance. Calculate the cable resistance from the cross-section and length, check the inductance and stator resistance using the motor data sheet, measure the stator resistance, e.g. using a multimeter – and if required, again identify the values using the stationary motor data identification.

  • With pole position identification activated, check the procedure for pole position identification and force a new pole position identification procedure by means of de-selection followed by selection.


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:


  • Do not attempt to change over to closed-loop torque-controlled operation.

  • Check the encoder cable connection.


F7431

Changeover to encoderless operation not possible

Cause:

For closed-loop torque control, the converter cannot change over to encoderless operation.



Remedy:


  • Do not attempt to change over to encoderless operation.

  • Check the encoder cable connection.


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.

  • Position loop gain too low.

  • Position loop gain too high (instability/oscillation).

  • Mechanical overload.

  • Connecting cable, motor/drive converter incorrect (phase missing, interchange).




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.

  • The drive torque or accelerating capacity exceeded.

  • Position measuring system fault.

  • Position control sense incorrect.

  • Mechanical system locked.

  • Excessively high traversing velocity or excessively high position reference value (setpoint) differences.




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:


  • Check the “reference cam” input.

  • Check the maximum permissible distance to the reference cam (p2606).


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:


  • Check the encoder regarding zero mark.

  • Check the maximum permissible distance between the reference cam and zero mark (p2609).

  • Use an external encoder zero mark (equivalent zero mark).


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:


  • Check the “reference cam” input.

  • Repeat the search for reference.


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:


  • Correct the target position.

  • Change software limit switch minus (CI: p2580).


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:


  • Correct the target position.

  • Change software limit switch plus (CI: p2581).


F7490

Enable signal withdrawn while traversing

Cause:


  • For a standard assignment, another fault may have occurred as a result of withdrawing the enable signals.

  • The drive is in the “switching on inhibited” state (for a standard assignment).




Remedy:


  • Set the enable signals or check the cause of the fault that first occurred and then result (for a standard assignment).

  • Check the assignment to enable the basic positioning function.


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:


  • Leave the STOP cam minus in the positive traversing direction and return the axis to the valid traversing range.

  • Check the wiring of the STOP cam.


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:


  • Leave the STOP cam plus in the negative traversing direction and return the axis to the valid traversing range.

  • Check the wiring of the STOP cam.


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.

  • The position actual value (r2521) has exceeded the value range.

  • The encoder position actual value has exceeded the value range.

  • The maximum encoder value times the factor to convert the absolute position from increments to length units (LU) has exceeded the value range for displaying the position actual value.




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:

  • IPOS: p29247 * p29248 * 4096 / p29249 for multiturn encoders

  • PTI: 1048576 * p29012[X] * 4096 / p29013 for multiturn encoders


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:

  • IPOS: p29247 * p29248 * 4096 / p29249 for multiturn encoders

  • PTI: 1048576 * p29012[X] * 4096 / p29013 for multiturn encoders


F7801

Motor overcurrent

Cause:

The permissible motor limit current was exceeded.

  • Effective current limit set too low.

  • Current controller not correctly set.

  • Motor was braked with an excessively high stall torque correction factor.

  • Up ramp was set too short or the load is too high.

  • Short-circuit in the motor cable or ground fault.

  • Motor current does not match the current of Motor Module.




Remedy:



  • Reduce the stall torque correction factor.

  • Increase the up ramp or reduce the load.

  • Check the motor and motor cables for short-circuit and ground fault.

  • Check the Motor Module and motor combination.


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:

  • Monitoring time is too short.

  • DC link voltage is not present.

  • Associated infeed or drive of the signaling component is defective.




Remedy:



  • Ensure that there is a DC link voltage. Check the DC link busbar. Enable the infeed.

  • Replace the associated infeed or drive of the signaling component.


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:



  • Check whether the servo motor can rotate freely or not.

  • Check the torque limit.

  • Check the inversion of the actual value.

  • Check the motor encoder connection.

  • Check the encoder pulse number.


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.

  • Closed-loop control is incorrectly parameterized.

  • Controller parameters are not proper.

  • Motor has a short-circuit or fault to ground (frame).

  • Power cables are not correctly connected.

  • Power cables exceed the maximum permissible length.

  • Power unit defective.

  • Line phase interrupted.




Remedy:



  • Check the motor data – if required, carry out commissioning.

  • Modify speed loop Kp (p29120), position loop Kv (p29110).

  • Check the motor circuit configuration (star-delta).

  • Check the power cable connections.

  • Check the power cables for short-circuit or ground fault.

  • Check the length of the power cables.

  • Replace power unit.

  • Check the line supply phases.

  • Check the external braking resistor connection.


F30002

DC link voltage, overvoltage

Cause:

The power unit has detected overvoltage in the DC link.

  • Motor regenerates too much energy.

  • Device connection voltage too high.

  • Line phase interrupted.




Remedy:



  • Increase the ramp-down time.

  • Activate the DC link voltage controller.

  • Use a braking resistor.

  • Increase the current limit of the infeed or use a larger module.

  • Check the device supply voltage.

  • Check the line supply phases.


F30003

DC link voltage, undervoltage

Cause:

The power unit has detected an undervoltage condition in the DC link.

  • Line supply failure.

  • Line supply voltage below the permissible value.

  • Line supply infeed failed or interrupted.

  • Line phase interrupted.




Remedy:



  • Check the line supply voltage.

  • Check the line supply infeed and observe the fault messages relating to it (if there are any).

  • Check the line supply phases.

  • Check the line supply voltage setting.


F30004

Drive heat sink overtemperature

Cause:

The temperature of the power unit heat sink has exceeded the permissible limit value.

  • Insufficient cooling, fan failure.

  • Overload.

  • Surrounding temperature too high.

  • Pulse frequency too high.




Remedy:



  • Check whether the fan is running.

  • Check the fan elements.

  • Check whether the surrounding temperature is in the permissible range.

  • Check the motor load.

  • Reduce the pulse frequency if this is higher than the rated pulse frequency.


F30005

Power unit: Overload I²t

Cause:

The power unit was overloaded.

  • The permissible rated power unit current was exceeded for an inadmissibly long time.

  • The permissible load duty cycle was not maintained.




Remedy:



  • Reduce the continuous load.

  • Adapt the load duty cycle.

  • Check the motor and power unit rated currents.


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:

  • A line phase has failed.

  • The 3 line phases are inadmissibly unsymmetrical.

  • The fuse of a phase of a main circuit has ruptured.

  • A motor phase has failed.




Remedy:



  • Check the main circuit fuses.

  • Check whether a single-phase load is distorting the line voltages.

  • Check the motor feeder cables.


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:



  • Check the motor feeder cables.

  • Check the speed controller settings.


F30021

Ground fault

Cause:

Power unit has detected a ground fault.

  • Ground fault in the power cables.

  • Winding fault or ground fault at the motor.




Remedy:



  • Check the power cable connections.

  • Check the motor.


F30027

Precharging DC link time monitoring

Cause:

The power unit DC link was not able to be pre-charged within the expected time.

  • There is no line supply voltage connected.

  • The line contactor/line side switch has not been closed.

  • The line supply voltage is too low.

  • The pre-charging resistors are overheated as there were too many pre-charging operations per time unit.

  • The pre-charging resistors are overheated as the DC link capacitance is too high.

  • The pre-charging resistors are overheated.

  • The pre-charging resistors are overheated as the line contactor was closed during the DC link fast discharge through the Braking Module.

  • The DC link has either a ground fault or a short-circuit.

  • The pre-charging circuit is possibly defective.




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:

  • Check whether the fan is running.

  • Check the fan elements.

  • Check whether the surrounding temperature is in the permissible range.


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:

  • Check the 24 V power supply.

  • Replace the module if necessary.


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:

  • Check that the encoder cables are routed in compliance with EMC.

  • Check the plug connections.

  • Check the encoder type (encoder with equidistant zero marks).

  • Replace the encoder or encoder cable.


F31110
Serial communications error

Cause:

Serial communication protocol transfer error between the encoder and evaluation module.



Remedy:

  • Contact the Hotline.


F31112
Error bit set in the serial protocol

Cause:

The encoder sends a set error bit via the serial protocol.



Remedy:

  • Contact the Hotline.


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:

  • Check the encoder/cable.

  • Does the encoder supply signals and the associated inverted signals?


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:

  • 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.


F31150
Initialization error

Cause:

Encoder functionality is not operating correctly.



Remedy:

  • Check the encoder type used (incremental/absolute) and the encoder cable.

  • If relevant, note additional fault messages that describe the fault in detail.


F52903
Fault inconsistence between fault status and fault buffer

Cause:

Fault status and fault number buffer are inconsistent.



Remedy:

  • Repower on.


F52904
Control mode change

Cause:

When the control mode is changed, the drive must be saved and restarted.



Remedy:

  • Save and restart the drive.


F52911
Positive torque limitation value error

Cause:

One of positive torque limitation values (P29050) becomes less than 0.



Remedy:

  • Configure all of positive torque limitation values (P29050) not less than 0.


F52912
Negative torque limitation value error

Cause:

One of negative torque limitation values (P29051) becomes greater than 0.



Remedy:

  • Configure all of negative torque limitation values (P29051) not greater than 0.


F52931
Gear box limit

Cause:

The electronic gear ratio (p29012[x] / p29013[x]) exceeds the range from 0.02 to 200.



Remedy:

  • Adjust the electronic gear ratio within the permissible range from 0.02 to 200.


F52980
Absolute encoder motor changed

Cause:

The servo motor with absolute encoder is changed. Actual motor ID is different from commissioned motor ID.



Remedy:

  • The servo motor will be automatically configured after the acknowledgement of this fault.


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:

  • Use a suitable absolute encoder motor.


F52983
No encoder detected

Cause:

The servo drive in use does not support encoderless operation.



Remedy:

  • Check the encoder cable connection between the servo drive and the servo motor.

  • Use a servo motor with encoder.


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:

  • Configure the motor ID by setting the parameter p29000.


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:

  • Update the software.

  • Use a correct absolute encoder motor.


F52987
Absolute encoder replaced

Cause:

Incorrect absolute encoder data.



Remedy:

  • Contact the Hotline.


A1009
Control module overtemperature

Cause:

The temperature of the control module (Control Unit) has exceeded the specified limit value.



Remedy:

  • Check the air intake for the Control Unit.

  • Check the Control Unit fan.


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:

  • Remove and check the removable data medium.

  • Then run the data backup again.


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:

  • Save all parameters.


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:

  • Save the parameterization in SINAMICS V-ASSISTANT using the “Copy RAM to ROM” function or on the BOP.

  • This overwrites the incorrect parameter files in the non-volatile memory – and the alarm is withdrawn.


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:

  • Check bus configuration.

  • Check parameters for clock cycle synchronization (ensure To > Tdx).


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:

  • Is the surrounding temperature within the defined limit values?

  • Have the load conditions and the load duty cycle been appropriately dimensioned?

  • Has the cooling failed?


A7012
Motor temperature model 1/3 overtemperature

Cause: The motor temperature model 1/3 identified that the alarm threshold was exceeded.



Remedy:

  • Check the motor load and reduce it if required.

  • Check the motor surrounding temperature.


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:

  • Correct the traversing block.

  • Change software limit switch minus (p2580).


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:

  • Correct the traversing block.

  • Change software limit switch plus (p2581).


A7471
EPOS: Traversing block target position outside the modulo range

Cause: In the traversing block the target position lies outside the modulo range.



Remedy:

  • In the traversing block, correct the target position.

  • Change the modulo range (p29246).


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:

  • Correct the target position.

  • Change software limit switch minus (CI: p2580).


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:

  • Correct the target position.

  • Change software limit switch plus (CI: p2581).


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:

  • Correct the target position.

  • Change software limit switch minus (CI: p2580).


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:

  • Correct the target position.

  • Change software limit switch plus (CI: p2581).


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:

  • Remove the cause of a possible encoder fault.

  • Carry out a POWER ON (power off/on) for all components.


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:

  • Switch on the load supply.

  • Check the line supply if necessary.


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:

  • Closed-loop control is incorrectly parameterized.

  • Fault in the motor or in the power cables.

  • The power cables exceed the maximum permissible length.

  • Motor load too high.

  • Power unit defective.


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.

  • Check the motor circuit configuration (star-delta).

  • Check the motor load.

  • Check the power cable connections.

  • Check the power cables for short-circuit or ground fault.

  • Check the length of the power cables.


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:

  • Carry out a POWER ON (power off/on) for all components.

  • Check that the encoder cables are routed in compliance with EMC.

  • Check the plug connections.

  • Replace the encoder.


A52900
Failure during data copying

Cause:

  • Copying is halted.

  • The SD card was plugged out.

  • The drive is not in the stop state.





Remedy:

  • Re-plug in the SD card.

  • Make sure the drive is in the stop state.


A52901
Braking resistor reaches alarm threshold

Cause: The heat capacity reaches the threshold (p29005) of the braking resistor capacity.



Remedy:

  • Change the external braking resistor.

  • Increase deceleration time.


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:

  • For incremental encoder, when PTO frequency exceeds 120K, drive will output A52932 to remind that exceed limitation.

  • For absolute encoder, when PTO frequency exceeds 280K, drive will output A52932 to remind that exceed limitation.





Remedy: Change PTO ratio.