ACS580 Fault FF81 — Force trip from fieldbus

Overview

The FF81 Force trip from fieldbus fault on an ABB ACS580 variable frequency drive (VFD) indicates that the drive has been explicitly instructed to stop and enter a faulted state by an external controller over the industrial communications network. Unlike physical hardware faults (like overcurrent or overvoltage) or network loss events, an FF81 fault means that the communications network is functioning perfectly, but the master controller (such as a PLC or DCS) has deliberately written a command bit telling the drive to trip. It is a simulated or logical interlock trip initiated by your system's automation program.

Symptoms

When an ACS580 drive experiences a fieldbus-initiated forced trip, you will typically observe the following symptoms on the plant floor:

• The drive’s physical control panel (Assistant Keypad) displays a bright red LED indicator.
• The keypad screen displays Fault: FF81 and the description "Force trip from fieldbus."
• The connected AC motor immediately coasts or ramps to a complete stop, depending on the configured safe-stop settings.
• The communication adapter (such as a FENA-21, FEIP-21, or FPBA-01) flashes green or remains solid green, indicating that online communication with the PLC is still active and healthy.
• Standard reset commands issued from the keypad or local I/O may be rejected or automatically overridden as long as the PLC continues to write the active trip bit.

Possible Causes

An FF81 fault is almost always logical rather than physical. The most common underlying causes include:

• Active PLC Interlocks: The PLC application program has triggered an active safety or process interlock (e.g., a high-temperature limit, low lubrication pressure, or downstream jam) and chose to halt the drive via the fieldbus command loop.
• Incorrect Control Word Mapping: During commissioning or a recent PLC code update, a control bit in the PLC’s output assembly was erroneously mapped or forced high, targeting the specific register mapped to the drive's trip input.
• HMI Emergency/Stop Triggers: An operator pressed a virtual emergency stop or process-hold button on an HMI panel that is programmed to dynamically fault individual system drives.
• First-Run Commissioning Logic Errors: The system integrator has programmed an uninitialized or buggy variable block in the controller's logic, causing the control output word to default to high or unsafe bit patterns upon startup.
• Wrong Active Control Profile: The drive is configured for a specific fieldbus control profile (such as the ABB Drives Profile or ODVA AC/DC) but the PLC program is formatting commands using a conflicting profile, causing status bits to be misread as fault commands.

Step-by-Step Troubleshooting

Follow these sequential phases to isolate the controller logic, inspect the drive parameter values, and clear the logical command loop.

Step 1: Trace the ACS580 Control Word Input

Begin by checking exactly what command payload the drive is receiving from the network.

1. Navigate to the drive's control panel menu.
2. Go to Parameters > Complete List > Group 06 (Control and status words).
3. Check parameter 06.01 Main Control Word (or the corresponding fieldbus control word parameter, depending on your communication protocol).
4. Document the hexadecimal value shown on the screen (e.g., 0x047F). Translate this hex value to binary to identify which specific bit is set high. For instance, in standard ABB profiles, check if the bit assigned to emergency stop/forced trip commands is active.

Step 2: Correlate with Group 50 (Fieldbus Comm Settings)

Verify how the communication adapter is communicating the control word to the drive controller board.

1. Access parameter Group 50 (Fieldbus adapter (FBA)).
2. Verify the configuration of parameter 50.02 FBA A Comm Loss Func and 50.05 FBA A ref1 type to ensure the drive knows how to treat fieldbus control interfaces.
3. Verify whether any customizable functional inputs (such as external faults in Group 31) are mapped directly to a fieldbus bit. For example, if 31.01 External Event 1 Source is set to a fieldbus bit, check whether that bit has been toggle-tripped by the controller program.

Step 3: Audit the PLC/DCS Code and Tags

Since the trip command is generated externally, you must search and debug the automation code inside your PLC development environment (e.g., Studio 5000, TIA Portal, or EcoStruxure).

1. Connect your PC to the PLC and open the online project.
2. Cross-reference the specific memory map, controller tags, or output assembly instance being written to the ACS580 drive.
3. Look for the tag representing the "Force Trip" or "Fault Reset/Trigger" bit within the drive's output data structure.
4. Trace this tag backward through your logic to find what execution block, safety gate interlock, or process variable coil is turning this bit on.

Step 4: Examine Operator Interfaces (HMIs and SCADA)

Occasionally, operator terminals can lock up and write static high states to control tags.

1. Inspect your HMI or SCADA alarm banners for any active process alarms associated with the target machinery.
2. Confirm that there are no pressed and latched software "Emergency Stop" buttons or "Process Pause" switches on any field HMI panels.
3. If necessary, cycle power to localized operator touchscreens to ensure there are no stuck communication scripts writing to the PLC registers.

Step 5: Test Control Path Isolation

You can temporarily isolate the drive from the fieldbus to confirm the hardware functions independently.

1. Switch the ACS580 control location from Remote (Fieldbus) mode to Local (Keypad) control by pressing the "Loc/Rem" button on the Assistant Control Panel.
2. Attempt to reset the FF81 fault via the keypad.
3. If the fault clears and the motor runs under local control speed reference, this confirms the drive hardware, motor, and power stage are structurally sound. The problem exists purely within the fieldbus network control loop master side.

Recommended Actions

To safely resolve the FF81 fault and prevent its recurrence, apply the following corrective measures:

• Clear PLC Safe Interlocks: Resolve the process state (such as clearing a material jam, resetting low-flow valves, or resetting safety gates) that forced the controller to request the drive trip.
• Recode Uninitialized PLC Logic: Modify PLC code instructions to ensure that during PLC CPU power cycles or run-mode changes, the control word defaults to a safe, neutral pattern (representing a simple Stop state) rather than a faulted binary state.
• Check Software Profile Settings: Ensure parameter 50.04 FBA A Ref1 Type matches the fieldbus profile structured in your PLC. If the PLC outputs ODVA and the drive expects ABB Drives profile, standard control words will trigger unintended behaviors.
• Add Handshake Delay Filters: If transient network dropouts temporarily confuse the controller into sending panic trip bits, implement short software filter timers (e.g., 500ms) in the PLC logic before writing active fault bits to the VFD control structure.

Recommended Replacement Parts

Because Fault FF81 indicates a logical instruction and not a drive failure, hard component failures are rare. However, if communication ports drop packets or if controller interfaces fail interlocks repeatedly due to physical corruption, consider replacing these core components:

Related Articles

• How to Configure Ethernet/IP Communication on ABB ACS580 Drives
• Installing and Wiring FENA-21 Modules on ACS580 VFDs
• PLC and ABB Drives Profile Mapping Guide

FAQ

Q: Why can't I clear the FF81 fault using the drive's keypad reset button?

A: As long as the PLC controller continues to write the active "Force Trip" bit over the network, any manual reset from the local keypad will be instantly overwritten by the incoming cyclical fieldbus telegram. You must first clear the logic condition in the PLC program before resetting the drive.

Q: Is FF81 an indication of a damaged communication card or a broken network cable?

A: No. A broken cable or a hardware fault on your FENA-21 card will trigger communication loss faults like 7510 (FBA A communication loss). The FF81 fault is a logical command, meaning your network and communications cards are operating successfully but the host PLC is specifically commanding the drive to enter a faulted state.

Q: How do I know which bit in the control word is causing the trip?

A: Depending on the selected fieldbus profile (Parameter Group 50), the control word corresponds to a predefined register layout. Often, bit 10 or customized bits linked to external event triggers (e.g., Parameter 31.01) are defined as fault triggers. Compare your PLC output word configuration in your communication software with the technical description of the mapped profile in the ACS580 Firmware Manual.

Q: Can this fault occur due to high electrical noise (EMI) on the communication cables?

A: While electromagnetic interference can disrupt data packets, it typically triggers checksum errors, packet drops, or communication losses rather than an FF81 command. However, if your network is unshielded, corrupt packets may theoretically mimic a valid control word pattern, though this is highly unusual. Ensure all communication lines are routed away from high-power motor leads.