Mitsubishi Air Conditioner Error Code E.16

E.16 on a Mitsubishi air conditioner indicates a user-defined protective function has been activated through the system's PLC function. Specifically, the value 16 has been written into special register SD1214, triggering a protective shutdown. This is a custom fault condition configured by the installer or facility manager, not a standard factory error. A technician familiar with the PLC programming for that system is needed to diagnose the root cause.

E.16 means the system's user-defined protective logic has detected a condition serious enough to shut down operation. Whether that condition represents a genuine safety hazard depends entirely on what the custom PLC logic was programmed to monitor. It is advisable to treat the fault as a real protective event and have the system inspected before restarting, since the original programmer may have configured that protection for an important reason.

Repair costs for E.16 vary widely depending on the cause. If the issue is a misconfigured or incorrectly set register value that only requires a PLC access and parameter correction, costs may be in the range of a standard service call fee, typically around $75 to $200. If a failed external sensor or interlock device is involved, parts and labor could bring the total to $150 to $500 or more depending on the component and access difficulty.

Resolving E.16 requires access to the PLC programming environment and the ability to read and interpret special register SD1214, which is beyond typical homeowner troubleshooting. If you have access to the system's PLC software and know what the custom logic is monitoring, you can check what condition triggered the fault. Otherwise, a qualified technician with PLC programming experience is the appropriate resource for this repair.

A simple power reset may temporarily clear the error code, but if the underlying condition that caused 16 to be written into register SD1214 still exists, the fault will return when the PLC logic evaluates its conditions again. Clearing the fault properly requires identifying and resolving the condition that triggered the user-defined protection, or correcting the PLC program if the trigger was unintentional.