V/f operation and Hiperface encoder (0x2C40=2) parameterized: Drive controller cannot be enabled (no change intended)
Corrected from:
Servo inverter i700, V1: no change planned for V1
Servo inverter i700, V2: from V02.xx.xx.xx (currently no change planned)
Response of the new version:
(currently no firmware change is planned as there is only a very low probability of occurrence and there is a simple remedy, see below)
What happens?
The drive controller cannot be enabled unexpectedly after power-on if a Hiperface absolute encoder is parameterized but none is actually connected.
In this constellation, the system waits for a valid position value to be supplied by the encoder via Hiperface communication as a precondition for controller enable.
When does the behaviour occur? In contrast to the Lenze setting, the motor encoder type is parameterised to Hiperface absolute endoder (0x2C40 = [2]),although no Hiperface absolute encoder is actually connected.
Resolver device i700: Always leave encoder type selection in default: 0x2C40 = [1] 'SinCos-Encoder'.
Encoder device i700: Only if a Hiperface absolute encoder is actually connected, 0x2C40 = [2] 'Hiperface absolute encoder'.
In all other cases, leave the encoder type in default setting: 0x2C40 = [1] 'SinCos encoder'.
In practice, users will not actively set the encoder type to 0x2C40 = [2] if no Hiperface encoder is used. Possibly a wrong parameterization can occur if the parameter set of another device with Hiperface encoder is taken over.
Background:
The motor control type "V/f characteristic control" is mostly used on the i700 when no feedback system is available for the "servo control" to be preferred.
Lenze also provides the possibility of connecting and evaluating an encoder for application purposes in sensorless operation. For this reason, the encoder parameterization is not ignored even in the case of actual sensorless V/f operation. The parameterization of the feedback must therefore always correspond to the real encoder configuration.
