Scope of this technical record
ABB OVERCURRENT / 2310 routing for users deciding whether the trip belongs to motor/cable, mechanical load, ramp/motor data, output accessories, current feedback, gate driver or output power-stage evidence.
Do not repeatedly reset into an overcurrent. Isolate and prove the external output boundary before internal power-stage inspection; never insulation-test through the drive.
ABB 2310 overcurrent route
2310 must be split by timing and field boundary before output-stage work.
ABB 2310 overcurrent timing image
Searcher intent coverage
2310 users need a timing split that separates motor/cable/load evidence from output bridge or current-feedback repair.
| Observed situation | Decision needed | Evidence that satisfies the search |
|---|---|---|
| Instant trip | Short or output-stage boundary | Output isolation and static evidence |
| Ramp trip | Load/ramp/motor data | Current trend and settings |
| After module repair | Driver or unresolved field cause | Repair history and channel checks |
What 2310 users need beyond a fault definition
An overcurrent page must answer timing first. Does the drive trip at enable with no rotation, during the first acceleration ramp, only after load is applied, during reversing, or after a previous module repair? Each answer sends the technician to a different boundary. The visible 2310 label alone does not prove a failed IGBT.
ABB public training material for 2310-style overcurrent support separates drive testing, motor/wiring, motor data, input quality, application setup, long motor cables and contactors. Your historical repair material adds the board-level reason this matters: repeated module failure is often caused by unchecked driver circuits, optocouplers, small capacitors, zeners, loose module screws or a bad external load condition.
2310 timing map
| Trip timing | First likely boundary | Do not do first |
|---|---|---|
| Instant at enable | Motor cable short, wrong wiring, grounded output or damaged output bridge | Keep resetting to see if it clears |
| During acceleration | Ramp too aggressive, high inertia, brake not released, motor data mismatch | Replace power module before load/ramp review |
| Only under load | Mechanical overload, jam, pump/fan problem, process change | Assume electronics because the code says current |
| After long cable or contactor work | Output accessories, contactor timing, reflected-wave/noise route | Ignore installation changes |
| After module replacement | Driver/current feedback/cause not repaired | Install another module without fake-load/static checks |
Safe diagnostic sequence
Begin with the fault queue and trip timing. Then verify the machine condition: brake release, jammed load, acceleration requirement, motor nameplate data and whether output contactors or long cables are involved. A braked or jammed motor can present like a drive failure while the electronics are simply protecting themselves.
Next separate motor and cable from the drive using site-approved isolation and insulation procedures. If the fault disappears with the external output path removed, keep working outside the drive. If the fault remains after the external path is proven, the route moves inward to static output checks, current feedback, gate driver and power module evidence.
For a previously repaired drive, treat 2310 as a repeat-failure investigation. The old repair record should show what was done to the gate-drive path, optocouplers, zeners, small capacitors and driver supplies before the replacement module was energized. If that record does not exist, do not call the new module bad until the cause path is inspected.
2310 evidence split
| Evidence | External route stronger | Drive-side route stronger |
|---|---|---|
| Fault clears with motor/cable isolated | Yes: motor/cable/load path remains primary | No internal conclusion yet |
| Fault remains with output safely isolated | External route weaker | Output bridge/current sense/driver evidence needed |
| Brake command delayed or absent | Yes: mechanical held load can create overcurrent | Electronics may be responding correctly |
| Motor data/ramp recently changed | Yes: setup route likely | Power hardware not proven |
| Static IGBT short found | External checks still needed after module replacement | Internal power-stage route confirmed, driver check required |
Repair-boundary standard
A good close-out note names the corrected cause. Examples: motor cable insulation failed, brake contactor delayed, acceleration ramp corrected after load review, output contactor timing corrected, IGBT bridge short confirmed with driver repair, or current-feedback board fault confirmed after external isolation. A poor note says only “2310 reset” or “drive replaced”.
This page should also warn against the false economy of replacing only the visible failed module. Uploaded repair experience repeatedly stresses that when a module has failed, the driving circuit and small protective components must be checked before power is reapplied; otherwise the repair can destroy the new module.
Evidence before a repair request
| Evidence | Why it matters | Good note |
|---|---|---|
| Fault timing | Routes enable, ramp, load or heat-related causes | Trips at 8 Hz during acceleration with load attached |
| Motor/cable isolation | Separates external from internal fault | External cable isolated; insulation record attached |
| Load/brake state | Prevents blaming a good drive for a held machine | Brake coil command confirmed before start |
| Motor data/ramp | Finds setup-generated current trips | Nameplate current and acceleration values recorded |
| Previous repair | Repeat module failures need driver evidence | IGBT changed previously; gate driver not documented |
Field record checklist
- ABB type code and voltage class
- Exact 2310 message, aux/fault-history details and trip timing
- Motor/cable insulation and isolation evidence
- Brake, mechanical load, acceleration and motor-data notes
- Output contactor/long cable/accessory evidence
- Static output-stage, current-feedback and driver evidence if external path is proven
Technical basis and reference documents
This is an independent editorial technical reference. Original manufacturer documentation remains controlling for installation, repair and commissioning decisions.
Public ABB support material separates 2310 troubleshooting into drive test, motor/wiring, motor data, input power, application setup, long cables and contactor factors.
Used for repeat-module-failure, driver-circuit and fake-load repair-boundary guidance.