Lenze VFD Fault CE — What It Means
CE on a Lenze VFD (8400, E82, SMV, or i550 series) indicates a communication error. The drive has lost contact with its fieldbus master or serial communication controller — typically a PLC, DCS, or HMI communicating via PROFIBUS, CANopen, DeviceNet, Modbus, or EtherNet/IP. When the communication watchdog timer expires without receiving a valid message from the master, the drive trips on CE and stops the motor according to the configured communication fault response.
Common Causes
- Fieldbus cable disconnected or damaged — The communication cable between the Lenze drive and the PLC/master has been disconnected, broken, or the connector has vibrated loose.
- PLC communication fault or scan cycle overrun — The PLC master has stopped sending cyclic data to the drive due to a program fault, CPU overload, or network communication failure.
- Incorrect node address or baud rate — A mismatch between the drive’s configured node address or baud rate and the master network configuration causes the drive to appear offline to the network.
- Communication watchdog timeout set too short — The communication timeout parameter in the drive is configured more aggressively than the PLC’s actual update cycle, causing false CE faults.
Step-by-Step Fix
- Inspect the fieldbus cable and connectors — Physically check the communication cable from the Lenze drive to the PLC or fieldbus coupler. Look for disconnected plugs, damaged cable insulation, or loose terminal screws on the drive’s communication board.
- Verify the PLC is sending data — Check the PLC’s network diagnostics for the Lenze drive node. Confirm the PLC is online, the communication module is active, and the I/O scan for the drive node shows no errors.
- Check node address and baud rate — Access the Lenze communication parameters (typically group C-xx or L-xx depending on the model). Confirm the node address and baud rate match what the PLC or network configurator expects.
- Check the communication watchdog timeout — Find the communication watchdog parameter in the Lenze drive. Increase the timeout value to provide more margin against brief PLC scan delays without triggering CE.
- Test the cable for continuity — Use a multimeter or fieldbus tester to verify the communication cable has no open circuits or shorts between conductors. For RS485/Modbus, verify correct polarity on A+ and B- terminals.
- Check termination resistors — RS485 and PROFIBUS networks require 120Ω termination resistors at each end of the bus. Verify the drive end and the PLC/master end are correctly terminated.
- Reset the fault — After resolving the communication issue, reset the CE fault via the drive keypad or a digital input reset command from the PLC.
Parts Often Needed
| Part | Notes |
|---|---|
| Fieldbus cable (shielded) | Replace damaged communication cable runs |
| Lenze communication module | Replace if drive’s comm board is physically damaged |
| Network termination plug | 120Ω terminator for RS485/PROFIBUS bus ends |
Need Replacement Parts?
Finding the right replacement parts for your equipment is critical to getting it running again. Check current prices on Amazon — prices and availability change frequently.
When to Call a Pro
If CE persists after verifying all physical connections and PLC network health, a Lenze-authorized technician with fieldbus diagnostic tools (protocol analyzer) can trace the communication fault to a specific node, timing issue, or hardware defect.