REFTHEREFRIGERATION TECHNOLOGY

Drives / Route index / Allarmi ABB

TECHNOLOGY REFTHE · SCHEDA 19
ACH580 · fault 2310 · manual hardware variant

ACH580 2310: overcurrent

The output current exceeded the internal limit. The code does not distinguish itself from load, ramp, engine data, wiring or insulation.

Family
ACH580 · fault 2310 · manual hardware variant
Code or symptom
2310 · Overcurrent
Topic
Alarms ABB
Objective
Demonstrate the cause before changing parameters or replacing components.
SINTESI

The case in 60 seconds

What does it mean?

The output current exceeded the internal limit. The code does not distinguish itself from load, ramp, engine data, wiring or insulation.

First data to be stored

Record auxiliary code and code, cycle phase, frequency, current and load status.

Diagnosis

The code or symptom directs research, but does not show the fault component alone.

METODO

Diagnostic map

Follow the rows in order. Each phase must produce evidence before moving to the next.

PhaseControlsEvidence to obtainNext decision
01Recognize and collect
  • Record auxiliary code and code, cycle phase, frequency, current and load status.
  • Compare drive and motor plates, star/triangle connection and mechanical conditions before a new start.
Event context and complete initial data.If a data is missing, do not reset to attempts: complete the initial picture first.
02Check and separate hypotheses
  • Check load, group ramps 23/28, scaling 46.01–46.03, group 99 engine data and engine circuit integrity.
  • Exclude contact switches on the engine side and the presence of rewind capacitors or suppressors not allowed.
External causes, configuration, circuit and separate process.If the data does not match, return to the correct schema and revision before changing parameters.
03Interpret and demonstrate
  • Perform insulation tests only with the disconnected drive and second hardware manual and engine/compressor instructions.
  • Compare the event with trends and auxiliary code; correct the cause, not the only protection limit.
Cause supported by repeatable data and authorized evidence.If the cause is not proven, stop changes and involve manufacturer, OEM or machine manager.
CAPITOLO 01

Reading and observation

Recognize and collect

  1. Record auxiliary code and code, cycle phase, frequency, current and load status.
  2. Compare drive and motor plates, star/triangle connection and mechanical conditions before a new start.
Result of the chapter

Event context and complete initial data.

If the result does not match

If a data is missing, do not reset to attempts: complete the initial picture first.

CAPITOLO 02

Qualified technician

Check and separate hypotheses

  1. Check load, group ramps 23/28, scaling 46.01–46.03, group 99 engine data and engine circuit integrity.
  2. Exclude contact switches on the engine side and the presence of rewind capacitors or suppressors not allowed.
Result of the chapter

External causes, configuration, circuit and separate process.

If the result does not match

If the data does not match, return to the correct schema and revision before changing parameters.

CAPITOLO 03

Specialist deepening

Interpret and demonstrate

  1. Perform insulation tests only with the disconnected drive and second hardware manual and engine/compressor instructions.
  2. Compare the event with trends and auxiliary code; correct the cause, not the only protection limit.
Result of the chapter

Cause supported by repeatable data and authorized evidence.

If the result does not match

If the cause is not proven, stop changes and involve manufacturer, OEM or machine manager.

ERRORI FREQUENTI

What to avoid

  • Use repeated resets as a diagnostic test.
  • Transfer codes, thresholds or parameters from one Drives family to another.
  • Change a protection before connecting symptoms, measurement and phase of the cycle.
  • If the block is immediate or recurring, do not repeat the warnings and do not increase the limits. Secure and separate electrical, mechanical and parametric circuit.
COLLAUDO

When the problem is really solved

The 2310 does not reappear in the reproduced condition, the currents are balanced and the proven cause was correct without reducing protection.

  • The cause is supported by data and not only by the momentary absence of the alarm.
  • The cycle that generated the problem has been repeated in authorized conditions.
  • Final configuration, measurements and outcome are consistent with applicable machine, drive and documentation.
PRIMARY SOURCES

Applicable documents

Always check size, firmware, options and revision. These sources do not extend the case to other families.