F33153 — Encoder 3: Identification error

F33153 is raised when the automatic identification of the encoder connected as Encoder 3 does not succeed: the drive waits for the identification result with p0400 = 10100, and the connected encoder was not able to be identified. The component concerned is the Sensor Module Encoder 3. Depending on how the drive is configured, the same condition can also be signalled with no reaction (N) or as an alarm (A) instead of a fault.

• The drive tried to identify the connected encoder automatically; an error occurred during this identification while it was still pending (p0400 = 10100), so the encoder could not be identified.
• The fault value in r0949 gives the concrete reason: bit 0 set means the data length was incorrect.

1. Read the fault value in r0949. Bit 0 set means the identification failed because of an incorrect data length. Note that the S120/S150 manual says to interpret this value as binary, while the G130/G150 manual says hexadecimal.
2. Look at p0400 (encoder type selection): the identification this fault belongs to is pending while p0400 = 10100.
3. Carry out the remedy the manual prints: configure the encoder manually according to its data sheet.

• The drive stores the fault value in r0949 and transmits it as the message value (%1).
• Bit 0: Data length incorrect.
• Interpretation: binary according to the S120/S150 manual, hexadecimal according to the G130/G150 manual.

• p0400 (encoder type selection): identification of the connected encoder is pending while p0400 = 10100 (waiting); the parameter selects the encoder type.
• r0949 (fault value): shows the fault value of F33153, where bit 0 set means data length incorrect.

The fault is acknowledged immediately on the drive; once the encoder has been configured manually according to its data sheet, it can be cleared. If the drive issues the condition with no reaction (N) or as an alarm (A), the manuals specify no acknowledgement for those variants.