66ErrorCode Details of Error code Display Coping strategies37Line, etc., is busy when logging intoDPMS when firmware such as SubCPU, DSP, FPGA, and PLD wasrewritten.S e r v e r i s b u s y3 7Carry out the update in an environmentthat has little network load.38Connection to DPMS failed whenfirmware such as Sub CPU, DSP,FPGA, and PLD was rewritten..C o n n e c t i o n f a i l3 8Check the network connection.Carry out the update in an environmentthat has little network load.39Connection to DPMS timed outwhen firmware such as Sub CPU,DSP, FPGA, and PLD was rewritten.C o n n e c t i o n f a i l3 9Check the network connection.Carry out the update in an environmentthat has little network load.3AError (NG) message was receivedwhen firmware was downloaded orMain CPU was rewritten.D o w n l o a d f a i l3 ATurn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.3BError (line congestion) messagereceived when firmware wasdownloaded or Main CPU wasrewritten.D o w n l o a d f a i l3 BTurn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.3CError (connection failure) messagereceived when firmware wasdownloaded or Main CPU wasrewritten.D o w n l o a d f a i l3 CTurn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.3DFailure to acquire (Boot LoaderMode) IP address before rewritingDM860 (AutoIP).C o n n e c t i o n f a i l3 DCheck the network connection.Carry out the update in an environmentthat has little network load.3EFailure to acquire (Boot LoaderMode) IP address before rewritingDM860 (when timed out).C o n n e c t i o n f a i l3 ECheck the network connection.Carry out the update in an environmentthat has little network load50Log-in to DPMS failed whenfirmware such as Sub CPU, DSPand PLD was rewritten.S u b * * * m i nL o g i n f a i l e d 5 0Carry out the update in an environmentthat has little network load.51Line, etc., is busy when log-in intoDPMS when firmware such as SubCPU, DSP and PLD was rewritten.S u b * * * m i nS e r v e r i s b u s y 5 1Carry out the update in an environmentthat has little network load.52Connection to DPMS failed whenfirmware such as Sub CPU, DSPand PLD was rewritten.S u b * * * m i nC o n n e c t i o n F a i l 5 2Check the network connection.Carry out the update in an environmentthat has little network load.54Error message received regardingfirmware data after the log-in to DPMSwhen firmware such as Sub CPU, DSPand PLD was rewritten.S u b * * * m i nU p d a t i n g f a i l 5 4Turn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.55When firmware such as Sub CPU,DSP and PLD, request was made forfirmware data after the log-in to DPMS,but it timed out was rewritten.S u b * * * m i nU p d a t i n g f a i l 5 5Turn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.56Downloading firmware failed afterthe log-in to DPMS when firmwaresuch as Sub CPU, DSP and PLDwas rewritten.S u b * * * m i nD o w n l o a d f a i l 5 6Turn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.57Firmware download error received (linecongestion) after the log-in to DPMS whenrewriting firmware such as Sub CPU, DSPand PLD was rewritten.S u b * * * m i nS e r v e r i s b u s y 5 7Turn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.58Firmware download error was received(connection failure) after the log-in toDPMS when firmware such as Sub CPU,DSP and PLD was rewritten.S u b * * * m i nC o n n e c t i o n F a i l 5 8Turn off and on the power. Updatingstarts automatically.Carry out the update in an environmentthat has little network load.