Skip to main content

ZYPLC Blog

FEN-21 vs FEN-31: Identify the Feedback

Oct 19, 2026 5 min read Motion Control

Distinguish ABB FEN-21 resolver and FEN-31 HTL feedback interfaces. Send module labels and drive details for a precisely matched spare inquiry.

ABB FEN-21 FEN-31 spare parts 2026 resolver and encoder interface identification illustration

An encoder-interface request often starts with a photograph of a small option board and a brief instruction: send the same card. The difficulty is that similar-looking cards can serve different feedback devices, and a catalog description may group several applications under one broad drive-family label. That is not enough information to release a replacement for a controlled motion axis.

ABB FEN-21 and FEN-31 illustrate the problem. Both belong in the feedback discussion, but they should not be treated as interchangeable encoder cards. A useful purchasing record identifies the signal entering the module, the installed drive control unit and the software configuration that uses the feedback. It keeps those facts separate from a seller’s abbreviated product heading.

Start with the interface, not the board shape

ABB describes FEN-21 as a resolver interface with an additional TTL encoder connection and TTL emulation output. ABB identifies FEN-31 as an HTL encoder interface. The manufacturer’s FEN-21 description and FEN-31 quick guide provide primary references for that distinction. These names describe interface functions; they do not establish compatibility with every drive carrying the ABB name.

The practical consequence is straightforward: do not replace an identification problem with a connector comparison. The presence of a feedback connector or an output described as TTL does not mean the same type of input device is supported. Read each connection by its assigned function in the applicable manual, rather than by a word shared with another module.

For a request involving the ABB FEN-21 feedback interface, provide the installed module label and the motor feedback device identification. The catalog page is a sourcing destination, not a compatibility certificate for every drive family named in its title. Engineering confirmation should use the exact control unit and its approved option documentation.

Build an identification chain

Record four identities together: the feedback device, interface module, drive control unit and application software or parameter reference. A maintenance database that stores only the drive’s cabinet number loses the information needed to distinguish option variants. Photographs help preserve labels that may be difficult to read after a failure.

Include the complete manufacturer part number and hardware revision where shown. Do not assume that a number printed on a circuit board is automatically the order code for the complete assembly. A board marking, finished-unit identifier and catalog order reference can serve different purposes. Ask the supplier to reconcile them with label photographs before dispatch.

For an HTL feedback requirement, the FEN-31 interface listing can anchor that inquiry. Request confirmation of the actual supplied assembly and its full identification. Do not infer a different interface function from a general catalog category or use the page title as evidence of an approved substitution.

Capture settings without inventing defaults

The mechanical identity of the card is only part of the recovery record. Preserve the approved feedback settings, connection documentation and relevant commissioning report. Where the design uses hardware selections, record their actual approved positions and the manual revision that explains them. Avoid assuming that a replacement arrives configured for the installed encoder.

A familiar connector is particularly misleading when the old unit’s setup has been changed during earlier service. The safest procurement approach is to flag the configuration as a commissioning dependency rather than promise a plug-and-run replacement. The person accepting the spare should know which settings must be checked by qualified personnel before use.

Do not use this distinction as a reason to change feedback technology during a breakdown. Moving between resolver, TTL or HTL arrangements is a system-engineering question involving the feedback device and supported control configuration. It is not a purchasing shortcut based on which board is available fastest.

Acceptance should follow the feedback path

Ask what a supplier’s test establishes. A power-on observation is not equivalent to checking the relevant input function, and a generic drive test may not reproduce the site’s feedback arrangement. A meaningful record identifies the module, the supported test setup, the observed results and the functions that were not exercised.

The plant’s commissioning plan should then address the actual application under controlled conditions. It should define who checks feedback interpretation, machine behavior and any dependencies before production release. Keep motion hazards, stored energy and the site’s isolation procedures under the responsible engineering team’s control. This purchasing guide does not provide instructions for energized connection changes.

Preserve rejected candidates in the sourcing record as rejected, with the reason. Otherwise, a later urgent inquiry may revive the same superficially similar alternative after the engineer who reviewed it is unavailable. A short note such as interface mismatch is more useful than an unexplained crossed-out part number.

Frequently asked identification questions

Is FEN-31 an upgraded replacement for FEN-21?

Do not interpret the higher number that way. ABB identifies different feedback-interface functions. Select against the installed feedback system and the drive’s supported option documentation, not the numerical order of the product names.

Can the product page prove compatibility with my drive?

No. Use it to identify a sourcing candidate. The exact drive control unit, hardware and software requirements must be checked against the relevant manufacturer documentation before a replacement is approved.

Why is an encoder output description insufficient?

An output and an input perform different roles. A module can provide an emulation output while accepting another feedback technology at its input. Read the connection function rather than matching isolated terms in a description.

What if the original label is unreadable?

Gather the machine BOM, previous commissioning records, control-unit identification and clear photographs of the assembly. Mark the identification as unresolved until the evidence is reconciled; do not approve a substitute solely from appearance.

Send ZYPLC the feedback-device model, installed card photographs, control-unit identity and quantity. A focused FEN interface inquiry helps separate a genuine replacement candidate from a similar-looking board before the purchasing decision becomes a commissioning problem.

Image: AI-generated editorial illustration, not an exact product photograph or installation reference.

© 2026 ZYPLC. All rights reserved. Official Website: https://zyplc.com Inquiry: plc.sales@zyplc.com | WhatsApp/Tel: +86 19859288691