SIMODRIVE 611U error codes, fault codes and warnings: causes and remedies

Cause

• Communications to the drive have been interrupted.
• Different versions of the ”SimoCom U” start-up and parameterizing tool and the drive.

Cause

No drive firmware on the memory module.

Cause

The computation time of the drive processor is no longer sufficient for the selected functions in the specified cycle times.

Supplementary information: only for siemens-internal error diagnostics

Cause

The watchdog timer on the control module has expired. The cause is a hardware fault in the time basis on the control module.

Supplementary information: only for siemens-internal error diagnostics

Cause

The limits of the internal processor hardware stack or the software stack in the data memory have been violated. The cause is probably a hardware fault on the control module.

Supplementary information: only for siemens-internal error diagnostics

Cause

The processor has detected an illegal command in the program memory.

Supplementary information: only for siemens-internal error diagnostics

Cause

During the continuous check of the checksum in the program/data memory, a difference was identified between the reference and actual checksum. The cause is probably a hardware fault on the control module.

Supplementary information: only for siemens-internal error diagnostics

Cause

An error occurred when loading the firmware from the memory module. Cause: Data transfer error, FEPROM memory cell defective

Supplementary information: only for siemens-internal error diagnostics

Cause

Basic cycle has failed.

Possible causes: EMC faults, hardware fault, control module

Cause

An illegal processor interrupt has occurred. An EMC fault or a hardware fault on the control module could be the reason.

Cause

An illegal processor interrupt has occurred. An EMC fault or a hardware fault on the control module could be the reason.

Cause

An illegal processor interrupt has occurred. An EMC fault or a hardware fault on the control module could be the reason.

Cause

When the current actual value sensing runs up, or in cyclic operation at pulse inhibit, a 0 current is expected. The drive system then identifies that no currents are flowing (excessive deviation to the theoretical center frequency). It is possible that the hardware for the current actual value sensing is defective.

Cause

The motor measuring system has a motor encoder with voltage output which requires a measured circuit evaluation with voltage input, or a resolver with appropriate evaluation. Another measuring circuit evaluation was identified.

Supplementary information: only for siemens-internal error diagnostics

Cause

A fatal communication error was identified, or the drive software is no longer consistent. The cause is erroneous communications or a hardware fault on the control module.

Supplementary information: only for siemens-internal error diagnostics

Cause

Error in the internal data, e.g. errors in the element/block lists (incorrect formats, ...). The drive software is no longer consistant. The cause is propably a hardware fault on the control module.

Supplementary information: only for siemens-internal error diagnostics

Cause

An illegal number of current setpoint filters was entered (> 4) (maximum number = 4).

Cause

An inadmissible number of speed setpoint filters (> 2) was entered (max. number = 2).

Cause

The function for determining the number of axes that physically exist on the power section has calculated an illegal value.

Cause

An error occurred when saving the user data in the FEPROM on the memory module. Cause: Data transfer error, FEPROM memory cell defective

Note: The user data which was last saved, is still available as long as a new data backup was unsuccessful.

Supplementary information: only for siemens-internal error diagnostics

Cause

An error occurred when loading a new firmware release. Cause: Data transfer error, FEPROM memory cell defective

Note: As the previously used firmware was erased when downloading, the drive expects a new firmware download after RESET or POWER ON.

Supplementary information: only for siemens-internal error diagnostics

Cause

An error occurred when loading the user data from the memory module. Cause: Data transfer error, FEPROM memory cell defective

Supplementary information: only for siemens-internal error diagnostics

Cause

Supplementary information

0x100000: More than 1 power section type was identified.

0x200000: No power section type was identified, although it would have been possible.

0x30xxxx: The identified power module differs from the entered PM (P1106). To xxxx: the code of the identified PM is entered here.

0x400000: Different power section codes (P1106) are entered for this 2-axis module.

Cause

The parameterization (P0875) expects an option module which is not available on this control module.

Cause

Supplementary info = 1: An option module is inserted (P0872) or parameterized (P0875), which is not supported by the firmware release of the control module.

Cause

There is an internal software error.

Supplementary information: only for siemens-internal error diagnostics

Cause

The option module does not contain the currently required firmware.

Cause

The BUS coupling has failed.

Cause

The option module type, expected from the parameterization, is different for the two axes of a two-axis module.

Cause

An illegal status of the PROFIBUS controller was recognized.

Cause

The target position specified in this block lies outside the range limited by P0316 (plus software limit switch).

Cause

The target position specified in this block lies outside the range limited by P0315 (minus software limit switch).

Cause

For the SET_O or RESET_O command, an illegal value was entered in P0086:64 (command parameter).

Cause

A jump is programmed to a non-existent block number in this traversing block.

Cause

Illegal data is in P0087:64/P0097 (mode). A data position in P0087:64/P0097 has an inadmissible value.

For the commands SET_O and RESET_O, the CONTINUE EXTERNAL block change enable is not permissible.

For MDI: The configuration of the external block change P0110 is incorrect. The external block change is only permissible with P0110 = 2 or 3. Block change enable only with ”END” or ”CONTINUE EXTERNAL”.

For axis couplings: For COUPLING_IN/COUPLING_OUT via a traversing block (P0410 = 3, 4 or 8), a block change enable with CONTINUE FLYING is not possible.

Cause

For a linear axes, the positioning mode ABS_POS was programmed (only for rotary axes).

Cause

For a linear axes, the positioning mode ABS_NEG was programmed (only for rotary axes).

Cause

There are several traversing blocks with the same block number in the program memory. The block numbers must be unique over all traversing blocks.

Cause

External block change was not requested for a traversing block with block step enable CONTINUE EXTERNAL and P0110 (configuration of external block change) = 0.

Cause

A block number was selected which is not available in the program memory or has been suppressed.

Cause

The step command GOTO may not be programmed for this block number.

Cause

A positive signal edge was simultaneously detected for the input signals ”Activate traversing task” and ”Start referencing” and ”Activate handwheel”. At power-on or POWER-ON RESET, if both input signals have a ”1” signal, then for both signals a 0/1 edge (positive edge) is simultaneously identified.

Cause

A positive signal edge was simultaneously detected for the input signals ”Activate traversing task” and ”Jog 1”, ”Jog 2” and ”Activate handwheel”. At power-on or POWER-ON RESET, if both input signals have a ”1” signal, then for both signals a 0/1 edge (positive edge) is simultaneously identified.

Cause

The traversing block with the highest block number does not have END as block step enable.

Cause

The axis has moved to the traversing range limit in a block with the command ENDLOS_NEG (–200 000 000 MSR).

Cause

The axis has moved to the traversing range limit in a block with the command ENDLOS_POS (200 000 000 MSR).

Cause

The target position specified in this block lies outside the absolute traversing range (–200 000 000 MSR).

Cause

The target position specified in this block lies outside the absolute traversing range (200 000 000 MSR).

Cause

For a block with the ENDLOS_POS command, the axis has actuated the plus software limit switch (P0316) for absolute or relative positioning. The behavior for software limit switch reached, can be set using P0118.0.

Cause

For a block with the ENDLOS_NEG command, the axis has actuated the minus software limit switch (P0315) for absolute or relative positioning. The behavior for software limit switch reached, can be set using P0118.0.

Cause

The input signals ”jog 1”, ”jog 2” or ”activate handwheel” were simultaneously activated.

Cause

The value range limit of the parameter was violated when the dimension system was changed over from inches to millimeters.

Cause

For a linear encoder, the dimension system was set to degrees.

Cause

For the ”start referencing” and ”Jog 1” and ”Jog 2” input signals, a positive edge was simultaneously identified.

Cause

When moving away from the reference cams, the traversing range limit was reached, as the 1/0 edge of the reference cam was not identified.

Cause

The ABS_POS positioning mode is only permitted for a rotary axis with activated module conversion (P0241 = 1).

Cause

The ABS_NEG positioning mode is only permitted for a rotary axis with activated modulo conversion (P0241 = 1).

Cause

The programmed target position (P0081:64/P0091) is outside the selected modulo range (P0242).

Cause

The programmed maximum velocity (P0102) is too high to correctly calculate the modulo offset. The maximum velocity may only be so high, that 90% of the modulo range (P0242) can be traveled through within one interpolation cycle (P1010).

Cause

Possible causes are:

• One of the following enable signals was withdrawn while moving: Terminals 48, 63, 64, 663, 65.x, PROFIBUS or bus enable signals, PC enable from SimoCom U
• Another fault has occurred, which causes the controller or pulse enable to be withdrawn
• The drive is in the power-on inhibit state

Cause

Possible causes are:

• The torque or acceleration capability of the drive is exceeded
• Position measuring system fault
• The position control sense is not correct (P0231)
• Mechanical system blocked
• Excessive traversing velocity or excessive position setpoint differences

Cause

The axis was moved to the minus software limit switch (P0315), jog mode. The fault can also occur if the software limit switches are inactive if the position actual value falls below the limit value of –200 000 000 MSR, that corresponds to 555 revolutions for a rotary axis.

Cause

The axis was moved to the plus software limit switch (P0316), jog mode. The fault can also occur if the software limit switches are inactive if the position actual value exceeds the limit value of 200 000 000 MSR, that corresponds to 555 revolutions for a rotary axis.

Cause

The drive has not yet reached the positioning window (P0321) after the positioning monitoring time (P0320) has expired.

Possible causes:

• Positioning monitoring time (P0320) parameters too low
• Positioning window (P0321) parameters too low
• Position loop gain (P0200) too low
• Position loop gain (P0200) too high (instability/tendency to oscillate)
• Mechanical block

Cause

The drive has left the standstill window (P0326) after the standstill monitoring time (P0325) has expired. Possible causes are:

• Position actual value inversion (P0231) incorrectly set
• Standstill monitoring time (P0325) parameters too low
• Standstill window (P0326) parameters too low
• Position loop gain (P0200) too low
• Position loop gain (P0200) too high (instability/tendency to oscillate)
• Mechanical overload
• Check connecting cable motor/converter (phase missing, exchanged)

Cause

The conversion factor in the position controller between velocity and speed cannot be displayed. This factor depends on the following parameters:

• Spindle pitch (P0236), for linear axes
• Gearbox ratio (P0238:8/P0237:8).

Cause

The conversion factor in the position controller between the following error and the speed setpoint cannot be displayed. This factor depends on the following parameters:

• Spindle pitch (P0236) (for linear axes)
• Gearbox ratio P0238:8/P0237:8
• Position control loop gain P0200:8

Cause

The conversion factor between the motor and load is greater than 2 to the power of 24 or less than 2 to the power of –24.

Cause

For multi-turn absolute value encoders, the ratio between the encoder and load must be selected so that the complete encoder range is an integer multiple of the modulo range. The following condition must be fulfilled: P1021 * P0238:8 / P0237:8 * 360 / P0242 must be integer numbers.

Cause

A 1/0 edge was identified at the ”Minus hardware limit switch” input signal.

Cause

A 1/0 edge was identified at the ”Plus hardware limit switch” input signal.

Cause

When entering an external signal as equivalent zero mark (P0174 = 2), input I0.x must be assigned ”equivalent zero mark” function (Fct. No.:79). if a direct measuring system is used, input I0.B must be assigned the ”equivalent zero mark” function (Fct. No.: 79).

Cause

The block change enable CONTINUE_EXTERNAL for the ENDLESS_POS or ENDLESS_NEG command is only permitted with P0110 = 0 or 1.

Cause

In the active traversing program, MDI was switched-in or, in the active MDI block, MDI was switched-out.

Cause

In a traversing block with the FIXED ENDSTOP command, the fixed endstop was not reached. The fixed endstop lies outside the position programmed in this block. After interrupting the traverse to fixed endstop function, the drive was forced out of the position (support position).

Cause

In the ”Fixed endstop reached” status, the axis has moved outside the defined monitoring window.

Cause

Possible causes are:

• One of the following enable signals was withdrawn while traversing to the fixed endstop: Terminals 48, 63, 64, 663, 65.x, PROFIBUS and bus enable signals, PC enable from SimoCom U
• Another fault has occurred, which causes the controller or pulse enable to be withdrawn

Cause

The velocity, specified in this block lies outside the range (1 000 to 2 000 000 000 c*MSR/min).

Cause

Data error for modulo drive with absolute encoder and any gear factor.

• Data was not able to be saved after power-on.
• Absolute position was not able to be read-out of the encoder.

Supplementary information: only for siemens-internal error diagnostics

Cause

The external position reference value has exceeded the upper traversing range limit.

Supplementary info = 0: Limit exceeded after the coupling factors P0401/P0402 identified, i.e.

P0032 > 200 000 000 MSR.

Supplementary info = 1: Limit exceeded after the coupling factors P0401/P0402 identified, i.e. P0032 * P0402 / P0401 > 200 000 000 MSR.

Cause

The external position reference value has fallen below the lower traversing range limit.

Supplementary info = 0: Limit fallen below after the coupling factors P0401/P0402 identified, i.e.

P0032 < – 200 000 000 MSR.

Supplementary info = 1: Limit fallen below after the coupling factors P0401/P0402 identified, i.e. P0032 * P0402 / P0401 < – 200 000 000 MSR.

Cause

The output of the position reference value, position actual value or position correction value is parameterized via PROFIBUS or the bus interface. However, the value to be output can no longer be represented in 32 bits and was therefore limited to the maximum values 0x7fffffff or 0x80000000. The traversing range which can be displayed is given by Lower limit: – 2147483648 * P896 / P884 Upper limit: + 2147483647 * P896 / P884 The supplementary information explains which process data has violated the lower or upper limit:

Supplementary info process data Violation xx1 Position reference value Xset (No. 50208) Upper limit exceeded xx1 Position reference value Xset (No. 50208) Lower limit fallen below x1x Position actual value Xact (No. 50206) Upper limit exceeded x2x Position actual value Xact (No. 50206) Lower limit fallen below 1xx Position correction value dxKorr (No. 50210) Upper limit exceeded 2xx Position correction value dxKorr (No. 50210) Lower limit fallen below

Cause

After starting the reference point approach, the axis moves through the distance in P0170 (max. distance to the reference cam) without finding the reference cam.

Cause

When the axis moves to the reference cam, and does not come to a standstill at the cam, then this error is signaled, i.e. the reference cam is too short.

Cause

• After the reference cam has been left, the axis has moved through the distance in P0171 (max. distance between the reference cam/zero pulse), without finding a zero pulse.
• For distance-coded measuring system (from SW 8.3 onwards): The maximum permissible distance (clearance) between two reference marks was exceeded.

Cause

Encoderless operation was parameterized (P1006) and the ”Positioning” mode selected.

Cause

The coupling was disconnected while a traversing task was running

Cause

Traversing blocks with absolute position data are not permitted while the axis coupling is activated.

Cause

• No coupling can be established in the actual operating status.
• For P0891=2 or 3, it is not possible to couple using the input signal ”Activate coupling through I0.x” (fast input).

Cause

• The input signal ”Activate coupling” is present. An edge of the input signal is necessary to activate the coupling.
• In the jog mode, while traversing, the input signal ”coupling on” was entered.
• The ”coupling in” input signal was entered in handwheel operation.

Cause

Occurs for couplings with queue functionality. A maximum of 16 positions can be saved in P0425:16.

Cause

Occurs for couplings with queue functionality. Synchronizatin is requested using the KOPPLUNG_ON command and it is identified that the position at which the coupling is switched-in, has already bee passed.

Cause

While the drive was executing a traversing program, the ”Activate coupling” input signal was reset.

Cause

While the drive was executing a traversing program, the ”Active coupling” input signal was set.

Cause

If there is an existing coupling, traversing blocks with external block enable are only permitted if P0110 = 2.

Cause

Not possible to simultaneously couple and traverse to the endstop.

Cause

For the passive referencing, the encoder interface must be switched as input and the ”Positioning” mode must be set.

Cause

While the master drive corrects the zero mark offset, the slave drive must pass over a zero mark.

Supplementary information 0 = Reference cam not found 1 = Reference cam not left 2 = Zero reference pulse not found

Cause

Passive referencing with absolute encoders (e.g. EnDat encoders) is only possible after the encoder has been adjusted.

Cause

The start-up help for passive referencing determines the reference point offset in P0162 in the slave drive. The following prerequisites must be available:

• (permanent) position coupling exists to the master drive
• Master drive must be precisely at its reference point
• Slave drive has passed the zero mark.

Cause

Teach-in only possible for a referenced axis.

Cause

The specified teach-in block is invalid.

Cause

The specified teach-in standard block is invalid.

Cause

The specified teach-in block is not found.

Cause

The specified teach-in standard block is not found.

Cause

For the ”Spindle positioning” function, the positioning mode (P0087) is not valid.

Cause

For the ”Spindle positioning” function, an error has occurred while positioning. Suppl. info Significance 0 The distance between the last two zero marks was not correct. 1 For two revolutions a zero mark was no longer detected, which was in a tolerance bandwidth of P0126.

Cause

Conversion factors for spindle positioning was not able to be intialized

Supplementary info, ones and tens position:

00: Conversion factor, velocity to speed too small

01: Conversion factor, velocity to speed too high

02: Conversion factor, adaptation filter too low (–> increase P0210)

03: Conversion factor, adaptation filter too high (–> reduce P0210)

04: Conversion factor, pre-control balancing filter too low (–> increase P0206)

05: Conversion factor, pre-control balancing filter too high (–> reduce P0206)

06: Conversion factor, sum delay too small

07: Conversion factor, sum delay too large

08: Conversion factor, following error model too small

09: Conversion factor, following error model too large The hundreds position of the supplementary info contains the parmeter set involved.

Cause

Spindle positioning requires the following parameteriation:

P0241 = 1

P0100 = 3

Cause

1. Jogging incremental is not valid in this mode.

2. An attempt was made to move an axis away from a software limit switch using incremental jogging – however the axis is not at the software limit switch, but behind it.

3. An attempt was made while executing one or several traversing blocks (also via an axis coupling) to activate incremental jogging.

Cause

This firmware does not support the spindle positioning function.

Cause

It is not possible to set the internal zero mark, if

1. Input signal ”Spindle positioning on” is set, or

2. Still no zero mark found.

Cause

The maximum search velocity for spindle positioning is greater than the maximum motor speed.

Cause

The zero mark (encoder or equivalent zero mark, e.g. BERO) was not found. Gearbox ratio (mechanical system) was not correctly parameterized using parameter P0237/P0238.

Cause

Spindle positioning is only possible with motor 1.

Cause

Speed pre-control is not permissible with spindle positioning.

Cause

An illegal combination of signals is present at the inputs, at the Profibus control words or at the appropriate bus signals. The detailed cause of the error can be taken from the help text associated with the warning that is entered as supplementary information. This fault can be activated or suppressed using Parameter P338.

Supplementary information: Warning number

Cause

1. The smoothed absolute current (P1254, current monitoring time constant) is greater than 120 % of the permissible power section current (P1107).

2. For an active rotor position identification, the permissible current threshold was exceeded.

3. The P gain of the controller (P1120) has been set too high.

Cause

The encoder signal level is too low, faulted (incorrect shielding), or the cable breakage monitoring function has responded. After separately shutting down the supply voltage at the drive, for SIMODRIVE 611 universal HRS with 1Vpp encoder or SIMODRIVE universalE HRS with 1Vpp encoder, this fault message can be output during the shutdown procedure without any significance for the control.

Cause

1. The motor absolute track (CD track) is monitored for an interrupted conductor. For optical encoders, the absolute track supports the evaluation of the mechanical position within one motor revolution.

2. For absolute encoders with EnDat interface, this fault displays an initialization error.

Note: Additional information on the reason for the fault is included in P1023 (IM diagnostics).

Cause

The difference between the actual rotor position and the new rotor position, which was determined by fine synchronization is greater than 45 degrees electrical. When commissioning a linear motor with rotor position identification (e.g. linear motor, 1FE1 motor), the fine synchronization was not adjusted.

Cause

The measured rotor position fluctuates between 2 encoder zero marks (encoder lines may have been lost).

Note: The encoder monitoring function can be disabled using P1600.8.

Cause

The speed actual value has exceeded the maximum permissible value.

Cause

The encoder signal level is too low, faulted (incorrect shielding), or the cable breakage monitoring function has responded.

Cause

For absolute encoders with EnDat interface, this fault indicates an initialization error.

Note: Additional information on the reason for the fault is included in P1033 (DM diagnostics).

Cause

A fluctuation in the measured values has occurred between 2 encoder zero marks (encoder pulses may have been lost).

Note: The encoder monitoring can be disabled using P1600.14.

Cause

The power section temperature is sensed using a temperature sensor on the heatsink. The drive is immediately shut down 20 seconds after the heatsink temperature alarm in order to prevent the power section being thermally destroyed (regenerative stop).

Cause

For a 2-axis module, one axis is in the n-set mode and one axis in the positioning mode. For the axis in the n-set mode, a position controller clock cycle (of the master) is entered via the clock-cycle synchronous Profibus or the bus interface. This position controller clock cycle differs from the parameterized position controller clock cycle (P1009) of the axis in the positioning mode. The position controller clock cycle of the master is obtained, in the n-set mode, from the DP clock cycle (Tdp) or the clock cycle of the bus interface multiplied by the time grid Tmapc.

Cause

The function ”spindle positioning” requires, for a clock-cycle synchronous PROFIBUS or the bus interface, that the position controller clock cycle of the master matches the parameterized position controller clock cycle (P1009). The position controller clock cycle of the master is obtained from the DP clock cycle (Tdp) multiplied by the time grid Tmapc.

Cause

Supplementary information

0x01: The master sign-of-life has more consecutive failures than permitted. The permissible sign-of-life errors are specified using P0879 bits 2–0 (configuration).

0x02: The Global Control telegram to synchronize the clock cycles has failed in operation for several consecutive DP clock cycles or in several DP clock cycles has violated the time grid specified using the parameterizing telegram (refer to times Tdp and Tpllw). If the complete DP communications permanently fails, at the latest after the response monitoring times specified when configuring the bus, fault 595 is also output.

Cause

The cyclic data transfer between the master and slave was interrupted due to the fact that cyclic frames were missing, or due to the reception of a parameterizing or configuring frame.

Examples:

• Bus connection interrupted
• Master runs up again
• Master has changed into the ’Clear’ state

For a passive axis, fault cannot be acknowledged using ”RESET FAULT MEMORY”.

Cause

Cyclic data transfer between this slave and a slave-to-slave communications publisher was interrupted as cyclic telegrams were missing.

Examples:

• Bus connection interrupted
• Publisher failure
• Master runs up again
• The response monitoring (Watchdog) for this slave was de-activated via the parameterizing telegram (SetPrm) (Diagnostics: P1783:1 bit 3 = 0).

Supplementary info: PROFIBUS address of the publisher

Cause

Supplementary information

0x01: The master sign-of-life (STW2, bits 12–15) has more consecutive failures than permitted. The permissible sign-of-life error is specified using P0879 bit 2–0 (PROFIBUS configuration).

0x02: The Global Control Telegram to synchronize the clock cycles in operation has consecutively failed over several consecutive DP clock cycles, or has violated the time grid, specified by the parameterizing telegram (refer to times Tdp and Tpllw) over several consecutive DP clock cycles. If the complete DP communications continuously fails, in addition, fault 599 is output, at the latest after the watchdog monitoring time specified when the bus was configured.

Cause

Supplementary information

0x01: The expected 1st global control clock cycle display did not occur within the waiting time.

0x02: PLL synchronization unsuccessful

0x03: When synchronizing to the clock cycle, the global control clock cycle had more consecutive failures than are permitted.

0x06: The data frames w. the process data (setpoint direction) were only received after the time (To–125us) in the slave has expired.

Cause

The cyclic data transfer between the master and slave was interrupted due to the fact that cyclic frames were missing, or due to the reception of a parameterizing or configuring frame.

Examples:

• Bus connection interrupted
• Master runs up again
• Master has changed into the ’Clear’ state

For a passive axis, fault cannot be acknowledged using ”RESET FAULT MEMORY”.

Cause

A timing error was identified when reading-out the A/D converter for terminal 56.x/14.x or 24.x/20.x. The read values are probably incorrect/faulty.

Cause

In the IM mode, open-loop torque controlled operation was selected via an input terminal or via PROFIBUS-DP or the bus interface.

Cause

An attempt was made to change over to a motor data set which was not parameterized.

Cause

For an EnDat motor measuring system, it was identified that the serial number does not match that saved, i.e. the encoder has still not run with this drive.

Cause

The speed setpoint requested from the position controller lies above the max. motor speed.

Possible causes:

• Programmed velocity (P0082:64) too high
• Max. acceleration (P0103) or deceleration (P0104) too high
• Axis is overloaded or blocked

Cause

The specified flux setpoint cannot be realized, although maximum current is input.

• Motor data are incorrect
• Motor data and motor connection type (star/delta) do not match
• Motor has stalled because motor data are extremely inaccurate
• Current limit is too low for the motor (0.9 * P1238 * P1103 < P1136)
• Power section is too small

Cause

The entered setpoint cannot be impressed in the motor, although the maximum voltage has been entered. The cause could be that the motor is not connected, or a phase is missing.

Cause

The speed controller is at its limit for an inadmissibly long time (torque or current limit). The permissible time is defined in P1605, the upper speed limit when the monitoring responds, in P1606.

Synchronous motor: In correct operation, the correctly optimized axis drive should never reach its current limit, not even with large speed changes (changing from rapid traverse in the positive direction to rapid traverse in the negative direction).

P1605 = 200 ms

P1606 = 8000 rev/min

Induction motor: Acceleration and braking with the maximum torque/current are usual in operation, only a stalled drive (0 speed) is monitored.

P1605 = 200 ms

P1606 = 30 rev/min

1. At the first commissioning, after the software has been replaced or the software has been upgraded, after the parameters have been entered the ”calculate motor data” or ”calculate controller data” function was not executed. The drive then keeps the default values (for the values to be calculated this is zero) which can, under certain circumstances, result in this fault (P1605 and P1606 should be adapted to the mechanical and dynamic capabilities of the axis).

2. An undesirable input of a high torque reduction via the analog inputs or via PROFIBUS and the bus interface. For PROFIBUS and the bus interface, this effect especially occurs when changing from the positioning mode to the speed setpoint input mode (check as to whether a torque reduction is entered. Diagnostics using P1717, 0%: No torque, 100%: Full torque).

Cause

The speed actual value exceeds the encoder frequency.

• Incorrect encoder
• P1005 does not correspond to the no. of encoder pulses
• Encoder defective
• Motor cable defective or not properly attached
• Shield on motor encoder cable is not connected
• Defective control module

Cause

if P1075=1 (technique based on saturation) A rotor position could not be determined from the measurement signals (motor current), as no significant saturation effects occurred. Also refer to parameter P1734 for detailed diagnostics. if P1075=3 (motion-based technique)

1. Current increase too low.

2. Maximum permissible duration exceeded.

3. No clear rotor position found.

Cause

During the rotor position identification (motor current measurement), the motor rotated more than the value entered in P1020. The rotation could be caused by having powered on with the motor already rotating, or caused by the identification routine itself.

Cause

1. Current was >= 1.2 * 1.05 * P1107 while rotor position identification was active

2. Current was >= P1104 while rotor position identification was active

Cause

The motor temperature (sensed via the temperature sensor KTY 84 and fed to the module via the motor encoder cable) has exceeded the temperature limit in P1607.

Cause

The motor temperature (sensed via the temperature sensor KTY 84 and fed to the module via the motor encoder cable) has exceeded the temperature in P1602 for a time longer than in P1603.

Cause

The speed actual value of the direct measuring system exceeds the permissible encoder limiting frequency.

• Incorrect encoder
• P1007 does not coincide with the encoder pulse number
• Encoder defective
• Defective encoder cable or not correctly retained
• Encoder cable shield is not connected
• Defective control module

Cause

The DC link voltage has exceeded the permissible lower limit P1162.

Cause

The DC link voltage has exceeded the permissible upper limit P1163.

Cause

A motor code was entered in P1102 for which no data is available.

Cause

A power section code was entered in P1106, for which no data is available.

Cause

An encoder code was entered in P1006 or P1036, for which there is no data. The direct measuring system (P0250/P0879.12) is activated, although an encoder was not specified in P1036.

Cause

An error occurred at the first start-up with ”calculate controller data”. Under fault conditions, the parameters for the current controller, flux controller and speed controller could not be optimally assigned.

Cause

An illegal value was entered in P1000.

Cause

An illegal value was entered in P1001.

Cause

The monitoring function identified a position controller cycle (P1009) outside the permissible limits.

Cause

The monitoring has identified an interpolation cycle (P1010) outside the permissible limits, or an illegal ratio between the interpolation cycle and the position controller cycle (P1009).

Cause

On a 2-axis module, the current controller cycle is different for both axes.

Cause

On a 2-axis module, the speed controller cycle is different for both axes.

Cause

For a 2-axis module, the position controller clock cycle (P1009) or the interpolation clock cycle (P1010) is different for the two axes.

Cause

The ratio between the rated torque and rated current (torque constant [Nm/A]) in P1113 is incorrect (less than/equal to zero) or the ratio P1113/P1112 is greater than 70.

Cause

When the star-delta changeover is activated using P1013, the motor is not parameterized for delta operation (motor 2).

Cause

Due to the high maximum motor speed in P1401 and the speed controller cycle in P1001, high partial speeds can occur which can result in a format overflow.

Cause

As a result of the high spindle speed and the interpolation clock cycle (P1010), the modulo value can no longer be correctly taken into account. The alarm is initiated, if jerky equalization motion occurs – e.g. due to incorrect parameter values.

Cause

For the selected setting of P1466, the induced voltage is too low in the lower speed range in order to be able to reliably guarantee sensorless operation. The induced voltage must be at least 40 Volt (phase-to-phase, RMS) at the particular speed.

Cause

On a 2-axis module, the gating unit configuration (P1003) is different for the two gating units.

Cause

Synchronous motors:

• The pole pair number in P1112 is zero or negative.
• Encoder with CD track (P1027.6 = 0): The pole pair number in P1112 is greater than 6.
• Encoder without CD track or with Hall sensors (P1027.6 = 1): The motor pole pair number is dependent on the encoder pulse number (max. 4096 for P1005 >= 32768). Induction motors:
• An invalid pole pair number was determined from P1134 and P1400. Motor with resolver:
• The maximum motor pole pair number for the modules 6SN1118–*NK01–0AA0 or 6SN1118–*NJ01–0AA0 is 64, otherwise 4 or 6.

Cause

The encoder pulse number of the motor measuring system (P1005) is set to zero.

Cause

The voltage constant of the motor in P1114 is set to zero.

Cause

The power module has not been released for synchronous motors.

Cause

The adaptation factor between the setpoint torque and the torque generating current (Iq) in the speed controller is too high.

Cause

The motor stall current (P1118) is less than or equal to zero.

Cause

The rated motor output (P1130) of the motor is less than or equal to zero.

Cause

The rated motor speed (P1400) of the motor is less than or equal to zero.

Cause

If the equalization controller is parameterized with P1490 = 1 –> then P0612 must be parameterized with the value 3

Cause

If the equalization controller is parameterized with P1490 = 2 –> two active axes must be available on the module.

Cause

In V/f operation, only drive converter frequencies of 4 or 8 kHz are permissible.

Cause

”

Cause

Motor changeover (P1013) may only be activated in the closed-loop speed controlled mode (P0700 = 1).

Cause

The maximum speed which can be achieved with speed feedback cannot be measured using the module.

Cause

P gain, speed controller for the lower speed range (P1407) and the upper speed range (1408) were selected to be too high.

Cause

A current was parameterized in P1019 (current, rotor position identification) which is less than the minimum value permissible for the motor.

Cause

The hysteresis of the speed for the current setpoint smoothing (P1246) may not be greater than the threshold speed of the hysteresis (P1245), as otherwise a ”negative” lower speed would be obtained.

Cause

The frame number set in P0922 is illegal or impermissible for the operating mode currently selected via P0700.

Cause

The selected setpoint source in P0891 is invalid. 1 Internal coupling not possible for POSMO or single-axis module 2 Internal coupling not possible for drive A 3 Coupling via PROFIBUS-DP or the bus interface selected, but the matching option module is not inserted

Cause

A linear motor was selected, and no linear scale configured (P1027.4 = 0). A rotating motor was selected and a linear scale configured (P1027.4 = 1). A resolver has been selected the pole pair number (P1018) of which is illegal. A pole pair number =1 or the pole pair number of the motor (P1112) is admissible. The maximum speed (P1146) cannot be measured with the resolver. The required resolution (1011[2] = 1 or 1030[2] = 1, resolver evaluation) cannot be set using this module.

For this setting, either 6SN1118–*NK01–0AA0 or 6SN1118–*NJ01–0AA0 is required.

Cause

For linear motors, the equivalent (internal) pole pair number and (internal) encoder pulse number are calculated from the pole pair width and grid division. In this case, the encoder pulse number must be an integer multiple of one or x pole pair widths. This error message is output if the pole pair width/grid division * x (up to x=4096) is not an integer multiple or if an internal encoder pulse number which was calculated is too high. A result with a tolerance of +/– 0.001 absolute is interpreted to be an integer.

Cause

The following settings are permitted (Order No.[MLFB] 6SN1118–....): Incremental measuring systems (7 bit) with sin/cos 1 Vpp without EnDat interface (..*NH00–0AA*, ..*NH10–0AA*) : 0 Incremental measuring systems (7 bits) with sin/cos 1 Vpp with EnDat interface (..*NH00–0AA*, ..*NH10–0AA*) : 0,1,2,3 Incremental measuring systems (11 bit) with sin/cos 1 Vpp (..*NH01–0AA*, ..*NH11–0AA*) : 0,1,2,3,4 resolver (12 bit) (..*NK00–0AA0 or ..*NJ00–0AA0) : 0,1,2,3 Resolver (12 bit) (..*NK01–0AA0 or ..*NJ01–0AA0) with 12-bit resolution (1011[2] = 0 or 1030[2] = 0) : 0,1,2,3,4,5 Resolver (14 bit) (..*NK01–0AA0 or ..*NJ01–0AA0) with 14-bit resolution (1011[2] = 1 or 1030[2] = 1) : –2,–1,0,1,2,3

Cause

For incremental measuring systems with sin/cos 1 Vpp without EnDat interface and for linear measuring systems with sin/cos 1 Vpp with EnDat interface, a zero pulse offset cannot be set via P0893.

Cause

When selecting 3 in P0890, from drive A or B (setpoint at terminal A and actual value at terminal B), it was identified, that terminal A or B were already being used by another drive. Thus, this configuration is not possible.

Cause

An actual value coupling is switched in (P0891 = 1) for drive B. Simultaneously, for the same drive, terminal A or B is parameterized as position setpoint input (P0890 = 2 or 3).

Cause

The bandstop frequency of a speed setpoint filter is greater than the Shannon sampling frequency from the sampling theorem.

Cause

The natural frequency of a speed setpoint filter is greater than the Shannon sampling frequency from the sampling theorem.

Cause

The numerator bandwidth of a current or speed setpoint filter is greater than twice the bandstop frequency. This alarm is only generated for the general bandstop, if the following is valid: Speed setpoint filter 1: P1516 > 2 * P1514 or P1520 <> 100.0 Speed setpoint filter 2: P1519 > 0.0 or P1521 <> 100.0 Current setpoint filter 1: P1212 > 0.0 Current setpoint filter 2: P1215 > 0.0 Current setpoint filter 3: P1218 > 0.0 Current setpoint filter 4: P1221 > 0.0

Cause

The denominator bandwidth of a current or speed setpoint filter is greater than twice the natural frequency. This alarm is only generated for the general bandstop, if the following is valid: Speed setpoint filter 1: P1516 > 2 * P1514 or P1520 <> 100.0 Speed setpoint filter 2: P1519 > 0.0 or P1521 <> 100.0 Current setpoint filter 1: P1212 > 0.0 Current setpoint filter 2: P1215 > 0.0 Current setpoint filter 3: P1218 > 0.0 Current setpoint filter 4: P1221 > 0.0

Cause

The calculated bandstop filter coefficients cannot be represented in the internal format.

Cause

In induction motor operation (selected by P1465 < P1146), drive converter frequencies of 4 or 8 kHz are permissible.

Cause

The P gain of the speed controller (P1451) is too high.

Cause

For this particular hardware version, it is not permissible to activate the analog input.

Cause

For mixed operation (with/without encoder) P1465 > 0, only closed-loop controlled induction motor operation is permissible (P1466 <= P1465).

Cause

Incorrect parameterization of the SSI absolute value encoder.

Supplementary info = 0x1, 0x11 (indirect, direct measuring system): ––> The single-turn resolution cannot be 0.

Supplementary info = 0x2, 0x12 (indirect, direct measuring system): ––> The number of parameterized bits is greater than the telegram length.

Supplementary info = 0x3, 0x13 (indirect, direct measuring system): ––> For linear encoders, it is not possible to have multi-turn resolution.

Cause

For an old basic module, which does not support TTL encoders, a TTL encoder was selected as motor measuring system.

Cause

A current was parameterized in P1019, which is greater than the current which is permissible for the motor and the power section used.

Cause

When selecting the rotor position identification (P1019), drive converter frequencies (P1100) of 4 or 8 kHz are permissible.

Cause

The motor moment of inertia (P1117) is incorrect (less than/equal to zero).

Cause

The motor no-load current (P1136) has been parameterized greater than the rated motor current (P1103).

Cause

The motor no-load current (P1136) has been set to higher values than the rated power section current. before SW 2.4 the following is valid: Rated power section current = P1111 from SW 2.4 the following is valid: Rated power section current = P1111 * P1099

Cause

The stator leakage reactance (P1139) or the rotor leakage reactance (P1140) or the magnetizing reactance (P1141) of the motor is incorrect (less than/equal to zero).

Cause

The rotor resistance (P1138, cold) of the motor is zero or there was a format overflow for an internal conversion.

Cause

Error in no-load voltage P1135:

• P1135 <= 0 or
• P1135 > P1132 or
• P1135 * P1142 / P1400 + Vser.react. > 450V. With Vser.react. = 0.181 * P1136 * P1142 * P1119

Cause

The no-load current (P1136) of the motor (ARM) is incorrect (less than/ equal to zero).

Cause

The threshold speed for field weakening for induction motors (P1142) is incorrect (less than/equal to zero).

Cause

The feedforward control gain for induction motors cannot be represented in the internal numerical format if the motor moment of inertia and rated motor torque were unfavorably selected.

Cause

An actual-value link has been activated (P0891 = 1) for drive A. The hardware does not permit this setting.

Cause

The setpoint transfer from SimoCom U to the drive was interrupted, i.e. there is no longer an online connection. The Master Control was returned to the drive. Communication between the two communication partners was faulty. When traversing the drive via SimoCom U, other functions were executed on the PG/PC (e.g. open online help, open file), so that the drive can only be irregularly supplied from SimoCom U.

Cause

The selected operating mode (P0700) is not permitted for this module or axis.

Supplementary info = 0x1: Operating mode ==0 selected on the 1st axis

Supplementary info = 0x2: ”Positioing” operating mode selected for the Nset control module

Supplementary info = 0x3: Operating mode is not possible with this firmware release

Supplementary info = ”External position reference value” operating mode no longer possible.

Cause

The TTL encoder interface may only be parameterized as follows for this particular hardware version: Drive A: P0890 = 0 or 4, 0: Interface inactive, 4: TTL encoder input Drive B: P0890 = 0

Cause

It is not permitted to parameterize the direct measuring system.

Supplementary info = 0x1: A direct measuring system cannot be used using this board.

Supplementary info = 0x2: The direct measuring system cannot be simultaneously operated with drive B.

Supplementary info = 0x3: The direct measuring system is active and drive A is set for encoderless operation (P1027 bit 5 = 1).

Cause

The input signal waveform for the angular encoder interface must be set the same for the drives.

Cause

This angular encoder interface setting is not permitted for drive B.

Cause

The position reference value normalization for the angular encoder interface is not permissible.

Supplementary info = 1 ––> Condition P0401 * P0895 < 8388608 violated = 2 ––> Condition P0402 * P0896 < 8388608 violated

Cause

The speed was too high during the center frequency measurement (current calibration). The center frequency is measured automatically at run-up, or when the pulses are inhibited.

Cause

The measured-value memory was active during power-up.

Cause

Parameters were re-calculated. Parameters must be saved and the module run up again after this new calculation.

Cause

A 1/0 edge was identified at the ”Minus hardware limit switch” input signal.

Cause

A 1/0 edge was identified at the ”Plus hardware limit switch” input signal.

Cause

The drive was not stationary as the zero pulse offset was programmed on the angular encoder interface. Low speeds are not critical, but the inaccuracy of the zero pulse position increases in proportion to speed.

Cause

When starting a traversing block, the controller enable has not been set, or the controller enable is missing during a traversing program when re-starting the axis from standstill. Controller enable missing, i.e. one of the following signals missing:

• PROFIBUS control signals (STW1.0: ON/OFF 1 (signal edge), STW1.1: OC/OFF2, STW1.2: OC/OFF 3, STW1.3: Enable inverter/pulse inhibit) and the appropriate signals of the bus interface
• PC enable (SimoCom U)
• Terminal 64
• Terminal 65.x

Cause

When starting a traversing block, the pulse enable is not set, or the pulse enable is missing during a traversing program when re-starting the axis from standstill. Pulse enable missing, i.e. one of the following signals missing:

• PROFIBUS control signals (STW1.1: OC/OFF 2, STW1.3: Enable inverter/pulse inhibit) or the appropriate signals of the bus interface
• Terminal 48 (NE module)
• Terminal NS1/NS2 (NE module)
• Terminal 63 (NE module)
• Terminal 663 (control module)

Cause

When starting a traversing block, the ”operating condition/reject traversing task” input signal is not set.

Cause

When starting a traversing block the ”operating condition/intermediate stop” input signal is not set.

Cause

When starting a traversing block, a reference point is not set.

Cause

When starting a traversing block or when starting referencing, the ”parking axis” function is selected.

Cause

The motor temperature is sensed via a temperature sensor (KTY84) and evaluated on the drive side. This alarm is output if the motor temperature reaches the alarm threshold motor overtemperature (P1602).

Cause

The heatsink temperature of the power section is sensed using a thermosensor on the main heatsink. If the overtemperature condition remains, then the drive shuts down after approx. 20 s.

Cause

At run-up, the speed with an existing resolver evaluation was extremely high. It is possible that this was not the actual speed, and that the resolver was not connected to the measuring circuit input.

Cause

The power module is being operated too long above the permissible load limit.

Cause

The bus interface is still not in the data exchange state or data exchange was interrupted.

Causes:

• The master has not yet run up, or has not yet established a connection to the slave.
• The bus addresses differ in the master configuring and slave parameterization.
• The bus connection has been physically interrupted.
• The master is still in the clear condition.
• An illegal parameterization or configuration was received.
• A BUS address was assigned several times.

Cause

The bus interface is in the data exchange state and was selected using the parameterizing telegram of the clock-cycle synchronous operation. It was not possible to synchronize to the clock cycle specified by the master and to the master sign of life.

Causes:

• The master does not send an equidistant global control frame although clock synchronism has been selected via the bus configuration.
• The master uses another equidistant DP clock cycle than was transferred to the slave in the parameterizing telegram.
• The master does not increment its sign-of-life in the configured time grid Tmapc.

Cause

An illegal parameterizing frame was received via PROFIBUS. Cyclic data transfer cannot start. Reasons: 8 = The parameterizing telegram has an illegal length 9 = The length data in the equidistant block is illegal 10 = A block header has an unknown ID. 11 = The basis time Tbasedp is not permissible (not equal to 125 µs). 12 = The DP clock cycle Tdp is not permissible (less than 1ms or greater than 32ms). 13 = The time Tmapc is less than 1*Tdp or greater than 14*Tdp. 14 = The base time Tbaseio is not permissible (not equal to 125 µs). 15 = Time Ti is greater than the DP clock cycle (Tdp). 16 = Time To is greater than the DP clock cycle (Tdp). 17 = For active Data Exchange, a new parameterization was received with different contents. 18 = Clock cycle synchronous operation was selected without a suitable option module having been activated (refer to P0875). 19 = IsoM_Req (state 3, bit 4) is requested in the DPV1 header without there being an isochron block (ID 0x04). 20 = Fail_Safe (state 1, bit 6), IsoM_Req (state 3, bit 4) or Prm_Structure (state 3, bit3) missing in the DPV1 header although an isochron block (ID 0x04) is available. 21 = The time Tdx is greater than (To – 125us) or greater than (Tdp – 250 µs). 22 = The time Tpllw is greater than 1us. 23 = Slave-to-slave communication access target address and length do not conform to word boundary. 24 = Maximum number (3 external + 1 internal) of slave-to-slave communication links has been exceeded. 25 = Maximum number (8) of accesses per link has been exceeded. 26 = Unknown version ID in the slave-to-slave communications block. 27 = The maximum overall length of the filter table has been exceeded. 31 = The permitted maximum length of the parameterizing telegram for the option module has been exceeded. 32 = The option module firmware does not support slave-to-slave communications

Cause

An illegal configuration frame was received via PROFIBUS. Cyclic data transfer cannot start. Reasons: 1 = In the master, more axes are configured than are physically present in the power module. 2 = The number of the axes configured in the master is not equal to the number axes where the PROFIBUS DP option module is switched active via P0875. Note: Communications with axis B are not automatically de-activated even when switching axis B into a passive state. 3 = Configuration incomplete (too short) for one of the PPL types (only for vor P875 = 2). 4 = No PPO type detected (only for P875 = 2). 5 = Length calculation different between firmware and option module. 6 = For active data exchange, a new configuration was received with different length. 7 = Configuration contained unknown S7 ID. 19 = More PZD’s have been configured than the maximum permissible. 20 = The configurtion contains an unknown special character (only axis separators are permitted). 22 = Target offset of slave-to-slave communications access exceeds the maximum number of PZDs 28 = Number of slave-to-slave communication IDs differs from the number of accesses in the parameterizing telegram. 29 = Setpoint PZDs are not uniformly supplied by the master or slave (drive) publisher. 30 = The permitted maximum length of the configuration telegram for the option module has been exceeded.

Cause

The PROFIBUS is not in a data transfer status (data exchange) or data transfer was interrupted.

Causes:

• The master has not yet run up, or has not yet established a connection to the slave.
• The bus addresses differ in the master configuring and slave parameterization.
• The bus connection has been physically interrupted.
• The master is still in the clear condition.
• An illegal parameterization or configuration was received.
• A PROFIBUS address was assigned several times.

Cause

The PROFIBUS is in a data transfer status (data exchange) and has been selected via the parameterizing frame of synchronous operation. It could not yet be synchronized to the clock preset by the master resp. to the master sign-of-life.

Causes:

• The master does not send an equidistant global control frame although clock synchronism has been selected via the bus configuration.
• The master uses another equidistant DP clock cycle than was transferred to the slave in the parameterizing telegram.
• The master increments its sign-of-life (STW2 Bits 12–15) not in the configured time frame Tmapc.

Cause

Cyclic data transfer between this slave and a slave-to-slave communications publisher was still not started or was interrupted.

Examples:

• Bus connection interrupted
• Publisher failure
• Master runs up again
• The response monitoring (Watchdog) for this slave was de-activated via the parameterizing telegram (SetPrm) (Diagnostics: P1783:1 bit 3 = 0).

Supplementary info: PROFIBUS address of the publisher

Cause

Teach-in was requested during a running traversing program.

Cause

The traversing block as ”teach in block” is relative instead of absolute.

Cause

The traversing block as ”teach in standard set”, is relative instead of absolute.

Cause

The search velocity for spindle positioning is too high for the selected maximum deceleration.

Cause

Jogging is not possible while a coupling is closed.

Cause

For a block with the ENDLOS_POS command, the axis has actuated the plus software limit switch (P0316) for absolute or relative positioning. The behavior for software limit switch reached, can be set using P0118.0.

Cause

For a block with the ENDLOS_NEG command, the axis has actuated the minus software limit switch (P0315) for absolute or relative positioning The behavior for software limit switch reached, can be set using P0118.0.

Cause

The upper adaption speed (P1412) was parameterized with a lower value than the lower adaption speed (P1411).

Cause

The signal number for the analog output is not permissible. An analog value can be output for diagnostic, service and optimization tasks Term. 75.x/15, 16.x/15, DAC1, DAC2

Cause

For the current controller adaption, the upper current limit (P1181) was parameterized with a lower value than the lower current limit (P1180). Adaption is de-activated when the parameterizing error is output.

Cause

The sum of the values in P1631 + P1632 is greater than the value in P1633.

Cause

The input value for the threshold voltage (P1631) is greater than the value in P1630.

Cause

The reference point coordinate is internally limited to the modulo range.

Cause

When calculating the jerk time T from the acceleration a and the jerk r, the result was an excessively high jerk time, so that the time is limited internally. The following is valid: T = a/r, where a: Acceleration (higher value from P0103 and P0104) r: Jerk (P0107)

Cause

In induction motor operation (selected by P1465 < P1146), drive converter frequencies of 4 or 8 kHz are permissible.

Cause

PARAMETERIZING ERROR: P gain, equalization controller does not fit into the format.

Cause

For the axes of a drive module, an unequal fixed voltage (P1161) has been set. As a fixed voltage <> 0 replaces the DC link voltage measured value, but the DC link voltage is only measured once for all drives of a drive module, the fixed voltage on all module axes must be equal, before it is accepted.

Cause

The function number, used as input terminal or distributed input (P0888) may not be used in the actual mode.

Cause

The function number, used as output, may not be used in the actual operating mode.

Cause

When entering an external signal as equivalent zero mark (P0174 = 2), input I0.x must be assigned ”equivalent zero mark” function (Fct. No.:79). if a direct measuring system is used, input I0.B must be assigned the ”equivalent zero mark” function (Fct. No.: 79).

Cause

P0205:8 may not be greater than two position controller clock cycles. Higher values are internally limited.

Cause

An undefined or illegal signal number in the current operating mode (P0700) was identified for the process data software. P0915:1 is not equal to 50001 (STW1). The process data for encoder 1 has been configured although encoderless operation is activated (P1011.5). The process data for encoder 2 were configured although the direct measuring system is not activated (P0879.12).

Cause

For signals with double words (length = 32 bits), the corresponding signal identifier must be configured twice for adjacent process data. The following subparameter must therefore also be parameterized with the same signal number.

Cause

An undefined or illegal signal number in the current operating mode (P0700) was identified for the process data software. P0916:1 is not equal to 50002 (ZSW1). The process data for encoder 1 has been configured although encoderless operation is activated (P1011.5). The process data for encoder 2 were configured although the direct measuring system is not activated (P0879.12).

Cause

For signals with double words (length = 32 bits), the corresponding signal identifier must be configured twice for adjacent process data. The following subparameter must therefore also be parameterized with the same signal number.

Cause

P1261 greater than 100.0 % is not permissible for permanent-magnet synchronous motors with field weakening (PE spindle, P1015 = 1). It is internally limited to 100.0 %.

Cause

The parameterized pre-tensioning torque (P1493) is greater than 16x the standstill torque (SRM), rated motor torque (ARM) and standstill force (SLM) of the motor.

Note: refer to the index entry ”Limits”

Cause

The axis has reached the fixed endstop, but was not able to establish the programmed clamping torque.

Cause

The acceleratino override or the deceleration override is not in the range from 1% to 100%. if the value > 100%, then it is limited to 100%. If the value < 1%, then limited to 1%. The traversing block is not interrupted.

Cause

With the actual master drive velocity, this coupling axis will probably reach or pass the PLUS software limit switch. This warning is output if the coupled axis has fallen below 200% of the braking travel up to the PLUS software limit switch.

Cause

With the actual master drive velocity, this coupling axis will probably reach or pass the MINUS software limit switch. This warning is output if the coupled axis has fallen below 200% of the braking travel up to the MINUS software limit switch.

Cause

The terminal function 73 ”Coupling on I0” is only effective at terminal I0.x.

Cause

The input terminals on the optional TERMINAL module can only be used by one drive.

Cause

Only one drive can use the output terminals on the optional TERMINAL module.