Samsung Error Codes

E101; Communication Error.

Indoor unit communication error. Indoor unit can not receive any data from outdoor unit.

⇒ Fix

Check wiring at F1/F2. Check that they are consistent color and have good solid connections. Shielding braid should only be grounded at outdoor unit and the braid should continued at each indoor unit.

E-102; Communication Error

Communication error between indoor unit and outdoor unit. Displayed in indoor unit.

⇒ Fix;

E-108; Addressing Error.

Error due to repeated address setting (When 2 or more devices have same address within the network).

⇒ Fix; Check Service Manual

Connect SNet Tool and review addresses. Change address so that all IDUs have different addresses. May require wireless controller or wireless controller and wireless reciever for ducted units to change address.

E-152; EEV Error

Error due to closed EEV of indoor unit (2nd detection).

⇒ Fix; Check IDU Service Manual

Check resistance readings of EEV in IDU, they should all be close to equal. In HR systems check Heat or Cool solenoid valve operaton with solenoid magnet. Verify MCU board is outputing 208v/230v to solenoid valve.

E-154; IDU Fan Error

RPM feedback error of indoor unit.

⇒ Fix;

Check the board and fan motor. If the board is running and there is no fluctuating DC voltage on the feed back circuit then the motor is bad. If there is fluctuation DC voltage on the feedback circuit then the board may be bad. 

E-163;  EEPROM Error

Indoor unit’s remote controller option input is Incorrect or missing. Outdoor unit EEPROM data error.

⇒ Fix;

Check product code is set correctly in SNet software. Correct code can be found in VRF Coder.

E-201;  F1/F2 Tracking Error

Communication error between indoor and outdoor units (installation number setting error, repeated indoor unit address, indoor unit communication cable error).

⇒ Fix;

• Check F1/F2 Wiring at terminal blocks for good secure connections
• Check # of IDUs was correctly setup in ODU.

E-213;  MCU Error

When total number of indoor units assigned to MCU is same as actual number of installed indoor units but there is indoor unit that is not installed even though it is assigned on MCU.

⇒ Fix; Check Service Manual

Error will display until pipe pairing is complete. This is not an issue during startup.

E-435;  Water Side Error

Flow switch error in DVM S Water outdoor units. Valve output is enabled 30 secs before Pump output. If flow switch Contact is closed for 30 sec within 3 min before compressor start then the compressor will be enabled. Otherwise compressor is disabled.

⇒ Fix; 

• Adjust screw on flow switch, Confirm that the flow switch is making at all flow conditions.
• Confirm that the pump is enabled. Flow range below.

E-436;  Water Side Error

System protection error to prevent equipment damage/pipe burst due to frozen pipes.

⇒ Fix; Common issue

• Add antifreeze to piping and setup antifreeze option in outdoor unit.
• Check pump for enough flow.

Alternate Issue; Low suction caused by restriction of EEV in highwall units.

• For systems with Highwall units (AMxxxTNV), check EEV setting, 02 Option code SEG11 may need to be changed from default of 0 to 7 or 8, see install manual for other EEV options.

E-461;  Power Systems Error

Error due to operation failure of inverter compressor 1.

⇒ Fix; 

• Check wiring at power connections to inverter and compressor.
• Check compressor windings.
• Check inverter board with inverter checker.
• Check Resistence and voltage of diodes. 
• See video for details https://phoenixenergysupply.com//phoenixenergysupply.com//youtu.be/FWo1Vi6Ofao

E-464;  Power Systems Error

Error due to over-current of inverter compressor 1.

⇒ Fix; 

• Check that all MCUs have the same firmware rev.
• Check model # of compressor.
• Check Compressor Resistance coil’s/chassis also inverter resistance/voltage of diode. See Service manual for values, pg 156.

E-604;  Power Systems Error

Wired LCD (controller) <-> Indoor Unit Tracking Error over 10 times or 5 mins.

⇒ Fix; 

Confirm that all F3/F4 wiring is connected correctly and then retry tracking