Having trouble with a WEG CFW300 VFD? Learn how to identify, troubleshoot, and reset Fxxx fault codes, "SUB" warnings, and "config" errors.

The WEG CFW300 is a highly versatile, compact micro variable frequency drive (VFD) equipped with a built-in SoftPLC and dual control options: Voltage Vector WEG (VVW) sensorless vector and V/f (scalar) control . Designed for small-scale industrial and commercial machinery, this micro drive features diagnostic monitoring to detect issues before they cause permanent hardware damage .

The CFW300 classifies system events into two main categories on its integrated display :

• Alarms (Axxx): Warning messages that do not stop the drive . They indicate that the drive is operating near a limit, automatically clearing once the condition returns to normal . The active alarm is stored in Parameter P0048 .
• Faults (Fxxx): Critical errors that instantly disable the motor output . The motor will coast to a stop, and the drive must be reset to resume operation . The active fault code is logged in Parameter P0049 .

In this guide, we walk you through reading the CFW300's unique errors, performing a safe reset, and resolving common faults.

WEG CFW300 Fault and Alarm Reference Table

Locate the active code on your drive’s HMI screen and match it to your reference table to isolate the specific electrical or mechanical issue.

WEG CFW300 Drive Fault Codes List

Fault / Alarm and Meaning	Cause and Remedy
F021 Undervoltage on the DC Link Undervoltage fault on the intermediate circuit.	Cause: Wrong voltage supply. Supply voltage too low, producing voltage on the DC Link below the minimum value (Level F021) according to Table 10.1 on page 10-3. Phase fault in the input. Fault in the pre-charge circuit. Remedy: Verify if the incoming supply voltage matches the inverter rating label and parameter P296. Inspect input phases and check the pre-charge circuit elements.
F022 Overvoltage on the DC Link Overvoltage fault on the intermediate circuit.	Cause: Wrong voltage supply. Supply voltage is too high, producing voltage on the DC Link above the maximum value (Level F022) according to Table 10.1 on page 10-3. Load inertia is too high or deceleration ramp is too fast. Parameter P151 setting is configured too high. Remedy: Verify incoming supply voltage complies with label specifications and parameter P296. Increase the deceleration ramp time, adjust load inertia, or reduce parameter P151 configuration.
F031 Fault in Communication with Expansion Accessory Main control cannot establish the communication link with the IOs expansion accessory.	Cause: Accessory is damaged. Poor contact or loose connection of the accessory. Problem in the identification of the accessory (refer to P027). Remedy: Check the physical fit and contact connection of the expansion card. Replace the accessory if damaged, or inspect settings inside parameter P027.
F032 Comm. Plug-in module communication Lost Main control cannot establish the communication link with the communication accessory.	Cause: Accessory is damaged. Poor contact or loose connection of the accessory. Problem in the identification of the accessory (refer to P028). Remedy: Check the physical fit and contact pins of the plugin card. Replace the accessory if damaged, or inspect settings inside parameter P028.
F033 VVW Self-tuning Fault Stator resistance setting fault P409.	Cause: Stator resistance value in parameter P409 does not comply with the inverter power capacity. Motor connection error. Motor power is configured too low or too high in relation to the inverter size. Remedy: Turn off the power supply and inspect all connections at the motor terminal box. Verify if the stator resistance parameter P409 and motor power parameters are correctly scaled.
A046 Motor Overload Motor overload alarm.	Cause: Settings of parameter P156 are configured too low for the used motor. Overload on the motor shaft. Remedy: Check current rating parameter P156 configuration. Inspect motor shaft and load for mechanical overload/blockages.
A050 IGBTs Overtemperatures Overtemperature alarm from the power module temperature sensor (NTC).	Cause: High temperature at the IGBTs (parameter P030 exceeds Level A050, according to Table 11.2 on page 11-4). High ambient temperature around the inverter and high output current. Blocked or defective cooling fan. Heatsink is dirty, preventing proper cooling airflow. Remedy: Check the current temperature in parameter P030. Improve airflow around the drive or lower ambient room temperature. Clear any dust or debris build-up from the heatsink fins. Verify fan operation.
F051 IGBTs Overtemperatures Overtemperature fault measured on the temperature sensor of the power pack.	Cause: High temperature at the IGBTs (parameter P030 exceeds Level F051, according to Table 11.2 on page 11-4). High ambient temperature around the inverter and high output current. Blocked or defective cooling fan. Heatsink is dirty, preventing proper cooling airflow. Remedy: Check temperature via parameter P030. Inspect the cooling fan and clean the heatsink fins. Improve room ventilation.
F067 Incorrect Encoder/ Motor Wiring Fault related to the phase relation of the encoder signals.	Cause: Output motor cables U, V, W are inverted. Encoder channels A and B are inverted. Encoder was not properly mounted. Remedy: Verify the sequence of output motor phases U, V, W and encoder channels A and B. Check the physical mounting of the encoder.
F070 Overcurrent/Shortcircuit Overcurrent or short-circuit on the output, DC Link, or braking resistor.	Cause: Short-circuit between two motor phases. IGBTs module is short-circuited or damaged. Drive started with an acceleration ramp that is too short. Drive started with the motor already spinning without using the Flying Start function. Remedy: Verify motor winding and connection cables for phase-to-phase shorts. Increase the acceleration ramp time. Enable the Flying Start function if the motor is prone to rotating during startup.
F072 Motor Overload Motor overload fault.	Cause: Parameter P156, P157, or P158 setting is configured too low in relation to the motor's operating current. Overload on the motor shaft. Remedy: Check and adjust the motor nominal current values in parameters P156, P157, or P158. Check the motor shaft and driven load for mechanical blockages or excessive friction.
F078 Motor Overtemperature Overtemperature fault measured on the motor temperature sensor (Triple PTC) via analog input AIx.	Cause: Overload on the motor shaft. Load cycle is too high (high number of starts and stops per minute). High ambient temperature around the motor. Poor contact or short-circuit (3k9 < RPTC < 0k1). Motor thermistor is not installed. Motor shaft is stuck. Remedy: Inspect motor shaft for binding/sticking. Check duty cycles. Measure thermistor loop resistance (ensure it is within correct normal ranges).
F079 Encoder Signal Fault Fault of encoder signals absent.	Cause: Wiring between encoder and interface accessory to encoder is broken. Encoder is defective. Remedy: Check encoder wiring for breaks or loose connections. Test the encoder and verify the mounting of the encoder accessory board.
F080 CPU Fault (Watchdog) Fault related to the supervision algorithm of the inverter main CPU.	Cause: High electrical noise. Inverter firmware fault. Remedy: Inspect the installation grounding and shield connections to mitigate electrical noise. Update the control unit firmware if the issue is recurring.
F081 End of User’s Memory Fault of end of memory to save user’s parameter table.	Cause: Attempted to save (parameter P204 = 9) more than 32 parameters with values different from the factory default on the User parameter table. Remedy: Limit custom user parameters with non-default values to 32 items or less within the User parameter table configuration.
F082 Fault in Data Transfer (MMF) Fault in data transfer using MMF accessory.	Cause: Attempt to download data from the flash memory module to the inverter with the inverter energized/running. Attempt to download a SoftPLC application incompatible with the destination inverter. Problems saving data downloaded to the inverter. Remedy: Ensure the inverter is not in run state before downloading. Verify SoftPLC application compatibility.
F084 Auto-diagnosis Fault Fault related to the automatic identification algorithm of the inverter hardware.	Cause: Poor contact in the connection bridge between the main control board and the power pack. Hardware components are incompatible with the firmware version. Defect detected in the internal circuits of the inverter. Remedy: Check the connection and alignment of the boards inside the drive. Ensure firmware compatibility. Contact technical support if an internal hardware defect is suspected.
A090 External Alarm External alarm via DIx (option “no external alarm” in P263 to P270).	Cause: Wiring on digital inputs DI1 through DI8 is open or has poor contact. Remedy: Inspect connection terminals for digital inputs DI1 through DI8. Tighten any loose screws and ensure clean wire contact on the terminal strip.
F091 External Fault External fault via DIx (“no external fault” in P263 to P270).	Cause: Wiring on digital inputs DI1 through DI8 is open or has poor contact. Remedy: Verify external cabling loops to the assigned digital inputs. Tighten loose screw terminals and check contact switches.
A128 Telegram Reception Timeout It indicates that the device stopped receiving valid telegrams for a period longer than the setting in P314. The time counting starts as soon as it receives the first valid telegram, with correct address and error-checking field.	Cause: Issues in the network installation, broken cable, or poor contact on the network connections/grounding. The master controller is not sending telegrams within the time window set in parameter P314. Remedy: Check communication cable paths, shield grounding, and terminal blocks. Ensure the polling rate of the master controller is faster than the timeout set in P314. Alternatively, disable this timeout function by adjusting parameter P314.
A133 No Power Supply on the CAN Interface It indicates that the CAN interface has no power supply between pins 25 and 29 of the connector.	Cause: Power supply cables are misconnected or inverted. Poor contact on the cable or connector of the CAN interface. Remedy: Measure the voltage on the CAN interface connector to verify it falls within the permitted range between pins 25 and 29. Ensure external power lines are secure and correctly polarized.
A134 Bus Off Bus off error detected on the CAN interface.	Cause: Short circuit on the CAN circuit transmission cable. CAN cables are misconnected or inverted. Mismatched baud rates among network devices. Improperly placed termination resistors (should only be installed at the physical ends of the main bus). Incorrectly installed CAN network. Remedy: Check CAN high and low wires for short circuits or inverted lines. Verify that all nodes on the network are configured with the same communication baud rate. Check termination resistor values and placement.
A135 Node Guarding/ Heartbeat CANopen communication error control detected communication error using the guarding mechanism.	Cause: Mismatched message exchange times between the master and slave. Master controller is not sending the guarding telegrams within the assigned interval. Transmission delays or signal loss on the communication line. Remedy: Check the times set on both the master and slave nodes. To prevent delay conflicts, configure the error detection time on the slave to be a multiple of the master's exchange interval. Verify the master's active polling state.
A136 Idle Master Alarm indicates that the DeviceNet network master is in Idle mode.	Cause: The master operation switch or run-bit is in the IDLE state in the host software. Remedy: Configure the master switch or corresponding bit to RUN in the configuration word of the master software. Refer to specific master software documentation.
A137 DeviceNet Connection Timeout Alarm that indicates that one or more DeviceNet connections timed out.	Cause: Problem with the network master status. Issues in the network installation, broken cable, or poor contact on the network connections/grounding. Remedy: Verify the DeviceNet master status. Check general cable routing, connection shield lines, and grounding terminals.
A138 Profibus DP Interface in Clear Mode It indicates that the inverter received the command from the Profibus DP network master to go into clear mode.	Cause: The network master status is not in run mode. Remedy: Verify the network master status, making sure it is in execution mode (Run). Refer to the Profibus DP communication manual for more information.
A139 Offline Profibus DP Interface It indicates interruption in the communication between the Profibus DP network master and the inverter. The Profibus DP communication interface went into offline status.	Cause: The network master is not configured or operating normally. Short circuit or loose contact on the communication cables. Cables are misconnected or inverted. Improperly placed termination resistors (should only be installed at the physical ends of the main bus). Profibus DP network cable routing or grounding is inadequate. Remedy: Check the PLC state. Check general cable routing, connection shield lines, and grounding terminals. Refer to the Profibus DP communication manual.
A140 Profibus DP Module Access Error It indicates error in the access to the Profibus DP communication module data.	Cause: The Profibus DP module is not seated properly in the slot. Hardware errors due to improper handling or installation of the accessory module. Remedy: Verify whether the Profibus DP module is correctly fitted. Swap modules if handling or installation errors caused defective pins on the interface board.
A147 EtherNet/IP Communication Offline It indicates interruption in the cyclic communication with EtherNet/IP master. It occurs when, for any reason, after the cyclic communication of the master with the product is started, this communication is interrupted.	Cause: Status of the network master has entered offline or fault state. Network installation issue, broken cable, or failed/bad contact in the network connections. Remedy: Verify the status of the network master controller. Inspect network cables for breaks or damage, and ensure all RJ45 or terminal block connections are secure.
A149 Timeout Modbus TCP It indicates that the device stopped receiving valid telegrams for a period longer than the setting in P868. The time counting starts as soon as it receives the first valid telegram.	Cause: Network installation issue, broken cable, or fault/poor contact on the connections with the network or grounding. The Modbus TCP client is not actively sending telegrams to the equipment in a time shorter than the setting in parameter P868. Remedy: Verify network cabling, connectors, and grounding paths. Ensure the master/client is programmed to send polling telegrams faster than the timeout interval set in parameter P868, or disable this timeout check in parameter P868.
A163 Signal Fault AI1 4...20 mA Analogue input signal AI1 at 4 to 20 mA or 20 to 4 mA is below 2 mA.	Cause: Current signal on the analogue input AI1 is interrupted or null. Parameterization error on analogue input AI1. Remedy: Check current loop wiring on analogue input AI1 for breaks or open circuits. Verify terminal screw contacts and parameter configuration settings for AI1.
A164 Signal Fault AI2 4...20 mA Analogue input signal AI2 at 4 to 20 mA or 20 to 4 mA is below 2 mA.	Cause: Current signal on the analogue input AI2 is interrupted or null. Parameterization error on analogue input AI2. Remedy: Check current loop wiring on analogue input AI2 for breaks or open circuits. Verify terminal screw contacts and parameter configuration settings for AI2.
A177 Replace Fan Alarm to replace the fan (P045 > 50000 hours).	Cause: Maximum number of operation hours of the heatsink fan has been exceeded. Remedy: Replace the heatsink cooling fan as part of scheduled preventative maintenance to prevent drive overtemperature issues.
F182 Pulse Feedback Failure Pulse feedback circuit fault of the output voltage.	Cause: Hardware identification fault (compare P295 and P296 to the inverter identification label). Inverter internal pulse feedback circuit fault. Remedy: Verify that parameters P295 and P296 match the ratings listed on the inverter's product label. If internal circuits are not defective, this monitoring can be disabled in parameter P397.
A211 Drive in Fire Mode Indicates that the drive is in Fire Mode.	Cause: The digital input programmed for activating the Fire Mode is active. Remedy: Check the status of the digital input assigned to activate the Fire Mode. Confirm that external switch logic is correct and not stuck in the active state.
F228 Timeout in Receipt of Telegrams It indicates that the device stopped receiving valid telegrams for a period longer than the setting in P314. The time counting starts as soon as it receives the first valid telegram, with correct address and error-checking field.	Cause: Network installation issue, broken cable, or fault/poor contact on the connections with the network or grounding. The master controller is not sending telegrams within the time window set in parameter P314. Remedy: Check serial communication cables, connectors, and shield grounding lines. Ensure the master's polling interval is shorter than parameter P314, or disable this timeout check in parameter P314.
F233 No Power Supply on the CAN Interface It indicates that the CAN interface has no power supply between pins V(-) and V(+) of the connector.	Cause: The power supply cables are misconnected or inverted. Contact problems on the cable or connector of the CAN interface. Remedy: Measure if there is voltage within the allowed range between pins V(-) and V(+) of the CAN interface connector. Check terminal strip alignment and cable contact.
F234 Bus Off Bus off error detected on the CAN interface.	Cause: Short circuit on the CAN circuit transmission cable. Cables are misconnected or inverted. Not all network devices are configured with the same communication baud rate. Termination resistors with the right specification were not installed correctly (should only be at the physical ends of the main bus). CAN network was improperly installed. Remedy: Check CAN high and low lines for short circuits or inverted signals. Match node baud rates across the network. Check termination resistor values and placement.
F235 Node Guarding/ Heartbeat CANopen communication error control detected communication error using the guarding mechanism.	Cause: Mismatched message exchange times between the master and slave. Master controller is not sending guarding telegrams within the assigned interval. Transmission delays or signal loss on the communication line. Remedy: Check times configured on both master and slave. To prevent conflicts, set the slave's error detection time to be a multiple of the master's exchange interval. Verify guarding telegram transmission.
F236 Idle Master Fault indicates that the DeviceNet network master is in Idle mode.	Cause: The master operation switch or run-bit is in the IDLE state in the host software. Remedy: Configure the master switch or corresponding bit to RUN in the configuration word of the master software. Refer to the documentation of the master device used.
F237 DeviceNet Connection Timeout Fault that indicates that one or more DeviceNet connections timed out.	Cause: Problem with the network master status. Issues in the network installation, broken cable, or poor contact on the network connections/grounding. Remedy: Verify the DeviceNet master status. Check general cable routing, connection shield lines, and grounding terminals.
F238 Profibus DP Interface in Clear Mode It indicates that the inverter received a command from the Profibus DP network master to enter the clear mode.	Cause: The network master status is not in run mode. Remedy: Verify the network master status, making sure it is in execution mode (Run).
F239 Offline Profibus DP Interface It indicates an interruption in the communication between the Profibus DP network master and the inverter. The Profibus DP communication interface went into offline status.	Cause: The network master is not configured or operating normally. Short circuit or loose contact on the communication cables. Cables are misconnected or inverted. Improperly placed termination resistors (should only be installed at the physical ends of the main bus). Profibus DP network cable routing or grounding is inadequate. Remedy: Check the PLC state. Check general cable routing, connection shield lines, and grounding terminals. Refer to the Profibus DP communication manual.
F240 Profibus DP Module Access Fault It indicates fault in the access to the Profibus DP communication module data.	Cause: The Profibus DP module is not seated properly in the slot. Hardware errors due to improper handling or installation of the accessory module. Remedy: Verify Profibus module mounting in slot. Replace communication module if handling errors damaged the pins.
F247 EtherNet/IP Communication Offline It indicates interruption in the cyclic communication with EtherNet/IP master. It occurs when, for any reason, after the cyclic communication of the master with the product is started, this communication is interrupted.	Cause: Status of the network master has entered offline or fault state. Network installation issue, broken cable, or failed/bad contact in the network connections. Remedy: Verify the status of the network master controller. Inspect network cables for breaks or damage, and ensure all RJ45 or terminal block connections are secure.
F249 Timeout Modbus TCP It indicates that the device stopped receiving valid telegrams for a period longer than the setting in P868. The time counting starts as soon as it receives the first valid telegram.	Cause: Network installation issue, broken cable, or fault/poor contact on the connections with the network or grounding. The Modbus TCP client is not actively sending telegrams to the equipment in a time shorter than the setting in parameter P868. Remedy: Verify network cabling, connectors, and grounding paths. Ensure the master/client is programmed to send polling telegrams faster than the timeout interval set in parameter P868, or disable this timeout check in parameter P868.
A700 Remote HMI Communication No communication with remote HMI, but there is no frequency command or reference for this source.	Cause: HMI cable is disconnected. Communication interface with the HMI is incorrectly configured in parameter P312. Remedy: Check parameter P312 to verify that the HMI communication interface is configured correctly. Reconnect or replace the HMI serial cable.
F701 Remote HMI Communication Fault No communication with the remote HMI; however, there is command or frequency reference for this source.	Cause: HMI cable is disconnected. Communication interface with the HMI is incorrectly configured in parameter P312. Remedy: Check parameter P312 to verify that the HMI communication interface is configured correctly. Reconnect or replace the HMI serial cable.
A702 Inverter Disabled This failure occurs when there is a SoftPLC movement block (REF block) active and the “General Enable” command is disabled.	Cause: The General Enable command for the drive is not active. Remedy: Check the drive control terminal states to ensure the General Enable input command is active.
A704 Two Movem. Enabled It occurs when 2 or more SoftPLC movement blocks (REF Block) are enabled at the same time.	Cause: Logic block overlap in the user program. Remedy: Check the user’s SoftPLC program logic to ensure only one movement block is active at any given time.
A706 Refer. Not Progr. SPLC This failure occurs when a SoftPLC movement block is enabled and the speed reference is not programmed for the SoftPLC.	Cause: Speed reference is missing or incorrectly routed in the configuration. Remedy: Check and verify the speed reference configuration in parameters P221 and P222 (Local and Remote modes).
A708 SoftPLC Application Stopped SoftPLC Application not running.	Cause: SoftPLC Application is stopped (parameters set as: P901 = 0 and P900 = 3). SoftPLC application code is incompatible with the firmware version of the frequency inverter. Remedy: Verify parameter settings for P900/P901. Ensure the application code is compatible with the inverter's active firmware version.
F709 SPLC Application Stopped SoftPLC application not running.	Cause: SoftPLC Application is stopped (parameters set as: P901 = 0 and P900 = 3). SoftPLC application code is incompatible with the firmware version of the frequency inverter. Remedy: Verify parameter configurations for P900 and P901. Upload a compatible version of the SoftPLC application.
F710 Size of the SoftPLC Application The size of the SoftPLC user’s program exceeded the maximum memory capacity.	Cause: The program size of the SoftPLC logic is too large. Remedy: Check project size. Optimize and compress the SoftPLC code structure to fit within permitted memory limits.
F711 Fault on SoftPLC Application Fault found in SoftPLC user’s program.	Cause: SoftPLC user’s program stored on flash memory is corrupted. Timeout during execution of SoftPLC scan cycle. Remedy: Reload the user program onto the flash memory. Optimize program execution routines to prevent scan cycle timeouts.
A712 SPLC Protected Against Copy It occurs when there is an attempt to copy the SoftPLC application protected against copies.	Cause: Attempting to copy a WLP application protected with "never permit copies" rules. Attempting to copy a WLP application protected with "no permission to copy from a copy" rules. Remedy: Verify the copyright and permission settings of the WLP application you are trying to manage.
F750/A750 to F799/A799 User’s Faults/Alarms for SoftPLC Fault/Alarm range intended for the user’s application developed in the SoftPLC function.	Cause: Condition defined inside the user's specific application block programmed in the SoftPLC. Remedy: Check the custom user application documentation developed within the SoftPLC environment.
A750 Sleep Mode Active It indicates that the PID Controller is in the sleep mode.	Cause: The motor speed remained below the value programmed in P938 for the time programmed in P939. Remedy: Check the system demand. Verify sleep mode parameters P938 (sleep speed) and P939 (sleep time) configurations.
A760 Low Level of the Control Process Variable It indicates that the level of the control process variable (P916) is low.	Cause: The control process variable (P916) remained below the value programmed in P924 for 150 ms. Remedy: Check the process loop and ensure the feedback sensor/variable matches configured limits. Adjust P924 if necessary.
F761 Low Level of the Control Process Variable It indicates the motor was switched off due to the low level of the control process variable.	Cause: The control process variable (P916) remained below the value programmed in P924 for a certain time (P925). Remedy: Analyze the process loop. Inspect sensors and feedback lines. Check parameter values for P924 and P925.
A762 High Level of the Control Process Variable It indicates that the level of the control process variable (P916) is high.	Cause: The control process variable (P916) remained above the value programmed in P926 for 150 ms. Remedy: Analyze system pressure/flow limits. Check parameter P926 and adjust if necessary.
F763 High Level of the Control Process Variable It indicates the motor was switched off due to the high level of the control process variable.	Cause: The control process variable (P916) remained above the value programmed in P926 for a certain time (P927). Remedy: Check the process line and analyze the system design. Adjust values in parameters P926 and P927 as needed.
A790 Speed reference source not programmed for the SoftPLC It indicates that parameters of the speed reference sources in local mode (P221) and in remote mode (P222) were not programmed for the SoftPLC.	Cause: The PID Controller was enabled, the Run/Stop command is active, and neither of the two parameters of the speed reference source was programmed in 12 (SoftPLC). Remedy: Ensure parameters of the speed reference sources in local mode (P221) and remote mode (P222) are set to 12 (SoftPLC) to allow correct control.

Decoding "SUB" Warnings and "Config" Errors

In addition to standard Fxxx and Axxx codes, the CFW300 displays specific status messages that often puzzle operators :

1. The "SUB" Status Indication

If your display reads "SUB", the drive is in an undervoltage state . This occurs when the DC bus voltage drops below the minimum operating threshold (typically around 200V for 230V single-phase models) . It generally points to low input utility voltage or a temporary mains sag . Once the voltage rises above the minimum threshold, the "SUB" message clears, though repeated drops can trigger a hard F021 undervoltage fault .

2. The "Config" Error

If the drive display scrolls "config", the drive's output is blocked because of an incompatible parameter setting . You do not need to guess the issue; you can find the exact configuration mismatch by reading Parameter P0047 . For example, if Parameter P0047 displays a value of "4", it indicates that two or more digital inputs have been programmed to the "STOP" function simultaneously .

How to Safely Reset a WEG CFW300 Fault

Before clearing any fault, make sure you have addressed the underlying cause of the trip. The CFW300 offers several reset pathways :

1. Keypad Reset: Press the red O/RESET key on the integrated HMI .
2. Digital Input Reset: If using an I/O expansion module (such as the CFW300-IODR) , you can configure a digital input to trigger a reset on transition.
3. Power Cycle: Disconnect the incoming main power supply . Safety Requirement: Wait at least 10 minutes to allow the internal DC-link capacitors to discharge to a safe voltage level before handling wiring or restoring power .
4. Serial/USB Communication Reset: If utilizing Modbus RTU or another communication interface, toggle Bit 7 of the control word to trigger a fault reset remotely .

Most Common CFW300 Faults and Troubleshooting

The vast majority of field trips on the CFW300 are caused by a small group of faults:

1. F070 (Overcurrent / Short Circuit)

F070 occurs if the drive detects current levels far exceeding its rated threshold . This can be caused by a phase-to-phase short in the motor windings, damaged output cabling, or an acceleration ramp time that is set too short for a heavy mechanical load .

• Diagnostic: Power down the drive, disconnect the motor cables, and attempt to run the drive with no motor connected . If the F070 fault clears when running disconnected, the problem lies in your motor or cabling . If the fault persists, try increasing the acceleration ramp time (Parameter P0100) .

2. F021 (Undervoltage) & F022 (Overvoltage)

These faults indicate that the internal DC bus voltage has slipped outside its safe operating window :

• F021 (Undervoltage): Usually follows a severe line voltage sag or mains loss . Check the input voltage using a digital multimeter .
• F022 (Overvoltage): Often occurs during quick deceleration of a high-inertia load . Try increasing the deceleration ramp time (Parameter P0101) or add a dynamic braking resistor if your drive model supports it .

3. F072 (Motor Overload)

This thermal trip is triggered if the motor operates above its rated current for an extended period . The drive uses internal algorithms to calculate heat buildup based on parameter configurations .

• Diagnostic: Ensure that Parameter P0401 (Motor Rated Current) is configured to match the physical motor's nameplate rating . Check for any mechanical friction or binding on the driven load.

Best Practices to Avoid CFW300 Drive Trips

Because the CFW300 is designed for a compact footprint, keeping its operating environment stable prevents many common faults :

• Ensure Zero-Stack Clearances are Maintained: While the CFW300 supports side-by-side (zero-stack) mounting , make sure there is sufficient vertical clearance above and below the unit to allow natural convective heat transfer .
• Isolate Sensor Signals: Keep control and analog signal cables physically separated from high-voltage motor lines to prevent electrical noise from causing intermittent alarms .
• Periodically Check Terminal Screw Torques: Loose connections due to heat cycles or vibrations can lead to local hot spots, triggering undervoltage or phase loss faults .

By keeping the CFW300’s parameters properly configured and performing basic preventive care, you can ensure smooth motor control and a longer service life for your drive .