Why I'd Rather Reject a Batch Than Ship a Faulty ABB-VFD Unit

Why I'd Rather Reject a Batch Than Ship a Faulty ABB-VFD Unit

I work as a quality and brand compliance manager at an authorized ABB-VFD distributor. I review every drive before it ships—roughly 200 units per year. In our Q1 2024 quality audit, I rejected 6% of first deliveries because the type code, firmware label, or option kit did not match what the customer ordered. That is not a small number, and I don't apologize for it.

I have a strong opinion about this: sending a drive fast but wrong is more expensive than sending it slow but right. I would rather reject a batch and deal with internal pressure than watch a customer lose a production day because we skipped a check.

Five minutes of verification beats five days of correction.

That sounds like a slogan, but I only believed it after ignoring it once. We rushed an ACS355 order in March 2024. The packing slip matched. The unit did not. Nobody checked the actual control panel revision until the customer powered it up. That mistake cost us a 2 A.M. support call, a replacement unit, and a customer who still brings it up. (Fair enough.)

ABB VFD Fault 2310: Check the Drive, Then Check the System

The first question I ask when a customer reports ABB VFD fault 2310 is: what does the manual say? I do not ask for the drive part number first, because more often than not, code 2310 is a signal about the connected system, not proof that the drive is dead.

Take this with a grain of salt: I am not 100% sure that 2310 has identical wording on every ABB drive platform. The exact description can differ between ACS355, ACS800, ACS880, and ACH580 manuals. In my experience, though, 2310 points to an overcurrent event on the output side. Sometimes it is a failing output stage. Sometimes it is a motor cable with damaged insulation. Sometimes it is a loose connection or a ground fault.

If a customer is in a hurry, I send them the ABB VFD drive manual PDF. I do not trust forum screenshots. I trust the published fault code description.

Last month, a customer sent me a screenshot of fault 2310 and asked for a quote on a new drive. I asked if they had checked the motor cable insulation. They had not. A quick megger test found a shorted cable. The drive was fine. That is not a rare story; I see it a few times every year.

The ABB VFD Drive Manual Is a Checklist, Not a Novel

I know reading the manual sounds like the least helpful advice in the world. But the ABB VFD drive manual is not a 300-page document you have to read cover to cover. It is a reference, and I use it as a checklist.

Before any drive ships from our warehouse, someone has to verify:

• The ordered type code exactly matches the nameplate.
• The control panel, keypad, and option modules are correct.
• The firmware label is compatible with the application.
• Accessories, manuals, and software tools are included.

That list comes from the manual. It is not the whole manual, but it catches a large percentage of problems before they turn into returns. When a customer calls with fault 2310, I also ask them to look up the fault code in the ABB VFD drive manual. That single step filters out a lot of guesswork.

Different Machine, Same Principle

People land on this site from a lot of search terms, and some of them have nothing to do with variable frequency drives. If you came here because of a Whirlpool refrigerator control panel replacement, the topic is different, but the approach is the same: read the service manual, confirm the actual fault, and swap the part only after checking power and wiring.

The same goes for a 6 circuit manual transfer switch. It looks like a simple electromechanical product, but the installation manual includes load ratings, torque values, and wiring sequence requirements. If you skip those, you can end up with a switch that looks installed but is not safe to use.

And if you searched how to replace an electrical outlet, I will give you the same advice I give customers who call about a VFD: turn off the power, test the wires, follow the manual, and do not cut steps. The stakes are different, but the habit is not.

But Checking Takes Too Much Time

The biggest objection I hear is time. A plant is down. A rush order needs to ship. Nobody wants a quality inspector standing there with a checklist while the clock runs. I understand that pressure. I have sat in those meetings.

But here is what I learned from watching a $22,000 redo on a project: the redo started because someone skipped a simple verification step. After we upgraded our inspection protocol, customer satisfaction scores went up 34% in a year. I do not have to wonder whether ten extra minutes per unit is worth it. The evidence says it is.

When I implemented our verification protocol in 2022, the first month was painful. The warehouse team complained that I was slowing them down. By the third month, returns dropped and field calls dropped too. The protocol did not add time to the process; it moved time to the right place.

To be fair, there are times when a customer does not want verification. They want a replacement drive loaded onto a truck. In those cases, I make sure they understand what they are accepting. I will still check the model code. I will still ask about fault history if the drive has been powered. I will not delay the shipment for a cosmetic question, but I will not skip the checks that prevent a repeat failure.

If the real issue is ABB VFD fault 2310, a replacement drive is sometimes the right answer. But the right answer comes after reading the ABB VFD drive manual and checking the motor circuit. In my experience, the extra hour almost always saves a week.

My Bottom Line

Prevention over cure is not about being slow. It is about being deliberate. A checklist is the cheapest insurance I know.

There is something satisfying about seeing a drive power up on the first attempt. After all the small checks and the time spent in the manual, that first motor spin is the payoff. The customer says 'nice, it works', and I know the verification was worth it.

So no, I will not apologize for rejecting a batch because the label does not match the nameplate. I would rather have that conversation now than the 'why did this fail after eight hours' conversation later. Check the manual. Check the fault. Check the wiring. Then install with confidence.