• Code: 345.321
• Description: MK_Panel_NG. Communication error between IM and MK (when receiving Pitch Check, the corresponding Panel Build is not received)
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.322
• Description: MK_Pitch_NG. Communication error between IM and MK (when receiving Pitch Notify, the corresponding Pitch Check is not received)
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.331
• Description: MK_MKIF_MSG_Reject. Communication error between IM and MK (the received message was rejected).
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.332
• Description: MK_MMIF_MSG_Reject. Communication error between MM and Sub Module (the received message was rejected).
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.350
• Description: MK_Emergency_Over_Wait. MK internal mismatch (panel creation is obstructed continuously over the predetermined time).
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.351
• Description: MK_Emergency_No_Timer. MK internal mismatch (Call Back Timer has ran out and can't be controlled).
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.352
• Description: MK_Emergency_Enforced_Stop. MK internal mismatch (the MM has performed a forced stop process).
• Remedy: 1. Turn the power Off and On. 2. Install the correct version of the IOT firmware. 3. Initialize the IOT NVM (includes writing back the adjustment NVM). If the problem persists, replace the MCU PWB.

• Code: 345.370
• Description: LPH Power On Fault Multi. Power source error during LPH batch download complete verification or MCU error. (Fail has occurred in multiple LPHs.)
• Remedy: Turn the power Off and remove the Rear Upper Cover. Turn the power On. Is the voltage between the MD PWB P/J532-4/8/12/16 (+) and the GND (-) +5VDC? Y↓ N→Go to +5VDC Power RAP. Is the voltage between the MD PWB P/J532-2/6/10/14 (+) and the GND (-) +1.8VDC? Y↓ N→Turn the power Off and disconnect the MD PWB connector P/J532. Measure the resistance between the MD PWB P/J532-2/6/10/14 and the Frame. Is the resistance infinite for all? Y↓ N→Check the wires of the pins with non-infinite resistance for peeled-off coatings and short circuits due to pinching. Replace the MD PWB. Turn the power Off and check the following connectors for open circuit, short circuit, and poor connection. • Between MCU PWB P/J557 and LPH Rear PWB P/J561 • Between MCU PWB P/J556 and LPH Rear PWB P/J560 • Between MCU PWB P/J555 and LPH Rear PWB P/J559 • Between MCU PWB P/J554 and LPH Rear PWB P/J558 If no problems are found, replace the MCU PWB. If the problem persists, refer to dc131 NVM Read/Write [749-001] (LPH Fail Color) to go to the appropriate RAP. (1: Error has occurred at Y, 2: Error has occurred at M, 4: Error has occurred at C, 8: Error has occurred at K) • Y color: 361.350 RAP • M color: 361.351 RAP • C color: 361.352 RAP • K color: 361.353 RAP