CDS 803: from code to targeted verification
The CDS 803 distinguishes warning, alarm and triple locked. Each code must be connected to size, software, compressor status and electrical conditions before reset.
The case in 60 seconds
The CDS 803 distinguishes warning, alarm and triple locked. Each code must be connected to size, software, compressor status and electrical conditions before reset.
Transcribe code, status, power 6–10 or 18–30 kW, software version and time of the cycle in which it appears.
The code or symptom directs research, but does not show the fault component alone.
Diagnostic map
Follow the rows in order. Each phase must produce evidence before moving to the next.
| Phase | Controls | Evidence to obtain | Next decision |
|---|---|---|---|
| 01Recognize and collect |
| 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 |
| 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 |
| Cause supported by repeatable data and authorized evidence. | If the cause is not proven, stop changes and involve manufacturer, OEM or machine manager. |
Reading and observation
Recognize and collect
- Transcribe code, status, power 6–10 or 18–30 kW, software version and time of the cycle in which it appears.
- Keep compressor data, speed reference and last events without enabling the autoreset.
Event context and complete initial data.
If the result does not matchIf a data is missing, do not reset to attempts: complete the initial picture first.
Qualified technician
Check and separate hypotheses
- Follow the official table: separates network/DC bus, load and temperature, overcurrent, land/race, control word, start failed and motor phases.
- For 18 or 99 verify that the rotor can move and that selection and engine data are consistent; do not transform the phrase “Check fan resistance” into an undefined test.
External causes, configuration, circuit and separate process.
If the result does not matchIf the data does not match, return to the correct schema and revision before changing parameters.
Specialist deepening
Interpret and demonstrate
- Compare the code with the parameters mentioned by Programming Practical guides and the limits of the compressor approved by OEM.
- After correction, run a controlled start, recording current, frequency, pressure and process response.
Cause supported by repeatable data and authorized evidence.
If the result does not matchIf the cause is not proven, stop changes and involve manufacturer, OEM or machine manager.
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.
- The authorset can produce an unexpected start. Only qualified personnel: stop, disconnect all sources, wait for the expected download and check with appropriate tool.
When the problem is really solved
The code remains absent in the reproduced cycle, the cause is demonstrated and the electric and cold quantities fall within the limits of the machine and compressor.
- 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.
Applicable documents
Always check size, firmware, options and revision. These sources do not extend the case to other families.
- Primary source of the caseOpen the official source la
- Danfoss · Installation and operationManual · EN · CDS803-OPER · Official PDF
- Danfoss · Programming and parametersProgramming · EN · CDS803-PROG · Official PDF