F33916 — Encoder 3: Encoder parameterization error

F33916 signals that a parameter of encoder 3 has been detected as incorrect. The manuals point to one typical situation: the encoder type stored in the parameterization does not match the encoder actually connected. Depending on the drive configuration, the same condition can also be issued as an alarm (A) or with no reaction (N) instead of a fault.

• An encoder parameter of encoder 3 was detected as being incorrect.
• It is possible that the parameterized encoder type does not match the connected encoder.

1. Check whether the connected encoder type matches the encoder type that has been parameterized.
2. Determine the parameter number of the incorrect parameter from the fault value r0949, interpreting the value as a decimal number.
3. Determine the parameter index from p0187.
4. Correct the parameter specified by the fault value (r0949) and p0187.

• Fault value (r0949, interpret decimal): parameter number — the fault value holds the number of the parameter detected as incorrect.
• Message value: Parameter: %1, supplementary information: %2.

• r0949 — fault value of the message; for F33916 it contains the number of the incorrect encoder parameter and must be interpreted as a decimal number.
• p0187 — encoder 1 encoder data set (EDS) number; for this fault the entry uses it to read out the parameter index that, together with r0949, identifies the parameter to correct.

The fault must be acknowledged immediately (IMMEDIATELY); when it trips, the drive executes OFF1, so operation can only resume after the incorrect parameter has been corrected and the message acknowledged. Where the condition is output as alarm A or with no reaction (N), the drive neither reacts nor requires an acknowledgement.