Lenze i550 cabnet Drive

Lenze i550 cabnet Drive Fault Codes:

Fault Code and MeaningCause and Remedy
8784 0x2250

CiA: Continuous over current (internal)
Cause:

  • Continuous overcurrent on the inverter/motor side.

  • Overcurrent at the brake chopper (brake transistor).

  • DC bus relay has not been closed due to a malfunction.





Remedy:

  • Check motor and wiring for short circuits.

  • Check brake resistor and wiring.

  • Check motor switching.

  • Check settings of the motor data.
8992 0x2320

Short circuit or earth leakage at the motor end
Cause:

  • Short circuit/earth fault of motor cable.

  • Capacitive charging current of the motor cable too high.





Remedy:

  • Check motor cable.

  • Check length of the motor cable.

  • Use shorter or lower-capacitance motor cable.
9024 0x2340

Short circuit at the motor end
Cause:

Short circuit of motor cable.



Remedy:

  • Check motor cable for short circuit.
9040 0x2350

CiA: i²xt overload (thermal state)
Cause:

Motor thermally overloaded, e. g. by an impermissible continuous current or by frequent or too long acceleration processes.



Remedy:

  • Check drive sizing.

  • Check machine/driven mechanics for excessive load.

  • Check settings of the motor data.

  • Reduce values for slip compensation and oscillation damping.
9090 0x2382

Fault – Device utilization (ixt) too high
Cause:

Device utilisation (ixt) too high by frequent and too long acceleration processes.



Remedy:

  • Check drive sizing.

  • Reduce the maximum current of the inverter.

  • In case of high mass inertias, reduce maximum current of the inverter to 150 %.
9091 0x2383

Warning – Device utilization (ixt) too high
Cause:

Device utilisation (ixt) too high by frequent and too long acceleration processes.



Remedy:

  • Check drive dimensioning.
9095 0x2387

Clamp responded too often
Cause:

Maximum current of the axis has been reached too often in succession.



Remedy:

  • Select a flatter speed ramp.

  • Reduce the load.

  • Set Imax controller more dynamically.
9096 0x2388

SL-PSM stall detection active
Cause:

Overload of the motor with sensorless control for synchronous motors (SL-PSM).



Remedy:

  • Reduce load at the axis.

  • Check settings of the SL-PSM parameters.
9098 0x238A

Maximum current reached
Cause:

The actual current is equal to or higher than the max. current.



Remedy:

  • Reduce the load on the motor or change the settings for the maximum current.
12576 0x3120

Mains phase fault
Cause:

Mains phase failure.



Remedy:

  • Check wiring of the mains connection.

  • Check fuses.
12672 0x3180

UPS operation active
Cause:

Operation on uninterrupted 1x230V current supply (UPS) has been activated: Only a reduced output current is provided.



Remedy:

  • Switch back to operation with regular mains voltage.
12816 0x3210

Fault – DC bus overvoltage
Cause:

DC-bus voltage has exceeded the error threshold for overvoltage due to a too high braking energy or a too high mains voltage.



Remedy:

  • Reduce dynamic performance of the load profile.

  • Check mains voltage.

  • Check settings for brake energy management.

  • Connect brake resistor to the power unit and activate the integrated brake chopper.
12817 0x3211

DC bus overvoltage warning
Cause:

DC-bus voltage has exceeded the warning threshold for overvoltage.



Remedy:

  • Reduce dynamic performance of the load profile.

  • Check mains voltage.

  • Check settings for brake energy management.

  • Connect brake resistor to the power unit and activate the integrated brake chopper.
12832 0x3220

Fault – DC bus undervoltage
Cause:

DC-bus voltage has fallen below the error threshold for undervoltage.



Remedy:

  • Check mains voltage.

  • Check DC-bus voltage.

  • Check mains settings.

  • Check fuses.
12833 0x3221

DC bus undervoltage warning
Cause:

DC-bus voltage has fallen below the warning threshold for undervoltage.



Remedy:

  • Check mains voltage.

  • Check DC-bus voltage.

  • Check mains settings.

  • Check fuses.
12834 0x3222

DC-bus voltage too low for power up
Cause:

The input voltage is too low to switch on the inverter.



Remedy:

  • Check mains voltage.

  • Check mains settings.

  • Check fuses.
16912 0x4210

Fault – Power unit overtemperature
Cause:

  • The heatsink temperature of the power unit has exceeded the fixed error threshold (100 °C).

  • Ambient temperature too high.

  • Fan or ventilation slots are polluted.

  • Fan is defective.





Remedy:

  • Check mains voltage.

  • Provide for a sufficient cooling of the device.

  • Clean fan and ventilation slots. If required, replace fan.

  • Reduce switching frequency.
17024 0x4280

Fault – Heat sink temperature sensor
Cause:

Sensor for the temperature monitoring of the power unit is defective.



Remedy:

  • Hardware error: it is necessary to contact the manufacturer, since the device must be replaced.
17025 0x4281

Heat sink fan warning
Cause:

Warning of the heatsink fan.



Remedy:

  • Clean fan and ventilation slots. If required, replace fan.
17029 0x4285

PU overtemperature warning
Cause:

  • The heatsink temperature has exceeded the warning threshold.

  • Ambient temperature too high.

  • Fan or ventilation slots are polluted.

  • Fan is defective.





Remedy:

  • Provide for a sufficient cooling of the device.

  • Clean fan and ventilation slots.

  • If required, replace fan.
17168 0x4310

Motor overtemperature
Cause:

  • The motor temperature sensor measures a too high motor temperature.

  • Motor too hot by impermissibly high currents.

  • Motor too hot by frequent and too long acceleration processes.





Remedy:

  • Check drive dimensioning.

  • Check motor temperature sensor and wiring.
20754 0x5112

External supply voltage critical
Cause:

External supply voltage failed or too low.



Remedy:

  • Check optional external 24V voltage supply (terminal X3/24E), if connected.

  • Check mains voltage.
20864 0x5180

Overload 24 V supply
Cause:

Output current at the 24V output or at the digital outputs too high.



Remedy:

  • Check 24V output and digital outputs for earth fault or overload.
21376 0x5380

OEM hardware incompatible
Cause:

The control unit (OEM hardware) is not compatible with the power unit (OEM hardware).



Remedy:

  • Use compatible hardware.

  • Contact the OEM.
24970 0x618A

Warning – Internal fan
Cause:

Warning of the internal fan.



Remedy:

  • Check/replace internal fan.
25216 0x6280

Trigger/functions connected incorrectly
Cause:

  • The assignment directives have not been observed.

  • Flexible I/O configuration active but Enable/Run not connected correctly.

  • Use of incompatible Start/Run functions (CW/CCW) simultaneously.





Remedy:

  • Check and correct the assignment of the triggers to the functions.
25217 0x6281

User-defined fault 1
Cause:

Flexible I/O configuration: the “Activate fault 1” function was activated via the trigger selected.



Remedy:

  • Eliminate error cause and then reset error.
25218 0x6282

User-defined fault 2
Cause:

Flexible I/O configuration: the “Activate fault 2” function was activated via the trigger selected.



Remedy:

  • Eliminate error cause and then reset error.
25232 0x6290

Warning invert rotation
Cause:

  • Negative setpoint selection with an active limitation of rotation.

  • The “Reverse rotational direction” function was requested with an active limitation of rotation.





Remedy:

  • Check setpoint selection and trigger.

  • Check setting in parameters.
25233 0x6291

Maximum allowed troubles exceeded
Cause:

The number of permitted restart attempts after a fault was exceeded. The fault occurred too frequently and could not be reset.



Remedy:

  • Check and eliminate the fault.
25248 0x62A0

User-defined fault (LECOM)
Cause:

The “Activate fault” function was triggered via bit 10 of the LECOM control word.



Remedy:

  • Eliminate error cause and then reset error.
25249 0x62A1

Network: user fault 1
Cause:

The “Activate fault 1” function was triggered via the NetWordIN1 data word.



Remedy:

  • Eliminate error cause and then reset error.
25250 0x62A2

Network: user fault 2
Cause:

The “Activate fault 2” function was triggered via the NetWordIN1 data word.



Remedy:

  • Eliminate error cause and then reset error.
25265 0x62B1

NetWordIN1 configuration incorrect
Cause:

Two bits of the NetWordIN1 data word were assigned to the same function.



Remedy:

  • Check and correct configuration of the NetWordIN1 data word.
25266 0x62B2

Changed device ID not yet active
Cause:

The device ID of the device was changed manually.



Remedy:

  • Execute device command “Save user data”.

  • Switch inverter off and on again.
25267 0x62B3

Default settings not yet active
Cause:

The “Back-to-Box” system command has been executed. The standard parameter set has been written and saved.



Remedy:

  • Switch inverter off and on again.
25505 0x63A1

CU: load error ID tag
Cause:

Calibration data of the control unit not compatible or faulty.



Remedy:

  • Update firmware of the inverter to the most recent version.

  • If the error persists, the control unit or the device has to be replaced.
25506 0x63A2

PU: load error ID tag
Cause:

Calibration data of the power unit not compatible or faulty.



Remedy:

  • Update firmware of the inverter to the most recent version.

  • If the error persists, the power unit or the device has to be replaced.
25507 0x63A3

Power unit unknown
Cause:

The power unit installed is not supported by the software.



Remedy:

  • Update firmware of the inverter to the most recent version.
28800 0x7080

Assertion level monitoring (Low/High)
Cause:

The last setting of the connection level differs from the saved setting.



Remedy:

  • Execute device command “Save user data”.

  • Switch inverter off and on again.
28801 0x7081

Fault – Analog input 1
Cause:

The monitoring function of the input signal configured for analog input 1 has been triggered.



Remedy:

  • Check input signal at analog input 1.

  • Check configuration of the monitoring function.
28802 0x7082

Analog input 2 fault
Cause:

The monitoring function of the input signal configured for analog input 2 has been triggered.



Remedy:

  • Check input signal at analog input 2.

  • Check configuration of the monitoring function.
28803 0x7083

HTL input fault
Cause:

(No specific cause listed in OCR, implies signal failure)



Remedy:

  • No response (configurable).
28833 0x70A1

Analog output 1 fault
Cause:

Open circuit or short circuit at analog output 1.



Remedy:

  • Check wiring of analog output 1.

  • Check definition of the output range.
28834 0x70A2

Analog output 2 fault
Cause:

Open circuit or short circuit at analog output 2.



Remedy:

  • Check wiring of analog output 2.

  • Check definition of the output range.
28961 0x7121

Fault – Pole position identification
Cause:

  • Too many deviations during the pole position identification.

  • Compared to the inverter, the rated motor current is too high or too low.





Remedy:

  • Check setting of the motor data.

  • Ensure that the motor is at a standstill during the pole position identification process.

  • Ensure that the motor and inverter match each other in terms of power.
29056 0x7180

Motor overcurrent
Cause:

The motor current has exceeded the warning/error threshold for the motor current monitoring.



Remedy:

  • Check motor load.

  • Check drive dimensioning.

  • Check warning threshold or error threshold.
29445 0x7305

Encoder open circuit
Cause:

The encoder signal loss monitoring function has detected a failure of the encoder signal.



Remedy:

  • Check the encoder connection.

  • Check encoder cable for wire breakage.

  • Check encoder current supply.
29573 0x7385

Feedback system: speed limit
Cause:

The feedback system exceeds the maximum permissible frequency range of the digital inputs.



Remedy:

  • Check feedback system.
30336 0x7680

Memory module is full
Cause:

The memory module contains too many parameter settings.



Remedy:

  • Execute “Save user data” device command again. This reinitialises the user memory with the current parameter settings.
30337 0x7681

Memory module not present
Cause:

The inverter memory module was removed.



Remedy:

  • Switch off inverter.

  • Plug the memory module into the inverter.

  • Switch the inverter on again.
30338 0x7682

Invalid user data
Cause:

The user parameter settings in the memory module are invalid.



Remedy:

  • Execute user parameter settings again.

  • Execute device command “Save user data”.
30340 0x7684

Data not compl. saved before powerdown
Cause:

Saving of the parameter settings was interrupted by an unexpected disconnection.



Remedy:

  • Check user parameter settings.

  • If required, repeat the changes made last.

  • Execute device command “Save user data”.
30345 0x7689

Memory module: invalid OEM data
Cause:

The OEM memory contains invalid parameter settings or is empty.



Remedy:

  • Execute device command “Save OEM data”.
30346 0x768A

Memory module: wrong type
Cause:

The memory module connected is not supported by the inverter.



Remedy:

  • Switch off inverter.

  • Replace plugged-in memory module by a memory module that matches the inverter.

  • Switch the inverter on again.
30352 0x7690

EPM firmware version incompatible
Cause:

The parameter settings saved in the memory module are incompatible with the firmware version.



Remedy:

  • Execute device command “Load default settings”.

  • Execute “Save user data” or “Save OEM data” device command.
30353 0x7691

EPM data: firmware type incompatible
Cause:

The parameter settings saved in the memory module are incompatible with the firmware type.



Remedy:

  • Execute device command “Load default settings”.

  • Execute “Save user data” or “Save OEM data” device command.
30354 0x7692

EPM data: new firmware type detected
Cause:

The parameter settings saved in the memory module do not match the inverter hardware.



Remedy:

  • Check parameter settings.

  • Reset error.

  • Execute “Save user data” or “Save OEM data” device command.
30355 0x7693

EPM data: PU size incompatible
Cause:

The parameter settings saved in the memory module are incompatible with the inverter.



Remedy:

  • Execute device command “Load default settings”.

  • Execute “Save user data” or “Save OEM data” device command.
30356 0x7694

EPM data: new PU size detected
Cause:

The parameter settings saved in the memory module comply with a different hardware.



Remedy:

  • Check parameter settings.

  • Reset error.

  • Execute “Save user data” or “Save OEM data” device command.
30357 0x7695

Invalid parameter changeover configuration
Cause:

One or more parameters can no longer be used for the “Parameter change-over” function.



Remedy:

  • Check error message for parameter change-over.

  • Correct the list entry shown in parameters.
30358 0x7696

EPM data: unknown parameter found
Cause:

The memory module contains parameter settings for one or several parameters that are not known to the inverter.



Remedy:

  • Execute the “Save user data” device command. This reinitialises the user memory with the current parameter settings.
30359 0x7697

Parameter changes lost
Cause:

A voltage failure has occurred and changed parameter settings that had not been saved yet were available.



Remedy:

  • Execute parameter settings again.

  • Execute device command “Save user data”.
33042 0x8112

Network – Time-out explicit message
Cause:

  • Within the time-out period for explicit messages, no “explicit message” was received.

  • The connection to the scanner has been interrupted.

  • Failure of an explicit connection.





Remedy:

  • Check cables and terminals.

  • Plug network cables into the Ethernet port.

  • Check the requested package interval (RPI) of the explicit connection.

  • Increase time limit for explicit messages in the scanner.
33044 0x8114

Network – Overall communication time-out
Cause:

  • EtherNet/IP: the maximum permissible time-out period for the CIP communication has been exceeded.

  • Modbus TCP/IP: the maximum permissible time-out period for the TCP communication has been exceeded.





Remedy:

  • Check cables and terminals.

  • Connect network cable.
33045 0x8115

Time-out (PAM)
Cause:

The parameter access monitoring (PAM) function has been activated, but no value was entered into the “Keep-alive-Register” in time.



Remedy:

  • Check communication.

  • Check settings of the parameter access monitoring (PAM) function.
33046 0x8116

Modbus TCP master time-out
Cause:

No valid messages have been received by the Modbus master for a time longer than the time-out period set.



Remedy:

  • Check communication with the master.
33047 0x8117

Modbus TCP Keep Alive time-out
Cause:

For a time longer than the time-out period set, no value was entered into the Keep alive register.



Remedy:

  • Check communication with the master.
33154 0x8182

CAN: bus off
Cause:

  • Too many faulty frames have been received.

  • Defective cable (e. g. loose contact).

  • Two nodes with the same node address.





Remedy:

  • Check wiring of the network.

  • Check bus terminating resistor.

  • Set the identical baud rate for each node of the network.

  • Assign a unique node address to each node of the network.

  • Eliminate EMC interferences.
33155 0x8183

CAN: warning
Cause:

  • Too many faulty frames have been received.

  • Defective cable (e. g. loose contact).

  • Two nodes with the same node address.





Remedy:

  • Check wiring of the network.

  • Check bus terminating resistor.

  • Set the identical baud rate for each node of the network.

  • Assign a unique node address to each node of the network.

  • Eliminate EMC interferences.
33156 0x8184

CAN: heartbeat time-out consumer 1
Cause:

Within the heartbeat time, no heartbeat telegram was received by node 1 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
33157 0x8185

CAN: heartbeat time-out consumer 2
Cause:

Within the heartbeat time, no heartbeat telegram was received by node 2 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
33158 0x8186

CAN: heartbeat time-out consumer 3
Cause:

Within the heartbeat time, no heartbeat telegram was received by node 3 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
33159 0x8187

CAN: heartbeat time-out consumer 4
Cause:

Within the heartbeat time, no heartbeat telegram was received by node 4 to be monitored.



Remedy:

  • Check communication with the heartbeat producer.

  • Reactivate heartbeat producer.
33168 0x8190

Network – Watchdog time-out
Cause:

Time-out during cyclic data reception, e.g. due to an interrupted communication link to the master or missing cyclic data.



Remedy:

  • Check wiring of the network.

  • Eliminate EMC interferences.
33169 0x8191

Network – Disruption of cyclic data exchange
Cause:

The communication partner has interrupted the cyclic data exchange.



Remedy:

  • Check wiring of the network.

  • The slave must receive new parameterisation and configuration files by the master.
33170 0x8192

Network – Initialization error
Cause:

The initialisation of the communication stack has been interrupted due to an incorrect address setting or communication configuration.



Remedy:

  • Check master/slave configuration and restart the devices.
33171 0x8193

Network – Invalid cyclic process data
Cause:

The cyclic process data received are invalid.



Remedy:

  • Check cyclic process data sent by the master.
33185 0x81A1

Modbus: network time-out
Cause:

No valid messages have been received via the Modbus for a longer time than the time-out time set.



Remedy:

  • Check communication with the master.

  • Check wiring.

  • Check bus termination.
33186 0x81A2

Modbus: incorrect request by master
Cause:

The request by the master is invalid, e. g. invalid CRC checksum, non-supported function code, or impermissible data access.



Remedy:

  • Check request by the master.

  • Check value in the valid range.

  • Check function code valid.

  • Check if write access is impermissible.
33200 0x81B0

Network communication faulty
Cause:

In case of the Ethernet communication interface, an internal software error has occurred.



Remedy:

  • Switch inverter off and on again.

  • In the event of a power failure during a firmware download, reload the firmware via the USB module.
33381 0x8265

POWERLINK: Loss of SoC
Cause:

SoC of master was not received.



Remedy:

  • Check configuration and system setup.
33382 0x8266

POWERLINK: CRC error
Cause:

CRC frame defective.



Remedy:

  • Check system setup.
33414 0x8286

Network – PDO mapping error
Cause:

  • Invalid PDO assignment by the master.

  • Internal PDO assignment was changed and does not comply with the configuration available in the master.





Remedy:

  • Check data mapping in the master and slave.
33425 0x8291

CAN: RPDO1 time-out
Cause:

RPDO1 was not received within the time-out period set or with the sync configured.



Remedy:

  • (Check setting parameters)
33426 0x8292

CAN: RPDO2 time-out
Cause:

RPDO2 was not received within the time-out period set or with the sync configured.



Remedy:

  • (Check setting parameters)
33427 0x8293

CAN: RPDO3 time-out
Cause:

RPDO3 was not received within the time-out period set or with the sync configured.



Remedy:

  • (Check setting parameters)
33553 0x8311

Torque limit reached
Cause:

Motor has reached the torque limit (positive or negative).



Remedy:

  • Observe load requirements.

  • Reduce motor load.

  • Check set torque limits and sources for the torque limits.
33664 0x8380

Function not allowed in selected operating mode
Cause:

The selected function is not permissible in the chosen operating mode.



Remedy:

  • Check settings of operation modes.

  • Note selection of torque modes with incompatible motor control.
36992 0x9080

Keypad removed
Cause:

The keypad was removed while the keypad control was activated.



Remedy:

  • Plug keypad back in or activate another control source.
65282 0xFF02

Fault – Brake resistor overload
Cause:

The calculated thermal load of the brake resistor has reached the error threshold. The regenerative energy is too high.



Remedy:

  • Check drive dimensioning.

  • Check settings for the brake energy management.
65285 0xFF05

Safety option – Internal error
Cause:

The safety module or safety circuit of the device was detected as being defective. The integrated safety technology is defective.



Remedy:

  • Hardware error: it is necessary to contact the manufacturer since the device must be replaced.

  • The safety module must not be removed.
65286 0xFF06

Motor overspeed
Cause:

The motor speed has reached the error threshold for overspeed.



Remedy:

  • Adapt the maximum motor speed and the warning/error thresholds.
65289 0xFF09

Motor phase missing
Cause:

A failure of several motor phases has been detected.



Remedy:

  • Check wiring between inverter and motor.

  • In case of a false tripping, adapt the settings for the motor phase failure detection.
65290 0xFF0A

Motor phase failure phase U
Cause:

A failure of the motor phase U has been detected.



Remedy:

  • Check wiring between inverter and motor.

  • In case of a false tripping, adapt the settings for the motor phase failure detection.
65291 0xFF0B

Motor phase failure phase V
Cause:

A failure of the motor phase V has been detected.



Remedy:

  • Check wiring between inverter and motor.

  • In case of a false tripping, adapt the settings for the motor phase failure detection.
65292 0xFF0C

Motor phase failure phase W
Cause:

(Implied failure of phase W based on previous faults).



Remedy:

  • No response (configurable).
65305 0xFF19

Motor parameter identification fault
Cause:

During the automatic identification of the motor, an error has occurred.



Remedy:

  • Set motor data so that they comply with the data on the motor nameplate.

  • Check wiring of the motor.
65311 0xFF1F

FMF Error
Cause:

Configuration or runtime error.



Remedy:

  • Check configuration.

  • Check FMF error code 0x4050:002 to determine the error cause.
65317 0xFF25

Cascading overload
Cause:

Cascade function for pumps and fans: The maximum frequency has been reached and no free additional pump is available.



Remedy:

  • Check configuration of the cascade function.

  • Check drive sizing.
65334 0xFF36

Warning – Brake resistor overload
Cause:

The calculated thermal load of the brake resistor has reached the warning threshold. The regenerative energy is too high.



Remedy:

  • Check drive dimensioning.

  • Check settings for the brake energy management.
65335 0xFF37

Automatic start disabled
Cause:

At mains connection, a start command was already available and the automatic start at power-up is set to “Off”.



Remedy:

  • Deactivate starting command and reset error.
65336 0xFF38

Load loss detected
Cause:

In a running motor, the motor load (current) falls below the threshold value specified in Load loss detection.



Remedy:

  • Check utilisation.
65337 0xFF39

Motor overload
Cause:

If the apparent motor current exceeds a defined threshold value for a certain amount of time.



Remedy:

  • Check the motor load.
65366 0xFF56

Maximum motor frequency reached
Cause:

  • The limitation of the maximum motor speed is active.

  • The maximum output frequency of the inverter has been reached.





Remedy:

  • Check application.
65370 0xFF5A

Manual mode disabled
Cause:

Indicates the deactivation of the manual speed control.



Remedy:

  • (Warning only)
65371 0xFF5B

Manual mode activated
Cause:

Indicates the activation of the manual speed control.



Remedy:

  • (Warning only)
65372 0xFF5C

Manual mode time-out
Cause:

If “manual operation” is active, an error is generated in case the communication links get lost.



Remedy:

  • The error can be only be reset if the connection is restored or the control mode is changed to a different value than “manual operation”.
65393 0xFF71

Wrong password
Cause:

A wrong password has been entered several times.



Remedy:

  • Wait until the blocking time has elapsed and then enter the correct password.
65394 0xFF72

Warning
Cause:

  • Inverter is not compatible with the Controller/PLC (brand protection).

  • The Controller has not written a deactivation password in the parameter yet.





Remedy:

  • Use corresponding (compatible) OEM components.
65395 0xFF73

Fatal Error
Cause:

Error when reading the data from the control unit.



Remedy:

  • Switch inverter off and on again.

  • If the error occurs again, the manufacturer must be contacted.
65396 0xFF74

Power unit fatal error
Cause:

Error when reading the data from the power unit.



Remedy:

  • Switch inverter off and on again.

  • If the error occurs again, the manufacturer must be contacted.
65413 0xFF85

Keypad full control active
Cause:

If the “Keypad Full Control” control mode is active.



Remedy:

  • To exit the control mode, press the keypad key CTRL.