Year: 2026

1. Fault Overview

Schneider ATV340 series variable frequency drives are widely used in industrial applications such as conveyors, hoisting systems, centrifuges, winding machines, fans, pumps, and other equipment with medium or high inertia loads. In applications requiring fast deceleration, the drive often needs an external braking resistor. During deceleration, the motor may enter a regenerative state and feed energy back into the DC bus. If this energy is not dissipated in time, the DC bus voltage rises and may eventually cause overvoltage faults or damage to the power stage.

A Schneider ATV340D37N4E drive was received for repair after the customer reported a bUF braking unit short-circuit fault at the site. After the drive was brought back for bench testing, normal start and stop operation appeared to be fine. The motor could run, and no obvious abnormality was observed during ordinary operation. However, when the deceleration time was set very short, the drive triggered the braking unit short-circuit fault.

Further testing showed that this model has a parameter related to braking unit detection or braking function enablement. When this function was enabled, the drive reported a braking unit short-circuit fault during fast deceleration. When the braking function was disabled, the drive no longer generated the fault even under fast stop conditions.

At first glance, this appeared to be a typical external braking resistor fault, braking transistor fault, or braking IGBT short circuit. However, the actual repair process proved that the braking IGBT power device itself was not the root cause. The real fault was located in the DESAT detection circuit of the intelligent IGBT driver optocoupler used for the braking IGBT.

The final diagnosis confirmed that resistor R704, connected to the DESAT pin of the TLP5214A intelligent IGBT driver optocoupler, had become abnormally high resistance or open circuit. Its correct value should be 681, meaning 680Ω, but the faulty board measured more than 10MΩ, effectively open circuit. After replacing R704 with a 680Ω resistor, the braking function returned to normal, fast stop testing passed, and the bUF braking unit short-circuit fault disappeared.

This case is highly representative. It shows that when troubleshooting a braking unit short-circuit fault, technicians should not only check whether the braking IGBT is shorted with a multimeter, nor should they only focus on the external braking resistor value. In circuits using intelligent gate drivers and DESAT protection, an open, leaky, contaminated, or drifted detection circuit can also cause the drive to falsely report a braking unit short circuit.

2. Basic Working Principle of the Braking Unit

In an inverter drive such as the ATV340, when the motor decelerates a high-inertia load, the motor may act as a generator. Mechanical energy is converted into electrical energy and fed back into the DC bus through the inverter bridge. This causes the DC bus voltage to rise. If the voltage rises beyond the protection threshold, the drive will trip on DC bus overvoltage. In severe cases, power components may be damaged.

The braking unit is used to dissipate this regenerative energy. When the DC bus voltage reaches the braking threshold, the drive turns on the braking IGBT. Current flows through the external braking resistor, converting the excess electrical energy into heat.

A typical braking current path is:

P/+ DC bus positive → braking resistor → PB terminal → braking IGBT → N/- DC bus negative

When the braking IGBT is off, the PB terminal is not pulled toward N/-, and almost no braking current flows through the resistor. When the braking IGBT turns on, PB is pulled down toward N/-, current flows through the braking resistor, and the regenerative energy is dissipated.

Therefore, whether the braking unit works correctly depends on several factors:

1. The resistance and power rating of the external braking resistor;
2. The reliability of the P/+, PB, and N/- power connections;
3. Whether the braking IGBT turns on and off correctly;
4. Whether the braking IGBT gate drive is normal;
5. Whether the overcurrent, short-circuit, and DESAT detection circuits are normal;
6. Whether the control board correctly receives the braking unit fault feedback signal.

In practical repairs, the first two items are relatively easy to check. The third can also be roughly checked with a multimeter. However, the fourth, fifth, and sixth items require deeper understanding of the gate driver optocoupler, DESAT detection, FAULT feedback, and dynamic waveforms.

3. Common Causes of bUF Braking Unit Short-Circuit Fault

When a drive reports a braking unit short-circuit fault, the common causes can be grouped into the following categories.

3.1 External Braking Resistor Value Too Low

If the braking resistor value is lower than the minimum value allowed by the drive, the current through the braking IGBT becomes excessive as soon as the IGBT turns on. The driver or protection circuit may then immediately report a braking transistor short circuit or braking unit fault.

For a 400V-class drive, the DC bus voltage is commonly around 540V to more than 700V, especially during deceleration. If the braking resistor value is too low, the instantaneous braking current can become very high, placing excessive electrical and thermal stress on the braking IGBT.

3.2 Braking Resistor Wiring Short Circuit or Ground Leakage

Incorrect wiring between P/+ and PB, damaged braking resistor cables, carbonized terminals, loose connections, or ground leakage in the braking resistor box can all cause abnormal braking circuit behavior. In environments with moisture, dust, oil mist, or conductive contamination, insulation failure at the resistor terminals and cables is especially common.

3.3 Braking IGBT Collector-Emitter Short Circuit

This is the most direct cause. If the braking IGBT collector and emitter are shorted, PB is effectively pulled toward N/- continuously. Once the braking resistor is connected, an abnormal current path may exist from P/+ to N/- through the resistor. This type of fault can often be detected with a multimeter in diode or resistance mode.

3.4 Braking IGBT Gate Leakage or Abnormal Gate Drive

Some IGBTs do not fail as a direct C-E short. Instead, the gate insulation may degrade, the G-E path may leak, or the gate resistor, gate clamp, or turn-off circuit may become abnormal. In such cases, the IGBT may partially turn on when it should remain off, or it may fail to saturate properly when it should conduct.

These faults are not always easy to detect with a normal multimeter.

3.5 Driver Optocoupler Failure or Driver Power Supply Abnormality

Medium and high-power drives usually use isolated driver optocouplers or intelligent gate driver chips to drive IGBTs. The braking IGBT is no exception. If the driver output voltage is too low, negative turn-off voltage is abnormal, or the driver supply decoupling capacitor has failed, the IGBT may not turn on fully or may turn off incorrectly.

3.6 DESAT Detection Circuit Abnormality

This is the core issue in this case.

Many intelligent IGBT driver optocouplers include DESAT protection. DESAT detection is used to determine whether an IGBT has entered normal saturation when it is commanded to turn on. If the IGBT receives a gate drive command but the C-E voltage remains too high, it may indicate short circuit, overcurrent, insufficient gate drive, module failure, or load abnormality. The driver chip then quickly shuts down the IGBT and outputs a fault signal.

However, if the DESAT detection circuit itself is open, leaky, contaminated, drifted, or has a cracked solder joint, the driver chip may falsely detect desaturation even when the IGBT is actually normal. The result is a false braking unit short-circuit fault.

4. Diagnostic Process in This Case

4.1 Fault Condition Confirmation

The ATV340D37N4E could run normally under ordinary conditions. Normal start and stop operation did not produce any abnormal alarm. The bUF braking unit short-circuit fault appeared only when the deceleration time was set very short and the braking unit participated in energy dissipation.

This indicated that the main inverter bridge, current detection circuit, control logic, and auxiliary power supply were unlikely to be the primary fault areas. If the main inverter bridge or the main DC power stage had a serious defect, the drive would likely report overcurrent, short circuit, undervoltage, phase loss, or drive faults even during ordinary operation.

Since the fault was strongly associated with fast deceleration and braking unit activation, the diagnostic focus was shifted to the braking circuit.

4.2 External Braking Resistor Check

During bench testing, a temporary resistance wire of approximately 10Ω was connected between P/+ and PB to simulate the braking resistor, and the same fault could be reproduced. Although a temporary resistance wire is not equivalent to a standard braking resistor in every aspect, the customer’s site also reported the same fault with a standard braking resistor. Therefore, the external resistor itself was not considered the main suspect.

In real repair practice, the following items should still be checked:

• Actual braking resistor resistance;
• Whether the resistance is below the minimum value allowed by the drive;
• Braking resistor power rating;
• Wiring reliability between P/+ and PB;
• Insulation resistance of the braking resistor to ground;
• Cable damage, loose terminals, overheating, carbonization, or arcing marks.

In this case, because the same fault occurred with the customer’s standard braking resistor and the temporary resistor was only used to reproduce the fault, the investigation continued inside the drive, focusing on the braking IGBT driver circuit.

4.3 Braking IGBT Inspection

The braking IGBT module was checked using conventional methods. No obvious C-E short circuit, G-E short circuit, or severe leakage was found. Based on standard repair experience, the braking IGBT appeared normal in static testing.

However, this point must be emphasized:

A normal static IGBT test does not prove that the IGBT and its protection circuit will behave normally under dynamic braking conditions.

DESAT faults usually occur at the instant when the IGBT is driven on. Only when the braking IGBT is under high DC bus voltage, carrying braking current, and controlled by the gate driver will dynamic problems such as desaturation, insufficient drive, or detection circuit failure appear.

Therefore, relying only on a diode-mode multimeter test of the IGBT can easily lead to an incorrect conclusion.

4.4 Misleading Comparison with an ATV610 Control Board

During troubleshooting, an ATV610 control board was used for comparison. Since some ATV610 and ATV340 power boards, driver boards, and modules may look similar or share similar hardware structures, it was tempting to conclude that if the ATV610 board did not trigger the fault, the power board must be normal.

Further analysis showed that this comparison was not decisive. The ATV610 control board did not have the same braking detection or braking function logic as the ATV340. It may not have actually triggered the braking IGBT in the same way, or it may not have monitored the braking unit fault feedback in the same manner.

Therefore, the fact that the ATV610 board did not report the same fault could not be used as proof that the braking driver circuit was healthy.

This is an important lesson. Even if two drive series share similar hardware platforms, their firmware logic, alarm judgment, drive enable conditions, and fault feedback processing may be different. A drive not reporting a fault does not necessarily mean that the tested power board is fully normal.

4.5 Locking the Fault Area to the TLP5214A and DESAT Circuit

The braking driver section of the board used a TLP5214A intelligent IGBT driver optocoupler. This device is not an ordinary optocoupler. It integrates IGBT gate drive, undervoltage protection, soft shutdown, fault feedback, and DESAT detection.

Pin 14 of the TLP5214A is the DESAT detection pin. When the IGBT is turned on, the DESAT pin monitors the IGBT C-E voltage through an external diode, resistor, and capacitor network. If the detected voltage exceeds the internal threshold, the driver interprets this as IGBT desaturation, shuts down the output, and sends a fault signal through the FAULT pin.

Around the TLP5214A DESAT pin, components such as R703, R704, D705, and C708 were identified. R704 was found to be related to the DESAT path. Its measured resistance was more than 10MΩ, clearly abnormal.

To confirm the expected value, a 55kW drive driver board was used for comparison. The corresponding positions on the comparison board showed the following resistor markings:

• R704: 681, meaning 680Ω;
• R703: 472, meaning 4.7kΩ.

On the faulty board, R703 measured around 5kΩ, consistent with 4.7kΩ. However, R704 measured more than 10MΩ, completely inconsistent with the expected 680Ω. This strongly indicated that R704 was open circuit or had failed to a very high resistance.

5. Why an Open R704 Causes a Braking Unit Short-Circuit Fault

When technicians see the alarm description “braking unit short circuit,” the first reaction is often to suspect a shorted braking IGBT or shorted braking resistor. However, in a circuit using DESAT detection, the alarm name does not always mean that there is a physical short circuit. It may be the result of the intelligent driver detecting an abnormal protection condition.

Under normal operation, when the braking IGBT is turned on:

1. The control board sends a braking IGBT drive command;
2. The TLP5214A outputs the gate drive voltage;
3. The braking IGBT turns on normally;
4. PB is pulled toward N/-;
5. The IGBT C-E voltage drops to a low value;
6. The DESAT detection circuit confirms that the IGBT has entered saturation;
7. The driver optocoupler does not output a fault signal, and braking proceeds normally.

When R704 is open:

1. The control board sends a braking IGBT drive command;
2. The TLP5214A outputs the gate drive;
3. The braking IGBT may actually turn on normally;
4. But the DESAT detection path loses its normal sampling or clamping function because R704 is open;
5. The internal DESAT charging current inside the TLP5214A causes the DESAT pin voltage to rise abnormally;
6. The driver falsely determines that the IGBT has not entered saturation;
7. The TLP5214A shuts down the output and sends a FAULT signal;
8. The control board receives the braking unit fault feedback and displays bUF / braking unit short circuit.

Therefore, the real problem in this case was not an actual shorted braking IGBT. It was a false braking unit short-circuit fault caused by an open DESAT detection resistor.

Typical characteristics of this type of fault include:

• Normal ordinary running;
• Normal ordinary stopping;
• Fault appears only when the braking unit is activated;
• Disabling the braking function makes the fault disappear;
• Braking IGBT passes static testing;
• External braking resistor is normal;
• DESAT circuit components show open circuit, drift, leakage, cracked solder joints, or contamination.

6. Repair Procedure

The final repair procedure in this case was as follows:

1. Lift or remove one side of R704 and confirm its abnormal resistance;
2. Compare with a similar driver board and confirm the correct value of R704 as 681, meaning 680Ω;
3. Replace R704 with a 680Ω SMD resistor;
4. Clean the area around TLP5214A, R703, R704, D705, and C708;
5. Reflow or resolder relevant TLP5214A pins, especially DESAT, VOUT, VCC2, VE, and VEE pins;
6. Check connector S23 and its solder joints to ensure reliable connection to the braking IGBT circuit;
7. Reassemble and test the drive;
8. Enable the braking function, perform fast deceleration testing, and verify that the bUF fault no longer appears.

After R704 was replaced, the drive passed fast stop testing. The braking unit worked normally, and the fault was eliminated.

7. Key Measurement Points for Similar Faults

For similar braking unit short-circuit faults, the following diagnostic sequence is recommended.

7.1 External Braking Resistor

Measure the resistance between P/+ and PB. Confirm that the resistor value is not below the minimum allowed value for the drive. Also inspect the resistor box, cable, terminals, and insulation to ground.

7.2 Static Test of the Braking IGBT

After power is removed and the DC bus capacitors are fully discharged, check the braking IGBT C-E, G-E, and G-C paths for short circuit or leakage. If an obvious short circuit is present, the power device must be handled first.

7.3 Gate Drive Voltage

Under safe test conditions, observe the braking IGBT G-E voltage at the instant of braking. During conduction, a gate drive voltage of around +15V is typically expected. During turn-off, the voltage may be 0V or negative depending on the driver design.

7.4 TLP5214A FAULT Pin

Observe whether the FAULT pin of the TLP5214A changes state when the fault occurs. If the FAULT pin is pulled low, the driver itself has detected an abnormal condition. If the FAULT pin does not change but the control board still reports a braking unit fault, then the control board’s fault feedback input circuit should be checked.

7.5 DESAT Pin and Peripheral Circuit

Focus on the DESAT-related components connected to pin 14 of the TLP5214A, including the series resistor, sampling diode, blanking capacitor, clamping components, and solder joints. In this case, R704 was the key component.

7.6 Connectors and Solder Joints

The braking IGBT driver signal is often transmitted through a small connector. Loose connectors, cracked solder joints, oxidation, poor contact, or damaged harnesses may cause abnormal gate drive or abnormal detection signals.

8. Why a Small Resistor Can Cause a Major Fault

R704 is only a small SMD resistor with a value of 680Ω. However, because it is located in the DESAT detection path of the braking IGBT driver, it has a critical protection role.

A drive protection system does not only determine whether a large power device is physically shorted. It depends on many small signal detection circuits to judge whether the power stage is operating safely.

In the high-voltage, high-current, and high-dv/dt environment of a variable frequency drive, the intelligent driver optocoupler must quickly determine whether the IGBT is healthy during turn-on. If the DESAT circuit becomes abnormal, the driver will prioritize protection and shut down the IGBT, even if the result is a false alarm.

When a 680Ω resistor becomes open circuit, the braking IGBT may still be good, and the external braking resistor may also be normal. However, because the driver cannot receive correct DESAT information, the system reports a braking unit short circuit.

If the technician only follows the literal meaning of the alarm and repeatedly replaces the IGBT module or suspects the external resistor, the repair will go in the wrong direction.

9. Diagnostic Logic for Similar Braking Faults

When handling braking-related faults on Schneider ATV340, ATV630, ATV930, ATV610, or similar drives, the following logic is useful.

9.1 Is the Fault Strongly Related to Braking Action?

If the fault appears only during fast stop, regenerative operation, DC bus voltage rise, or braking resistor operation, the braking unit should be the first diagnostic target.

9.2 Does the Fault Disappear When Braking Is Disabled?

If disabling the braking function makes the fault disappear, the problem is related to braking IGBT drive or detection. However, this does not mean the drive can be safely returned to the customer with the braking function disabled. The customer’s load may require braking resistor operation to prevent DC bus overvoltage.

9.3 Is a Normal Static IGBT Test Sufficient?

No. A normal static test only rules out obvious breakdown. It does not rule out dynamic desaturation, insufficient drive, false detection, or DESAT circuit open faults.

9.4 Is There a Similar Board for Comparison?

If a similar power driver board is available, compare DESAT circuit resistor values, diode direction, capacitor placement, and component markings. In this case, comparison with a 55kW driver board helped confirm that R704 should be 681 rather than a high-resistance value.

9.5 Is There Contamination, Moisture, or Solder Cracking?

DESAT detection is a high-speed protection signal circuit. Board contamination, flux residue, moisture, carbonization, and cracked solder joints can all cause false triggering. Cleaning, drying, and resoldering are often necessary.

10. Suggested Technical Repair Report

The repair conclusion for this case can be written as follows:

The Schneider ATV340D37N4E drive reported a bUF braking unit short-circuit fault during fast deceleration. Inspection confirmed that the external braking resistor wiring method was correct, and the braking IGBT module showed no obvious C-E short circuit or G-E short circuit. Further inspection of the braking IGBT driver circuit found an abnormality in the DESAT detection circuit of the TLP5214A intelligent IGBT driver optocoupler. The resistor R704 connected to the DESAT circuit of pin 14 had drifted to an abnormally high resistance, measuring more than 10MΩ. On a similar driver board, the corresponding component value was 681, meaning 680Ω. The open R704 caused the DESAT detection signal to become abnormal when the braking IGBT was triggered. As a result, the driver optocoupler falsely detected IGBT desaturation or short circuit and sent a FAULT signal to the control board, triggering the bUF braking unit short-circuit alarm. After replacing R704 with a 680Ω resistor and cleaning/resoldering the related driver detection circuit, the braking function and fast deceleration operation returned to normal.

11. Conclusion

The bUF braking unit short-circuit fault on a Schneider ATV340 drive does not always mean that the braking IGBT is physically shorted. In circuits using intelligent IGBT driver optocouplers such as the TLP5214A, an abnormal DESAT detection circuit can also trigger the same alarm.

The key features of this case were: the fault appeared only when braking was enabled and fast deceleration was performed; the braking IGBT passed static testing; the external braking resistor condition could not explain the fault; and comparison with a similar driver board showed that R704 should be 680Ω, while the faulty board measured more than 10MΩ. After replacing R704, the drive returned to normal.

This case reminds repair technicians that VFD power-stage fault diagnosis should not focus only on large power components. In many cases, the component that actually triggers the alarm is a small part of the drive, protection, feedback, or detection circuit. DESAT resistors, sampling diodes, blanking capacitors, driver optocouplers, FAULT feedback circuits, and connector solder joints can all determine whether the braking unit operates correctly.

A correct repair approach should begin by confirming the fault trigger condition, then distinguishing between a real power-stage fault and a false detection fault, and finally verifying the driver optocoupler and protection circuit point by point. Only by understanding the braking unit operating principle and DESAT protection mechanism can technicians avoid unnecessary module replacement and improve repair accuracy.

1. Equipment Background and Fault Overview

The Schneider Electric Altivar Process ATV660 is a cabinet-type variable frequency drive designed for medium- and high-power industrial motor control applications. It is commonly used on large fans, pumps, compressors, cooling systems, process machinery, and other heavy-duty industrial equipment. The case discussed in this article involves a Schneider Electric ATV660C31Q4X10-EP drive system.

According to the drive nameplate, the unit is rated:

• Model: ATV660C31Q4X10-EP
• Input voltage: 3-phase 380–415 V
• Power rating: ND 315 kW / HD 250 kW
• Output current: ND 590 A / HD 477 A
• Protection class: IP23

The connected motor is a WEG three-phase induction motor. The motor nameplate indicates approximately:

• Voltage: 400 V
• Frequency: 50 Hz
• Power: 260 kW
• Rated current: 435 A
• Speed: 2984 rpm
• Power factor: 0.90

From a capacity-matching point of view, the motor current of 435 A is lower than the drive’s HD current rating of 477 A. Therefore, under normal conditions, this motor and drive combination should be basically suitable.

However, after startup, the drive reports:

SCF1 – Motor short circuit

The diagnostic screen also shows:

IGBT Diag w motor
Power Brick 1 Diag: Not OK

These two pieces of information are very important. This is not a simple communication setting issue, and it should not be treated as an ordinary keypad configuration problem. The fault must be analyzed from the perspectives of motor insulation, motor cable condition, output wiring, IGBT power module condition, gate driver circuit, current detection, and cabinet environment.

For a 250–315 kW class drive, this type of fault has a high repair risk. Repeatedly resetting and restarting the drive without diagnosis may damage the IGBT module, gate driver board, DC bus components, fuses, or even the entire power section. Therefore, the correct approach is to stop repeated startup attempts and perform a structured electrical diagnosis.

2. Meaning of SCF1 “Motor Short Circuit”

The keypad fault SCF1 Motor short circuit literally means that the drive has detected a short-circuit condition related to the motor output. However, in actual VFD diagnosis, this fault does not only mean that the motor winding is physically shorted.

SCF1 may be triggered by several conditions:

1. Phase-to-phase short circuit inside the motor winding.
2. Motor winding insulation breakdown to ground.
3. Phase-to-phase short circuit in the motor cable.
4. Motor cable insulation leakage to ground.
5. Incorrect wiring at the output terminals U/V/W.
6. Capacitor bank or power factor correction device connected at the drive output.
7. Old star-delta starter circuit not fully removed.
8. Output contactor contact failure or incorrect switching sequence.
9. IGBT power module internal short circuit.
10. Gate driver board failure causing abnormal IGBT switching.
11. Current sensor or current detection circuit abnormality.
12. Severe parameter mismatch between motor and drive.
13. Mechanical load locked or jammed, causing abnormal starting current.

Therefore, SCF1 should not be interpreted too narrowly. It does not automatically prove that the motor is bad, and it does not automatically prove that the VFD is bad. The correct diagnostic strategy is to determine whether the problem is located outside the drive, such as motor, cable, or output wiring, or inside the drive power stage, such as IGBT, gate driver, current sensor, or power brick.

3. Importance of “Power Brick 1 Diag: Not OK”

The second fault indication is more serious:

IGBT Diag w motor
Power Brick 1 Diag: Not OK

In a high-power cabinet drive such as the ATV660, the power section is typically composed of IGBT modules, gate driver boards, current sensors, DC bus capacitors, copper busbars, cooling fans, control boards, and internal diagnostic circuits. “Power Brick” can be understood as a power module group or power unit inside the drive.

When the diagnostic page shows Power Brick 1 Diag: Not OK, it means the drive has detected an abnormal condition related to the first power brick or power module group.

This diagnostic result may be caused by two different situations:

First, the motor or motor cable is connected and has a short circuit or leakage problem. The external fault causes the drive to report an abnormal power brick diagnostic result.

Second, the power brick itself is defective. In this case, the diagnostic result may remain Not OK even after the motor cables are disconnected.

This distinction is very important. The next diagnostic action should not be to keep changing communication parameters or command source settings. The first critical test is to disconnect the motor cables from the drive output and check whether the Power Brick 1 diagnostic result changes.

4. Electrical Mechanism Behind the Fault

A VFD output is not a normal sine-wave power supply. It is generated by high-speed switching of IGBTs using PWM modulation. The drive control board monitors output current, DC bus voltage, IGBT feedback, current balance, and protection signals from the gate driver circuit.

When there is a short circuit or severe insulation failure at the output side, the following conditions may occur during startup:

1. One output phase current rises abnormally.
2. Three-phase output current becomes seriously unbalanced.
3. IGBT desaturation protection is triggered.
4. DC bus current rises sharply.
5. The gate driver board detects an unsafe switching condition.
6. The control board judges the output circuit as shorted.
7. The drive stops output and reports SCF1.

If the IGBT module itself is already damaged, a similar fault can occur even when the motor is normal. Examples include shorted IGBT chips, damaged gate resistors, abnormal gate drive signals, faulty desaturation detection, damaged driver optocouplers, or defective current feedback circuits.

This is why repeated startup is dangerous. Every restart applies another high-current stress to the IGBT power stage. If there is a real short circuit, the damage may become much worse.

5. First Rule: Do Not Repeatedly Reset and Restart

When an ATV660 displays SCF1 together with Power Brick 1 diagnostic failure, the first rule is:

Do not repeatedly press RUN or reset the fault again and again.

For some minor alarms, such as temporary undervoltage or external interlock faults, reset and restart may sometimes be acceptable. But SCF1 is a short-circuit-related fault. Repeated startup may cause serious damage.

Possible consequences include:

1. IGBT module explosion.
2. Gate driver board failure.
3. DC bus fuse failure.
4. Copper busbar arcing.
5. Rectifier section stress.
6. Additional internal faults.
7. Higher repair cost.

The correct procedure is:

Stop the drive, isolate the power supply, wait for DC bus discharge, disconnect the motor output, perform insulation tests, and diagnose section by section.

6. Key Diagnostic Step: Disconnect the Motor and Test the Drive Alone

The most important step is to separate the drive from the motor and cable.

Recommended procedure:

1. Switch off the main power supply.
2. Wait until the DC bus is fully discharged.
3. Confirm with a multimeter that the voltage between DC+ and DC- is at a safe level.
4. Disconnect the motor cables from the drive output terminals U/T1, V/T2, and W/T3.
5. Leave the drive output terminals open, with no motor connected.
6. Power on the drive.
7. Enter the diagnostic menu.
8. Check whether Power Brick 1 Diag changes from Not OK to OK.

The interpretation is as follows:

If Power Brick 1 Diag becomes OK after disconnecting the motor, the drive power section is probably not internally shorted. The fault is more likely related to the motor, motor cable, output wiring, output contactor, capacitor, or load.

If Power Brick 1 Diag remains Not OK after disconnecting the motor, the fault is very likely inside the drive. The main suspects are IGBT Power Brick 1, gate driver board, current sensor, busbar insulation, power module connection, or detection circuit.

If the drive still reports SCF1 with the motor disconnected, this strongly suggests an internal power stage fault or a short/leakage near the output terminals.

If the drive is normal without the motor but immediately faults when the motor is connected, then the focus should shift to the motor, cable, terminal box, and output circuit.

This single test is critical because it divides the fault into two major categories: external circuit fault or internal drive fault.

7. Motor and Cable Insulation Testing

For a 400 V, 260 kW motor, insulation testing must not be done only with a standard multimeter. A normal multimeter may detect a dead short, but it cannot reliably identify moisture, insulation aging, partial breakdown, or leakage that only appears under higher test voltage.

A 1000 V insulation resistance tester, commonly called a megger, should be used.

Before insulation testing, the motor cables must be disconnected from the drive output terminals. This is essential because megger voltage can damage the VFD output circuit if applied while the drive is still connected.

Recommended insulation tests:

1. U phase to earth.
2. V phase to earth.
3. W phase to earth.
4. U to V.
5. V to W.
6. U to W.

For this class of motor, the insulation resistance should ideally be in the tens or hundreds of megaohms. If the value is low, the motor should not be connected back to the drive until the cause is found.

A practical interpretation:

• Above 100 MΩ: generally good.
• 10–100 MΩ: suspicious, especially in a humid site.
• Below 10 MΩ: not recommended for VFD operation without further investigation.
• Below 1 MΩ: serious insulation problem.

The cable should also be tested separately if possible. Many SCF1 faults are caused not by the motor winding itself, but by the motor cable.

Common cable-related causes include:

1. Damaged cable insulation.
2. Moisture in cable joints.
3. Cable crushed inside conduit.
4. Shielding layer touching a phase conductor.
5. Carbonized terminals.
6. Loose cable lugs.
7. Water inside the motor terminal box.
8. Phase conductor touching the motor frame.

For large drives, cable insulation problems are very common, especially after equipment relocation, long shutdown, humid storage, or poor cabinet maintenance.

8. Checking the Output Circuit

The drive output terminals U/V/W should normally be connected directly and correctly to the motor. Any device inserted between the drive and motor must be checked carefully.

The following components can cause SCF1 if incorrectly connected at the VFD output:

1. Power factor correction capacitor.
2. Capacitor bank.
3. Old star-delta starter circuit.
4. Output contactor with poor contact.
5. Output contactor switching during drive operation.
6. Incorrectly connected thermal overload relay.
7. Incorrect output filter.
8. Incorrectly placed reactor.
9. Multi-motor connection without proper configuration.
10. Carbonized or loose output terminals.

A capacitor at the output of a VFD is especially dangerous. Since the VFD output is PWM, a capacitor can produce large high-frequency charging currents. This may be detected as a short circuit and may also damage the IGBT module.

Output contactors also require special attention. If a contactor opens or closes while the drive is producing output voltage, it can generate severe electrical stress and trigger short-circuit or overcurrent protection. If an output contactor must be used, it should be properly interlocked so that it never switches while the drive is actively running.

9. Can Parameter Errors Cause SCF1?

Parameter errors usually cause overcurrent, overload, unstable speed, motor overheating, or poor starting torque. However, in severe cases, incorrect parameters may contribute to SCF1 or short-circuit-like protection.

Possible parameter-related causes include:

1. Motor rated current set too high.
2. Motor rated voltage or frequency set incorrectly.
3. Wrong motor control law.
4. Acceleration time too short.
5. Excessive torque boost.
6. Incorrect starting frequency.
7. Incorrect auto-tuning result.
8. Motor power rating mismatch.
9. Multi-motor system configured as a single motor.
10. Heavy mechanical load with aggressive acceleration.

For the motor in this case, the basic motor parameters should be entered according to the nameplate:

• Motor rated voltage: 400 V
• Motor rated frequency: 50 Hz
• Motor rated power: 260 kW
• Motor rated current: 435 A
• Motor rated speed: 2984 rpm
• Motor power factor: 0.90

Initial acceleration and deceleration times should not be too short. For a high-power motor, an initial acceleration time of 30–60 seconds is safer. Heavy-load applications may require even longer ramp times.

However, if the diagnostic menu already shows Power Brick 1 Diag: Not OK, parameter adjustment alone is not enough. Parameters should be checked, but they cannot replace hardware diagnosis.

10. Mechanical Load Considerations

Although SCF1 is mainly related to electrical short-circuit protection, the mechanical side should not be ignored. If the motor is mechanically locked or the driven equipment is jammed, the starting current may become extremely high and trigger protection.

The following items should be checked:

1. Whether the motor shaft can rotate freely.
2. Whether the pump or fan is jammed.
3. Whether the bearing is seized.
4. Whether the coupling is locked.
5. Whether the fan impeller touches the casing.
6. Whether the belt or mechanical transmission is too tight.
7. Whether the pump has foreign material inside.
8. Whether the valve position is correct.
9. Whether the process line is blocked.
10. Whether reverse pressure or backflow exists.

If it is safe to disconnect the motor from the load, an unloaded motor test can help identify whether the fault is electrical or mechanical. If the motor runs normally without load but faults immediately under load, the mechanical system must be investigated.

11. Diagnosing Internal Drive Hardware Faults

If Power Brick 1 Diag remains Not OK even after disconnecting the motor, the fault is likely inside the drive.

The main parts to inspect are:

1. Power Brick 1 IGBT module.
2. IGBT gate driver board.
3. Gate driver power supply.
4. Gate resistors.
5. Driver optocouplers or isolation devices.
6. DC busbar.
7. Output copper busbar.
8. Current sensors.
9. Power module connection cables.
10. Cooling system.
11. Control board to power board connection.
12. Dust, moisture, oil contamination, or metal particles inside the cabinet.

IGBT module faults can appear in different forms. Sometimes the module has an obvious collector-emitter short circuit that can be found with a multimeter in diode mode. Sometimes static testing looks normal, but the IGBT fails under voltage or switching conditions. Sometimes the IGBT itself is good, but the gate driver board is defective and causes abnormal triggering or protection.

Therefore, a simple multimeter test is only a preliminary check. It cannot fully prove that a high-power IGBT module is good. A proper repair workshop should also check gate drive signals, driver power supply, desaturation feedback, current feedback, and insulation conditions.

12. Current Sensor and Detection Circuit Problems

The SCF1 judgment depends heavily on current feedback. If the current sensor or its detection circuit is faulty, the drive may incorrectly detect a short-circuit condition.

Possible symptoms include:

1. Output current displayed when the drive is not running.
2. Unbalanced phase current display.
3. Overcurrent or short-circuit fault with no motor connected.
4. Power brick diagnostic failure.
5. Fault condition changing when cabinet wiring is touched or vibrated.
6. Intermittent SCF1 after the drive warms up.

The current monitoring values should be checked from the keypad. When the drive is stopped, output current should be close to zero. If the displayed current is abnormal in the stopped state, the current sensor, sensor power supply, signal cable, or control board input circuit should be checked.

Loose connectors, oxidized plugs, moisture, dust, and damaged shielding can all affect current detection accuracy.

13. Cabinet Environment and Maintenance Factors

The ATV660 is a cabinet drive. Its reliability depends strongly on the cabinet environment and cooling condition. Dust, moisture, oil mist, metal powder, blocked filters, and poor ventilation can all cause electrical and thermal problems.

Environmental problems may cause:

1. IGBT overheating.
2. Gate driver board leakage.
3. Conductive dust between busbars.
4. Oxidized connectors.
5. Cooling fan failure.
6. Heat sensor abnormality.
7. Capacitor aging.
8. Condensation inside the cabinet.
9. Terminal overheating.
10. Control board misdiagnosis.

The cabinet should be inspected carefully. Air filters should be cleaned or replaced. Cooling fans should be checked. The power section should be inspected for black marks, smell of burning, carbon tracking, loose screws, and foreign objects.

For high-power drives, poor cooling can gradually weaken the power module and finally cause power brick diagnostic failure.

14. Recommended Troubleshooting Procedure

A structured troubleshooting process for this fault should be as follows:

1. Record the fault code, diagnostic screen, running frequency, current, status word, and command word.
2. Stop repeated reset and restart attempts.
3. Switch off the main power and wait for full DC bus discharge.
4. Check output terminals U/V/W for looseness, burn marks, wrong wiring, or foreign objects.
5. Disconnect the motor cables from the drive output.
6. Power on the drive without the motor connected.
7. Check whether Power Brick 1 Diag changes to OK.
8. If the drive is normal without the motor, test the motor and cable insulation with a 1000 V megger.
9. Check the motor terminal box for water, loose terminals, carbon marks, and winding imbalance.
10. Check whether there are contactors, capacitors, star-delta circuits, output filters, or other devices between the drive and motor.
11. If all external circuits are normal, perform a cautious low-frequency local test.
12. If Power Brick 1 Diag remains Not OK without the motor, inspect the internal power section.
13. Test the IGBT module, gate driver board, current sensor, busbar, and power module connections.
14. After repair, test the drive without load first.
15. Reconnect the motor only after the drive and external circuit pass inspection.
16. Start with low frequency, observe current balance, then gradually increase speed.
17. Restore remote UCP or PLC control only after the hardware fault is cleared.

The key principle is to separate the system into sections and test each section independently.

15. Commissioning After Repair

After the fault is repaired, the drive should not be returned to full operation immediately. A gradual commissioning process is necessary.

Recommended steps:

1. Confirm all power terminals are tightened.
2. Confirm motor insulation is acceptable.
3. Confirm no tools, screws, or metal particles remain inside the cabinet.
4. Confirm all fans and cooling paths are working.
5. Confirm motor nameplate data is correctly entered.
6. Select Local mode from the keypad.
7. Start at low frequency, such as 5 Hz.
8. Observe motor direction, current, sound, and vibration.
9. Increase to 10 Hz, 20 Hz, and 30 Hz step by step.
10. Check three-phase current balance.
11. Check motor temperature and mechanical load condition.
12. Only after stable local running should Remote or UCP control be restored.
13. Confirm the command source and speed reference source before automatic operation.

For UCP or PLC control, the command source and reference source must be correctly configured. Start/stop may come from terminals, communication, or keypad. Speed reference may come from analog input, Ethernet communication, Modbus RTU, or another fieldbus. Incorrect communication setup usually does not directly cause SCF1, but it may cause unintended run commands, wrong speed reference, or confusion during troubleshooting. Therefore, communication configuration should be handled after the SCF1 fault source has been identified and cleared.

16. Conclusion

When a Schneider ATV660 drive reports SCF1 Motor short circuit and the diagnostic page shows IGBT Diag w motor / Power Brick 1 Diag: Not OK, the fault must be treated as a serious output short-circuit or power-stage diagnostic failure. It should not be considered a simple keypad setting issue, and it should not be handled by repeatedly resetting and restarting the drive.

The correct diagnostic logic is to first protect the equipment, then isolate the motor from the drive, and then determine whether the fault is external or internal. If Power Brick 1 Diag becomes OK after disconnecting the motor, the focus should be on motor insulation, motor cable, output wiring, contactors, capacitors, old starter circuits, and mechanical load. If Power Brick 1 Diag remains Not OK after disconnecting the motor, the drive itself probably has an internal hardware problem, such as IGBT module failure, gate driver board fault, current sensor abnormality, busbar insulation issue, or power brick detection failure.

For a 250–315 kW cabinet drive, the cost of misdiagnosis can be high. A systematic approach using isolation testing, megger testing, output circuit inspection, power module checking, and controlled low-frequency commissioning is essential. Only after the motor, cable, output circuit, and drive power section are confirmed normal should the system be returned to UCP, PLC, or remote automatic control.

The SCF1 fault is not merely a single alarm code. It is a protection result generated by the interaction of the drive, motor, cable, load, and control system. A professional repair approach must follow the principle of safety first, isolation second, measurement third, judgment fourth, and commissioning last. This is the only reliable way to avoid secondary damage and restore the drive system safely.

Abstract

Industrial variable frequency drives (VFDs) play a critical role in modern automation systems, providing precise control of motor speed and torque. The Schneider Electric Altivar Process ATV660 series is widely used in heavy industrial applications, where high reliability and operational continuity are paramount. Despite robust design, certain internal errors can occur, potentially disrupting production. This article examines Internal Error 29, a common fault code reported on the ATV660, and analyzes a case where the root cause was identified as a poorly connected X22 communication cable, rather than a control board failure. The discussion covers system architecture, error diagnostics, maintenance best practices, and preventive strategies for engineers and technicians.

1. Introduction

Variable frequency drives (VFDs) regulate AC motor operation by adjusting frequency and voltage supplied to the motor. In high-power industrial environments, failures in VFDs can result in substantial downtime and production losses. Schneider Electric’s ATV660 series is designed for demanding applications, offering integrated process control, energy efficiency, and communication with higher-level automation systems via standardized protocols.

Despite their robustness, internal errors such as Internal Error 29 occasionally occur. Traditionally, this error has been associated with control board malfunctions, EEPROM issues, or firmware anomalies. However, real-world case studies demonstrate that internal errors can sometimes arise from external hardware connections, particularly communication cables. This article documents a case study, explores root cause analysis, and provides guidelines for troubleshooting similar faults.

2. ATV660 System Architecture Overview

The ATV660 drive consists of several key modules:

1. Power Module (PM): Handles the conversion from AC input to controlled AC output for the motor. Includes IGBT bridges, DC bus capacitors, and output filters.
2. Control Board (CB): Implements drive logic, motor control algorithms, and communication with other modules and supervisory systems.
3. Interface and Communication Modules: Facilitate connectivity to process automation networks and higher-level SCADA systems. The X22 cable is one of the internal communication links connecting the control board to the power module.
4. Input/Output Terminals: Accepts field signals for start/stop, speed commands, and feedback.
5. HMI Panel: Provides status, parameter configuration, and fault reporting to operators.

The X22 cable specifically transmits critical synchronization and monitoring signals between the control board and power module. Any disruption in this link can cause the drive’s self-diagnostic routine to report Internal Error 29, as the control board detects a lack of expected communication.

3. Internal Error 29: Typical Causes

The drive’s self-diagnostics categorize Internal Error 29 as a critical internal communication or control failure. Common triggers include:

• Faulty control board components (logic IC, FPGA, or EEPROM)
• Power module faults affecting control signals
• Firmware corruption or mismatch
• Poor connections in internal communication cables (e.g., X22, X21)
• Intermittent or loose wiring between modules
• Environmental factors (vibration, dust, or moisture)

Historically, many engineers default to assuming the error indicates a board failure, leading to unnecessary control board replacements. While hardware faults can cause this error, as demonstrated in this case study, cable issues may produce identical symptoms without damaging the main boards.

4. Case Study: X22 Communication Cable Issue

4.1 Fault Description

A client in Nigeria reported an ATV660C31Q4X10-EP drive displaying Internal Error 29. Initial assessment assumed a control board malfunction, given the error’s reputation. The drive was rated at 315 kW / 250 kW, connected to a 3-phase 380–415V input, and used in a heavy industrial process.

4.2 Initial Diagnostic Approach

1. Power cycle and reset via the HMI panel
2. Verified input and output voltages
3. Inspected motor connections for short circuits
4. Checked drive parameters and firmware version using SoMove

Despite these steps, the error persisted. No visible damage was found on the control board or power module.

4.3 Root Cause Identification

A detailed visual inspection revealed the X22 communication cable was not properly fixed. The connector had a slight displacement, leading to intermittent loss of signal between the control board and power module. This misalignment caused the drive’s internal logic to detect a failure in communication, thus triggering Internal Error 29.

After securely reconnecting the X22 cable:

• Internal Error 29 cleared immediately
• Drive returned to normal operation without replacing any hardware
• No additional faults or error codes appeared

This case highlights the importance of inspecting all internal communication links, especially following maintenance or transport.

5. Diagnostic Strategy for Internal Error 29

To troubleshoot Internal Error 29 effectively, engineers should follow a structured approach:

1. Document Drive Status
   • Note error codes, operating conditions, and drive parameters.
2. Perform Controlled Restart
   • Power down the drive for 5–10 minutes.
   • Power it back on and attempt a reset.
3. Verify External Connections
   • Ensure motor cables, field wiring, and grounding are correct.
   • Inspect X22 and other internal communication cables for proper seating.
4. Examine Internal Modules
   • Check the control board, power module, and interface connections.
   • Look for loose connectors, dust, or mechanical stress on boards.
5. Software and Firmware Verification
   • Backup parameters via SoMove or Drive Composer.
   • Confirm firmware versions and compatibility.
6. Controlled Test Operation
   • Run the drive without a load, monitor for error recurrence.
   • If errors persist after cable inspection, consider module replacement.

By following this approach, unnecessary control board replacements can be avoided, reducing downtime and repair costs.

6. Maintenance Best Practices

1. Cable Management
   • Ensure all internal connectors are securely fastened.
   • Label cables and document connections for future reference.
2. Periodic Inspection
   • Schedule visual inspections of connectors, especially after maintenance or shipping.
   • Use retention clips or cable ties to prevent loosening due to vibration.
3. Environmental Control
   • Keep drive compartments clean and dry.
   • Limit exposure to dust, moisture, and extreme temperatures.
4. Operator Training
   • Train personnel on proper handling of internal connectors.
   • Emphasize the importance of checking communication cables when errors occur.
5. Parameter Backup
   • Regularly backup drive parameters and firmware.
   • Maintain logs of firmware updates and maintenance activities.

7. Preventing Recurrence

Internal Error 29 caused by communication cable issues is entirely preventable:

• Ensure proper mechanical fixation of X22 and other critical cables.
• Verify connectors after any maintenance, transport, or vibration exposure.
• Document all maintenance and inspections to provide traceability.

Implementing these preventive measures ensures higher operational reliability, minimizes unnecessary hardware replacements, and maintains consistent production uptime.

8. Conclusion

The Schneider ATV660 series is robust, but like all industrial drives, it is vulnerable to internal errors triggered by minor issues such as improperly fixed communication cables. The case study presented here demonstrates that:

• Internal Error 29 is not always indicative of control board failure.
• Loose or poorly connected X22 cables can produce identical error conditions.
• Systematic diagnostics, careful inspection, and preventive maintenance can resolve errors efficiently without hardware replacement.

By adopting structured troubleshooting and preventive strategies, industrial engineers can enhance drive reliability, reduce repair costs, and prevent unnecessary downtime.

9. References

1. Schneider Electric, Altivar Process ATV660 User Guide, 2021.
2. SoMove / Drive Composer Software Manuals, Schneider Electric.
3. Industrial VFD Maintenance Best Practices, ISA (International Society of Automation), 2020.