REFTHEREFRIGERATION TECHNOLOGY
TECHNOLOGY REFTHE · SCHEDA 14
General method · no equivalence between codes

Replacement and commissioning: minimum dossier

Replace a drive is not equivalent to copying few values. Power, motor, options, control and safety functions must remain consistent with the machine.

Family
General method · no equivalence between codes
Code or symptom
WARNING · SUPPORT · PARAMETRI
Topic
Commissioning
Objective
Demonstrate the cause before changing parameters or replacing components.
SINTESI

The case in 60 seconds

What does it mean?

Replace a drive is not equivalent to copying few values. Power, motor, options, control and safety functions must remain consistent with the machine.

First data to be stored

Collect old and new drive references, engine plate, schematics and configuration available.

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
  • Collect old and new drive references, engine plate, schematics and configuration available.
  • Identifies who approves replacement and who performs testing.
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
  • Compare mechanical, electrical and functional compatibility in the applicable documentation.
  • Record wiring, modified parameters and initial conditions before authorized tests.
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
  • Prepare a test plan for permissive, direction, command, reference, stop and reaction to Troubleshooting according to the project.
  • For autotuning and engine data follow the conditions of the manufacturer: the possibility of movement and the connected load must be evaluated before.
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. Collect old and new drive references, engine plate, schematics and configuration available.
  2. Identifies who approves replacement and who performs testing.
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. Compare mechanical, electrical and functional compatibility in the applicable documentation.
  2. Record wiring, modified parameters and initial conditions before authorized tests.
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. Prepare a test plan for permissive, direction, command, reference, stop and reaction to Troubleshooting according to the project.
  2. For autotuning and engine data follow the conditions of the manufacturer: the possibility of movement and the connected load must be evaluated before.
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.
  • Do not copy configurations between families or firmware without verification. Do not perform autotuning as a generic attempt to repair.
COLLAUDO

When the problem is really solved

Final configuration delivery, differences, tests performed, outcome and responsibility of the recommissioning.

  • 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.