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

The compressor turns but the capacity fridge is low

The output frequency is a given of the system, not a measure of the cooling capacity. The verification must connect request, drive and circuit conditions.

Family
General method · no equivalence between codes
Code or symptom
COMPRESENTATION · PID · PRESSION
Topic
Refrigeration
Objective
Demonstrate the cause before changing parameters or replacing components.
SINTESI

The case in 60 seconds

What does it mean?

The output frequency is a given of the system, not a measure of the cooling capacity. The verification must connect request, drive and circuit conditions.

First data to be stored

Request for cold, frequency shown, available temperatures and environmental conditions.

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
  • Request for cold, frequency shown, available temperatures and environmental conditions.
  • Locate the compressor model and its approved operating field.
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 the control to the drive with the consents and limits of the refrigerator controller.
  • Collect consistent measurements by point, unit and moment, following machine procedure.
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
  • Check OEM sequences and constraints for lubrication, speed field and compressor management; do not set a generic minimum frequency.
  • If the reference is correct, continue with the controls of the refrigerator circuit instead of automatically increasing the speed.
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. Request for cold, frequency shown, available temperatures and environmental conditions.
  2. Locate the compressor model and its approved operating field.
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 the control to the drive with the consents and limits of the refrigerator controller.
  2. Collect consistent measurements by point, unit and moment, following machine procedure.
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. Check OEM sequences and constraints for lubrication, speed field and compressor management; do not set a generic minimum frequency.
  2. If the reference is correct, continue with the controls of the refrigerator circuit instead of automatically increasing the speed.
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.
  • Stop operational analysis if the compressor works outside the allowed field or has noise, vibration or recurring protection.
COLLAUDO

When the problem is really solved

The report must distinguish control limit, drive behaviour and circuit performance with comparable data.

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