TECHNICAL OFFICINE / Drives

Find the route.
Follow the verification.

An operating center for refrigerators and maintenance: parts from the problem, identify the drive, find the exact source and follow the controls in order.

RICERCA RAPIDA

What do you see on the Drives?

Write the exact code, model or what the machine does not.

71 verified codes · 10 families

I have an alarm code

Start from what you read on the display or from what the machine does not.

CENTRO OPERATIVO / PARTENZA RAPIDA

Tell me where you're still.

Enter the real problem. Each path keeps model, state, measures and source before proposing the next verification.

21 routes32 Official PDF10 trademark3 levels

01 / IDENTIFICA

I don't know the model.

Collect complete reference, size, power supply, firmware and application.

Start with the identification →02 / DISPLAY

I have a Drives code

Enter exact code and tool, without transferring meanings between different families.

Search code and model →03 / COMANDO

The engine does not depart

Separate drive status, consents, command source, reference and engine circuit.

Open the diagnosis →04 / PROCESSO

The compressor turns, the capacity is low

Connect frequency, demand, compressor limits and measured refrigerator conditions.

Test drive and process →05 / BACKUP

I need to read or save parameters

Align software, DTM, interface and family before transferring configurations.

Open software and backup →06 / SOURCES

I look for the official manual

Filter documents for manufacturer, family, language and type of activity.

Explore 32 documents →

01Identifyingmodel · firmware · application

02Conservationcode · time · cycle stage

03Comparecommand · reference · status

04Measuresonly with suitable tools and skills

05Confirmationproven cause · final verification · outcome

What do you want to leave?

21 routes · 3 levels

Drive FamilyCode or problemFrom where you want to read

The level organizes reading, does not allow to intervene. With a selected family, the cases of other families are excluded; the general routes remain indicated as method.

21 routes available

ATV320

OCF: overcurrent on ATV320

The drive signals an excessive current. The code does not show itself a failure of the Drives: it is necessary to distinguish start, regime and stop.

Alarm

ATV320

SCF1: distinguish engine circuit and configuration

SCF1 reports a short circuit event. The Schneider FAQ also considers wiring, engine characteristics and adjustment data: does not authorize to declare failure the power stage from the code only.

Alarm

ATV320

ObF: alarm during deceleration

The Schneider source associates ObF with too fast braking, dragging load or high power. The choice of correction depends on the process and hardware installed.

Alarm

ATV320

OHF: high drive temperature

OHF covers the superheat of the drive. It is distinguished from the thermal protection of the engine: the framework context and the load are part of the diagnosis.

Alarm

ATV320

SLF1: loss of local Modbus communication

In the manual ATV320 SLF1 identifies the interruption of the local Modbus serial communication. It is not the generic code for all networks and all options.

Communication

ATV630 · configuration described in the FAQ

ATV630 ready, but RUN on the terminal does not start

A ready drive does not necessarily receive the command from the terminal. The ATV630 FAQ distinguishes control from clamps and HMI control; the local/remote key may not be enabled.

Command

ATV630 · configuration described in the FAQ

nSt on ATV630: check the stop command

The ATV630 FAQ describes a case of free wheel stop in three-wire control: the opening of the stop entry leads to nSt. It should be read the real configuration, not applied a universal scheme.

Command

ATV212

ATV212: understand local, remote and reference

The ATV212 FAQ separates the command and reference channel. ATV320 or ATV600 settings should not be copied to this family.

Command

ATV320 / ATV600 / ATV212

SoMove: connection, DTM and configuration

SoMove and the DTM library are distinct elements. The DTM must match the family; connection and compatibility must be verified in official documentation.

Software