To Next PageTo Next PageWhat to do if Mitsubishi Electric PKA-A30KA8 Air Conditioner trouble is reoccurring?
If the trouble with your Mitsubishi Electric Air Conditioner is reoccurring, assess the problem and take corrective action as outlined in the “9-3. SELF-DIAGNOSIS ACTION TABLE”. Also, perform troubleshooting to identify the cause of the issue, referring to “9-4. TROUBLESHOOTING OF PROBLEMS”.
What to do if Mitsubishi Electric Air Conditioner trouble is not reoccurring and not logged?
If the trouble with your Mitsubishi Electric Air Conditioner is not reoccurring and not logged, re-check the abnormal symptom. If the cause isn't clear, continue operating the unit for the time being. Also, conduct troubleshooting and ascertain the cause of the trouble according to “9-4. TROUBLESHOOTING OF PROBLEMS”. There is no abnormality concerning of parts such as electrical component, controller board, remote controller, etc.
What to do if Mitsubishi Electric PKA-A30KA8 Air Conditioner trouble is not reoccurring and logged?
If the trouble with your Mitsubishi Electric Air Conditioner is not reoccurring but is logged, consider temporary issues like protection device activity in the refrigerant circuit including compressor, loose wiring, or electrical noise. Re-check the symptom, and check the installation environment, refrigerant amount, weather when the trouble occurred, matters related to wiring, etc. After finishing service, reset the error code logs and restart the unit. There is no abnormality in electrical component, controller board, remote controller, etc.
General| Brand | Mitsubishi Electric |
|---|---|
| Model | PKA-A30KA8 |
| Category | Air Conditioner |
| Language | English |
General safety rules to follow before accessing unit terminals.
Specific precautions for handling R410A refrigerant during repairs.
Explains how to interpret error codes displayed by the remote controller for self-diagnosis.
Provides a table correlating check codes with their causes and countermeasures for self-diagnosis.
Guides on viewing error codes, history, performing self-diagnosis, and checking controller status.
