R-J3iB Ver.6.30PXX Error Codes

Class ID Severity Error MessageARC 1 PAUSE.L Illegal arc equipment config ARC 2 PAUSE.L Illegal arc schedule number (%s^4,%d^5) ARC 3 PAUSE.L No gas flow (%s^4,%d^5) ARC 4 WARN Gas flow after weld (%s^4,%d^5) ARC 5 PAUSE.L Gas fault (%s^4,%d^5) ARC 6 PAUSE.L Wire fault (%s^4,%d^5) ARC 7 PAUSE.L Water fault (%s^4,%d^5) ARC 8 PAUSE.L Power supply fault (%s^4,%d^5) ARC 10 PAUSE.L Wire stick detected (%s^4,%d^5) ARC 11 PAUSE.L Wire stick, not reset (%s^4,%d^5) ARC 12 PAUSE.L Wire stick reset(s) failed (%s^4,%d^5) ARC 13 PAUSE.L Arc Start failed (%s^4,%d^5) ARC 14 WARN Teach pendant is disabled ARC 15 WARN Press shift with this key ARC 16 PAUSE.L Weld by Shift FWD is disabled ARC 17 WARN Arc Start was disabled (%s^4,%d^5) ARC 18 PAUSE.L Lost arc detect (%s^4,%d^5) ARC 19 PAUSE.L Can't read arc detect input (%s^4,%d^5) ARC 20 PAUSE.L No plan data area available ARC 21 ABORT.L Program aborted while welding (%s^4,%d^5) ARC 22 WARN Weld AO scaling limit used (%s^4,%d^5) ARC 23 PAUSE.L Illegal arc schedule type (%s^4,%d^5) ARC 24 WARN Invalid equipment range ARC 25 WARN Invalid A/D or D/A range ARC 26 WARN Cannot scale AIO while welding ARC 30 WARN Wire stick is still detected (%s^4,%d^5) ARC 31 PAUSE.L No motion while welding (%s^4,%d^5) ARC 32 PAUSE.L Weld stopped by single step (%s^4,%d^5) ARC 33 PAUSE.L Override must be 100%% to weld (%s^4,%d^5) ARC 34 PAUSE.L Task does not control welding (%s^4,%d^5) ARC 35 PAUSE.L Equipment number isn't set (%s^4,%d^5) ARC 36 PAUSE.L Such equipment mask isn't supported (%s^4,%d^5) ARC 37 WARN Another equipment is inching now ARC 38 PAUSE.L Already held another equipment (%s^4,%d^5) ARC 39 PAUSE.L %s^1 AO[%d^2] is not scaled (%s^4,%d^5) ARC 40 PAUSE.L Missing I/O: %s^1 (%s^4,%d^5) ARC 41 PAUSE.L Weld EQ needs DeviceNet option ARC 42 PAUSE.L Weld EQ needs Expl Msg option ARC 43 PAUSE.L Weld EQ needs DeviceNet board ARC 44 PAUSE.L Weld EQ needs DeviceNet defn. ARC 45 WARN Weld EQ Device is OFFLINE ARC 46 WARN Weld EQ communication error ARC 47 WARN Not allowed during a weld ARC 48 WARN Auto AI/O setup is unsupported ARC 49 WARN Process %d switch to %d failed ARC 50 WARN Process %d NOT found ARC 51 WARN Weld EQ ONLINE: %s ARC 52 WARN Bad %s %s Prc %d ARC 53 WARN No ramp at process switch (%s^4,%d^5) ARC 54 PAUSE.G No motion while arc welding ARC 72 PAUSE.L Illegal AMR packet ARC 84 ABORT.L Application process is changed during welding ARC 85 PAUSE.L Incomplete of conversion factor setup ARC 86 PAUSE.L Invalid of binary data in conversion factor ARC 87 PAUSE.L Invalid conversion factor data ARC 88 PAUSE.L Over selected AO factor No. ARC 90 WARN Weld disable by reason[%d] ARC 100 PAUSE.L SVT: Unsupported Wire material ARC 101 PAUSE.L SVT: Unsupported Wire size ARC 102 WARN SVT: Unsupported speed unit ARC 103 PAUSE.L SVT: WFS conversion failed ARC 104 PAUSE.L SVT: Invalid sequence mode ARC 105 PAUSE.L Cannot read WSTK input signal ARC 106 WARN Config of Roboweld is invalid ARC 107 PAUSE.L Roboweld internal Error(%d) ARC 120 WARN Enable/Disable Sim mode failed ARC 121 WARN Weld not performed(Sim mode) ARC 122 WARN Cannot SIM/UNSIM(%s,Id:%d) ARC 123 SYSTEM Memory size is too small ARC 150 PAUSE.G Invalid op. in weld(0x%X)(E:%d) ARC 151 PAUSE.G Invalid wire size(E:%d) ARC 152 PAUSE.G Invalid weld process(E:%d) ARC 153 PAUSE.G Invalid wire material(E:%d) ARC 154 PAUSE.G Invalid Arc Loss Time(E:%d) ARC 155 PAUSE.G Comm. Timeout(E:%d) ARC 156 SYSTEM RoboWeld Error(0x%X, %d) ARC 157 PAUSE.G Receive error(0x%X)(E:%d) ARC 158 PAUSE.G 1st currency (E:%d) ARC 159 PAUSE.G 2nd currency (E:%d) ARC 160 PAUSE.G Temperature alaram(E:%d) ARC 161 PAUSE.G High voltage(E:%d) ARC 162 PAUSE.G Low voltage(E:%d) ARC 163 PAUSE.G Start signal error(E:%d) ARC 164 PAUSE.G Power source error(E:%d) ARC 165 PAUSE.G EQ is detached(E:%d) ARC 166 PAUSE.G Comm. stopped in weld(E:%d) ARC 167 SYSTEM I/O asginment overlap(%d)(E:%d) ARC 168 SYSTEM I/O error(%d)(%d, E:%d) ARC 169 PAUSE.G Invalid wire op.(E:%d) ARC 170 PAUSE.G Detect Arc OFF(E:%d) ARC 171 PAUSE.G Unified data RCV error(%d,0x%X)(E:%d) ARC 172 WARN Warning, Rcv(0x%X)(E:%d) ARC 173 WARN Warning, Retry(0x%X)(E:%d) ARC 174 WARN Warning, NAK for(0x%X)(E:%d) ARC 175 PAUSE.G Signal change is ignored(E:%d) ARC 176 WARN No sysvar $RBWLD for E:%d ARC 177 WARN RoboWeld(E:%d) reset complete ARC 178 PAUSE.G Arc short alarm(E:%d) ARC 179 PAUSE.G Power supply com alarm(E:%d) ARC 180 PAUSE.G Gabana alarm(E:%d) ARC 181 PAUSE.G Encoder alarm(E:%d) ARC 182 PAUSE.G Motor alarm(E:%d) ARC 183 PAUSE.G 2nd High voltage(E:%d) ARC 184 PAUSE.G Run signal alarm(E:%d) ARC 185 PAUSE.G CT offset alarm(E:%d) ARC 186 PAUSE.G VT offset alarm(E:%d) ARC 187 PAUSE.G Water circuit alarm(E:%d) ARC 188 PAUSE.G External emergency input(E:%d) ARC 189 PAUSE.G External input1(E:%d) ARC 190 PAUSE.G External input2(E:%d) ARC 191 PAUSE.G Memory alarm(E:%d) ARC 192 PAUSE.G CPU alarm(E:%d) ARC 193 PAUSE.G Arc start alarm(E:%d) ARC 194 PAUSE.G Gas low pressure(E:%d) ARC 195 PAUSE.G Not support weld type(E:%d) ARC 196 WARN Changing weld type ...(E:%d) ARC 197 WARN Complete weld type change(E:%d) ARC 200 WARN Arclink ch%d heartbeat timeout ARC 201 WARN Arclink ch%d obj #%d no resp ARC 202 WARN Arclink ch%d obj #%d error resp ARC 203 WARN Arclink ch%d reset by master ARC 204 WARN Arclink ch%d available ARC 205 WARN Arclink ch%d h/s event lost ARC 206 WARN Arclink ch%d too many errors ARC 207 WARN Arclink ch%d no bus power ARC 208 WARN Arclink ch%d no nodes on bus ARC 209 WARN Arclink ch%d bus errors ARC 210 WARN Arclink ch%d network flooded ARC 211 WARN Arclink ch%d comm error %d CD 1 WARN No global variables CD 2 WARN Unable to allocate memory CD 3 PAUSE.G Follower recv invalid segment CD 4 PAUSE.G Illegal leader INTR point data CD 5 PAUSE.G Non-coordinated group detected CD 6 PAUSE.G Illegal follower joint motion CD 7 PAUSE.G Circular motype not supported CD 8 PAUSE.G No leader CD 9 PAUSE.G More than one leader CD 10 PAUSE.G Invalid angle in point data CD 11 PAUSE.G Error in flushing CD mailbox CD 12 PAUSE.G Illegal leader motion CD 13 WARN Jog group is not a leader CD 14 WARN Jog group has multi follower CD 15 PAUSE.G Wrist joint is not supported CD 16 PAUSE.G INC motion is not supported CD 17 PAUSE.G INDEP motn is not supported CD 18 PAUSE.G No calibration for CD CD 19 PAUSE.G Illegal follower setting CD 20 WARN Not reach relative speed CD 21 PAUSE.G No kinematics in CD group CD 22 PAUSE.G Prev term type is not FINE CD 23 PAUSE.G Illegal CD setting CD 24 WARN Calibration was inaccurate CD 25 PAUSE.G Can't convert position CD 26 PAUSE.G Illegal transition:nonCD<->CD CD 27 PAUSE.G Illegal follower transition CD 28 PAUSE.G T1 speed limit(G:%d^2) CMND 1 WARN Directory not found CMND 2 WARN File not found CMND 3 WARN File already exists CMND 6 WARN Self copy not allowed CMND 10 WARN Source type code is invalid CMND 11 WARN Destination type code is invalid CMND 12 WARN Type codes do not match CMND 13 WARN Representation mismatch CMND 14 WARN Positions are not the same CMND 15 WARN Both arguments are zero CMND 16 WARN Division by zero CMND 17 WARN Angle is out of range CMND 18 WARN Invalid device or path CMND 19 WARN Operation cancelled CMND 20 WARN End of directory CMND 21 WARN Cannot rename file CMND 22 PAUSE.G Time motion with dist before CNTR 1 WARN No global variables CNTR 2 WARN No MIR pointer CNTR 3 WARN No sysvar pointer CNTR 4 WARN No cnir pointer CNTR 5 WARN Wrong CN Axis/N1 or N2(G:%d^2) CNTR 6 WARN Unable to Allocate Memory CNTR 7 PAUSE.G Serious Internal error (G:%d^2) CNTR 8 PAUSE.G Invalid dest. angle, (G:%d^2) CNTR 9 WARN Warn-Cont Vel too high(G:%d^2) CNTR 10 PAUSE.G Ind.EV option not allowed. CNTR 11 PAUSE.G Axis speed exceeds lim(G:%d^2) CNTR 12 PAUSE.G Ending Cont Rot on Rel Motion COMP 0 SYSTEM Unknown error COMP 1 PAUSE.G Retry count over COMP 2 PAUSE.G Retry count over(Hardware) COMP 3 PAUSE.G Retry count over(Undefind TCC) COMP 4 PAUSE.G Retry count over(Parity) COMP 5 PAUSE.G Retry count over(Interval) COMP 6 PAUSE.G DSR off when transmission COMP 7 PAUSE.G Invalid data format COMP 8 PAUSE.G Response time over COND 1 WARN Condition does not exist COND 2 WARN Condition handler superseded COND 3 WARN Already enabled, no change COND 4 WARN Already disabled, no change COND 5 WARN No more conditions defined COND 9 WARN Break point encountered COND 10 WARN Cond exists, not superseded COND 11 WARN Scan time took too long COPT 1 WARN Send_PC error COPT 2 WARN Add PC Uninit prog or var name COPT 3 WARN Add PC Variable not found COPT 4 WARN Add PC Var type not supported COPT 5 WARN Add PC illegal index into buffer COPT 6 WARN Add PC buffer overflow - parm %s COPT 7 WARN Add PC Un-initialized parameter %s COPT 8 WARN Send_PC Un-initialized parameter COPT 9 WARN Send_PC Illegal event number COPT 10 WARN Send_PC Illegal wait flag COPT 11 WARN Send_PC Buffer too big for packet COPT 20 WARN Send_PC builtin failed COPT 21 WARN Send_PC event parm %s error COPT 22 WARN Still waiting for %s COPT 23 WARN Abort wait for %s COPT 24 WARN Continuing without %s COPT 25 WARN Received answer for %s COPT 26 WARN Wait timer cannot be set COPT 27 WARN Reg %s could not be set COPT 28 WARN Register %s not defined COPT 29 WARN Macro Table too small for send option COPT 30 WARN Parameter %s error COPT 31 WARN Send Macro - no data to send COPT 32 WARN Send_n_wait - Illegal action COPT 33 WARN Send_n_wait - Uninit parm %s COPT 34 WARN %s missing COPT 35 WARN Aborting TP program COPT 36 WARN %s Illegal type DICT 1 WARN Dictionary already loaded DICT 2 WARN Not enough memory to load dict DICT 3 WARN No dict found for language DICT 4 WARN Dictionary not found DICT 5 WARN Dictionary element not found DICT 6 WARN Nested level too deep DICT 7 WARN Dictionary not opened by task DICT 8 WARN Dictionary element truncated DICT 9 WARN End of language list DICT 10 WARN End of dictionary list DICT 11 WARN Dict opened by too many tasks DICT 12 WARN Not enough memory to load dict DICT 13 WARN Cannot open dictionary file DICT 14 WARN Expecting $ in dictionary file DICT 15 WARN Reserved word not recognized DICT 16 WARN Ending quote expected DICT 17 WARN Expecting element name or num DICT 18 WARN Invalid cursor position DICT 19 WARN ASCII character code expected DICT 20 WARN Reserved word expected DICT 21 WARN Invalid character DICT 22 WARN Dict already opened by task DICT 23 WARN Dict does not need to be opened DICT 24 WARN Cannot remove dictionary file DICT 28 WARN Not enough memory to load dict DICT 29 WARN Help element not found DICT 30 WARN Function key element not found DICT 31 WARN %4s-%03d $%8lX, no message found DICT 32 WARN %4s-%03d, see posted error DICT 40 WARN Expecting element num after $ DICT 41 WARN Expecting element name after , DICT 42 WARN Expecting add constant name DICT 43 WARN Element number out of sequence DICT 44 WARN Warning - large hole in ele seq DICT 45 WARN .LIT or .END mismatch DICT 46 WARN Command already encountered DICT 47 WARN File extension required DICT 48 WARN Invalid file extension DICT 49 WARN Expecting file name DICT 50 WARN Expecting facility number DICT 51 WARN Symbol invalid for dictionary type DICT 52 WARN Expecting .ENDFORM symbol DICT 53 WARN Cannot open include file DICT 54 WARN Form is being displayed DNET 1 PAUSE.G No system device file DNET 2 PAUSE.G No application device file DNET 3 PAUSE.G Too many DNet motherboards DNET 4 PAUSE.G Board init failed: Bd %d DNET 5 WARN User dev def Err, line:%d DNET 6 SYSTEM System error: %d DNET 7 WARN Invalid device definition DNET 8 WARN Invalid board index DNET 9 WARN Invalid MAC Id: Bd %d MAC %d DNET 10 WARN Board already online DNET 11 WARN Board not online DNET 12 WARN Device already online DNET 13 WARN Device not online DNET 14 WARN Request timed out DNET 15 WARN Board not initialized DNET 16 SYSTEM System failed DNET 17 WARN Board not found DNET 19 WARN Code file open failed DNET 20 WARN Code file read failed DNET 21 WARN Code file checksum error DNET 22 WARN Board initialization timeout DNET 23 WARN Board initialization error DNET 25 WARN No device assigned for Bd/MAC DNET 26 WARN No match on dev type look-up DNET 27 PAUSE.G Dev online err: Bd %d MAC %d DNET 28 PAUSE.G Board online err: Bd %d DNET 30 PAUSE.G Std dev file fmt err: Line %d DNET 31 PAUSE.G App dev file fmt err: Line %d DNET 33 WARN Unknown keyword DNET 34 WARN Cycle power to bring online DNET 35 WARN Bad format or out of range DNET 36 WARN I/O size/type not specified DNET 37 WARN No PDTCODE line DNET 38 WARN No MODULE lines with MULTIMOD DNET 39 WARN Too many MODULE lines DNET 40 WARN MODULE specified w/o MULTIMOD DNET 41 WARN Required field missing DNET 42 WARN DEVTYPE line absent/invalid DNET 43 WARN VENDORID line absent/invalid DNET 44 WARN PRODCODE line absent/invalid DNET 45 WARN No I/O mode line supplied DNET 46 WARN No PDTCODE line supplied DNET 47 PAUSE.G DeviceNet motherboard not found DNET 48 WARN Multiple DEFAULT modes; ignored DNET 49 WARN Device Name not found DNET 50 WARN Board or network warning: Bd %d DNET 51 WARN Netwk comm errors: Bus warning DNET 52 WARN Data line too long DNET 53 WARN Line above DEVICE line ignored DNET 54 WARN All space in shared RAM used DNET 55 PAUSE.G Board or network error: Bd %d DNET 56 WARN Network power lost DNET 57 WARN Network communications error DNET 58 WARN Message queue overrun DNET 59 WARN Message lost DNET 60 WARN Xmit timeout: Network flooded DNET 61 WARN No other nodes on network DNET 62 WARN Bus off due to comm errors DNET 63 PAUSE.G Device error: Bd %d MAC %d DNET 64 WARN Connection error DNET 65 WARN Incorrect vendor Id DNET 66 WARN Incorrect product code DNET 67 WARN Incorrect device type DNET 68 WARN Device timeout DNET 69 PAUSE.G Unknown error code %d DNET 70 WARN Connection allocation error DNET 71 PAUSE.G Dup dbrd: Bd:%d Mbd:%s DNET 72 WARN Found dupl. DNet daughterboard DNET 73 WARN No match on mod type look-up DNET 74 PAUSE.G Load only at ctrl start DNET 76 WARN $DN_DEV_DEFS array is full DNET 77 WARN DNet I/O inactive at CTRL start DNET 78 WARN No room for more devices DNET 79 PAUSE.G Unknown dev type: Bd %d MAC %d DNET 80 PAUSE.G Loaded config too large DNET 82 WARN Press RESET to reconnect DNET 83 WARN Board %d auto-restarted DNET 84 PAUSE.G Board reset failed: Bd %d DNET 85 PAUSE.G Dev reset failed: Bd %d MAC %d DNET 86 PAUSE.G Stop scan cmd failed: Bd %d DNET 87 PAUSE.G Bd offline cmd failed: Bd %d DNET 88 PAUSE.G Ignored: Bd %d MAC %d Slot %d DNET 89 WARN Can't specify POLL and STROBE DNET 90 WARN Can't STROBE w/ num outs > 0 DNET 91 WARN Input size error DNET 92 WARN Output size error DNET 93 WARN Error reading vendor ID DNET 94 WARN Error reading device type DNET 95 WARN Error reading product code DNET 96 WARN Error setting packet rate DNET 97 WARN Connection sync fault DNET 102 WARN Invalid board MAC Id DNET 103 WARN Invalid board baud rate DNET 104 WARN Duplicate MAC Id error DNET 105 WARN Duplicate device error DNET 106 WARN Device not found error DNET 107 WARN Bus offline error DNET 108 WARN Scanner active error DNET 109 WARN Bus not offline error DNET 110 WARN Error: board scanning DNET 111 WARN Error: board not scanning DNET 112 WARN Board not ready; pls. wait DNET 114 WARN Bus fault error detected DNET 115 WARN Invalid I/O connection attempt DNET 119 PAUSE.G Dup. MAC Ack Fault DNET 120 WARN Dev online err: Bd %d MAC %d DNET 121 WARN Device not ready: Bd %d MAC %d DNET 122 WARN Device error: Bd %d MAC %d DNET 123 WARN Dev reset failed: Bd %d MAC %d DNET 124 WARN Device not autorec: Bd %d MAC %d DNET 125 WARN Slave Conn. Idle: Bd %d DNET 130 PAUSE.G Invalid parameter DNET 131 WARN Invalid board number DNET 132 WARN Invalid MAC ID DNET 133 WARN I/O Size mismatch DNET 134 WARN Mode mismatch DNET 135 WARN Analog size mismatch DNET 136 WARN Name does not match DNET 137 WARN Name and Analog do not match DX 0 PAUSE.G Unknown error (DX00) DX 1 PAUSE.G No global variables DX 2 PAUSE.G Error allocating data memory DX 3 PAUSE.G No system variables DX 4 PAUSE.G Illegal schedule number DX 5 WARN Schedule already enabled DX 6 WARN Schedule not enabled DX 7 PAUSE.G Schedule not enabled DX 8 PAUSE.G Internal error DX 9 PAUSE.G Internal error DX 10 PAUSE.G DeltaJ DeltaT/F incompatible DX 11 PAUSE.G DeltaT DeltaF incompatible DX 12 PAUSE.G Specified group already enabled DX 13 PAUSE.G Invalid robot link group tracking DX 14 PAUSE.G Invalid offset orientation DX 15 PAUSE.G Invalid offset distance DX 16 PAUSE.G UT is changed ELOG 0 WARN ELOG 9 WARN call a service man ELOG 11 WARN Power off, if you want to recover. ELOG 12 WARN A system error has been occurred. FIG 0 WARN UNUSED ERROR CODE(FCT00) FIG 10 PAUSE.L Parameter error FIG 11 PAUSE.L L1,L2 is different FIG 12 PAUSE.L Length,Width is different FIG 13 PAUSE.L R is different FIG 14 PAUSE.L L1 is short FIG 15 PAUSE.L Length is short FIG 16 PAUSE.L L1 is long FIG 17 PAUSE.L Length is long FIG 18 PAUSE.L L2 is short FIG 19 PAUSE.L Width is short FIG 20 PAUSE.L L2 is long FIG 21 PAUSE.L Width is long FIG 22 PAUSE.L $FCMIN_INTR is short FIG 23 PAUSE.L $FCMIN_INTR is long FIG 24 PAUSE.L BRC is short FIG 25 PAUSE.L BRC is long FIG 26 PAUSE.L MJ is different FIG 27 PAUSE.L MJ is short FIG 28 PAUSE.L Figure not write FIG 29 WARN Don't effective Lof FIG 30 PAUSE.L Index value code is different FIG 31 PAUSE.L Speed value is different FIG 32 WARN Group setup is wrong FIG 33 PAUSE.L Speed unit is different FIG 34 PAUSE.L MJ is long FIG 35 PAUSE.L Diameter is long FILE 1 WARN Device not ready FILE 2 WARN Device is Full FILE 3 WARN Device is protected FILE 4 WARN Device not assigned FILE 5 WARN Device not mounted FILE 6 WARN Device is already mounted FILE 8 WARN Illegal device name FILE 9 WARN Illegal logical unit number FILE 10 WARN Directory not found FILE 11 WARN Directory full FILE 12 WARN Directory is protected FILE 13 WARN Illegal directory name FILE 14 WARN File not found FILE 15 WARN File is protected FILE 17 WARN File not open FILE 18 WARN File is already opened FILE 19 WARN File is locked FILE 20 WARN Illegal file size FILE 21 WARN End of file FILE 22 WARN Illegal file name FILE 23 WARN Illegal file number FILE 24 WARN Illegal file type FILE 25 WARN Illegal protection code FILE 26 WARN Illegal access mode FILE 27 WARN Illegal attribute FILE 28 WARN Illegal data block FILE 29 WARN Command is not supported FILE 30 WARN Device lun table is full FILE 31 WARN Illegal path name FILE 32 WARN Illegal parameter FILE 33 WARN System file buffer full FILE 34 WARN Illegal file position FILE 35 WARN Device not formatted FILE 36 WARN File already exist FILE 37 WARN Directory not empty FILE 38 WARN File locked by too many tasks FILE 39 WARN Directory already exists FILE 40 WARN Illegal file access mode FILE 41 WARN File not locked FILE 45 WARN need to set $FILE_MAXSEC FILE 49 WARN File is not standard file FILE 50 WARN PChamp %s device NOT ready - device FULL FILE 51 WARN NESTED kread issued FILE 52 WARN Kread re-call with different buf_p FILE 53 WARN MC Inserted FILE 54 WARN MC Removed FILE 55 WARN MC not detected FILE 56 WARN Modem Card Inserted FILE 57 WARN Modem Card Removed FILE 58 WARN Illegal Character in Name FILE 59 WARN Not enough TEMP memory for file operation FILE 60 WARN Max %d,Req %d,Ac %d FILE 61 WARN Requested RD Sz too big FILE 62 WARN Backup files are not correct FILE 63 PAUSE.G (%s) is not loaded FLPY 1 WARN End of directory reached FLPY 2 WARN File already exists FLPY 3 WARN File does not exist FLPY 4 WARN Unsupported command FLPY 5 WARN Disk is full FLPY 6 WARN End of file reached FLPY 8 WARN Only one file may be opened FLPY 9 WARN Communications error FLPY 15 WARN Write protection violation FLPY 100 WARN Directory read error FLPY 101 WARN Block check error FLPY 103 WARN Seek error FLPY 104 WARN Disk timeout FLPY 105 WARN Write protection violation FLPY 106 WARN Memory Card hardware error FLPY 107 WARN Not formatted card FORC 1 WARN Sensor board doesn't exist FORC 2 WARN Sensor board doesn't exist 2 FORC 3 PAUSE.G Force control error (F:%d^1, E:%d^2) FORC 4 SYSTEM Communication error FORC 5 WARN Sensor board is disabled FORC 6 WARN Sensor board is disabled 2 FORC 11 PAUSE.G Force group mismatch FORC 12 PAUSE.G Time out error occurred FORC 13 PAUSE.G Communications error FORC 14 PAUSE.G Invalid tool number FORC 15 PAUSE.G Force sensor error exceed limit FORC 16 WARN Diagnosis normal end FORC 17 PAUSE.G Init data already set up FORC 18 PAUSE.G Uninitialized data FORC 19 PAUSE.G Tolerance data is 0 or less FORC 20 PAUSE.G Sensor error excess (S:%d E:%X) FORC 21 PAUSE.G Sensor index does not exist FORC 22 PAUSE.G Offset value is needed FORC 23 PAUSE.G Force sensor error occurred FORC 24 PAUSE.G Force control error occurred FORC 25 PAUSE.G Function type is unused FORC 26 WARN Init data has been set FORC 27 PAUSE.G Another tuning already enabled FORC 28 PAUSE.G Customize tuning little DOF FORC 101 WARN Default data is incorrect FORC 102 WARN Default data is not selected FORC 103 WARN Index value is incorrect FORC 104 WARN Number of array is incorrect FORC 105 WARN Force group is incorrect FORC 106 WARN Mass data is out of range FORC 107 WARN Damper data is out of range FORC 108 WARN Input data is out of minimum FORC 109 WARN Input data is out of maximum FORC 110 WARN Setting data is not enough FORC 111 WARN Number of array mismatch FORC 112 WARN Program data is incomplete FORC 113 WARN Specified data doesn't exist FORC 114 WARN Converted individual difference FORC 115 WARN Insert direction is changed FORC 116 WARN Bearing rot axis is changed FORC 117 WARN Auto tuning not done FORC 118 WARN Groove direction is changed FORC 119 WARN Customize infinit loop FORC 120 WARN Customize exceed rty-child num FORC 121 WARN Customize exceed ins-child num FORC 122 WARN Customize exceed retry num FORC 123 WARN Customize syncro change OK FORC 124 WARN Customize syncro change NG FORC 125 WARN Customize intr. TP err0 FORC 126 WARN Customize intr. TP err1 FORC 127 WARN Customize intr. TP err2 FORC 129 WARN Direction is same as ins. dir. FORC 130 PAUSE.G Illegal insert data index FORC 151 PAUSE.G F/S SLDM non response error (F:%d^1) FORC 152 PAUSE.G F/S SCL2 slave error (F:%d^1) FORC 153 PAUSE.G F/S SLC2 frmaing error (F:%d^1) FORC 154 PAUSE.G F/S SLC2 internal parity error (F:%d^1) FORC 155 PAUSE.G F/S SLC2 external parity error (F:%d^1) FORC 156 PAUSE.G F/S head data request error (F:%d^1) FORC 157 PAUSE.G F/S force data calc. overflow (F:%d^1) FORC 158 PAUSE.G F/S gauge data overflow (F:%d^1) FORC 159 PAUSE.G F/S sensor limit overflow (F:%d^1) FORC 160 PAUSE.G F/S cable is cut (F:%d^1) FORC 161 PAUSE.G F/S timeout error (F:%d^1) FORC 162 PAUSE.G F/S temperature data overflow (F:%d^1) FORC 163 PAUSE.G F/S watch dog error (F:%d^1) FORC 164 PAUSE.G F/S temp. lower limit error (F:%d^1) FORC 165 PAUSE.G F/S temp. upper limit error (F:%d^1) FORC 167 SYSTEM SCRDY set error (F:%d^1) FORC 168 SYSTEM HCRDY set error (F:%d^1) FORC 169 SYSTEM SCRDY reset error (F:%d^1) FORC 170 SYSTEM HCRDY reset error (F:%d^1) FORC 171 PAUSE.G F/S output data frozen (F:%d^1) FORC 172 PAUSE.G F/S communication error (F:%d^1) FORC 173 PAUSE.G F/S external error (F:%d^1) FORC 175 PAUSE.G F/S force differential limit (F:%d^1) FORC 176 PAUSE.G F/S shard memory parity error (F:%d^1) FORC 177 PAUSE.G F/S local memory parity error (F:%d^1) FORC 178 WARN F/S SLC2 slave data error (F:%d^1) FORC 179 WARN F/S SLC2 slave comm. error (F:%d^1) FORC 180 PAUSE.G F/S ITP counter error (F:%d^1) FORC 199 PAUSE.G Single singularity error (F:%d^1) FORC 201 PAUSE.G Complex singularity error (F:%d^1) FORC 203 PAUSE.G Joint axis limit error (F:%d^1) FORC 205 PAUSE.G Cool down fail in pause (F:%d^1) FORC 206 PAUSE.G Pos. error limit at Hot Start (F:%d^1) FORC 207 PAUSE.G Force error limit at Hot Start (F:%d^1) FORC 208 PAUSE.G Hot Start after pause error (F:%d^1) FORC 209 PAUSE.G Inverse kinematics Error (F:%d^1) FORC 211 SERVO Servo error occurred (F:%d^1) FORC 215 PAUSE.G Force calc. timeout error (F:%d^1) FORC 216 PAUSE.G X Force Limit (F:%d^1) FORC 217 PAUSE.G Y Force Limit (F:%d^1) FORC 218 PAUSE.G Z Force Limit (F:%d^1) FORC 219 PAUSE.G W Moment Limit (F:%d^1) FORC 220 PAUSE.G P Moment Limit (F:%d^1) FORC 221 PAUSE.G R Moment Limit (F:%d^1) FORC 223 PAUSE.G Ilegal end force control (F:%d^1) FORC 224 PAUSE.G Not detect the touch (F:%d^1) FORC 225 PAUSE.G Not move specified distance (F:%d^1) FORC 226 PAUSE.G Tool correction calc. error (F:%d^1) FORC 227 PAUSE.G Unknown status from orbit func (F:%d^1) FORC 228 PAUSE.G Unknown status from sub func (F:%d^1) FORC 263 PAUSE.G Approach timeout error (F:%d^1) FORC 264 PAUSE.G Insertion timeout error (F:%d^1) FORC 265 PAUSE.G Angle change limit error (F:%d^1) FORC 266 PAUSE.G Returning approach pos. failed (F:%d^1) FORC 267 PAUSE.G Retry count exceeds limits (F:%d^1) FORC 268 PAUSE.G Approach position error (F:%d^1) FORC 269 PAUSE.G Insert direction error (F:%d^1) FORC 270 PAUSE.G Insert length error (F:%d^1) FORC 271 PAUSE.G Invalid teaching (F:%d^1) FORC 272 PAUSE.G Invalid torque data is set (F:%d^1) FORC 273 PAUSE.G Setting end cond. failed (F:%d^1) FORC 275 PAUSE.G Phase matching timeout (F:%d^1) FORC 276 PAUSE.G Recovering timeout (F:%d^1) FORC 277 PAUSE.G Approach angle limit (F:%d^1) FORC 278 PAUSE.G Overrun error (F:%d^1) FORC 279 WARN Contouring aborted FORC 280 PAUSE.G F. Ctrl during Contouring (F:%d^1) FORC 281 WARN Contouring start (F:%d^1) FORC 282 WARN Contouring normal end (F:%d^1) FORC 283 PAUSE.G Contouring limit error (F:%d^1) FORC 284 PAUSE.G Contouring option is not ordered FORC 285 PAUSE.G Auto tuning is impossible FORC 286 PAUSE.G impedance ctrl. impossible FORC 287 PAUSE.G Contouring 07 (F:%d^1) FORC 288 PAUSE.G Contouring 08 (F:%d^1) FORC 289 PAUSE.G Contouring 09 (F:%d^1) FORC 290 PAUSE.G Contouring 10 (F:%d^1) FORC 291 PAUSE.G Contouring 11 (F:%d^1) FORC 292 PAUSE.G Contouring 12 (F:%d^1) FORC 293 PAUSE.G Contouring 13 (F:%d^1) FORC 294 PAUSE.G Contouring 14 (F:%d^1) FORC 295 PAUSE.G Contouring 15 (F:%d^1) FORC 301 SYSTEM Illegal physical ITP (F:%d^1) FORC 302 SYSTEM Illegal logical ITP (F:%d^1) FORC 303 SYSTEM Illegal axis module number (F:%d^1) FORC 304 SYSTEM Illegal axis number (F:%d^1) FORC 305 SYSTEM Illegal axis order (F:%d^1) FORC 316 SYSTEM Illegal F/C axis number (F:%d^1) FORC 317 SYSTEM Illegal mech. parameter (F:%d^1) FORC 318 SYSTEM Illegal DH parameter (F:%d^1) FORC 319 SYSTEM Illegal motor parameter (F:%d^1) FORC 320 PAUSE.G Unfinished master (F:%d^1) FORC 321 SYSTEM Unfinished quick master (F:%d^1) FORC 322 SYSTEM Unknown master type (F:%d^1) FORC 323 SYSTEM Illegal limit data (F:%d^1) FORC 324 SYSTEM Illegal joint singular (F:%d^1) FORC 325 SYSTEM Illegal F/S coord. system (F:%d^1) FORC 326 SYSTEM Illegal F/S range (F:%d^1) FORC 327 SYSTEM Illegal F/C motion group (F:%d^1) FORC 328 SYSTEM Illegal F/C motion group order (F:%d^1) FORC 329 SYSTEM Timer variable init. error (F:%d^1) FORC 380 PAUSE.G Program copy failed(ROM->RAM) (F:%d^1) FORC 381 PAUSE.G F/S SLC2 error(STATERR) (F:%d^1) FORC 382 PAUSE.G F/S SLC2 error(BITERR) (F:%d^1) FORC 412 PAUSE.G Unestablished F/C data (F:%d^1) FORC 413 PAUSE.G Established F/C data at hot start (F:%d^1) FORC 414 PAUSE.G Illegal basic data array num. (F:%d^1) FORC 415 PAUSE.G Illegal Insert data array num. (F:%d^1) FORC 416 PAUSE.G Unknown F/C mode (F:%d^1) FORC 420 PAUSE.G Search Retry Limit (F:%d^1) FORC 421 PAUSE.G Search Range over (F:%d^1) FORC 422 PAUSE.G Search Frc/Vel wrong (F:%d^1) FORC 423 PAUSE.G Search Vel order error (F:%d^1) FORC 424 PAUSE.G Search direction error (F:%d^1) FORC 425 PAUSE.G Search range param. error (F:%d^1) FORC 426 PAUSE.G Search velocity Calc. error (F:%d^1) FORC 427 PAUSE.G Search reverse SW invalid (F:%d^1) FORC 428 PAUSE.G Search velocity MAX error (F:%d^1) FORC 444 PAUSE.G Illegal user frame(B/D) (F:%d^1) FORC 445 PAUSE.G Illegal tool frame(B/D) (F:%d^1) FORC 446 PAUSE.G Too much B/D number (F:%d^1) FORC 447 PAUSE.G Illegal B/D (F:%d^1) FORC 448 PAUSE.G Exchange impedance data failed (F:%d^1) FORC 449 PAUSE.G Exchange frequency failed (F:%d^1) FORC 450 PAUSE.G Unknown F/C type (F:%d^1) FORC 451 PAUSE.G Unknown initializing status (F:%d^1) FORC 452 PAUSE.G Illegal cool down rate (F:%d^1) FORC 453 PAUSE.G Illegal tool weight get time (F:%d^1) FORC 454 PAUSE.G Tool weight is uninit (F:%d^1) FORC 455 PAUSE.G Illegal tool weight (F:%d^1) FORC 476 PAUSE.G Illegal I/D number (F:%d^1) FORC 477 PAUSE.G Illegal I/D (F:%d^1) FORC 478 PAUSE.G Illegal vision tool comp. data (F:%d^1) FORC 479 PAUSE.G Illegal vision user comp. data (F:%d^1) FORC 480 PAUSE.G Unknown insertion mode (F:%d^1) FORC 481 PAUSE.G Illegal insertion direction (F:%d^1) FORC 482 PAUSE.G Illegal end condition(approach) (F:%d^1) FORC 483 PAUSE.G Illegal retry number (F:%d^1) FORC 484 PAUSE.G Illegal insertion force (F:%d^1) FORC 485 PAUSE.G Setting torque error failed (F:%d^1) FORC 486 PAUSE.G Setting end cond. failed(TEACH) (F:%d^1) FORC 487 PAUSE.G Setting end cond. failed(USE) (F:%d^1) FORC 488 PAUSE.G Display graph data on debug console (F:%d^1) FORC 489 PAUSE.G Illegal pushing depth (F:%d^1) FORC 490 PAUSE.G Illegal rotation angle max (F:%d^1) FORC 491 PAUSE.G Illegal decelerate time (F:%d^1) FORC 492 PAUSE.G Illegal decel depth rate (F:%d^1) FORC 493 PAUSE.G Illegal rotation direction (F:%d^1) FORC 494 PAUSE.G Illegal initial Fd (F:%d^1) FORC 495 PAUSE.G Illegal velocity adjust gain (F:%d^1) FORC 496 PAUSE.G Illegal starting rate (F:%d^1) FORC 497 PAUSE.G Illegal ending rate (F:%d^1) FORC 498 PAUSE.G Illegal approach length (F:%d^1) FORC 499 PAUSE.G Illegal approach modify time (F:%d^1) FORC 500 PAUSE.G Illegal reduction ratio (F:%d^1) FORC 501 PAUSE.G Illegal velocity adjust switch (F:%d^1) FORC 502 PAUSE.G Illegal overrun length (F:%d^1) FORC 508 PAUSE.G AIT X direction environment NG (F:%d^1) FORC 509 PAUSE.G AIT Y direction environment NG (F:%d^1) FORC 510 PAUSE.G AIT Z direction environment NG (F:%d^1) FORC 511 PAUSE.G AIT W direction environment NG (F:%d^1) FORC 512 PAUSE.G AIT P direction environment NG (F:%d^1) FORC 513 PAUSE.G AIT R direction environment NG (F:%d^1) FORC 514 PAUSE.G AIT X direction unstable (F:%d^1) FORC 515 PAUSE.G AIT Y direction unstable (F:%d^1) FORC 516 PAUSE.G AIT Z direction unstable (F:%d^1) FORC 517 PAUSE.G AIT W direction unstable (F:%d^1) FORC 518 PAUSE.G AIT P direction unstable (F:%d^1) FORC 519 PAUSE.G AIT R direction unstable (F:%d^1) FORC 520 PAUSE.G AIT all switch OFF (F:%d^1) FORC 521 PAUSE.G AIT X direction fail (F:%d^1) FORC 522 PAUSE.G AIT Y direction fail (F:%d^1) FORC 523 PAUSE.G AIT Z direction fail (F:%d^1) FORC 524 PAUSE.G AIT W direction fail (F:%d^1) FORC 525 PAUSE.G AIT P direction fail (F:%d^1) FORC 526 PAUSE.G AIT R direction fail (F:%d^1) FORC 527 PAUSE.G AIT system error (F:%d^1) FORC 528 PAUSE.G AIT system error (F:%d^1) FORC 529 PAUSE.G AIT system error (F:%d^1) FORC 530 PAUSE.G AIT system error (F:%d^1) FORC 531 PAUSE.G AIT system error (F:%d^1) FORC 532 PAUSE.G AIT system error (F:%d^1) FORC 533 PAUSE.G AIT system error (F:%d^1) FORC 534 PAUSE.G AIT system error (F:%d^1) FORC 535 PAUSE.G AIT system error (F:%d^1) FORC 536 PAUSE.G AIT system error (F:%d^1) FORC 537 PAUSE.G AIT system error (F:%d^1) FORC 538 PAUSE.G AIT system error (F:%d^1) FORC 539 PAUSE.G AIT system error (F:%d^1) FORC 540 PAUSE.G AIT system error (F:%d^1) FORC 541 PAUSE.G AIT system error (F:%d^1) FORC 542 PAUSE.G Rotate angle limit (F:%d^1) FORC 543 PAUSE.G AIT system error (F:%d^1) FORC 544 PAUSE.G clutch ins. force lim. (F:%d^1) FORC 545 PAUSE.G clutch ins. & tuning (F:%d^1) FORC 546 PAUSE.G No custom cont. exe. (F:%d^1) FORC 547 PAUSE.G Customize no parent (F:%d^1) FORC 548 PAUSE.G Customize Position NG (F:%d^1) FORC 549 PAUSE.G Customize parent err (F:%d^1) FORC 550 PAUSE.G Customize intr. err0 (F:%d^1) FORC 551 PAUSE.G Customize intr. err1 (F:%d^1) FORC 552 PAUSE.G Customize intr. err2 (F:%d^1) FRSY 1 WARN FROM disk is full FRSY 2 WARN Device not formatted FRSY 3 WARN Invalid parameter FRSY 4 WARN RAM disk must be mounted FRSY 5 WARN Device not mounted FRSY 6 WARN Device is already mounted FRSY 7 WARN Invalid device name FRSY 8 WARN File already exists FRSY 9 WARN Too many files opened FRSY 10 WARN Invalid file position FRSY 11 WARN Directory full FRSY 12 WARN Invalid file access mode FRSY 13 WARN Device is too fragmented FRSY 14 WARN File not found FRSY 15 WARN Invalid file name FRSY 16 WARN Invalid file type FRSY 17 WARN File not open FRSY 18 WARN File is already opened FRSY 19 WARN Command is not supported FRSY 20 WARN RAM disk is full FRSY 21 WARN End of file FRSY 22 WARN File ID exceeded maximum FRSY 23 WARN No blocks were purged FRSY 24 WARN Purge is disabled FRSY 26 WARN CRC check failed FRSY 28 WARN %d out of %d bad FROM blocks HOST 1 WARN End of directory reached HOST 2 WARN File already exists HOST 3 WARN File does not exist HOST 4 WARN Illegal command received HOST 5 WARN Disk is full HOST 6 WARN End of file reached HOST 8 WARN Only one file may be opened HOST 100 WARN Communications error HOST 101 WARN Directory read error HOST 102 WARN Block check error HOST 103 WARN Seek error HOST 104 WARN Disk timeout HOST 105 WARN Write protection violation HOST 106 WARN $PROTOENT entry not found HOST 107 WARN $SERVENT entry not found HOST 108 WARN Internet address not found HOST 109 WARN Host name not found HOST 110 WARN Node not found HOST 111 WARN Cycle power to use Ethernet HOST 112 WARN PANIC: %s HOST 113 WARN PROXY: %s bind error HOST 114 WARN PROXY: %s socket error HOST 115 WARN PROXY: %s listen error HOST 116 WARN PROXY: Remote proxy error HOST 117 WARN PROXY: PMON error HOST 126 WARN Invalid Ethernet address HOST 127 WARN Ethernet firmware not loaded HOST 128 WARN Ethernet hardware not installed HOST 129 WARN Receiver error HOST 130 WARN Buffer alignment wrong HOST 131 WARN Wrong state HOST 132 WARN Can't allocate memory HOST 133 WARN Wrong setup conditions HOST 134 WARN BCC or CRC error HOST 135 WARN Timeout HOST 136 WARN Device not ready HOST 137 WARN Request cancelled HOST 138 WARN Request aborted HOST 139 WARN Invalid function HOST 140 WARN Device offline HOST 141 WARN Protocol Start/Stop error HOST 142 WARN Connection error HOST 143 WARN Comm port cannot be closed HOST 144 WARN Comm Tag error HOST 145 WARN Permission denied HOST 146 WARN Bad address for Comm Tag HOST 147 WARN Block device required HOST 148 WARN Mount device busy HOST 149 WARN No such device HOST 150 WARN Invalid argument HOST 151 WARN No more Ethernet buffers. HOST 158 WARN FTP: no connection available HOST 159 WARN FTP: login failed HOST 160 WARN FTP: tag dismount request ignored HOST 161 WARN FTP: need remote host name HOST 162 WARN FTP: Error on Ethernet Init. HOST 163 WARN EXMG: Invalid Buffer Size HOST 164 WARN EXMG: Read Pending HOST 165 WARN EXMG: Internal Error HOST 166 WARN EXMG: Write Pending HOST 167 WARN EXMG: Connection Error HOST 168 WARN EXMG: Invalid Channel HOST 169 WARN EXMG: Invalid Path HOST 170 WARN EXMG: Invalid Name HOST 171 WARN EXMG: Message Truncated HOST 172 WARN DNS: Host Not Found HOST 173 WARN DNS: Server Failure HOST 174 WARN DNS: Format or Recovery Error HOST 175 WARN DNS: Server Has No Address HOST 176 WARN DNS: Configuration Error HOST 177 WARN Router Name Not Defined HOST 178 WARN Router Address Not Defined HOST 180 WARN NETMEM: buffer is not created HOST 181 WARN NETMEM: time out HOST 182 WARN NETMEM: BD error HOST 183 WARN NETMEM: buffer is auto ack mode HOST 184 WARN NETMEM: transmit BD error HOST 185 WARN NETMEM: receive BD error HOST 186 WARN NETMEM: send socket open fail HOST 187 WARN NETMEM: receive socket open fail HOST 188 WARN PPP init on port %d fails HOST 189 WARN Invalid port number HOST 190 WARN Invalid baud rate HOST 191 WARN Invalid device type HOST 192 WARN PPP channel already initialized HOST 193 WARN TLNT:Login to %s HOST 194 WARN TLNT:Logout of %s HOST 195 WARN TLNT:rejected conn request HOST 196 WARN TLNT:%s already connected HOST 197 WARN TLNT:invalid login id HOST 198 WARN TLNT:invalid password %s HOST 199 WARN TLNT:timeout on %s HOST 200 WARN TLNT:FSAC need lvl %d for %s HOST 201 WARN TLNT:bad access lvl for %s HOST 202 WARN TLNT:invalid port for %s HOST 203 WARN TLNT:from %s HOST 204 WARN SM: Remote Client Name is invalid HOST 205 WARN SM: Tag Already Mounted HOST 206 WARN SM: Bad Port Number HOST 207 WARN SM: Tag is not mounted HOST 208 WARN SM: Not Yet Connected HOST 209 WARN SM: Connection Aborted HOST 210 WARN SM: Connection Timed Out HOST 211 WARN SM: Connection Write Buffer is full HOST 212 WARN SM: Write Direction shut down by Peer HOST 213 WARN SM: Read Direction shut down by Peer HOST 214 WARN SM: Connection is Pending HOST 215 WARN SM: Connection is in use HOST 216 WARN SM: Invalid Socket HOST 217 WARN SM: Socket Error HOST 218 WARN DTP: Connect %s HOST 219 WARN DTP: Monitor %s HOST 220 WARN DTP: Disconnect %s HOST 221 WARN DTP: ident %s HOST 222 WARN DHCP: server %s HOST 223 WARN DHCP: using IP %s HOST 224 WARN DHCP: No response from server HOST 225 WARN DHCP: duplicate IP %s HOST 226 WARN DHCP: Lease time expired HOST 227 WARN DHCP: shutting down ethernet HOST 228 WARN DHCP: invalid reply from server HOST 229 WARN DHCP: request rejected by server HOST 230 WARN DHCP: renewal attempt failed HOST 231 WARN Initializing HOST 232 WARN In progress HOST 233 WARN Failed HOST 234 WARN Success HOST 235 WARN Disabled HOST 236 WARN FTP: servers not auto-started HOST 237 WARN FTP: server tags not available HOST 238 WARN Protected KCL command HOST 239 WARN KCL option not loaded HRTL 1 WARN Not owner HRTL 2 WARN File/Comm Tag does not exist HRTL 3 WARN No such process HRTL 4 WARN Interrupted system call HRTL 5 WARN I/O error HRTL 6 WARN No protocol or device dest HRTL 7 WARN Arg list too long HRTL 8 WARN Exec format error HRTL 9 WARN Bad file number HRTL 10 WARN No children HRTL 11 WARN No more processes HRTL 12 WARN Not enough core HRTL 13 WARN Access permission denied HRTL 14 WARN Invalid Comm Tag HRTL 15 WARN Port device required HRTL 16 WARN Comm Tag already defined HRTL 17 WARN File exists HRTL 18 WARN Cross-device link HRTL 19 WARN Invalid device type HRTL 20 WARN Not a directory HRTL 21 WARN Is a directory HRTL 22 WARN Invalid argument HRTL 23 WARN File table overflow HRTL 24 WARN Too many open files HRTL 25 WARN Not a typewriter HRTL 26 WARN Text file busy HRTL 27 WARN File too large HRTL 28 WARN No space left on device HRTL 29 WARN Illegal seek HRTL 30 WARN Read-only file system HRTL 31 WARN Too many links HRTL 32 WARN Broken pipe HRTL 35 WARN Operation would block HRTL 36 WARN Operation now in progress HRTL 37 WARN Operation now in progress HRTL 38 WARN Socket operation on non-socket HRTL 39 WARN Destination address required HRTL 40 WARN Message size too long HRTL 41 WARN Protocol wrong type HRTL 42 WARN Protocol not available HRTL 43 WARN Protocol not supported HRTL 44 WARN Socket type not supported HRTL 45 WARN Operation not supported HRTL 47 WARN Address family not supported HRTL 48 WARN Address already in use HRTL 49 WARN Can't assign requested address HRTL 50 WARN Network is down HRTL 51 WARN Network is unreachable HRTL 52 WARN Connection dropped on reset HRTL 53 WARN Software caused connect abort HRTL 54 WARN Connection reset by peer HRTL 55 WARN No buffer space available HRTL 56 WARN Socket is already connected HRTL 57 WARN Socket is not connected HRTL 58 WARN Can't send, socket is shutdown HRTL 60 WARN Ethernet Connection timed out HRTL 61 WARN Ethernet Connection refused HRTL 63 WARN Protocol family not supported HRTL 64 WARN Host is down HRTL 65 WARN Host is unreachable HRTL 66 WARN No urgent data HRTL 67 WARN No out of bound data HRTL 68 WARN Device is already attached HRTL 69 WARN Device Function Code invalid HRTL 70 WARN Cannot detach with open files HRTL 71 WARN Device is already allocated HRTL 72 WARN Device doesn't support attach HRTL 73 WARN End of device list reached HRTL 74 WARN Device is not supported HRTL 75 WARN Compressed File too small IB-S 1 PAUSE.G Slave system error(%d) IB-S 2 WARN Slave board not installed IB-S 3 PAUSE.G Slave PCB abnormal(%d) IB-S 4 PAUSE.G Slave No Data Exchange IB-S 5 PAUSE.G Slave watch dog error IB-S 6 PAUSE.L Can not find IBS Group IB-S 7 PAUSE.L IBS Config change Timeout IB-S 8 PAUSE.G Slave Length code error IB-S 9 WARN %s I/O Overmapping no.:%d IB-S 10 WARN Please power OFF/ON for Master IB-S 11 PAUSE.G Master system error(%d) IB-S 12 WARN Master board not installed IB-S 13 PAUSE.G Master PCB abnormal(%d) IB-S 14 PAUSE.G Master No Data Exchange IB-S 15 PAUSE.G Module error IB-S 16 PAUSE.G Module reconfiguration IB-S 17 PAUSE.G Defect W1-interface IB-S 18 PAUSE.G Defect W2-interface IB-S 19 WARN %d: %d.%d %s IB-S 20 PAUSE.G All clear done IB-S 21 PAUSE.G External periphery error IB-S 22 PAUSE.G Defective Datacycle & Rescan IB-S 23 PAUSE.G Transmission Quality Down IB-S 30 PAUSE.G Device missing in last scan IB-S 31 PAUSE.G Device reports other ID IB-S 32 PAUSE.G Device reports other length IB-S 33 PAUSE.G Further device Interface 1 IB-S 34 PAUSE.G Further device Interface 2 IB-S 35 PAUSE.G Device missing in last scan IB-S 36 PAUSE.G Device peripheral error IB-S 37 PAUSE.G Device reconfiguration req IB-S 38 PAUSE.G Dev detect checksum error IB-S 40 PAUSE.G Defective Interface1(local) IB-S 41 PAUSE.G DefectiveInterface2(remote) IB-S 42 PAUSE.G No report ID & length code IB-S 43 PAUSE.G Interrupt IBS connection IB-S 44 PAUSE.G Interrupt IBS local before IB-S 45 PAUSE.G Interrupt IBS local behind IB-S 46 WARN Connect force stopped IB-S 52 PAUSE.G Unknown process data handshake IB-S 56 PAUSE.G No device table found IB-S 57 PAUSE.G IBS controller is defective IB-S 70 PAUSE.G Double address configured IB-S 71 PAUSE.G Device data set len fault IB-S 72 PAUSE.G Process data cfg len fault IB-S 73 PAUSE.G Additional table len fault IB-S 74 PAUSE.G PCP data length fault IB-S 75 PAUSE.G Whole size length fault IB-S 76 PAUSE.G Add table inconsistent IB-S 77 PAUSE.G Max Output offset overstep IB-S 78 PAUSE.G Max Input offset overstep IB-S 79 PAUSE.G Max Offset overstep > 255 IB-S 80 PAUSE.G Module count or offset er IB-S 81 PAUSE.G Out Mod No <> out ofs IB-S 82 PAUSE.G In Mod No <> in ofs IB-S 83 PAUSE.G Real out len <> cfg len IB-S 84 PAUSE.G Real in len <> cfg len IB-S 85 PAUSE.G Overlapped output data IB-S 86 PAUSE.G Overlapped input data IB-S 87 PAUSE.G Out Dev define In module IB-S 88 PAUSE.G In Dev define Out module IB-S 89 PAUSE.G Out Dev define In module IB-S 90 PAUSE.G In Dev define Out module IB-S 91 PAUSE.G Installation depth error IB-S 92 PAUSE.G Length code is unknown IB-S 93 PAUSE.G Remove non exist device IB-S 94 PAUSE.G Device is active IB-S 95 PAUSE.G Config is differ from msg IB-S 101 PAUSE.G Not match Configuration list IB-S 102 PAUSE.G Too many device are connected IB-S 103 PAUSE.G Configuration change (ID-scan) IB-S 104 PAUSE.G Multi data cycle error IB-S 105 PAUSE.G InterBus Timeout process cycle IB-S 106 PAUSE.G Device missing in setup config IB-S 107 PAUSE.G Configuration change (runtime) IB-S 108 PAUSE.G No connection to InterBus-S IB-S 150 PAUSE.G Sequence error IB-S 170 PAUSE.G No warm start command IB-S 171 PAUSE.G Too many modules configured IB-S 172 PAUSE.G More module are connected IB-S 173 PAUSE.G Less module are connected IB-S 174 PAUSE.G Non supported length code IB-S 175 PAUSE.G Wrong length code IB-S 176 PAUSE.G Wrong ident code IB-S 177 PAUSE.G Wrong segment level IB-S 178 PAUSE.G Master Watch dog error IB-S 220 PAUSE.G HOST watchdog failed, timeout IB-S 221 PAUSE.G HOST not acknowledge process IB-S 224 PAUSE.G Error in IBS Controller comm IB-S 260 WARN bit len is set with byte len IB-S 261 WARN %s:New error IB-S 262 WARN %s: %d.%d %s IB-S 263 SYSTEM InterBus has no I/O assignment IB-S 264 PAUSE.G Set system pointer failed IB-S 300 PAUSE.G %s:Bus error IB-S 301 PAUSE.G %s:Max. number was exceeded IB-S 302 PAUSE.G %s:Too many faulty data cycle IB-S 303 PAUSE.G %s:Configuration not activated IB-S 304 PAUSE.G %s:Control_Device_Function IB-S 305 PAUSE.G %s:CRC error in segment IB-S 306 PAUSE.G %s:Error at interface (In) IB-S 307 PAUSE.G %s:Bus error occured IB-S 308 PAUSE.G %s:Device is missing IB-S 309 PAUSE.G %s:Multiple errors in segment IB-S 310 PAUSE.G %s:Multiple timeouts in segment IB-S 311 PAUSE.G %s:CRC error (In) IB-S 312 PAUSE.G %s:Defective interface (In) IB-S 313 PAUSE.G %s:Error at interface (In) IB-S 314 PAUSE.G %s:Interrupted interface (In) IB-S 315 PAUSE.G %s:Transmission error IB-S 316 PAUSE.G %s:Error in segment IB-S 317 PAUSE.G %s:Wrong length code IB-S 318 PAUSE.G %s:Wrong ID code IB-S 319 PAUSE.G %s:Data register error IB-S 320 PAUSE.G %s:Invalid ID code IB-S 321 PAUSE.G %s:Remote device in local bus IB-S 322 PAUSE.G %s:Device not possible IB-S 323 PAUSE.G %s:Defective interface (Out1) IB-S 324 PAUSE.G %s:Defective interface (Out2) IB-S 325 PAUSE.G %s:Interrupted interf. (Out1) IB-S 326 PAUSE.G %s:Interrupted interf. (Out2) IB-S 327 PAUSE.G %s:I/O timeout IB-S 328 PAUSE.G %s:Reset of device IB-S 329 PAUSE.G %s:Device not initialized yet IB-S 330 PAUSE.G %s:Invalid mode at device IB-S 331 PAUSE.G %s:Wrong data length IB-S 332 PAUSE.G %s:Wrong ID code (PCP) IB-S 333 PAUSE.G %s:Inadmissible width (PCP) IB-S 334 PAUSE.G %s:Dynamic PCP cannot be used IB-S 335 PAUSE.G %s:State conflict (On) IB-S 336 PAUSE.G %s:State conflict (Off) IB-S 337 PAUSE.G %s:Operation not possible IB-S 338 PAUSE.G %s:Multiple errors (Out1) IB-S 339 PAUSE.G %s:Multiple timeout (Out1) IB-S 340 PAUSE.G %s:Further device at bus IB-S 341 PAUSE.G %s:Data register error (Out1) IB-S 342 PAUSE.G %s:Defective interface (Out1) IB-S 343 PAUSE.G %s:Further local bus device IB-S 344 PAUSE.G %s:Invalid ID code (Out1) IB-S 345 PAUSE.G %s:Too many devices at local bus IB-S 346 PAUSE.G %s:Multiple errors (Out2) IB-S 347 PAUSE.G %s:Multiple timeouts (Out2) IB-S 348 PAUSE.G %s:Further device at (Out2) IB-S 349 PAUSE.G %s:Data register error (Out2) IB-S 350 PAUSE.G %s:Too many devices activated IB-S 351 PAUSE.G %s:Error in local bus IB-S 352 PAUSE.G %s:Too many devices in local bus IB-S 353 PAUSE.G %s:Invalid ID code (Out2) IB-S 354 PAUSE.G %s:Error on channel IB-S 355 PAUSE.G %s:Short circuit at output IB-S 356 PAUSE.G %s:Initiator supply error IB-S 357 PAUSE.G %s:Power supply error IB-S 358 PAUSE.G %s:Configuration error IB-S 359 PAUSE.G %s:Peripheral electronic error IB-S 360 PAUSE.G %s:Temperature excess IB-S 361 PAUSE.G %s:Loop error (Out2) IB-S 362 PAUSE.G %s:Isolated disconnection error IB-S 380 PAUSE.G %s:Look for Failure IB-S 381 WARN %s:Peripheral warning IB-S 382 PAUSE.G %s:Control Fault IB-S 383 PAUSE.G %s:User Fault IB-S 384 PAUSE.G %s:User Fault (%s) IB-S 390 PAUSE.G %s:Controller Board Error IB-S 391 PAUSE.G %s:Board has not enough memory IB-S 392 PAUSE.G %s:Board checksum error IB-S 393 PAUSE.G %s:Board system error IB-S 394 PAUSE.G %s:is reported by firmware IB-S 395 PAUSE.G %s: Can't execute service IB-S 396 WARN Board status is READY IB-S 397 WARN Board status is ACTIVE IB-S 398 WARN Board status is RUN IB-S 399 WARN Board status is Bus Fail IB-S 400 PAUSE.G %s:Service called w/o Rights IB-S 401 WARN %s:Firmw.command busy now IB-S 402 SYSTEM %s:Board error reported IB-S 403 SYSTEM %s:Firmware error reported IB-S 404 WARN %s:Bus warning time elapsed IB-S 405 WARN %s:Wrong Variable ID IB-S 420 WARN %s:1st Seg. Unswitchable IB-S 421 PAUSE.G %s:Can't enable multiple Alt.Group IB-S 422 PAUSE.G %s:Dev dependency conflict IB-S 423 PAUSE.G %s:Can't take Exclusive Rights IB-S 424 WARN Peripheral warning exists IB-S 425 WARN Peripheral warning cleared IB-S 447 WARN Seg.%d at outgoing remote bus IB-S 448 WARN Seg.%d at outgoing local bus IB-S 449 WARN %d.%d device not found IB-S 450 WARN %d.%d %s IB-S 451 WARN Additional Info %s IB-S 452 PAUSE.G Slave No data Exchange IB-S 453 PAUSE.G Bus Fault is indicated IB-S 454 PAUSE.G CMD mode is selected IB-S 455 PAUSE.G TP mode is selected IB-S 456 WARN Device %d is inserted IB-S 457 WARN Device %d is deleted IB-S 458 PAUSE.G Please power OFF/ON for Master IB-S 459 PAUSE.G Too many device IB-S 461 WARN Can't swich at READY state IB-S 462 WARN Parameterization is performed IB-S 463 WARN Load SVC successful IB-S 464 WARN Clear parm mem is performed IB-S 465 WARN Load Config is performed IB-S 466 SYSTEM Board not ready IB-S 467 WARN BackUp %d board files (%s) IB-S 468 PAUSE.G Slave external power off IB-S 469 PAUSE.G Slave not Init/Ready IB-S 470 PAUSE.G Slave DIP setting mismatch IB-S 471 PAUSE.G Firmware version mismatch IB-S 472 PAUSE.G Please power OFF/ON for Slave IB-S 473 PAUSE.G Parameterization not finished IB-S 474 WARN "Use CMD" setting mismatch IB-S 475 PAUSE.G PCI motherboard not installed IB-S 476 SYSTEM newmem %d failed IB-S 477 SYSTEM mktsk %d failed %d IB-S 478 PAUSE.G Slave Parameterization invalid IB-S 479 SYSTEM Firmware Updating Mode IB-S 480 SYSTEM Sysfail Reset Failed IB-S 481 SYSTEM MPM1 Ready Bit OFF IB-S 482 WARN Alternative Recovery Disabled IB-S 483 PAUSE.G Execute param. for Baud-Rate IB-S 484 PAUSE.G Slave : Power off, Discon. 24V IB-S 485 PAUSE.G Power off or Execute param. IB-S 486 PAUSE.G Power OFF/ON is necessary IB-S 487 PAUSE.G Trying to reset Bus Fault IB-S 488 PAUSE.G Master is not running IB-S 489 WARN Update Dev. Name by Load Conf. IB-S 490 PAUSE.G Parameterization by SVC failed IB-S 491 PAUSE.G SVC file is not loaded IB-S 492 PAUSE.G Alternative is not recovered IB-S 493 PAUSE.G Firmware reply %s timeout IB-S 494 PAUSE.G Slave err1shot is disabled IB-S 495 WARN Failed to enable byte swap IB-S 496 WARN len/ofs not multiple of 16 IB-S 497 WARN Failed to change len/ofs IB-S 498 WARN len/ofs must be multiple of 16 IB-S 500 PAUSE.G Analog I/O setting is invalid IB-S 501 PAUSE.G Welding I/O setting is invalid IB-S 502 WARN AI/AO needs analog I/O option IB-S 503 WARN Welding I/O needs Arc Tool IB-S 504 WARN Restore Alternative manually IB-S 505 PAUSE.G Loading IBPXC.SV (need 1 minute) IB-S 510 PAUSE.G Print: Internal error (%s) IB-S 511 WARN Printing of config. devices IB-S 512 WARN Printing finished IB-S 520 PAUSE.G DevName: Internal error (%s) IB-S 521 PAUSE.G Port already assigned IB-S 522 PAUSE.G Port is invalid IB-S 523 PAUSE.G Set assignment failed IB-S 530 PAUSE.G Save: Internal error (%s) IB-S 531 WARN Start saving DevName List IB-S 532 WARN Saving DevName List finished IB-S 534 PAUSE.G Save: System error (%s) IB-S 535 PAUSE.G Load: Internal error (%s) IB-S 536 WARN Start loading DevName List IB-S 537 WARN Loading DevName List finished IB-S 538 WARN No Integer in Line (%s) IB-S 539 PAUSE.G Load: System error (%s) INTP 1 PAUSE.G Cannot lock the motion grp INTP 2 ABORT.G Program manager internal error INTP 3 ABORT.G Invalid request INTP 4 PAUSE.G Cannot ATTACH with TP enabled INTP 5 PAUSE.G Cannot release motion control INTP 100 ABORT.L (%s^4, %d^5) Internal error (PXnn) INTP 101 ABORT.L (%s^4, %d^5) Internal error (system) INTP 102 ABORT.L (%s^4, %d^5) Code format is invalid INTP 103 ABORT.L (%s^4, %d^5) Program error INTP 104 ABORT.L (%s^4, %d^5) Single step failed INTP 105 ABORT.L (%s^4, %d^5) Run request failed INTP 106 PAUSE.L (%s^4, %d^5) Continue request failed INTP 107 ABORT.L (%s^4, %d^5) Pause request failed INTP 108 ABORT.L (%s^4, %d^5) Abort request failed INTP 109 WARN (%s^4, %d^5) BWD motion request failed INTP 110 WARN (%s^4, %d^5) Get task status request failed INTP 111 WARN (%s^4, %d^5) Skip statement request failed INTP 112 PAUSE.L Cannot call interrupt routine INTP 113 PAUSE.L (%s^4, %d^5) Stop motion request failed INTP 114 PAUSE.L (%s^4, %d^5) Cancel motion request failed INTP 115 PAUSE.L (%s^4, %d^5) Resume motion request failed INTP 116 PAUSE.L (%s^4, %d^5) Hold motion request failed INTP 117 PAUSE.L (%s^4, %d^5) Unhold motion request failed INTP 118 PAUSE.L (%s^4, %d^5) Walk back data request failed INTP 119 PAUSE.L (%s^4, %d^5) Get trace data request failed INTP 120 PAUSE.L (%s^4, %d^5) Unwait action request failed INTP 121 PAUSE.L (%s^4, %d^5) Release inquiry request failed INTP 122 PAUSE.L (%s^4, %d^5) Process motion data failed INTP 123 PAUSE.L (%s^4, %d^5) Process application data failed INTP 124 ABORT.L (%s^4, %d^5) Invalid ITR routine INTP 125 ABORT.L Failed to convert position INTP 126 ABORT.L Vision built-in return failed INTP 127 WARN Power fail detected INTP 128 PAUSE.L Pos reg is locked INTP 129 ABORT.L Cannot use motion group INTP 130 ABORT.L (%s^4, %d^5) Exec status recovery failed INTP 131 ABORT.L Number of stop exceeds limit INTP 132 PAUSE.L Unlocked groups specified INTP 133 PAUSE.L Motion is already released INTP 134 PAUSE.L Over automatic start Max counter INTP 135 PAUSE.L Recovery DO OFF in auto start mode INTP 136 WARN Can not use motion group for dry run function INTP 137 WARN Program specified by $PAUSE_PROG doesn't exist. INTP 138 WARN Program specified by $RESM_DRYPROG doesn't exist. INTP 139 PAUSE.L (%s^4, %d^5) Local variable request failed INTP 200 PAUSE.L (%s^4, %d^5) Unimplemented TP instruction INTP 201 PAUSE.L (%s^4, %d^5) Untaught element encountered INTP 202 PAUSE.L (%s^4, %d^5) Syntax error INTP 203 PAUSE.L (%s^4, %d^5) Variable type mismatch INTP 204 PAUSE.L (%s^4, %d^5) Invalid value for index INTP 205 PAUSE.L (%s^4, %d^5) Analog port access error INTP 206 PAUSE.L (%s^4, %d^5) Digital port access error INTP 207 PAUSE.L (%s^4, %d^5) Group I/O port access error INTP 208 PAUSE.L (%s^4, %d^5) Divide by 0 INTP 209 PAUSE.L (%s^4, %d^5) SELECT is needed INTP 210 PAUSE.L (%s^4, %d^5) Start TIMER failed INTP 211 PAUSE.L (%s^4, %d^5) Delete TIMER failed INTP 212 PAUSE.L (%s^4, %d^5) Invalid value for OVERRIDE INTP 213 PAUSE.L %s^7 (%s^4, %d^5) UALM[%d^9] INTP 214 PAUSE.L (%s^4, %d^5) Specified group not locked INTP 215 PAUSE.L (%s^4, %d^5) Group mismatch INTP 216 PAUSE.L (%s^4, %d^5) Invalid value for group number INTP 217 PAUSE.L (%s^4, %d^5) SKIP CONDITION needed INTP 218 PAUSE.L (%s^4, %d^5) Skip failed INTP 219 ABORT.L (%s^4, %d^5) Pause task failed INTP 220 ABORT.L (%s^4, %d^5) Abort task failed INTP 221 PAUSE.L (%s^4, %d^5) Application failed INTP 222 PAUSE.L (%s^4, %d^5) Call program failed INTP 223 PAUSE.L (%s^4, %d^5) Delay time failed INTP 224 PAUSE.L (%s^4, %d^5) Jump label failed INTP 225 PAUSE.L (%s^4, %d^5) Motion statement failed INTP 226 PAUSE.L (%s^4, %d^5) Read position register failed INTP 227 PAUSE.L (%s^4, %d^5) Write position register failed INTP 228 PAUSE.L (%s^4, %d^5) Read register failed INTP 229 PAUSE.L (%s^4, %d^5) Write register failed INTP 230 PAUSE.L (%s^4, %d^5) Wait condition failed INTP 231 PAUSE.L (%s^4, %d^5) Read next line failed INTP 232 PAUSE.L (%s^4, %d^5) Invalid frame number INTP 233 PAUSE.L (%s^4, %d^5) Read frame value failed INTP 234 PAUSE.L (%s^4, %d^5) Write frame value failed INTP 235 PAUSE.L (%s^4, %d^5) Read pos item failed INTP 236 PAUSE.L (%s^4, %d^5) Write pos item failed INTP 237 WARN (%s^4, %d^5) No more motion for BWD INTP 238 WARN (%s^4, %d^5) BWD execution completed INTP 239 WARN (%s^4, %d^5) Cannot execute backwards INTP 240 PAUSE.L (%s^4, %d^5) Incompatible data type INTP 241 PAUSE.L (%s^4, %d^5) Unsupported parameter INTP 242 PAUSE.L (%s^4, %d^5) Offset value is needed INTP 243 ABORT.L (%s^4, %d^5) Def grp is not specified INTP 244 PAUSE.L (%s^4, %d^5) Invalid line number INTP 245 PAUSE.L (%s^4, %d^5) RCV stmt failed INTP 246 PAUSE.L (%s^4, %d^5) SEMAPHORE stmt failed INTP 247 PAUSE.L (%s^4, %d^5) Pre exec failed INTP 248 PAUSE.L (%s^4, %d^5) MACRO failed INTP 249 PAUSE.L Macro is not set correctly INTP 250 PAUSE.L (%s^4, %d^5) Invalid uframe number INTP 251 PAUSE.L (%s^4, %d^5) Invalid utool number INTP 252 PAUSE.L User frame number mismatch INTP 253 PAUSE.L Tool frame number mismatch INTP 254 PAUSE.L (%s^4, %d^5) Parameter not found INTP 255 PAUSE.L (%s^4, %d^5) CAL_MATRIX failed INTP 256 PAUSE.L (%s^4, %d^5) No data for CAL_MATRIX INTP 257 PAUSE.L (%s^4, %d^5) Invalid delay time INTP 258 PAUSE.L (%s^4, %d^5) Weld port access error INTP 259 PAUSE.L (%s^4, %d^5) Invalid position type INTP 260 PAUSE.L (%s^4, %d^5) Invalid torque limit value INTP 261 PAUSE.L (%s^4, %d^5) Array subscript missing INTP 262 PAUSE.L (%s^4, %d^5) Field name missing INTP 263 PAUSE.L (%s^4, %d^5) Invalid register type INTP 265 PAUSE.L (%s^4, %d^5) Invalid value for speed value INTP 266 ABORT.L (%s^4, %d^5) Mnemonic in interupt is failed INTP 267 PAUSE.L (%s^4, %d^5) RUN stmt failed INTP 268 PAUSE.L (%s^4, %d^5) This statement only one in each line INTP 269 PAUSE.L (%s^4, %d^5) Skip statement only one in each line INTP 270 PAUSE.L (%s^4, %d^5) Different group cannot BWD INTP 271 WARN (%s^4, %d^5) Excessive torque limit value INTP 272 PAUSE.L (%s^4, %d^5) Unsupported operator INTP 273 PAUSE.L (%s^4, %d^5) Too many conditions INTP 274 PAUSE.L (%s^4, %d^5) CH program error INTP 275 PAUSE.L Invalid sub type of CH program INTP 276 PAUSE.L (%s^4, %d^5) Invalid combination of motion option INTP 277 PAUSE.L (%s^4, %d^5) Internal MACRO EPT data mismatch INTP 278 PAUSE.L %s^7 INTP 279 PAUSE.L (%s^4, %d^5) Application instruction mismatch INTP 280 PAUSE.L (%s^4, %d^5) Application data mismatch INTP 281 PAUSE.L No application data INTP 283 PAUSE.L (%s^4, %d^5) Stack over flow for fast fault recovery INTP 284 PAUSE.L No detection of fast fault recovery INTP 285 WARN Karel program cannot entry in fast fautl recovery INTP 286 WARN MAINT program isn't defined in fast fautl recovery INTP 287 PAUSE.L Fail to execute MAINT program INTP 288 PAUSE.L (%s^4, %d^5) Parameter does not exist INTP 289 PAUSE.L Can't save ffast point at program change INTP 290 PAUSE.L Fast fault recovery position is not saved INTP 291 WARN (%s^4, %d^5) Index for AR is not correct INTP 292 PAUSE.L more than 6 motion with DB executed INTP 293 PAUSE.L (%s,%d)DB too small(away)(%dmm). INTP 294 ABORT.G TPE parameter error INTP 295 WARN (%s,%d)DB too small(away)(%dmm). INTP 296 WARN (%s,%d) $SCR_GRP[%d].$M_POS_ENB is FALSE. INTP 297 WARN (%s,%d)DB too small(done)(%dmm) INTP 298 WARN (%s,%d)DB interrupt error(%d) INTP 299 PAUSE.L (%s,%d)DB interrupt error(%d) INTP 300 ABORT.L (%s^4, %d^5) Unimplemented P-code INTP 301 ABORT.L (%s^4, %d^5) Stack underflow INTP 302 ABORT.L (%s^4, %d^5) Stack overflow INTP 303 ABORT.L (%s^4, %d^5) Specified value exceeds limit INTP 304 ABORT.L (%s^4, %d^5) Array length mismatch INTP 305 ABORT.L (%s^4, %d^5) Error related condition handler INTP 306 ABORT.L (%s^4, %d^5) Attach request failed INTP 307 ABORT.L (%s^4, %d^5) Detach request failed INTP 308 ABORT.L (%s^4, %d^5) No case match is encountered INTP 309 ABORT.L (%s^4, %d^5) Undefined WITHCH parameter INTP 310 ABORT.L (%s^4, %d^5) Invalid subscript for array INTP 311 PAUSE.L (%s^4, %d^5) Uninitialized data is used INTP 312 ABORT.L (%s^4, %d^5) Invalid joint number INTP 313 ABORT.L (%s^4, %d^5) Motion statement failed INTP 314 ABORT.L (%s^4, %d^5) Return program failed INTP 315 ABORT.L (%s^4, %d^5) Built-in execution failed INTP 316 ABORT.L (%s^4, %d^5) Call program failed INTP 317 ABORT.L (%s^4, %d^5) Invalid condition specified INTP 318 ABORT.L (%s^4, %d^5) Invalid action specified INTP 319 ABORT.L (%s^4, %d^5) Invalid type code INTP 320 ABORT.L (%s^4, %d^5) Undefined built-in INTP 321 ABORT.L (%s^4, %d^5) END stmt of a func rtn INTP 322 ABORT.L (%s^4, %d^5) Invalid arg val for builtin INTP 323 ABORT.L (%s^4, %d^5) Value overflow INTP 324 ABORT.L (%s^4, %d^5) Invalid open mode string INTP 325 ABORT.L (%s^4, %d^5) Invalid file string INTP 326 ABORT.L (%s^4, %d^5) File var is already used INTP 327 ABORT.L (%s^4, %d^5) Open file failed INTP 328 ABORT.L (%s^4, %d^5) File is not opened INTP 329 ABORT.L (%s^4, %d^5) Write variable failed INTP 330 ABORT.L (%s^4, %d^5) Write file failed INTP 331 ABORT.L (%s^4, %d^5) Read variable failed INTP 332 ABORT.L (%s^4, %d^5) Read data is too short INTP 333 ABORT.L (%s^4, %d^5) Invalid ASCII string for read INTP 334 ABORT.L (%s^4, %d^5) Read file failed INTP 335 ABORT.L (%s^4, %d^5) Cannot open pre-defined file INTP 336 ABORT.L (%s^4, %d^5) Cannot close pre-defined file INTP 337 ABORT.L (%s^4, %d^5) Invalid routine type INTP 338 ABORT.L (%s^4, %d^5) Close file failed INTP 339 ABORT.L (%s^4, %d^5) Invalid program name INTP 340 ABORT.L (%s^4, %d^5) Invalid variable name INTP 341 ABORT.L (%s^4, %d^5) Variable not found INTP 342 ABORT.L (%s^4, %d^5) Incompatible variable INTP 343 ABORT.L (%s^4, %d^5) Reference stack overflow INTP 344 ABORT.L (%s^4, %d^5) Readahead buffer overflow INTP 345 ABORT.L (%s^4, %d^5) Pause task failed INTP 346 ABORT.L (%s^4, %d^5) Abort task failed INTP 347 ABORT.L (%s^4, %d^5) Read I/O value failed INTP 348 ABORT.L (%s^4, %d^5) Write I/O value failed INTP 349 ABORT.L (%s^4, %d^5) Hold motion failed INTP 350 ABORT.L (%s^4, %d^5) Unhold motion failed INTP 351 ABORT.L (%s^4, %d^5) Stop motion failed INTP 352 ABORT.L (%s^4, %d^5) Cancel motion failed INTP 353 ABORT.L (%s^4, %d^5) Resume motion failed INTP 354 ABORT.L (%s^4, %d^5) Break point failed INTP 355 ABORT.L (%s^4, %d^5) AMR is not found INTP 356 ABORT.L (%s^4, %d^5) AMR is not processed yet INTP 357 ABORT.L (%s^4, %d^5) WAIT_AMR is cancelled INTP 358 ABORT.L (%s^4, %d^5) Timeout at read request INTP 359 ABORT.L (%s^4, %d^5) Read request is nested INTP 360 ABORT.L (%s^4, %d^5) Vector is 0 INTP 361 PAUSE.L (%s^4, %d^5) FRAME:P2 is same as P1 INTP 362 PAUSE.L (%s^4, %d^5) FRAME:P3 is same as P1 INTP 363 PAUSE.L (%s^4, %d^5) FRAME:P3 exists on line P2-P1 INTP 364 ABORT.L (%s^4, %d^5) String too short for data INTP 365 ABORT.L (%s^4, %d^5) Predefined window not opened INTP 366 ABORT.L (%s^4, %d^5) I/O status is not cleared INTP 367 ABORT.L (%s^4, %d^5) Bad base in format INTP 368 PAUSE.L (%s^4, %d^5) Cannot use specified program INTP 369 ABORT.L (%s^4, %d^5) Timeout at WAIT_AMR INTP 370 ABORT.L (%s^4, %d^5) Vision CPU not plugged in INTP 371 ABORT.L (%s^4, %d^5) Vision built-in overflow INTP 372 ABORT.L (%s^4, %d^5) Undefined vision built-in INTP 373 ABORT.L (%s^4, %d^5) Undefined vision parameter type INTP 374 ABORT.L (%s^4, %d^5) Undefined vision return type INTP 375 ABORT.L (%s^4, %d^5) System var passed using BYNAME INTP 376 ABORT.L (%s^4, %d^5) Motion in ISR failed INTP 377 WARN (%s^4, %d^5) Local COND recovery failed INTP 378 WARN (%s^4, %d^5) Local variable is used INTP 379 ABORT.L Bad condition handler number INTP 380 ABORT.L Bad program number INTP 381 ABORT.L (%s^4, %d^5) Invalid Delay Time INTP 382 ABORT.L (%s^4, %d^5) Invalid bit field value INTP 383 PAUSE.L (%s^4, %d^5) Path node out of range INTP 400 ABORT.L (%s^4, %d^5) Number of motions exceeded INTP 401 ABORT.L (%s^4, %d^5) Not On Top Of Stack INTP 420 PAUSE.L (%s^4, %d^5) OFIX is not available INTP 421 WARN (%s^4, %d^5) Stitch disable(S/S) INTP 422 WARN (%s^4, %d^5) Stitch enable signal off INTP 423 PAUSE.L (%s^4, %d^5) Eq.condition signal error INTP 424 PAUSE.L (%s^4, %d^5) Stitch speed error INTP 425 PAUSE.L (%s^4, %d^5) Illegal motion type(J) INTP 426 PAUSE.L (%s^4, %d^5) Another prog is in stitching INTP 427 WARN (%s^4, %d^5) Stitch disable(T1 mode) INTP 430 PAUSE.L (%s^4, %d^5) Dry Run needs other groups INTP 431 PAUSE.L (%s^4, %d^5) Dry Run on Incremental motion INTP 432 PAUSE.L (%s^4, %d^5) Dry Run on Circular motion INTP 433 PAUSE.L (%s^4, %d^5) Dry Run in P-SPS INTP 434 PAUSE.L Please do BWD to exit P-SPS INTP 435 PAUSE.L Dry Run execution error INTP 436 PAUSE.L (%s^4, %d^5) Invalid item for output INTP 437 PAUSE.L (%s^4, %d^5) Marker nesting too deep INTP 438 PAUSE.L (%s^4, %d^5) Undefined Marker INTP 439 PAUSE.L (%s^4, %d^5) Marker conflict INTP 440 PAUSE.L (%s^4) Stopped by TC_ONLINE INTP 441 WARN Please stop Background Logic INTP 442 PAUSE.G (%s^4, %d^5) Background program is changed INTP 443 PAUSE.L (%s^4, %d^5) Invalid item for Mixed Logic INTP 444 PAUSE.L (%s^4, %d^5) Invalid item for Fast mode INTP 445 WARN (%s^4, %d^5) Indirection in Fast mode INTP 446 PAUSE.L (%s^4, %d^5) Too many parentheses INTP 447 PAUSE.L (%s^4, %d^5) Parentheses mismatch INTP 448 WARN Fast mode programs too big INTP 449 PAUSE.L (%s^4, %d^5) Marker recursion INTP 450 PAUSE.L (%s^4, %d^5) Cannot call KAREL program INTP 451 PAUSE.L (%s^4, %d^5) Cannot call Motion program INTP 452 PAUSE.L (%s^4, %d^5) Robot link type mismatch INTP 453 PAUSE.L (%s^4, %d^5) Not in remote INTP 454 ABORT.L (%s^4, %d^5) Illegal return occurred INTP 455 PAUSE.L (%s^4, %d^5) Group mismatch(Link pattern) INTP 456 PAUSE.L (%s^4, %d^5) Group mismatch(Slave group) INTP 457 PAUSE.L (%s^4, %d^5) Master tool number mismatch INTP 458 PAUSE.L (%s^4, %d^5) Robot is still moving INTP 459 PAUSE.L (%s^4, %d^5) Slave cannot JOINT motion INTP 460 PAUSE.L (%s^4, %d^5) Cannot use JOINT pos for Slave INTP 461 PAUSE.L (%s^4, %d^5) Master TP is enabled INTP 462 ABORT.L (%s^4, %d^5) Cannot start Robot Link INTP 463 PAUSE.L (%s^4, %d^5) Motion group is Master INTP 464 PAUSE.L (%s^4, %d^5) Motion group is Slave INTP 465 ABORT.L (%s^4, %d^5) Tracking error INTP 466 PAUSE.L (%s^4, %d^5) Robot link not calibrated INTP 467 PAUSE.L (%s^4, %d^5) Cannot use INC for Slave INTP 468 PAUSE.L (%s^4, %d^5) Cannot use OFFSET for Slave INTP 469 PAUSE.L (%s^4, %d^5) BWD is failed for Master INTP 470 PAUSE.L (%s^4, %d^5) Not support BWD for Slave INTP 471 PAUSE.L (%s^4, %d^5) Robot is Master(Manual) INTP 472 PAUSE.G (%s^4, %d^5) Robot is Slave(Manual) INTP 473 PAUSE.L (%s^4, %d^5) Synchro ID is ZERO INTP 474 PAUSE.L (%s^4, %d^5) Synchro ID mismatch INTP 475 PAUSE.L (%s^4, %d^5) Cannot single step INTP 476 ABORT.L (%s^4, %d^5) BWD is failed INTP 477 ABORT.L (%s^4, %d^5) Cannot run Slave directly INTP 478 WARN This group can not be MASTER INTP 479 PAUSE.G Bad Hostname or Address(MASTER) INTP 480 PAUSE.G Bad Hostname or Address(SLAVE) INTP 481 PAUSE.G Bad Synchronization ID INTP 482 PAUSE.G Bad Link Pattern Number INTP 483 PAUSE.G Bad Master Number INTP 484 PAUSE.G Bad Group number (MASTER) INTP 485 PAUSE.G Bad Group number (SLAVE) INTP 486 PAUSE.G SLAVE is not calibrated INTP 487 PAUSE.G No Valid SLAVE in Link Pattern INTP 488 PAUSE.G RLINK communication timeout INTP 489 PAUSE.G Bad Hostname or Address, Group INTP 490 PAUSE.G Timeout for link start INTP 491 PAUSE.G Linked robot or comm stopped INTP 492 PAUSE.G Master program stopped INTP 493 PAUSE.G Slave program stopped INTP 530 PAUSE.L (%s^4, %d^5) PS is not available INTP 531 PAUSE.L (%s^4, %d^5) PS motion limit INTP 532 PAUSE.L (%s^4, %d^5) PS item limit INTP 533 PAUSE.L PS(%s^4,%d^5-%d^9)Invalid PS INTP 534 PAUSE.L PS(%s^4,%d^5-%d^9)time is not available INTP 535 WARN PS(%s,%d-%d)Undone PS exists INTP 536 ABORT.L PS error (0x%X) INTP 537 ABORT.L PS Failed to get cur pos(G:%d) INTP 538 PAUSE.L PS(%s,%d-%d)Error PS exists INTP 539 WARN PS(%s,%d-%d,%dmm)Already in area INTP 540 PAUSE.L PS(%s,%d-%d,%dmm)Already in area INTP 541 WARN PS(%s,%d-%d,%dmm)Forced trigger INTP 542 PAUSE.L PS(%s,%d-%d,%dmm)No trigger INTP 543 WARN PS(%s,%d-%d)Cancel pending PS INTP 544 WARN PS(%s,%d-%d)Time value limit INTP 560 WARN DB was deleted INTP 561 PAUSE.L DB was deleted INTP 570 ABORT.L IBGN internal error INTP 571 PAUSE.L IBGN file format error(%d^9) INTP 572 PAUSE.L IBGN file cannot open INTP 573 WARN IBGN rtcp and usual tool mixed INTP 574 PAUSE.L No motion statement exected before RECORD start INTP 575 PAUSE.L IBGN ITP time does not match INTP 576 PAUSE.L IBGN TCP data does not match INTP 577 PAUSE.L IBGN Program can not be restarted INTP 578 WARN IBGN RECORD interrupted INTP 579 WARN IBGN RECORD doesn't work in single step mode INTP 580 PAUSE.L IBGN Buffer is empty INTP 581 ABORT.L IBGN Cannot execute backwards INTP 582 WARN IBGN RECORD buffer is full INTP 583 WARN IBGN program call/return during RECORD INTP 584 WARN IBGN tool changed during RECORD INTP 585 WARN IBGN user frame changed during RECORD INTP 586 WARN IBGN jmp label during RECORD INTP 587 WARN IBGN illegal speed unit(%s,%d) INTP 588 PAUSE.L IBGN Buffer is full INTP 589 PAUSE.L IBGN teach error INTP 590 WARN IBGN File transfer failed INTP 591 PAUSE.L IBGN FWD execution cannot be done INTP 592 PAUSE.L IBGN RECORD index mismatch(%d, %d) INTP 593 PAUSE.L IBGN file cannot read INTP 594 PAUSE.L IBGN record file is being copied INTP 595 WARN Updating IBGN exe file INTP 596 WARN Saving IBGN exe file INTP 597 WARN IBGN exe file is in use INTP 598 WARN IBGN no record data INTP 599 PAUSE.L IBGN Now recording INTP 600 WARN IBGN RECORD file index error INTP 601 PAUSE.L IBGN more than 256 characters in a line JOG 1 WARN Overtravel Violation JOG 2 WARN Robot not Calibrated JOG 3 WARN No Motion Control JOG 4 WARN Illegal linear jogging JOG 5 WARN Can not clear hold flag JOG 6 WARN Subgroup does not exist JOG 7 WARN Press shift key to jog JOG 8 WARN Turn on TP to jog JOG 9 WARN Hold deadman to jog JOG 10 WARN Jog pressed before shift JOG 11 WARN Utool changed while jogging JOG 12 WARN manual brake enabled JOG 13 WARN Stroke limit (G:%d A:%x Hex) JOG 14 WARN Vertical fixture position JOG 15 WARN Horizontal fixture position JOG 16 SERVO Softfloat time out(G:%d) JOG 17 WARN At R-Theta robot posture JOG 18 WARN Not at R-Theta robot posture JOG 20 WARN Can not PATH JOG now JOG 21 WARN Multi key is pressed JOG 22 WARN Disabled in JOINT path JOG 23 WARN Available only in PAUSE JOG 24 WARN Currently this key is invalid JOG 25 WARN J4 is not zero JOG 26 WARN J4 is zero JOG 27 WARN Reverse direction from J4=0 JOG 28 WARN OFIX TCP config limit JOG 29 WARN OFIX jog error JOG 30 WARN Can't jog as OFIX KCLI 2 WARN Undefined parse syntax error. KCLI 7 WARN Not enough memory to perform command. KCLI 8 WARN Integer expected. KCLI 9 WARN PATH data type is not allowed in arrays. KCLI 10 WARN Number of array dimensions exceeded maximum. KCLI 11 WARN Number of values entered exceeds maximum. KCLI 12 WARN A maximum of 3 values can be entered for VECTOR types. KCLI 13 WARN Entry not allowed when multiple values entered. KCLI 14 WARN Multiple entries not allowed. KCLI 15 WARN Id must be defined before this use. Id: %s KCLI 16 WARN Id is undefined, it must be defined before use in a TYPE section. Id: %s KCLI 17 WARN Group number is not in valid range. KCLI 18 WARN Number expected. KCLI 19 WARN Integer or "*" expected. KCLI 20 WARN Program name expected. KCLI 21 WARN "=" expected. KCLI 22 WARN "[" expected. KCLI 23 WARN "]" expected. KCLI 24 WARN "OF" expected. KCLI 25 WARN "GROUP" expected. KCLI 26 WARN "," or "]" expected. KCLI 27 WARN ":" expected. KCLI 28 WARN 'dd-mmm-yy hh:mm' expected. KCLI 29 WARN Type name expected. KCLI 30 WARN Field name expected. KCLI 31 WARN Variable name or value expected. KCLI 32 WARN Variable not defined. Var: %s KCLI 33 WARN Indexing invalid. Index: %s KCLI 34 WARN Id type is not an ARRAY or indexing exceeded number of dimensions. Id: %s KCLI 35 WARN Id type is not a STRUCTURE. Id: %s KCLI 36 WARN Id type is not a field in a STRUCTURE. Id: %s KCLI 37 WARN Data type mismatch. KCLI 38 WARN Wildcard characters are permitted only in the SET VARIABLE command. KCLI 39 WARN Not valid element name. KCLI 40 WARN Error detected by Varaiable Manager. KCLI 41 WARN Variable to be set is specified incorrectly. KCLI 42 WARN Array of user type is not implemented yet. KCLI 43 WARN User type not implemented yet. KCLI 44 WARN Cannot open file %s. KCLI 45 WARN A maximum of 6 entries is permitted. KCLI 46 WARN ALL, BREAK, DICT, PROG, or VARS expected. KCLI 47 WARN VAR expected. KCLI 48 WARN NODE, FILE or VAR expected. KCLI 49 WARN NODE expected. KCLI 50 WARN ALL, DICT, FORM, MASTER, PROG, SERVO, SYSTEM, TP, or VARS expected. KCLI 51 WARN PROG or VAR expected. KCLI 52 WARN FILE, VAR, or VARS expected. KCLI 53 WARN MASTER, SERVO, SYSTEM, TP, or VARS expected. KCLI 54 WARN TASK, TRACE, VAR, or VERIFY expected. KCLI 55 WARN TASKS, TRACE, TYPES, VAR, VARS or data_type expected. KCLI 56 WARN FILE or NODE expected. KCLI 57 WARN FILE expected. KCLI 58 WARN Variables of this type cannot be recorded. KCLI 59 WARN CONDITION or PROGRAM expected. KCLI 60 WARN Too many arguments specified. KCLI 61 WARN Structure type expected. KCLI 62 WARN ON or OFF expected. KCLI 63 WARN BREAK or CONDITION expected. KCLI 64 WARN PROGRAM expected. KCLI 65 WARN Variable name expected. KCLI 66 WARN File specification expected. KCLI 67 WARN DEFAULT, ENGLISH, JAPANESE, FRENCH, GERMAN, or SPANISH expected. KCLI 68 WARN Language has not been created yet. Use SHOW LANGS for available languages. KCLI 69 WARN DPADD returned a status of %d. KCLI 70 WARN Default program name not set. KCLI 71 WARN Device specification expected. KCLI 72 WARN "TO" expected. KCLI 73 WARN File name exceeds %d characters. KCLI 74 WARN "NODEDATA" expected. KCLI 75 WARN "PATHHEADER" expected. KCLI 76 WARN Dictionary name expected. KCLI 77 WARN File name expected. KCLI 78 WARN Integer or real expected. KCLI 79 WARN Unrecognized command. KCLI 80 WARN Must specify DRAM when loading from port device. KCLI 81 WARN ALL or port_name expected. KCLI 82 WARN Device not supported. KCLI 83 WARN DONE or PAUSE expected. KCLI 84 WARN Port name expected. KCLI 85 WARN Attribute name expected. KCLI 86 WARN Cannot record on extended axes robot. KCLI 87 WARN PRIORITY or TRACELEN expected. KCLI 88 WARN String size must be greater than 0 and less than 129. KCLI 89 WARN "CMOS" or "DRAM" expected. KCLI 90 WARN DICT or FORM expected. KCLI 91 WARN Keeping existing RD: KCLI 92 WARN Files exist in RD: KCLI 93 WARN DISMOUNT of existing RD: failed KCLI 94 WARN FORMAT of new RD: failed KCLI 95 WARN MOUNT of new RD: failed KCLI 96 WARN No user currently logged in. KCLI 97 WARN Could not open file %s KCLI 98 WARN Input file_spec must have an extension of .VR, .SV .IO, or .SP KCLI 99 WARN KCONVARS file_spec <out_file_spec> KCLI 100 WARN Routine name expected. KCLI 101 WARN Quoted string expected. KCLI 102 WARN VAR or VARS expected. KCLI 103 WARN Routine not found in program. KCLI 104 WARN No local data defined for routine. KCLI 105 WARN Local variable data size mismatch. KCLI 106 WARN Not allowed in AUTO mode KCLI 107 WARN Routine stack file (.RS) does not match loaded p-code file (.PC) KCLI 108 WARN PATH data types are not supported. LANG 4 WARN File is not open LANG 5 WARN Program type is different LANG 6 WARN Invalid or corrupted TP file LANG 14 WARN Program already exists LANG 15 WARN Can not write file LANG 16 WARN Can not read file LANG 17 WARN File format is incorrect LANG 18 WARN Group mask value is incorrect LANG 50 WARN %s contains %s, program/file names must match LANG 51 WARN Wrong daughter program name LANG 52 WARN Cannot load daughter program(%d) LANG 53 WARN Cannot process daughter program LANG 75 WARN Invalid attribute syntax LANG 76 WARN Invalid application syntax LANG 77 WARN Invalid mnenonic syntax LANG 78 WARN Invalid position syntax LANG 79 WARN Invalid section LANG 80 WARN Invalid filename LANG 81 WARN Invalid application header LANG 90 WARN Buffer is too small LANG 94 WARN File already exists LANG 95 WARN File does not exist LANG 96 WARN Disk is full LANG 97 WARN Only one file may be opened LANG 98 WARN Disk timeout LANG 99 WARN Write protection violation LANG 100 WARN Device error LSR 0 WARN UNUSED ERROR CODE(LW00) LSR 1 PAUSE.L Other program is locking laser LSR 2 ABORT.L This program doesn't have LE LSR 3 PAUSE.L System does't have laser-appl LSR 4 PAUSE.L Illegal VEIN revolution LSR 8 PAUSE.L AGS signals are not set LSR 9 WARN LE execution without LP, LS LSR 11 PAUSE.L Other motion is locking laser LSR 12 PAUSE.L Undefined EQ number in program LSR 13 PAUSE.L Program can't start in RFHV LSR 18 WARN Program is executing LSR 21 PAUSE.L Illegal number of equipment LSR 22 PAUSE.L Board condition has changed LSR 39 PAUSE.L Not ready of assist gas LSR 40 PAUSE.L Not set assist gas output data LSR 41 PAUSE.L Illegal assist gas output data LSR 55 PAUSE.L Shutter still not open LSR 56 PAUSE.L Shutter still not close LSR 62 PAUSE.L Illegal schedule data number LSR 74 PAUSE.L Joint motion in LASER exec LSR 79 PAUSE.L Jogged while laser is paused LSR 80 PAUSE.L Abnormal cabinet temparature LSR 81 PAUSE.L Not ready of laser oscillator LSR 82 PAUSE.L Not ready of chiller LSR 83 PAUSE.L Chiller water volume drop LSR 84 PAUSE.L Lower purge gas pressure LSR 85 PAUSE.L Abnormal blower temparature LSR 86 PAUSE.L Water leak or Over humidity LSR 87 PAUSE.L Abnormal absober temparature LSR 88 PAUSE.L Leak of tubes LSR 89 PAUSE.L Not arrive setting pressure LSR 90 PAUSE.L Lamp voltage drop LSR 91 PAUSE.L Fiber Overheat or disconnect LSR 92 PAUSE.L Safety interlock LSR 93 PAUSE.L Can't turn off in this status LSR 94 PAUSE.L Servo off alarm happened LSR 95 PAUSE.L Lamp discharge starting error LSR 96 PAUSE.L Uncorrect tube selection LSR 97 PAUSE.L Abnormal Shutter temparature LSR 98 PAUSE.L Abnormal external mirror LSR 99 PAUSE.L RDI7 broken LSR 100 PAUSE.L Hight sensor alarm happened LSR 102 PAUSE.L Emergency stop LSR 104 PAUSE.L Power supply system #1 alarm LSR 105 PAUSE.L Power supply system #2 alarm LSR 106 PAUSE.L Power supply system #3 alarm LSR 107 PAUSE.L Power supply system #4 alarm LSR 108 PAUSE.L Power supply system #5 alarm LSR 109 PAUSE.L Power supply system #6 alarm LSR 110 PAUSE.L Power supply system #7 alarm LSR 111 PAUSE.L Power supply system #8 alarm LSR 112 PAUSE.L Power supply system #9 alarm LSR 113 PAUSE.L Power supply system #10 alarm LSR 114 PAUSE.L Power supply system #11 alarm LSR 115 PAUSE.L Power supply system #12 alarm LSR 116 PAUSE.L Power supply system #13 alarm LSR 117 PAUSE.L Power supply system #14 alarm LSR 118 PAUSE.L Power supply system #15 alarm LSR 119 PAUSE.L Power supply system #16 alarm LSR 121 PAUSE.L Power fail recovery LSR 122 WARN Shutter is mechanical locked LSR 123 WARN Alignment beam is active LSR 124 PAUSE.L Laser oscillator down LSR 125 WARN External shtr signal is locked LSR 126 WARN External beam signal is locked LSR 127 WARN Warning of a power calibration coefficient LSR 128 PAUSE.L Abnormal inverter 1 LSR 129 PAUSE.L Abnormal inverter 2 LSR 130 WARN Blower Gress 1 LSR 131 WARN Blower Gress 2 LSR 132 PAUSE.L Abnormal turbo current 1 LSR 133 PAUSE.L Abnormal turbo current 2 LSR 134 PAUSE.L Abnormal turbo temparature 1 LSR 135 PAUSE.L Abnormal turbo temparature 2 LSR 136 PAUSE.L Abnormal revolution 1 LSR 137 PAUSE.L Abnormal revolution 2 LSR 138 PAUSE.L Not arrival AR 1 signal LSR 139 PAUSE.L Not arrival AR 2 signal LSR 140 PAUSE.L AD1 illegal conversion LSR 141 PAUSE.L AD2 illegal conversion LSR 142 PAUSE.L Laser output power drop LSR 143 PAUSE.L Abnormal laser gas pressure LSR 144 PAUSE.L Pressure sensor is negative LSR 145 PAUSE.L Lamp voltage drop LSR 146 PAUSE.L Power table error LSR 147 PAUSE.L Abnormal beam reflection LSR 148 PAUSE.L Laser beam not ready LSR 153 PAUSE.L No.1 Fiber is damaged LSR 154 PAUSE.L No.2 Fiber is damaged LSR 155 PAUSE.L No.3 Fiber is damaged LSR 156 PAUSE.L No.4 Fiber is damaged LSR 157 WARN Purity warning LSR 158 PAUSE.L Lamp alarm LSR 159 WARN Delay shutter open. LSR 160 PAUSE.L Waiting time over to beam on LSR 161 PAUSE.L Illegal paket name. LSR 162 PAUSE.L Laser door open. LSR 163 PAUSE.L In a few seconds, SIMMER ON again LSR 164 WARN Already under power calibration LSR 165 WARN In Running Calibration can't be LSR 166 WARN Reset the alarm status LSR 167 WARN Turn off the Teach pendant key LSR 168 WARN SFSPD signal is off LSR 169 WARN Lock the hardware shutter lock LSR 170 WARN Calibration needs LSTR condition LSR 171 WARN $LASERSETUP$PWR_CALIB is NOT 1 LSR 172 PAUSE.L Calibration is halted manually LSR 173 PAUSE.L I/O signal halt the Calibration LSR 174 PAUSE.L Calib-conditions got unsatisfied LSR 175 PAUSE.L Program is useless in calibration. LSR 176 PAUSE.L Shutter is out of order. LSR 177 PAUSE.L Shutter state is abnormal. LSR 178 PAUSE.L Shutter open with FENCE open MACR 1 WARN Can't assign to MACRO command MACR 3 WARN Can't assign motn_prog to UK MACR 4 WARN Can't execute motn_prog by UK MACR 5 WARN Please enable teach pendant MACR 6 WARN Please disable teach pendant MACR 7 WARN The same macro type exists MACR 8 WARN Remote-cond isn't satisfied MACR 9 WARN The index is out of range MACR 10 WARN This SOP button is disabled MACR 11 WARN This UOP button is disabled MACR 12 WARN Number of DI+RI is over MACR 13 WARN MACRO execution failed MACR 16 WARN The macro is not completed MCTL 1 WARN TP is enabled MCTL 2 WARN TP is disabled MCTL 3 WARN system is in error status MCTL 4 WARN motion is in progress MCTL 5 WARN not in control of motion MCTL 6 WARN TP has motion control MCTL 7 WARN PROG has motion control MCTL 8 WARN Operator panel has motion control MCTL 9 WARN Other has motion control MCTL 10 WARN Other than msrc is rel'ing MCTL 11 WARN Due to error processing MCTL 12 WARN subsystem code unknown MCTL 13 WARN ENBL input is off MCTL 14 WARN Waiting for Servo ready MCTL 15 WARN Manual brake enabled MEMO 2 WARN Specified program is in use MEMO 3 WARN Specified program is in use MEMO 4 WARN Specified program is in use MEMO 6 WARN Protection error occurred MEMO 7 WARN Invalid break number MEMO 8 WARN Specified line no. not exist MEMO 10 WARN Program name error MEMO 13 WARN Program type is different MEMO 14 WARN Specified label already exists MEMO 15 WARN Program already exists MEMO 19 WARN Too many programs MEMO 25 WARN Label does not exist MEMO 26 WARN Line data is full MEMO 27 WARN Specified line does not exist MEMO 29 WARN The line data can't be changed MEMO 32 WARN Specified program is in use MEMO 34 WARN The item can't be changed MEMO 38 WARN Too many programs MEMO 48 WARN Break point data doesn't exist MEMO 50 WARN Program does not exist MEMO 56 WARN Program does not exist MEMO 61 WARN No write access MEMO 65 WARN Too many opened programs MEMO 68 WARN Specified program is in use MEMO 71 WARN Position does not exist MEMO 72 WARN Position data already exists MEMO 73 WARN Program does not exist MEMO 74 WARN Program type is not TPE MEMO 75 WARN Program can't be used MEMO 78 WARN Program can't be used MEMO 80 WARN Protection error occurred MEMO 81 WARN Specified program is in use MEMO 88 WARN Program does not exist MEMO 93 WARN Specified program is in use MEMO 98 WARN EOF occurs in file access MEMO 99 WARN Program name is wrong MEMO 103 WARN Check sum error occurred MEMO 104 WARN Program already exists MEMO 112 WARN Break data already exists MEMO 113 WARN File access error MEMO 114 WARN Break point can't be removed MEMO 115 WARN Break point can't be removed MEMO 119 WARN Application data doesn't exist MEMO 120 WARN Application data doesn't exist MEMO 123 WARN Application data doesn't exist MEMO 124 WARN Program version is too new MEMO 125 WARN Program version is too old MEMO 126 WARN No more available memory MEMO 127 WARN Pos reference over 255 times MEMO 128 WARN %s parameters are different MEMO 130 SYSTEM Please power up again MEMO 131 SYSTEM Please power up again MEMO 132 WARN %s has been broken MEMO 133 SYSTEM Please power up again MEMO 134 WARN TPE program %s already exists MEMO 135 WARN Cannot create TPE program here MEMO 136 WARN Cannot load P-code here MEMO 137 WARN Load at Control Start Only MEMO 138 WARN Delete at Control Start Only MEMO 144 WARN Header size too big MEMO 145 WARN TPE cannot have KAREL routine MEMO 146 WARN Invalid variable is used MEMO 147 WARN Flash File access error(write) MEMO 148 WARN Flash File access error(read) MEMO 149 WARN Specified program is broken MEMO 151 WARN No more available memory(TEMP) MEMO 152 WARN Program %s is in use MEMO 153 WARN %s is not deleted MEMO 154 WARN Parent program still exists MEMO 155 WARN Too many positions MEMO 156 WARN Renumber program failed MEMO 157 WARN Cannot execute this program MOTN 0 WARN Unknown error (MO00) MOTN 1 PAUSE.G Internal error in osmkpkt MOTN 2 PAUSE.G Internal error in ossndpkt MOTN 3 PAUSE.G Internal error in oswrtmbx MOTN 4 PAUSE.G Internal error in ossigflg MOTN 5 PAUSE.G Internal error in osclrflg MOTN 6 PAUSE.G Internal error in osrcvpkt MOTN 7 PAUSE.G Internal error in osredmbx MOTN 8 PAUSE.G Internal error in oswaiflg MOTN 9 PAUSE.G Normal Single Step / BWD stop MOTN 10 PAUSE.G Internal error in osathpkt MOTN 11 PAUSE.G Internal error in osdltpkt MOTN 12 PAUSE.G Invalid softpart MIR MOTN 13 PAUSE.G Invalid softpart SEG MOTN 14 WARN unknown error (MO14) MOTN 15 WARN unknown error (MO15) MOTN 16 WARN unknown error (MO16) MOTN 17 PAUSE.G Limit error (G:%d^2, A:%x^3 Hex) MOTN 18 PAUSE.G Position not reachable MOTN 19 WARN In singularity MOTN 20 WARN Wristjoint warning MOTN 21 PAUSE.G No kinematics error MOTN 22 PAUSE.G Invalid limit number MOTN 23 PAUSE.G In singularity MOTN 24 PAUSE.G Kinematics not defined MOTN 25 WARN unknown error (MO25) MOTN 26 WARN unknown error (MO26) MOTN 27 WARN unknown error (MO27) MOTN 28 WARN unknown error (MO28) MOTN 29 PAUSE.G unknown error (MO29) MOTN 30 PAUSE.G Internal error in MMGR:PEND MOTN 31 PAUSE.G Internal error in MMGR:ESEG MOTN 32 PAUSE.G Internal error in MMGR:PRSD MOTN 33 PAUSE.G Internal error in MMGR:GNL MOTN 34 PAUSE.G Internal error in MMGR_MMR MOTN 35 PAUSE.G Internal error in MMGR_MIR MOTN 36 PAUSE.G Internal error in MMGR:MSTR MOTN 37 PAUSE.G Internal error in MMGR:MDON MOTN 38 PAUSE.G Internal error in MMGR:CAN MOTN 39 PAUSE.G Internal error in MMGR:FCAN MOTN 40 PAUSE.G Internal error in MMGR:CAND MOTN 41 PAUSE.G Internal error in MMGR:PSTR MOTN 42 PAUSE.G Internal in MSSR MOTN 43 PAUSE.G Internal error in MMGR:EPKT MOTN 44 PAUSE.G Internal error in MMGR:ERR MOTN 45 WARN Internal error in pro. start MOTN 46 PAUSE.G Internal error in MMGR:LSTP MOTN 47 PAUSE.G Internal error in MMGR:PRST MOTN 48 PAUSE.G unknown error (MO48) MOTN 49 PAUSE.G Attempt to move w/o calibrated MOTN 50 PAUSE.G Invlaid spdlim (G:%d^2 A:%x^3 H) MOTN 51 PAUSE.G Speed out of range (G:%d^2) MOTN 52 PAUSE.G Jntvellim out of range (G:%d^2) MOTN 53 PAUSE.G Internal planner error (G:%d^2) MOTN 54 PAUSE.G Uninitialized dest pos (G:%d^2) MOTN 55 PAUSE.G Uninitialized via pos (G:%d^2) MOTN 56 WARN Speed limits used (G:%d^2) MOTN 57 PAUSE.G Invalid mir (G:%d^2) MOTN 58 PAUSE.G Invalid cancel request (G:%d^2) MOTN 59 PAUSE.G Null segment received (G:%d^2) MOTN 60 PAUSE.G Uninitialized base vec (G:%d^2) MOTN 61 PAUSE.G Uninitialized distance (G:%d^2) MOTN 62 PAUSE.G Invalid position type (G:%d^2) MOTN 63 PAUSE.G Position config change (G:%d^2) MOTN 64 PAUSE.G Rs orientation error (G:%d^2) MOTN 65 PAUSE.G AES orientation error (G:%d^2) MOTN 66 PAUSE.G Degenerate circle (G:%d^2) MOTN 67 PAUSE.G Ata2 error in circle (G:%d^2) MOTN 68 PAUSE.G Invalid Prgoverride (G:%d^2) MOTN 69 PAUSE.G Error in mocmnd (G:%d^2) MOTN 70 PAUSE.G Error in motype (G:%d^2) MOTN 71 PAUSE.G Error in termtype (G:%d^2) MOTN 72 PAUSE.G Error in segtermtype (G:%d^2) MOTN 73 PAUSE.G Error in orientype (G:%d^2) MOTN 74 PAUSE.G Error in speed (G:%d^2) MOTN 75 PAUSE.G Error in rotspeed (G:%d^2) MOTN 76 PAUSE.G Error in contaxisvel (G:%d^2) MOTN 77 PAUSE.G Error in seg_time (G:%d^2) MOTN 78 PAUSE.G Error in accel_ovrd (G:%d^2) MOTN 79 PAUSE.G Error in accu_num (G:%d^2) MOTN 80 PAUSE.G Via position required (G:%d^2) MOTN 81 PAUSE.G Extended position error (G:%d^2) MOTN 82 PAUSE.G Null mir pointer (G:%d^2) MOTN 83 PAUSE.G Illegal SEG recvd (G:%d^2) MOTN 84 PAUSE.G Illegal CONSEG recvd (G:%d^2) MOTN 85 PAUSE.G Error in gp_concurrent(G:%d^2) MOTN 86 PAUSE.G Not all CON_SEGs recvd(G:%d^2) MOTN 87 PAUSE.G Utool change not allowed(G:%d^2) MOTN 88 PAUSE.G Not cartesian move (G:%d^2) MOTN 89 PAUSE.G Segment not planned (G:%d^2) MOTN 90 PAUSE.G MIR mismatch (G:%d^2) MOTN 91 PAUSE.G Va orientation error (G:%d^2) MOTN 92 PAUSE.G Extended not supported (G:%d^2) MOTN 93 PAUSE.G Internal PLAN blend err(G:%d^2) MOTN 94 PAUSE.G Blend corner too big (G:%d^2) MOTN 95 WARN Can't blend corner line:%d^5 MOTN 96 PAUSE.G Cart rate not equal(G:%d^2) MOTN 97 WARN INTR overrun %d^3 (G:%d^2) MOTN 98 PAUSE.G Circle angle too large MOTN 99 PAUSE.G INTR Fail to get MIRPKT (G:%d^2) MOTN 100 PAUSE.G INTR Fail to get FDO (G:%d^2) MOTN 101 PAUSE.G MIR list is empty (G:%d^2) MOTN 102 PAUSE.G SEG list is empty (G:%d^2) MOTN 103 PAUSE.G Send ENB pkt fail (G:%d^2) MOTN 104 PAUSE.G Send DSB pkt fail (G:%d^2) MOTN 105 PAUSE.G Send TRG pkt fail (G:%d^2) MOTN 106 PAUSE.G Process motion done (G:%d^2) MOTN 107 PAUSE.G Bad filter type (G:%d^2) MOTN 108 PAUSE.G INTR seglist error (G:%d^2) MOTN 109 PAUSE.G Internal INTR error (G:%d^2) MOTN 110 PAUSE.G Use FINE in last L (G:%d^2) MOTN 111 WARN Can't switch filter(G:%d^2) MOTN 112 ABORT.G Increment move turn Mismatch MOTN 113 WARN Robot not calibrated MOTN 114 WARN Servo is on (G:%d^2) MOTN 115 WARN Invalid brake mask (G:%d^2) MOTN 116 WARN Invalid solution (G:%d^2) MOTN 117 WARN Robot not mastered (G:%d^2) MOTN 118 WARN Robot in over travel (G:%d^2) MOTN 119 WARN Servo is off (G:%d^2) MOTN 120 WARN Invalid reference position (G:%d^2) MOTN 121 WARN Invalid config. string (G:%d^2) MOTN 122 PAUSE.G Dfilter not empty (G:%d^2) MOTN 123 WARN Not enough node (G:%d^2) MOTN 124 PAUSE.G INTR:Bad Mirpkt req_code(G:%d^2) MOTN 125 PAUSE.G INTR got illegal pkt (G:%d^2) MOTN 126 PAUSE.G Can't init CH KPT (G:%d^2) MOTN 127 PAUSE.G Can't detatch CH PKT (G:%d^2) MOTN 128 PAUSE.G Group mtn not supported(G:%d^2) MOTN 129 PAUSE.G Local cond ptr conflict(G:%d^2) MOTN 130 PAUSE.G Non-empty local cond list(G:%d^2) MOTN 131 PAUSE.G In singularity MOTN 132 PAUSE.G Group circ not supported(G:%d^2) MOTN 133 WARN Time after limit used(G:%d^2) MOTN 134 PAUSE.G Can not move path backward (G:%d^2) MOTN 135 PAUSE.G Last motype can't be circular (G:%d^2) MOTN 136 PAUSE.G Circular Points too close(L:%d^5) MOTN 137 PAUSE.G No circular softpart (G:%d^2) MOTN 138 PAUSE.G No joint short motion SP (G:%d^2) MOTN 139 PAUSE.G No cart short motion SP (G:%d^2) MOTN 140 PAUSE.G No KAREL motion softpart (G:%d^2) MOTN 141 PAUSE.G No KAREL motion func. ptr (G:%d^2) MOTN 142 PAUSE.G No Group Motion SP (G:%d^2) MOTN 143 PAUSE.G No Motion Resume SP (G:%d^2) MOTN 144 PAUSE.G No joint Turbo Move SP (G:%d^2) MOTN 145 PAUSE.G No cart Turbo Move SP (G:%d^2) MOTN 146 PAUSE.G INTR can't replan major axis(G:%d^2) MOTN 147 WARN L->J replan joint slowdown (G:%d^2) MOTN 148 WARN Can't move concurrently (G:%d^2) MOTN 149 PAUSE.G CF:rotspeedlim exceeded line:%d^5 MOTN 150 SERVO PM: XYZ data error (L:%d) MOTN 151 SERVO PM: WPR data error (L:%d) MOTN 152 SERVO PM: Can't current record data MOTN 153 SERVO PM: Joint move fast (L:%d) MOTN 154 SERVO PM: I/O data error (L:%d) MOTN 155 SERVO PM: No interpolation data MOTN 156 SERVO PM: Config changed(L:%d) MOTN 157 PAUSE.G PM: Internal error(%d) MOTN 158 PAUSE.G PM: Original path invalid MOTN 159 SERVO PM: Joint data error (L:%d) MOTN 161 WARN (%s^4 L:%d^5) Can't look ahead MOTN 170 WARN Load is close to capacity MOTN 171 WARN Overload MOTN 172 PAUSE.G Another robot is re-linked MOTN 173 PAUSE.G Robot link configuration error MOTN 174 PAUSE.G No motion control MOTN 175 PAUSE.G Failed to be MASTER MOTN 176 PAUSE.G Failed to be SLAVE MOTN 177 PAUSE.G Failed to end sync motion MOTN 178 PAUSE.G Link robot is HELD MOTN 179 PAUSE.G Robot link internal error MOTN 180 PAUSE.G Robot link Calib-data not found MOTN 181 ABORT.G Robot link Version mismatch MOTN 182 PAUSE.G Failed to get data from master MOTN 183 PAUSE.G Invalid MNUTOOLNUM data array MOTN 184 PAUSE.G Invalid MNUTOOL data array MOTN 185 WARN Protect of ACK BF to be sent MOTN 186 WARN Protect of BCST BF to be sent MOTN 187 WARN Protect of ACK BF to be read MOTN 188 WARN Protect of BCST BF to be read MOTN 189 WARN Slave motion remained MOTN 190 PAUSE.G Slave cannot use JOINT pos MOTN 191 PAUSE.G Slave cannot JOINT motion MOTN 192 PAUSE.G UT of MASTER was changed MOTN 193 PAUSE.G UT of SLAVE was changed MOTN 194 PAUSE.G Machine Lock is ENABLED MOTN 195 ABORT.G RLINK internal error %d^5 MOTN 198 WARN CRC Start-Via too close(L:%d^5) MOTN 199 WARN CRC Via-Dest too close(L:%d^5) MOTN 200 WARN (%s^4, %d^5) Too long anticipate time MOTN 205 WARN (%s^4, %d^5) Singularity MOTN 206 WARN (%s^4, %d^5) Singular Node MOTN 207 WARN WARN: An Axis Changes 180 MOTN 208 WARN Config Not Reached (L:%d) MOTN 209 WARN Modify Singular Dest(L:%d) MOTN 210 PAUSE.G Failed to resume program MOTN 211 PAUSE.G Dual ARC not allowed at T1 MOTN 212 PAUSE.G Link is in held status (G:%d^2) MOTN 213 PAUSE.G Org path resume not available MOTN 214 PAUSE.G Resume condition mismatch MOTN 220 PAUSE.G Group motion resume mismatch MOTN 230 WARN T1 rotspeed limit (G:%d^2) MOTN 231 WARN T1 speed limit (G:%d^2) MOTN 240 PAUSE.G J4 is not zero MOTN 241 PAUSE.G OFIX stroke limit MOTN 242 PAUSE.G OFIX is disabled MOTN 243 PAUSE.G OFIX error MOTN 244 PAUSE.G OFIX Detect J4 is not 0 MOTN 245 PAUSE.G OFIX Wrist config mismatch MOTN 246 PAUSE.G OFIX Invalid rail vector MOTN 247 PAUSE.G E-Effector is not vertical to rail MOTN 248 PAUSE.G OFIX Too large tool rotation MOTN 249 PAUSE.G OFIX Too large tool spin MOTN 250 PAUSE.G Use CNT0/FINE for L/C before OFIX MOTN 251 PAUSE.G Can't use OFIX with this motion MOTN 252 PAUSE.G OFIX: No plan data MOTN 253 PAUSE.G OFIX: Motion type mismatch MOTN 254 PAUSE.G OFIX: Detect large spin MOTN 255 PAUSE.G OFIX: Detect J4 is not 0 MOTN 256 PAUSE.G OFIX: TCP config limit MOTN 257 PAUSE.G Wrist start angle mismatch MOTN 258 PAUSE.G Not reached to dest rotation MOTN 259 PAUSE.G Not reached to dest spin MOTN 265 PAUSE.G MPDT not finished(G:%d^2 A:%d^3) MOTN 270 PAUSE.G TB parameter error 1(G:%d^2) MOTN 271 PAUSE.G TB parameter error 2(G:%d^2) MOTN 272 PAUSE.G TB parameter error 3(G:%d^2) MOTN 273 PAUSE.G TB parameter error 4(G:%d^2) MOTN 300 PAUSE.G CD not support:Use CNT L:%d^5 MOTN 301 PAUSE.G Path to resume is changed(G:%d^2) MOTN 302 WARN Corner speed slowdown L:%d^5 MOTN 303 WARN Can't maintain CDist L:%d^5 MOTN 304 WARN CS:Prog speed achieved L:%d^5 MOTN 305 WARN Can't maintain speed L:%d^5 MOTN 306 PAUSE.G Can't replan (G:%d^2, A:%x^3 Hex) MOTN 307 PAUSE.G Mismatch MMR (G:%d^2) MOTN 308 WARN FINE termtype used L:%d^5 MOTN 309 WARN Circular speed reduced L:%d^5 MOTN 310 PAUSE.G Pos. Cfg. change 2 (G:%d^2) MOTN 311 PAUSE.G Path to resume is changed(G:%d^2) MOTN 312 PAUSE.G Can't resume in single step CJ MOTN 313 PAUSE.G Can't resume motion CJ(2) MOTN 314 ABORT.G Can't resume motion CJ(3) MOTN 315 PAUSE.G Command speed is changed CJ MOTN 316 PAUSE.G Override change not allowed MOTN 317 PAUSE.G CJLP: Error Recovery is ENABLED MOTN 318 PAUSE.G unknown error (MO318) MOTN 319 PAUSE.G CRC large orient change (G:%d^2) MOTN 320 WARN Adj out of limit at line %s MOTN 321 WARN Posn unreachable at line %s MOTN 330 WARN MROT Limit Warn(G:%d^2, A:%x^3 Hex) MOTN 340 PAUSE.G Fast fault recovery MOTN 341 WARN NO Z offset for INC motion MOTN 342 PAUSE.G Override change not allowed MOTN 343 PAUSE.G Constant Path Low Override MOTN 345 PAUSE.G PS is not available MOTN 400 PAUSE.G No Coll. Guard Reg. Defined MOTN 401 PAUSE.G Coll. Guard Reg. Data Error MUPS 2 PAUSE.G Isolated offset destination MUPS 3 PAUSE.G Invalid motype with offset MUPS 4 PAUSE.G Segment too short using OFFSET MUPS 6 PAUSE.G BWD not allowed in M-PASS MUPS 7 PAUSE.G Illegal transition:nonCD<->CD MUPS 8 ABORT.G Invalid pass number MUPS 9 PAUSE.G Invalid Direction MUPS 10 PAUSE.G Invalid parameters MUPS 11 WARN Pass number is out of sequence MUPS 12 WARN Last pass was incomplete OPTN 0 WARN Unknown error (OPTN) OPTN 1 WARN Too many options installed OPTN 2 WARN Installed: `%s' OPTN 3 WARN Skipped: `%s' OPTN 6 WARN Not Installed: `%s' OPTN 7 WARN Unauthorized: `%s' OPTN 8 WARN Requires: `%s' OPTN 9 WARN Authorized: `%s' OPTN 10 WARN Force COLD start OPTN 11 SYSTEM Cycle Power OPTN 12 WARN ID file is missing/corrupt OPTN 13 WARN Invalid PAC OPTN 14 WARN Dependency nesting too deep OPTN 15 WARN Excludes: `%s' OPTN 16 WARN Key file is missing/corrupt OPTN 17 WARN No UPDATES on this media OPTN 18 WARN No CUSTOMIZATIONS on this media OPTN 19 WARN Versions mistmatched OS 0 WARN R E S E T OS 2 WARN System error - invalid function performed OS 144 SYSTEM System error %x, %x at %x OS 145 WARN Power off controller to reset OS 147 WARN Assert %d %d %s OS 148 WARN Assert %d %d %s PALT 0 WARN UNUSED ERROR CODE(PLER00) PALT 1 ABORT.G Inadequate register value PALT 4 ABORT.G Increment value is ill PALT 10 ABORT.G Route pattern unfound PALT 24 ABORT.G Calculation error occured PALT 26 ABORT.G Cannot read/write to PL[] PALT 30 WARN Pallet number is over max PALT 31 WARN Can not be set FREE or INTER PALT 33 WARN This speed type isn't supported PMON 1 WARN Failed to notify PC Monitor PMON 2 WARN Memory allocation failure PMON 3 WARN Connect to PMON server failed PMON 4 WARN PMON initialization failure PMON 5 WARN PMON timer failure PMON 6 WARN PMON task status read failed PMON 7 WARN Lost connection to %s PMON 8 WARN PMON curpos read failed PMON 9 WARN PMON monitor not found PRIO 1 WARN Illegal port type code PRIO 2 WARN Illegal port number PRIO 3 SYSTEM No memory available PRIO 4 WARN Too few ports on module PRIO 5 WARN bad port number PRIO 6 WARN bad port number PRIO 7 WARN No match in SET_PORT_ASG de-assign PRIO 8 WARN physical ports not found PRIO 9 WARN number of ports invalid PRIO 10 WARN bad physical port number PRIO 11 WARN Assignment overlaps existing one PRIO 12 WARN Bad board address PRIO 13 WARN No analog input sequence for bd PRIO 14 WARN Analog input sequnce too long PRIO 17 WARN I/O point not simulated PRIO 20 PAUSE.G I/O Link comm error %x, %x, %x, %x (hex) PRIO 21 SYSTEM Unknown I/O hardware PRIO 22 SYSTEM Too much I/O data on I/O link PRIO 23 WARN No ports of this type PRIO 33 WARN PLC interface init. fault %d PRIO 34 WARN PLC interface general fault %d PRIO 35 WARN PLC interface serial fault %d PRIO 37 SYSTEM Not supported for spec. port type PRIO 63 WARN Bad I/O asg: rack %d slot %d PRIO 70 WARN PLC interface option not loaded PRIO 72 WARN Too many pulses active PRIO 76 WARN PLC I/O hardware not installed PRIO 81 PAUSE.G I/O is not initialized PRIO 83 PAUSE.G Digital I/O is not recovered PRIO 89 PAUSE.G PMC is not supported on this hardware PRIO 90 WARN SNPX communication error PRIO 100 PAUSE.G Model B comm fault %srack:%d slot:%d PRIO 102 WARN Cycle power to restart PLC I/O PRIO 104 PAUSE.G Device is off-line PRIO 106 PAUSE.G Device with port is off-line PRIO 119 WARN Too many DIGITAL I/O ports PRIO 121 WARN Stop PMC program PRIO 125 SYSTEM SLC2 initialization error PRIO 126 WARN No PMC program PRIO 127 WARN PMC file load error PRIO 128 PAUSE.G T,C,K and D data may be lost PRIO 129 WARN SUB%d is not supported PRIO 130 WARN PMC option is not installed PRIO 131 WARN PMC file name error PRIO 132 WARN PMC operation is locked PRIO 133 WARN PMC program size is too big PRIO 134 WARN Invalid PMC addr %s%d.%d PRIO 135 WARN PMC address is not assigned PRIO 136 WARN BYTE access to %s%d.%d PRIO 137 WARN BIT access to %s%d.%d PRIO 138 WARN %s%d is used in SUB%d PRIO 139 WARN Invalid CNC addr %x.%x(hex) PRIO 140 WARN Can't display all PMC errors PRIO 141 WARN Invalid PMC program PRIO 142 WARN Need E-STOP or CTRL start PRIO 143 PAUSE.G Writting PMC program to ROM PRIO 144 PAUSE.G Faild to run PMC program PRIO 145 PAUSE.G Purging flash file, please wait PRIO 146 WARN Flash file purge is completed PRIO 147 SYSTEM DIO config file too new PRIO 148 SYSTEM DIO config file too old PRIO 149 WARN Invalid assignment recorded PRIO 150 PAUSE.G CNET Card Init Error Bd %d PRIO 151 WARN CNET Internal Error 0x%x PRIO 152 WARN CNET Invalid Scan Config Bd %d PRIO 153 WARN CNET Conn. Ownership Conflict PRIO 154 PAUSE.G CNET Duplicate Mac ID Bd %d PRIO 155 PAUSE.G CNET Network Error Bd %d PRIO 156 PAUSE.G CNET Er %s Bd %d MAC %d PRIO 157 PAUSE.G CNET Err Loading BIN file Bd %d PRIO 158 WARN CNET File Not Found PRIO 159 WARN CNET Cycle pwr to restart scan PRIO 160 PAUSE.G CNET Connections Broken Bd %d PRIO 161 WARN CNET Network Change Occuring PRIO 162 WARN CNET Connections Restored Bd %d PRIO 163 WARN CNET Network Change Complete PRIO 164 PAUSE.G CNET Scan list modified Bd %d PRIO 165 WARN CNET Connection Not Found PRIO 166 WARN CNET Invalid Connection Type PRIO 167 WARN CNET Vend ID/Prod. Code Mismatch PRIO 168 WARN CNET Invalid Connection Size PRIO 169 WARN CNET Device Not Configured PRIO 170 WARN CNET Product Type Mismatch PRIO 171 WARN CNET Maj/Min Revision Mismatch PRIO 172 WARN CNET Target App Out of Conn. PRIO 173 WARN CNET Needs Network Config. PRIO 174 WARN CNET Connection Lost PRIO 175 WARN CNET Bad Device State PRIO 176 WARN CNET Connection Request Failed PRIO 177 WARN CNET Invalid configuration PRIO 178 WARN Blk scns lost; %d %d %d PRIO 179 WARN Run scns lost; %d %d %d PRIO 180 WARN CNET Sys Err %d %d 0x%x PRIO 181 WARN CNET Conn. Req. Timeout PRIO 182 WARN CNET CCO Change Aborted PRIO 183 WARN Unknown port type name PRIO 184 WARN CNET Connection Idle PRIO 185 WARN CNET Config Er %d %d PRIO 186 WARN CNET Invalid Header size PRIO 187 WARN CNET Invalid Num of Slots PRIO 200 PAUSE.G FIPIO System Error %d PRIO 201 WARN FIPIO PCB not installed PRIO 202 PAUSE.G FIPIO PCB Abnormal PRIO 203 PAUSE.G FIPIO Duplicate FIP Address PRIO 204 PAUSE.G FIPIO Send Buffer Error PRIO 205 PAUSE.G FIPIO Receive Buffer Error PRIO 206 PAUSE.G FIPIO Physical Reset PRIO 207 PAUSE.G FIPIO BadPrm; CMD %x,%x PRIO 208 PAUSE.G FIPIO NRDY; CMD %d LNG %d PRIO 209 PAUSE.G FIPIO Connection Broken PRIO 210 PAUSE.G FIPIO Cnf/Adj not available PRIO 211 PAUSE.G FIPIO Bad Cnf/Adj status PRIO 212 PAUSE.G FIPIO Connection TimeOut PRIO 213 WARN FIPIO Connection Established PRIO 214 WARN FIPIO Connection Recovered PRIO 215 WARN FIPIO Configuration accepted PRIO 216 WARN FIPIO Adjustment accepted PRIO 217 WARN FIPIO Configuration refused PRIO 218 WARN FIPIO Adjustment refused PRIO 219 WARN FIPIO SetControl received PRIO 220 WARN EGD Producer name/IP not init PRIO 221 WARN EGD Producer host not found PRIO 222 WARN EGD Consumer init failed PRIO 223 WARN EGD Producer socket error PRIO 224 WARN EGD System Error PRIO 225 WARN EGD Consumer timeout - Id:%d PRIO 226 WARN EGD Consumer socket create error PRIO 227 WARN EGD Consumer socket bind error PRIO 228 WARN EGD System error - Code:%x PRIO 229 WARN EGD Producer Id:%d - Host error PRIO 240 PAUSE.G IO LinkII(S) System error(%d) PRIO 241 WARN IO LinkII(S) PCB not installed PRIO 242 PAUSE.G IO LinkII(S) PCB abnormal(%d) PRIO 243 PAUSE.G IO LinkII(S) Parameter error PRIO 244 PAUSE.G IO LinkII(S) Link Down(%d) PRIO 245 WARN IO LinkII(S) Detect Abort PRIO 246 WARN IO LinkII(S) Detect CRC Error PRIO 247 WARN IO LinkII(S) Incorrect BitData PRIO 248 WARN IO LinkII(S) RX Buf overflow PRIO 249 WARN IO LinkII(S) Overrun Error PRIO 260 PAUSE.G IO LinkII(M) System error(%d) PRIO 261 WARN IO LinkII(M) PCB not installed PRIO 262 PAUSE.G IO LinkII(M) PCB abnormal(%d) PRIO 263 PAUSE.G IO LinkII(M) Parameter error PRIO 264 PAUSE.G IO LinkII(M) Link Down(%d) PRIO 265 WARN IO LinkII(M) Detect Abort PRIO 266 WARN IO LinkII(M) Detect CRC Error PRIO 267 WARN IO LinkII(M) Incorrect BitData PRIO 268 WARN IO LinkII(M) RX Buf overflow PRIO 280 PAUSE.G FL-net System Error(%d) PRIO 281 WARN FL-net PCB not installed PRIO 282 PAUSE.G FL-net PCB Abnormal(%d) PRIO 283 PAUSE.G FL-net IP Address Incorrect PRIO 284 PAUSE.G FL-net Token Interval Error PRIO 285 PAUSE.G FL-net Init Error PRIO 286 WARN FL-net Wait Frame Status PRIO 287 PAUSE.G FL-net My Node Dupulicate No. PRIO 288 PAUSE.G FL-net My Node Leave network PRIO 289 WARN FL-net My Node Enter network PRIO 290 PAUSE.G FL-net My Node Dupulicate Adr PRIO 291 PAUSE.G FL-net Node %d Leave network PRIO 292 WARN FL-net Node %d Enter network PRIO 293 PAUSE.G FL-net Dupulicate Area Adr %d PRIO 320 PAUSE.G CC-LK System error(ID=%d) PRIO 321 WARN CC-LK Board not installed PRIO 322 PAUSE.G CC-LK St.No out of range(%d) PRIO 323 WARN CC-LK CRC error(%d) PRIO 324 PAUSE.G CC-LK Data link error(%d) PRIO 325 PAUSE.G CC-LK Seq. CPU stopped(%d) PRIO 326 PAUSE.G CC-LK Seq. CPU abnormal(%d) PRIO 327 PAUSE.G CC-LK Reg index error(%d) PRIO 328 PAUSE.G CC-LK AO/R too many(%d) PRIO 329 PAUSE.G CC-LK AI/R too many(%d) PRIO 330 PAUSE.G CC-LK PNTtoUOP not enough(%d) PRIO 331 WARN CC-LK Reg data invalid(%d) PROF 0 PAUSE.G System error(%d) PROF 1 WARN PROFIBUS PCB not installed PROF 2 PAUSE.G PROFIBUS PCB abnormal(%d) PROF 3 PAUSE.G Slave Config data error PROF 4 PAUSE.G Slave Param data error PROF 5 PAUSE.G Master Slave Param error(%d) PROF 6 PAUSE.G Another Master Lock(%d) PROF 7 PAUSE.G Parameter Fault(%d) PROF 8 PAUSE.G Invalid Slave Responce(%d) PROF 9 PAUSE.G Slave not supported(%d) PROF 10 PAUSE.G Config Fault(%d) PROF 11 PAUSE.G Slave not ready(%d) PROF 12 PAUSE.G Slave not existent(%d) PROF 13 PAUSE.G CMI error(code = %d) PROF 14 PAUSE.G DP error(code = %d) PROF 15 PAUSE.G DP sub error(code = %d) PROF 16 PAUSE.G Slave communicatin stop PROF 17 PAUSE.G Slave disconnected PROF 18 PAUSE.G Exist specific diag(%d) PROG 1 ABORT.L Invalid pointer is specified PROG 2 ABORT.L Invalid task name is specified PROG 3 ABORT.L Invalid prog name is specified PROG 5 WARN Program is not found PROG 6 WARN Line is not found PROG 7 WARN Program is already running PROG 8 WARN In a rtn when creating a task PROG 9 WARN Line not same rtn as paused at PROG 10 WARN Not same prg as paused PROG 11 PAUSE.L Cannot get the motion control PROG 12 WARN All groups not on the top PROG 13 WARN Motion is stopped by program PROG 14 WARN Max task number exceed PROG 15 WARN Cannot execute backwards PROG 16 WARN Task is not found PROG 17 WARN Task is not running PROG 18 ABORT.G Motion stack overflowed PROG 19 WARN Ignore pause request PROG 20 WARN Task is already aborted PROG 21 WARN Ignore abort request PROG 23 WARN Task is not paused PROG 24 WARN Not have motion history PROG 25 WARN Cannot execute backwards PROG 26 WARN No more motion history PROG 27 WARN Invalid task number PROG 29 WARN Buffer size is not enough PROG 30 WARN Attribute is not found PROG 31 WARN Attribute is write protected PROG 32 WARN Invalid value for attribute PROG 34 WARN Routine not found PROG 35 WARN Not locked the specified group PROG 36 WARN The length of trace array is 0 PROG 37 WARN No data in the trace array PROG 39 WARN locked, but not get mctl PROG 40 PAUSE.L Already locked by other task PROG 41 WARN mctl denied because released PROG 42 WARN Already released PROG 43 WARN Already released by you PROG 44 WARN Arm has not been released yet PROG 45 WARN Other than requestor released PROG 46 PAUSE.L TP is enabled while running (%s^7) PROG 47 PAUSE.L TP is disabled while running (%s^7) PROG 48 PAUSE.L Shift released while running (%s^7) PROG 49 WARN Cannot release, robot moving PROG 50 WARN Abort still in progress PROG 51 WARN Cannot skip the return stmt PROG 52 ABORT.L Process is aborted while executing PROG 53 ABORT.L User AX is not running PROG 54 PAUSE.L FWD released while running (%s^7) PROG 55 PAUSE.L BWD released while running (%s^7) PROG 56 ABORT.L Motion data out is enable PROG 57 SYSTEM Power Fail Rervoer memory is cleared PWD 1 WARN Login (%s) Install PWD 2 WARN Logout (%s) Install PWD 3 WARN Login (%s) Setup PWD 4 WARN Logout (%s) Setup PWD 5 WARN Login (%s) Program PWD 6 WARN Logout (%s) Program PWD 7 WARN Password Timeout (%s) PWD 8 WARN Create program %s.TP PWD 9 WARN Delete program %s.TP PWD 10 WARN Rename %s.TP as %s.TP PWD 11 WARN Set %s.TP subtype from %s to %s PWD 12 WARN Set %s.TP comment PWD 13 WARN Set %s.TP group mask PWD 14 WARN Set %s.TP write protect on PWD 15 WARN Set %s.TP write protect off PWD 16 WARN Set %s.TP ignore pause on PWD 17 WARN Set %s.TP ignore pause off PWD 18 WARN Write line %d, %s.TP PWD 19 WARN Delete line %d, %s.TP PWD 20 WARN Write pos %d, %s.TP PWD 21 WARN Delete pos %d, %s.TP PWD 22 WARN Renumber pos %d as %d, %s.TP PWD 23 WARN Set application data %s.TP PWD 24 WARN Delete application data %s.TP PWD 25 WARN Load %s PWD 26 WARN Load %s as Program %s PWD 27 WARN Edit %s Sch %d %s PWD 28 WARN Copy %s Sch %d to %d PWD 29 WARN Clear %s Sch %d PWD 30 WARN (%s to %s)%s PWD 31 WARN QUICK MENUS forced PWD 32 WARN Login (%s) Install from SMON PWD 33 WARN Login (%s) Install from KCL PWD 34 WARN Login (%s) Install from Teach Pendant PWD 35 WARN Login (%s) Install from CRT/Keyboard PWD 36 WARN Logout (%s) Install from SMON PWD 37 WARN Logout (%s) Install from KCL PWD 38 WARN Logout (%s) Install from Teach Pendant PWD 39 WARN Logout (%s) Install from CRT/Keyboard PWD 40 WARN Login (%s) Setup from KCL PWD 41 WARN Login (%s) Setup from Teach Pendant PWD 42 WARN Login (%s) Setup from CRT/Keyboard PWD 43 WARN Logout (%s) Setup from KCL PWD 44 WARN Logout (%s) Setup from Teach Pendant PWD 45 WARN Logout (%s) Setup from CRT/Keyboard PWD 46 WARN Login (%s) Program from Teach Pendant PWD 47 WARN Login (%s) Program from CRT/Keyboard PWD 48 WARN Logout (%s) Program from Teach Pendant PWD 49 WARN Logout (%s) Program from CRT/Keyboard PWD 50 WARN Pwd Timeout (%s) from SMON PWD 51 WARN Pwd Timeout (%s) from KCL PWD 52 WARN Pwd Timeout (%s) from Teach Pendant PWD 53 WARN Pwd Timeout (%s) from CRT/Keyboard PWD 54 WARN Login (%s) Install from Internet PWD 55 WARN Logout (%s) Install from Internet PWD 56 WARN Login (%s) Setup from Internet PWD 57 WARN Logout (%s) Setup from Internet PWD 58 WARN Login (%s) Program from Internet PWD 59 WARN Logout (%s) Program from Internet PWD 60 WARN Pwd Timeout (%s) from Internet PWD 61 WARN FULL MENUS forced PWD 62 WARN Login from MC is cancelled PWD 63 WARN User (%s) already logged in PWD 64 WARN User (%s) time extended PWD 65 WARN Password card inserted PWD 66 WARN Bad password data QMGR 1 WARN Queue is full QMGR 2 WARN Queue is empty QMGR 3 WARN Bad sequence no QMGR 4 WARN Bad n_skip value ROUT 22 PAUSE.G Bad index in ORD ROUT 23 PAUSE.G Bad index in SUBSTR ROUT 24 PAUSE.G SUBSTR length less than 0 ROUT 25 ABORT.G Illegal semaphore number ROUT 26 WARN Illegal group number ROUT 27 WARN String size not big enough ROUT 28 ABORT.G Illegal file attribute number ROUT 29 ABORT.G Illegal file attribute value ROUT 30 WARN Non existent register number ROUT 31 WARN Illegal register type ROUT 32 ABORT.G Position type mismach ROUT 33 ABORT.G Illegal attribute type ROUT 34 WARN Not a TPE program ROUT 35 WARN Value is out of range ROUT 36 ABORT.G Illegal port id value ROUT 37 ABORT.G Bad TPE header size ROUT 38 PAUSE.G Uninitialized TPE position ROUT 39 WARN Executing motion exists ROUT 40 WARN Stopped motion exists ROUT 41 ABORT.G Dym. disp. var. not static ROUT 42 WARN TPE parameters do not exist ROUT 43 WARN TPE parameter %s wrong data type ROUT 44 WARN Tag name too long ROUT 45 WARN Dictionary name too long ROUT 46 WARN Option array not initialized ROUT 47 WARN Stream buffer full ROUT 48 WARN Stream not active ROUT 49 WARN Invalid motion options ROUT 50 WARN SET comment builtin string too long RPC 1 WARN Can't encode arguments RPC 2 WARN Can't decode result RPC 3 WARN Unable to send RPC 4 WARN Unable to receive RPC 5 WARN Call timed out RPC 6 WARN Incompatible versions of RPC RPC 7 WARN Authentication error RPC 8 WARN Program unavailable RPC 9 WARN Program/version mismatch RPC 10 WARN Procedure unavailable RPC 11 WARN Server can't decode arguments RPC 13 WARN Unknown host RPC 16 WARN Remote procedure call failed RPC 18 WARN Low = %d, High = %d RPC 19 WARN PC Interface option not loaded RPM 1 WARN n_buffers invalid RPM 2 WARN record_size invalid RPM 5 SYSTEM memory allocation failed RPM 9 PAUSE.G segment not in buffer RPM 13 PAUSE.G invalid buffer no RPM 14 PAUSE.G record not stored RPM 20 WARN read record not stored RPM 26 ABORT.G Pitch value too small. RPM 27 PAUSE.G Illegal arc instruction. RPM 28 PAUSE.G Segment too short RPM 39 PAUSE.G Incompatible RPM data:nonCD/CD SCIO 3 WARN Cannot teach any more. SCIO 16 WARN Prog uses un-installed option. SCIO 20 WARN LBL[%d] exists in line %d: SCIO 30 WARN JOINT motion in slave program SCIO 31 WARN JOINT position in slave program SCIO 32 WARN Master UT mismatch SCIO 33 WARN Slave can have ony one motion line SENS 0 SYSTEM Unknown error SENS 1 PAUSE.G Hardware error occured SENS 2 PAUSE.G DSR off when transmission SENS 3 PAUSE.G Undefined TCC received SENS 4 PAUSE.G Invalid software parity SENS 5 PAUSE.G Invalid data format SENS 6 PAUSE.G Response time over SENS 7 PAUSE.G Interval time over SENS 8 PAUSE.G Calculate matrix error SENS 9 SYSTEM SENS 10 SYSTEM SENS 11 SYSTEM SENS 12 SYSTEM SENS 13 SYSTEM SENS 14 SYSTEM SENS 15 SYSTEM SENS 16 SYSTEM SENS 17 SYSTEM SENS 18 SYSTEM SENS 19 SYSTEM SVGN 1 PAUSE.G Serious Internal error SVGN 2 PAUSE.G No sysvar pointer SVGN 3 PAUSE.G No global variables SVGN 4 PAUSE.G Unable to Allocate Memory SVGN 5 PAUSE.G Wrong TPP inst. format SVGN 6 PAUSE.G Another TASK used this equip. SVGN 7 PAUSE.G Pre execution failed SVGN 8 PAUSE.G Syntax error SVGN 9 PAUSE.G Motion Group config. mismatch SVGN 10 PAUSE.G Invalid SG group config. SVGN 11 PAUSE.G Can not execute instruction(s). SVGN 12 PAUSE.G Invalid value for index SVGN 13 PAUSE.G Pressure exceeds limit SVGN 14 PAUSE.G Associate TID not found SVGN 15 PAUSE.G Setup Configuration error SVGN 16 PAUSE.G Specified pressure too low SVGN 17 PAUSE.G Invalid pressure coefficient SVGN 18 PAUSE.G Illegal torque limit value SVGN 19 WARN Pressure shortage SVGN 20 PAUSE.G Pressure shortage SVGN 21 PAUSE.G Uninitialized BU condition SVGN 22 PAUSE.G Uninitialized Pres. condition SVGN 23 PAUSE.G Incomplete Pressure calibration SVGN 24 PAUSE.G Incomplete Wear Down calibration SVGN 25 PAUSE.G Illegal BU condition number SVGN 26 PAUSE.G Illegal P condition number SVGN 27 PAUSE.G Untaught element encountered SVGN 28 PAUSE.G Pos. type is JOINT SVGN 29 PAUSE.G Over max motor torque value SVGN 30 PAUSE.G Tip Stick detection SVGN 31 PAUSE.G Tear Off is executing SVGN 32 PAUSE.G Tip increased error(Gun) SVGN 33 PAUSE.G Tip increased error(Robot) SVGN 34 PAUSE.G Excessive robot tip difference. SVGN 35 PAUSE.G Pressure enable time out SVGN 36 PAUSE.G Comp confirmation time out SVGN 37 PAUSE.G Illegal pressure enable signal SVGN 38 PAUSE.G Illegal comp confirmation signal SVGN 39 WARN Thickness out of tolerance SVGN 40 PAUSE.G Thickness out of tolerance SVGN 41 WARN No more available memory(PERM) SVGN 42 WARN Lack of $SGGUN SVGN 43 WARN AutoTuning Started. SVGN 44 WARN AutoTune Successfully Complete SVGN 45 WARN AutoTuning Failed. SVGN 46 WARN FAULTS must be reset. SVGN 47 WARN Step mode must be disabled. SVGN 48 WARN Machine lock must be disabled. SVGN 49 WARN Hold must be cleared. SVGN 50 SYSTEM Autuning: Re-power required SVGN 51 WARN Backup stroke is not selected. SVGN 52 WARN Motion group mismatch. SVGN 53 WARN Backup stroke is not set. SVGN 54 PAUSE.G $EQNUM is invalid number. SVGN 55 PAUSE.G $EQNUM is not Servo Gun. SVGN 56 PAUSE.G $GUNNUN is invalid number. SVGN 57 PAUSE.G Tip Wear Down Cal. is INCOMP. SVGN 58 PAUSE.G UT or UF is different. SVGN 59 PAUSE.G Cannot read specified PR[]. SVGN 60 WARN Pressure program is not set. SVGN 61 WARN Backup program is not set. SVGN 62 WARN Pressure data is not selected. SVGN 63 WARN Pressure data is not set. SVGN 64 WARN Servo Gun Lockout Enabled SVGN 65 WARN Servo Gun Lockout Disabled SVGN 66 WARN Servo Gun Lockout Activated SVGN 67 WARN Servo Gun Lockout De-Activated SVGN 70 PAUSE.L Gun Change is DISABLED. SVGN 71 PAUSE.L Machine lock is ENABLE. SVGN 72 PAUSE.L Illegal assignment of gun axis. SVGN 73 PAUSE.L Gun not detatched (AXISORDER). SVGN 74 PAUSE.L Gun not detatched. SVGN 75 PAUSE.L Gun not attached. SVGN 76 PAUSE.L Another process is executing. SVGN 77 PAUSE.L Gun identify signal is OFF. SVGN 78 PAUSE.L Gun set signal is OFF. SVGN 79 PAUSE.L Gun change canceled. SVGN 80 PAUSE.L Gun change timeout. SVGN 81 SYSTEM Gun mastering data is lost. SVGN 82 PAUSE.L Gun mastering is failed. SVGN 83 PAUSE.L GUN ATTACH is failed. SVGN 84 PAUSE.L GUN DETACH is failed. SVGN 85 PAUSE.L Robot not mastered(Gun axis). SVGN 86 PAUSE.L Robot not calibrated(Gun axis). SVGN 87 PAUSE.L Ref pos not set(Gun axis). SVGN 88 PAUSE.L Another gun is attached. SVGN 89 PAUSE.L Calibrate motion is failed. SVGN 90 PAUSE.L PR[] index is not set. SVGN 91 PAUSE.L Touch torque is not set. SVGN 92 PAUSE.L Detect signal is not set. SVGN 93 PAUSE.L Gun does not stop. SVGN 94 PAUSE.L GUN EXCHANGE failed SVGN 95 PAUSE.L Gun type is not opposable. SVGN 96 PAUSE.L Gun close is disabled. SVGN 97 PAUSE.L Tip wear down misdetection. SVGN 98 PAUSE.L Invalid inform signal(Gun). SVGN 99 PAUSE.L Invalid inform signal(Robot). SVGN 100 PAUSE.L Invalid register number. SVGN 101 PAUSE.L Invalid position reg number. SVGN 102 WARN Increased err. not set(Gun). SVGN 103 WARN Increased err. not set(Robot). SVGN 104 PAUSE.L Excessive load detected. SVGN 105 PAUSE.L Failed to reset pulse coder. SVGN 106 PAUSE.L Tip wear uninitialized. SVGN 107 PAUSE.L Tip wear no load threshold. SVGN 108 PAUSE.L Tip wear no standard pulse. SVGN 109 PAUSE.L Tip wear no standard opening. SVGN 110 PAUSE.L Tip wear no detect DI index. SVGN 111 PAUSE.L Failed to touch fixture. SVGN 112 PAUSE.L Incomplete Servo tuning. SVGN 113 PAUSE.L Gun must be open. SVGN 114 PAUSE.L Tip wear misdetection.(FIX). SVGN 115 PAUSE.L MP detection failed. SVGN 116 PAUSE.L MP detection unavailable. SVGN 117 PAUSE.L Ref pos auto-setup failed. SVGN 201 PAUSE.L Gun index 1 SVGN 202 PAUSE.L Gun index 2 SEAL 21 WARN Could not display seal data SEAL 41 PAUSE.G Seal not ready SEAL 43 PAUSE.G High pressure SEAL 46 PAUSE.G Seal not start SEAL 47 PAUSE.G Seal interrupt SEAL 48 ABORT.G Dispenser mode mismatch SEAL 49 ABORT.G Calibrations are not complete SEAL 50 ABORT.G Shot meter not full SEAL 51 ABORT.G Both Drums are empty SEAL 52 ABORT.G Same fault is posted repeatedly SEAL 53 WARN Robot is in dry run mode SEAL 54 WARN Robot lock mode is ON SEAL 55 WARN Sealing is disabled SEAL 61 WARN Seal not ready SEAL 63 WARN High pressure SEAL 64 WARN Not at purge position SEAL 65 WARN Maximum purge count reached SEAL 66 WARN Seal not start SEAL 67 WARN Seal interrupt SEAL 68 WARN Flow command excessive SEAL 69 WARN Equipment hardware error SEAL 70 WARN Gun malfunction SEAL 71 WARN Insufficient system pressure SEAL 72 WARN Nozzle pressure above rating SEAL 73 WARN Volume above allowable limit SEAL 74 WARN Volume below allowable limit SEAL 75 WARN Flow meter fault SEAL 76 WARN Bead defect detected SEAL 77 WARN Unknown equipment fault SEAL 78 WARN Cannot read equipment fault SEAL 79 WARN Dispenser E-stop SEAL 80 WARN Dispenser fault SEAL 81 WARN Dispenser still full SEAL 82 WARN Drum A empty SEAL 83 WARN Drum B empty SEAL 84 WARN Reload timed out SEAL 85 WARN Volume signal calib aborted SEAL 86 WARN Pro-Flo volume strb timeout SEAL 87 WARN Pro-Flo material cal aborted SEAL 88 WARN Pro-Flo material cal timeout SEAL 89 WARN Bead width calib aborted SEAL 90 WARN Bead width is zero SEAL 91 WARN Material weight input is zero SEAL 92 WARN Specific gravity is zero SEAL 93 WARN Volume read is zero SEAL 94 WARN Dispense time is zero SEAL 95 WARN Material pressure cal aborted SEAL 96 WARN Zero matl pressure user input SEAL 97 WARN Pressure read is zero SEAL 98 WARN Atomizing air calib aborted SEAL 99 WARN Zero air pressure user input SEAL 100 WARN NO scale factor or bias SEAL 101 WARN Volume strobe time out SEAL 102 WARN Pressure calib incomplete SEAL 103 WARN Analog voltage calib aborted SEAL 104 WARN Analog voltage cal incomplete SEAL 105 WARN Atomizing air cal incomplete SEAL 106 WARN Voltage step is zero SEAL 107 WARN Material calib incomplete SEAL 108 WARN Material timeout is zero SEAL 109 WARN Low press input >= high press SEAL 110 WARN Flow ctrl: volume cal aborted SEAL 111 WARN Negative volume read SEAL 112 WARN Volume signal cal incomplete SEAL 113 WARN Dispenser I/O setup incomplete SEAL 114 WARN Dispenser not ready SEAL 128 ABORT.G System error(%d)(%d) SEAL 129 PAUSE.G Index incorrect SEAL 132 WARN Can't change prev schedule SEAL 143 ABORT.G Joint motion SEAL 144 WARN Joint motion SEAL 147 PAUSE.G This equipment not exist SEAL 148 ABORT.L No SE Instruction SEAL 149 PAUSE.G Equipment not set SEAL 150 PAUSE.G This equipment already used SEAL 151 WARN Waiting to enter intf zone SEAL 152 WARN Unasigned I/O port SEAL 153 WARN Program is running SEAL 155 WARN No SS Instruction before SE SEAL 156 WARN MOV Program execution failure SEAL 157 WARN Seal schedule data is zero SEAL 158 WARN Tool offset calib aborted SEAL 159 WARN UTOOL #1 is not taught SEAL 160 WARN REFPOS is not taught SEAL 161 WARN OFFSET out of range SEAL 162 WARN OFFSET config mismatch SEAL 163 WARN File is not closed SEAL 164 WARN File does not exist SEAL 170 WARN Invalid tool position SEAL 171 WARN Tool gripper not opened SEAL 172 WARN Tool gripper not closed SEAL 173 WARN Part not present SEAL 174 WARN Part Present SEAL 175 WARN Unassigned Bit mask SEAL 176 WARN IO mode is not complementary SEAL 177 WARN Tool not in FLIP position SEAL 178 WARN Tool not in UNFLIP position SEAL 179 WARN Tool not extended SEAL 180 WARN Tool not retracted SEAL 181 WARN Robot is not calibrated SEAL 182 WARN Invalid kinematic solution SEAL 183 WARN Tool offset internal error SEAL 190 WARN Disabling motion triggering SEAL 191 WARN Gun on/off too late: Sch %d SEAL 192 WARN Cannot change during sealing SEAL 193 WARN Cannot use with motion trigger SEAL 194 WARN Air command exceeds max limit SEAL 195 WARN Air clamped minimum voltage SEAL 196 WARN Calibration aborted SEAL 197 PAUSE.G Atomizing air cal incomplete SEAL 198 ABORT.L Application process is changed during sealing SEAL 199 WARN Flow command clamped minimum voltage SEAL 200 PAUSE.G Invalid Max/Min value for flow command SEAL 201 PAUSE.G Invalid Max/Min value for atomized air SEAL 202 WARN Pre-Pressure is disabled SEAL 203 PAUSE.G Pre-Pressure command can't be executed SEAL 204 WARN Override must be 100%% (%s^4,%d^5) SPOT 0 WARN This is English element 0 SPOT 1 ABORT.L Internal Error (system) SPOT 2 ABORT.L Internal Error (spot) SPOT 3 ABORT.L Unknown packet was received SPOT 4 PAUSE.L Illegal spot instruction SPOT 5 PAUSE.L Weld Complete timed out SPOT 6 PAUSE.L Weld Alarm signal detected SPOT 7 PAUSE.L Gun cannot close SPOT 8 PAUSE.L Backup cannot be full open SPOT 9 PAUSE.L Backup cannot be half open SPOT 10 PAUSE.L Illegal register index SPOT 11 PAUSE.L I/O setup error (Close backup) SPOT 12 PAUSE.L I/O setup error (Close detect) SPOT 13 PAUSE.L I/O setup error (Clamp signal SPOT 14 PAUSE.L I/O setup error (Full detect) SPOT 15 PAUSE.L I/O setup error (Half detect) SPOT 16 PAUSE.L I/O setup error (Open backup) SPOT 17 PAUSE.L I/O setup error (Gun press) SPOT 18 PAUSE.L I/O setup error (Schedule asg) SPOT 19 PAUSE.L I/O setup error (H/M/L Valve) SPOT 20 PAUSE.L I/O setup error (Weld enable) SPOT 21 PAUSE.L I/O setup error (Weld on) SPOT 22 PAUSE.L I/O setup error (Weld comp) SPOT 23 WARN Weld Complete timed out SPOT 24 WARN Weld Control timed out SPOT 25 PAUSE.L Check the setting of DIN SPOT 26 PAUSE.L Check the setting of DOUT SPOT 27 PAUSE.L Illegal number of equipment SPOT 28 PAUSE.L Illegal value of register SPOT 29 PAUSE.L GUN1: Weld Complete signal already on SPOT 30 PAUSE.L GUN2: Weld Complete signal already on SPOT 31 PAUSE.L Locked by another program SPOT 54 WARN Spot variables not found SPOT 55 WARN Bad register index SPOT 58 WARN Cannot write DOUT SPOT 60 WARN Check the setting of DOUT SPOT 61 SYSTEM Equipment number is not much. SPOT 62 SYSTEM Please power on again. SPOT 63 WARN Please push shift key SPOT 64 WARN Macro program is not set SPOT 65 WARN Clear motion mask of MACRO SPOT 66 WARN IWC(DG) system error %d(%x) SPOT 67 PAUSE.L IWC(DG) illegal stepper number(%s) SPOT 68 PAUSE.L IWC(DG) illegal contactor status(%d) SPOT 69 PAUSE.L IWC(DG) leak input (%d) SPOT 70 PAUSE.L IWC(DG) illegal counter specified(%s) SPOT 71 PAUSE.L Reset stepper timeout %s SPOT 72 WARN IWC(DG) timer no response(%d) SPOT 73 WARN IWC(DG) timer acc stat err(%d) SPOT 74 WARN IWC(DG) timer exe flag err(%d) SPOT 75 WARN IWC(DG) timer bad response(%d) SPOT 76 PAUSE.L IWC(DG) timer memory error(%d) SPOT 77 SYSTEM IWC(DG) timer not running(%d) SPOT 78 PAUSE.L IWC(DG) timer support from Gun1 to Gun4 SPOT 79 WARN IWC(DG) drv sys err %d SPOT 80 PAUSE.L IWC(DG) timer now in weld %d SPOT 81 PAUSE.L %s SPOT 82 WARN %s SPOT 83 WARN Request Failed SPOT 84 WARN IWC board not found SPOT 85 PAUSE.L Iwc NOT ready SPOT 86 PAUSE.L illedal board specified(%d) SPOT 87 WARN Iwc NOT ready SPOT 88 PAUSE.L Iso contactor not ready SPOT 89 PAUSE.L IWC(DG) + Dual gun needs 2 boards SPOT 90 PAUSE.L Gun1 and Gun2 specified same board SPOT 91 PAUSE.L IWC(DG) timer com err %d(%x) SPOT 92 PAUSE.L IWC(DG) reset welder timeout(%d) SPOT 93 PAUSE.L IWC(DG) bad schedule(%d/%d) SPOT 94 WARN Please retry function again SPOT 95 PAUSE.L Reset welder timeout %s SPOT 96 WARN %s SPOT 97 PAUSE.L IWC(Md) illegal stepper(%s) SPOT 98 PAUSE.L IWC fault SPOT 99 WARN Weld enable mismatch SPOT 100 PAUSE.L IWC(Md) Weld Comp already on SPOT 101 SYSTEM IWC(DG) Can't read system_ready(%d) SPOT 102 SYSTEM IWC(DG) Failed to set Weld Current flag(%d) SPOT 103 PAUSE.L IWC(DG) Board number duplicated(%d) SPOT 104 WARN IWC(DG) MB Gun no out of range(%d) SPOT 105 SYSTEM IWC(DG) DPRAM error (%d) SPOT 106 SYSTEM %x,%x,%x SPOT 107 PAUSE.L IWC(DG) shunt trip DO error(%d) SPOT 108 PAUSE.L IWC(DG) stepper cmp DO error(%d) SPOT 109 PAUSE.L IWC(DG) DPRAM out DO error(%d,%d) SPOT 110 WARN IWC(DG) timer now in weld %d SPOT 111 PAUSE.L IWC(DG) No Weld detection DO error SPOT 351 WARN IWC driver not running SPOT 352 WARN Invalid IWC index SPOT 353 WARN IWC message in progress SPOT 354 WARN Invalid IWC msg buffers SPOT 355 WARN Invalid IWC function code SPOT 356 WARN Checksum error, IWC msg send SPOT 357 WARN Invalid buffer, IWC msg send SPOT 358 WARN Checksum error, IWC msg recv SPOT 359 WARN Invalid buffer, IWC msg recv SPOT 360 WARN IWC buffer too small SPOT 361 WARN Ack timeout, IWC msg send SPOT 362 WARN Timeout, IWC msg recv SPOT 363 WARN IWC motherboard error SPOT 364 WARN IWC has invalid DPRAM signature SPOT 365 WARN Unsupported IWC version/rev level SPOT 366 WARN Unable to register IWC interrupt SPOT 367 WARN Only 29 functions allowed in a schedule SPOT 368 WARN Imp. can only come before weld FCTN SPOT 369 WARN FCTN not supported by the timer SPOT 370 WARN Could not download schedule %d SPOT 371 WARN Could not download stepper %d SPOT 372 WARN Could not read sequence file %d SPOT 373 WARN Could not download setup data SPOT 374 WARN Could not download Dynamic data SPOT 375 WARN Could not read stepper file %d SPOT 376 WARN Could not read setup file %s SPOT 377 WARN Could not read file %s SPOT 378 WARN IWC ID jumpers incorrect SPOT 379 WARN IWC slave busy SPOT 380 WARN Invalid IWC Firmware Version SRIO 1 WARN S. PORT ILLEGAL FUNCTION CODE SRIO 2 WARN SERIAL PORT NOT OPEN SRIO 3 WARN SERIAL PORT ALREADY OPEN SRIO 4 WARN SERIAL PORT NOT INITIALIZE SRIO 5 WARN SERIAL PORT DSR OFF SRIO 6 WARN SERIAL PORT PARITY ERROR SRIO 7 WARN SERIAL PORT OVERRUN ERROR SRIO 8 WARN SERIAL PORT FRAME ERROR SRIO 9 WARN S. PORT PARITY & OVERRUN SRIO 10 WARN S. PORT PARITY & FRAME SRIO 11 WARN S. PORT OVERRUN & FRAME SRIO 12 WARN S. PORT PRTY & OVRRN & FRM SRIO 13 WARN S. PORT DSR OFF & HARDWARE ERR SRIO 14 WARN S. PORT ILLEGAL REQUEST COUNT SRIO 15 WARN SERIAL PORT CANCEL SRIO 16 WARN S. PORT POWER FAILURE CANCEL SRVO 1 SERVO Operator panel E-stop SRVO 2 SERVO Teach pendant E-stop SRVO 3 SERVO Deadman switch released SRVO 4 SERVO Fence open SRVO 5 SERVO Robot overtravel SRVO 6 SERVO Hand broken SRVO 7 SERVO External emergency stops SRVO 8 SERVO Brake fuse blown SRVO 9 SERVO Pneumatic pressure alarm SRVO 10 SERVO Belt broken SRVO 11 SERVO TP released while enabled SRVO 12 SERVO Power failure recovery SRVO 13 SYSTEM Srvo module config changed SRVO 14 WARN Fan motor abnormal SRVO 15 SERVO System over heat SRVO 16 SERVO Cooling water volume drop SRVO 17 SERVO No robot internal mirror SRVO 18 SERVO Brake abnormal SRVO 19 SERVO SVON input SRVO 20 SERVO SRDY off (TP) SRVO 21 SERVO SRDY off (Group:%d Axis:%d) SRVO 22 SERVO SRDY on (Group:%d Axis:%d) SRVO 23 SERVO Stop error excess(G:%d A:%d) SRVO 24 SERVO Move error excess(G:%d A:%d) SRVO 25 SERVO Motn dt overflow (G:%d A:%d) SRVO 26 WARN Motor speed limit(G:%d A:%d) SRVO 27 WARN Robot not mastered(Group:%d) SRVO 30 SERVO Brake on hold (Group:%d) SRVO 31 SERVO User servo alarm (Group:%d) SRVO 33 WARN Robot not calibrated(Grp:%d) SRVO 34 WARN Ref pos not set (Group:%d) SRVO 35 WARN Joint speed limit(G:%d A:%d) SRVO 36 SERVO Inpos time over (G:%d A:%d) SRVO 37 SERVO IMSTP input (Group:%d) SRVO 38 SERVO2 Pulse mismatch (G:%d A:%d) SRVO 39 SERVO Motor speed excess(G:%d A:%d) SRVO 40 WARN Mastered at mark pos(G:%d) SRVO 41 SERVO2 MOFAL alarm (Grp:%d Ax:%d) SRVO 42 SERVO MCAL alarm(Group:%d Axis:%d) SRVO 43 SERVO DCAL alarm(Group:%d Axis:%d) SRVO 44 SERVO HVAL alarm(Group:%d Axis:%d) SRVO 45 SERVO HCAL alarm(Group:%d Axis:%d) SRVO 46 SERVO2 OVC alarm (Group:%d Axis:%d) SRVO 47 SERVO LVAL alarm(Group:%d Axis:%d) SRVO 48 SERVO2 MOH alarm (Group:%d Axis:%d) SRVO 49 SERVO OHAL1 alarm (Grp:%d Ax:%d) SRVO 50 SERVO Collision Detect alarm (G:%d A:%d) SRVO 51 SERVO2 CUER alarm(Group:%d Axis:%d) SRVO 53 WARN Disturbance excess(G:%d A:%d) SRVO 54 SYSTEM DSM memory error (DSM:%d) SRVO 55 SERVO2 FSSB com error 1 (G:%d A:%d) SRVO 56 SERVO2 FSSB com error 2 (G:%d A:%d) SRVO 57 SERVO2 FSSB disconnect (G:%d A:%d) SRVO 58 SYSTEM FSSB 1 init error SRVO 59 SYSTEM Servo amp init error SRVO 60 SYSTEM FSSB 2 init error SRVO 61 SERVO2 CKAL alarm(Group:%d Axis:%d) SRVO 62 SERVO2 BZAL alarm(Group:%d Axis:%d) SRVO 63 SERVO2 RCAL alarm(Group:%d Axis:%d) SRVO 64 SERVO2 PHAL alarm(Group:%d Axis:%d) SRVO 65 WARN BLAL alarm(Group:%d Axis:%d) SRVO 66 SERVO2 CSAL alarm(Group:%d Axis:%d) SRVO 67 SERVO2 OHAL2 alarm (Grp:%d Ax:%d) SRVO 68 SERVO2 DTERR alarm (Grp:%d Ax:%d) SRVO 69 SERVO2 CRCERR alarm (Grp:%d Ax:%d) SRVO 70 SERVO2 STBERR alarm (Grp:%d Ax:%d) SRVO 71 SERVO2 SPHAL alarm (Grp:%d Ax:%d) SRVO 72 SERVO2 PMAL alarm(Group:%d Axis:%d) SRVO 73 SERVO2 CMAL alarm(Group:%d Axis:%d) SRVO 74 SERVO2 LDAL alarm(Group:%d Axis:%d) SRVO 75 WARN Pulse not established(G:%d A:%d) SRVO 76 SERVO Tip Stick Detection(G:%d A:%d) SRVO 77 SERVO Dynamic brake alarm(G:%d A:%d) SRVO 81 WARN EROFL alarm (Track enc:%d) SRVO 82 WARN DAL alarm(Track encoder:%d) SRVO 83 WARN CKAL alarm (Track enc:%d) SRVO 84 WARN BZAL alarm (Track enc:%d) SRVO 85 WARN RCAL alarm (Track enc:%d) SRVO 86 WARN PHAL alarm (Track enc:%d) SRVO 87 WARN BLAL alarm (Track enc:%d) SRVO 88 WARN CSAL alarm (Track enc:%d) SRVO 89 WARN OHAL2 alarm (Track enc:%d) SRVO 90 WARN DTERR alarm (Track enc:%d) SRVO 91 WARN CRCERR alarm (Track enc:%d) SRVO 92 WARN STBERR alarm (Track enc:%d) SRVO 93 WARN SPHAL alarm (Track enc:%d) SRVO 94 WARN PMAL alarm (Track enc:%d) SRVO 95 WARN CMAL alarm (Track enc:%d) SRVO 96 WARN LDAL alarm (Track enc:%d) SRVO 97 WARN Pulse not established(Enc:%d) SRVO 101 SERVO Robot overtravel(Robot:%d) SRVO 102 SERVO Hand broken (Robot:%d) SRVO 103 SERVO Air pressure alarm(Rbt:%d) SRVO 105 SERVO Door open or E.Stop SRVO 106 SERVO Door open/E.Stop(Robot:%d) SRVO 107 SERVO Ext brake abnormal(Rbt:%d) SRVO 108 SERVO Press RESET to enable robot SRVO 111 SERVO Softfloat time out(G:%d) SRVO 112 PAUSE.G Softfloat time out(G:%d) SRVO 113 SERVO Cart. error excess(G:%d %s) SRVO 121 SERVO Excessive acc/dec time(G:%d) SRVO 122 SERVO Bad last ang(internal)(G:%d) SRVO 125 WARN Quick stop speed over (G:%d) SRVO 126 SERVO Quick stop error (G:%d) SRVO 130 SERVO OHAL1(PSM) alarm (G:%d A:%d) SRVO 131 SERVO LVAL(PSM) alarm(G:%d A:%d) SRVO 132 SERVO HCAL(PSM) alarm(G:%d A:%d) SRVO 133 SERVO FSAL(PSM) alarm (G:%d A:%d) SRVO 134 SERVO DCLVAL(PSM) alarm (G:%d A:%d) SRVO 135 SERVO FSAL alarm (G:%d A:%d) SRVO 136 SERVO DCLVAL alarm (G:%d A:%d) SRVO 137 SERVO DAL alarm (G:%d A:%d) SRVO 138 SERVO SDAL alarm (G:%d A:%d) SRVO 141 SERVO OHAL1(CNV) alarm (G:%d A:%d) SRVO 142 SERVO OHAL1(INV) alarm (G:%d A:%d) SRVO 143 SERVO PSFLAL(CNV) alarm (G:%d A:%d) SRVO 144 SERVO LVAL(INV) alarm (G:%d A:%d) SRVO 145 SERVO LVAL(CNV-DC) alarm(G:%d A:%d) SRVO 146 SERVO LVAL(INV-DC) alarm(G:%d A:%d) SRVO 147 SERVO LVAL(DCLK) alarm (G:%d A:%d) SRVO 148 SERVO HCAL(CNV) alarm (G:%d A:%d) SRVO 149 SERVO HCAL(INV) alarm (G:%d A:%d) SRVO 150 SERVO FSAL(CNV) alarm (G:%d A:%d) SRVO 151 SERVO FSAL(INV) alarm (G:%d A:%d) SRVO 152 SERVO IPMAL(INV) alarm (G:%d A:%d) SRVO 153 SERVO CHGAL(CNV) alarm (G:%d A:%d) SRVO 154 SERVO HVAL(CNV-DC) alarm (G:%d A:%d) SRVO 155 SERVO DCAL(CNV) alarm (G:%d A:%d) SRVO 156 SERVO IPMAL alarm (G:%d A:%d) SRVO 157 SERVO CHGAL alarm (G:%d A:%d) SRVO 160 SERVO Panel/External E-stop SRVO 161 SERVO Fence open or Deadman SW SRVO 162 SERVO Deadman/Fence or Panel/External E-stop SRVO 163 SYSTEM DSM hardware mismatch SRVO 164 SYSTEM DSM/Servo param mismatch SRVO 171 WARN MotorSpd lim/DVC(G:%d A:%d) SRVO 172 WARN MotorSpd lim/DVC0(G:%d A:%d) SRVO 173 WARN MotorSpd lim/DVC1(G:%d A:%d) SRVO 174 WARN MotorAcc lim/DVC(G:%d A:%d) SRVO 176 SERVO CJ/Illegal Mode %d,%d SRVO 177 WARN CJ error %d,%d,%d,%d SRVO 178 SYSTEM CJ error %d,%d,%d,%d SRVO 179 WARN Motor torque limit(G:%d A:%d) SRVO 181 SERVO Mcmd input while estimating(G:%d) SRVO 182 PAUSE.G Needed init. has not been done SRVO 183 PAUSE.G ROBOT isn't ready SRVO 184 PAUSE.G Other task is processing SRVO 185 PAUSE.G Data is for other group SRVO 186 PAUSE.G Needed Data has not been got SRVO 187 PAUSE.G Need specfing Mass SRVO 188 PAUSE.G Memory is lacking SRVO 191 SYSTEM Illegal Joint Speed (G:%d A:%d) SRVO 192 SERVO Fence open/SVON input SRVO 193 SERVO SVON input SRVO 194 SERVO Servo disconnect SRVO 195 SERVO NTED/Servo disconnect SRVO 196 SYSTEM Fence open/SVON input (SVON abnormal) SRVO 197 SYSTEM SVON input (SVON abnormal) SRVO 199 PAUSE.G Control Stop SRVO 200 WARN Control box fan abnormal SRVO 201 SERVO Panel E-stop or SVEMG abnormal SRVO 202 SERVO TP E-stop or SVEMG abnormal SRVO 203 SYSTEM SVON input(SVEMG abnormal) SRVO 204 SYSTEM External(SVEMG abnormal) E-stop SRVO 205 SYSTEM Fence open(SVEMG abnormal) SRVO 206 SYSTEM Deadman switch (SVEMG abnormal) SRVO 207 SERVO TP switch abnormal or Door open SRVO 208 SERVO Extended axis brake abnormal SRVO 209 SERVO Robot-2 SVEMG abnormal SRVO 210 SERVO EX_robot SVEMG abnormal SRVO 211 SERVO TP OFF in T1,T2 SRVO 212 SERVO Trans over heat SRVO 213 SERVO Fuse blown (PanelPCB) SRVO 214 SERVO Fuse blown (Amp) SRVO 215 SERVO Fuse blown (Aux axis) SRVO 216 SERVO OVC(total) (%d) SRVO 221 SERVO Lack of DSP (G:%d A:%d) SRVO 222 SERVO Lack of Amp (Amp:%d) SRVO 230 SERVO Chain 1 (+24v) abnormal SRVO 231 SERVO Chain 2 (0v) abnormal SRVO 232 SERVO NTED input SRVO 233 SERVO TP OFF in T1,T2/Door open SRVO 234 WARN Deadman switch released SRVO 235 SERVO Short term Chain abnormal SRVO 236 WARN Chain failure is repaired SRVO 237 WARN Cannot reset chain failure SRVO 238 SERVO Chain 1 (SVON) abnormal SRVO 239 SERVO Chain 2 (SVON) abnormal SRVO 240 SERVO Chain 1 (FENCE) abnormal SRVO 241 SERVO Chain 2 (FENCE) abnormal SRVO 242 SERVO Chain 1 (EXEMG) abnormal SRVO 243 SERVO Chain 2 (EXEMG) abnormal SRVO 244 SERVO Chain 1 abnormal(Rbt:%d) SRVO 245 SERVO Chain 2 abnormal(Rbt:%d) SRVO 246 SERVO Chain 1 abnormal(EX_robot) SRVO 247 SERVO Chain 2 abnormal(EX_robot) SRVO 250 SERVO SVEMG/MAINON1 abnormal SRVO 260 SERVO Chain 1 (NTED) abnormal SRVO 261 SERVO Chain 2 (NTED) abnormal SRVO 262 SERVO Chain 1 (SVDISC) abnormal SRVO 263 SERVO Chain 2 (SVDISC) abnormal SRVO 264 SYSTEM E.STOP circuit abnormal 1 SRVO 265 SERVO E.STOP circuit abnormal 2 SRVO 266 SERVO FENCE1 status abnormal SRVO 267 SERVO FENCE2 status abnormal SRVO 268 SERVO SVOFF1 status abnormal SRVO 269 SERVO SVOFF2 status abnormal SRVO 270 SERVO EXEMG1 status abnormal SRVO 271 SERVO EXEMG2 status abnormal SRVO 272 SERVO SVDISC1 status abnormal SRVO 273 SERVO SVDISC2 status abnormal SRVO 274 SERVO NTED1 status abnormal SRVO 275 SERVO NTED2 status abnormal SRVO 276 SERVO Disable on T2 mode SRVO 277 SYSTEM Panel E-stop(SVEMG abnormal) SRVO 278 SYSTEM TP E-stop(SVEMG abnormal) SRVO 279 SYSTEM Circuit abnormal 3 (%d) SRVO 280 SERVO SVOFF input SRVO 281 SYSTEM SVOFF input(SVEMG abnormal) SRVO 282 SERVO Chain 1 (SVOFF) abnormal SRVO 283 SERVO Chain 2 (SVOFF) abnormal SRVO 286 SYSTEM E.STOP circuit abnl 1(G:%d) SRVO 287 SERVO E.STOP circuit abnl 2(G:%d) SRVO 290 SERVO DClink HC alarm(G:%d A:%d) SRVO 291 SERVO IPM over heat (G:%d A:%d) SRVO 292 SERVO EXT.FAN alarm (G:%d A:%d) SRVO 293 SERVO DClink(PSM) HCAL(G:%d A:%d) SRVO 294 SERVO EXT.FAN(PSM) alarm(G:%d A:%d) SRVO 295 SERVO SVM COM alarm(G:%d A:%d) SRVO 296 SERVO PSM DISCHG alm(G:%d A:%d) SRVO 297 SERVO PSM LowVolt alm(G:%d A:%d) SRVO 298 SYSTEM SRVO velocity alm(G:%d A:%d) SRVO 300 SERVO Hand broken/HBK disabled SRVO 301 SERVO Hand broken/HBK dsbl(Rbt:%d) SRVO 302 SERVO Set Hand broken to ENABLE SRVO 303 SERVO Set HBK to ENABLE(Rbt:%d) SRVO 304 SERVO C-flex: manual brake enabled SRVO 310 SERVO ABC Unexpected Motion(G:%d) SRVO 315 PAUSE.G MPDT failed(G:%d A:%d) SRVO 316 PAUSE.G MPDT time is up(G:%d A:%d) SRVO 317 PAUSE.G MPDT cannot start(Machine Lock) SRVO 318 PAUSE.G MPDT cannot start(SRDY Off) SRVO 320 SERVO E.STOP SRVO 321 SERVO TP SW/Deadman abnormal SRVO 322 SERVO SVOFF input / E.STOP SRVO 330 SERVO Retry count err(G:%d A:%d) SRVO 331 SERVO FB comp cnt err(G:%d A:%d) SRVO 332 SERVO Power off to reset CMAL SRVO 333 SYSTEM Power off to reset SSPC 1 WARN Waiting until space gets clear SSPC 2 PAUSE.G Occer dead lock condition SSPC 3 PAUSE.G AccuPath not allowed SSPC 4 PAUSE.G CTV option not allowed SSPC 5 PAUSE.G Disabled while waiting SSPC 11 SYSTEM APDT error %x SSPC 12 SERVO Invalid element (%s:%d %d) SSPC 13 SERVO Invalid hand num (G:%d UT:%d) SSPC 14 SERVO Common frame setting (G:%d) SSPC 15 SERVO Not calibrated (G:%d) SSPC 16 SERVO Invalid comb type (C:%d %s) SSPC 17 SERVO Invalid comb index (C:%d %s) SSPC 18 SERVO APDT is not supported (G:%d) SSPC 19 SERVO (G:%d) is close to target SSPC 20 SERVO Invalid fixture obj (F:%d) SSPC 21 SERVO Too many settings SSPC 101 SERVO (G:%d) is close to target SSPC 102 PAUSE.G (G:%d) is close to target(qstop) SSPC 103 PAUSE.G (G:%d) is near to target SSPC 104 SYSTEM APDT error %x SSPC 105 SERVO Too many settings SSPC 106 SERVO Failed to get dist (%d,C:%d) SSPC 111 SERVO Invalid comb type (ST,C:%d,%s) SSPC 112 SERVO Invalid comb index(ST,C:%d,%s) SSPC 113 SERVO APDT isn't supported (ST,G:%d) SSPC 114 SERVO Not calibrated (ST,G:%d) SSPC 115 SERVO Invalid utool number (ST,G:%d) SSPC 116 SERVO Invalid hand num(ST,G:%d,UT:%d) SSPC 117 SERVO Common frame setting (ST,G:%d) SSPC 118 SERVO Invalid element (ST,%s:%d,%d) SSPC 119 SERVO Can't get elem pos(ST,G:%d,%d) SSPC 120 SERVO Invalid fixture obj (ST,F:%d) SSPC 131 PAUSE.G Invalid comb type (WT,C:%d,%s) SSPC 132 PAUSE.G Invalid comb index(WT,C:%d,%s) SSPC 133 PAUSE.G APDT isn't supported (WT,G:%d) SSPC 134 PAUSE.G Not calibrated (WT,G:%d) SSPC 135 PAUSE.G Invalid utool number (WT,G:%d) SSPC 136 PAUSE.G Invalid hand num(WT,G:%d,UT:%d) SSPC 137 PAUSE.G Common frame setting (WT,G:%d) SSPC 138 PAUSE.G Invalid element (WT,%s:%d,%d) SSPC 139 PAUSE.G Can't get elem pos(WT,G:%d,%d) SSPC 140 PAUSE.G Invalid fixture obj (WT,F:%d) SSPC 151 WARN App_STOP (ST,C:%d) is disabled SSPC 152 WARN App_STOP (ST,C:%d) is disabled SSPC 153 PAUSE.G (WT,C:%d) is enabled by other SSPC 154 PAUSE.G (ST,C:%d) is disabled by other SSPC 155 PAUSE.G Invalid host name (ST,C:%d) SSPC 156 PAUSE.G Invalid host name (WT,C:%d) SSPC 157 PAUSE.G Intrupt signal (WT,C:%d) SSPC 158 PAUSE.G App_WAIT timeout (WT,C:%d) SSPC 159 PAUSE.G App_WAIT can't be used(WT,G:%d) SSPC 160 WARN App_STOP is TMP_DISed(ST,C:%d) SSPC 161 WARN App_STOP is enabled (ST,C:%d) SSPC 162 WARN App_WAIT is enabled (WT,C:%d) SSPC 163 WARN App_WAIT is disabled (WT,C:%d) SSPC 164 WARN (%s,%d) TMP_disabled (ST,C:%d) SSPC 165 WARN (%s,%d) enabled (ST,C:%d) SSPC 166 WARN (%s,%d) enabled (WT,C:%d) SSPC 167 WARN (%s,%d) disabled (WT,C:%d) SSPC 168 PAUSE.G (%s,%d) invalid group number SSPC 169 PAUSE.G (%s,%d) invalid rate value SSPC 181 WARN Comm init error %d %s SSPC 182 SERVO Invalid hostname (%s) SSPC 183 SERVO Invalid address (%s) SSPC 184 SERVO Number of host exceed limit SSPC 185 SERVO Number of element exceed limit SSPC 186 SERVO Invalid element (%s,%d,%d) SSPC 187 WARN Receive invalid data %d %s SSPC 188 SERVO Invalid data for send %d SSPC 189 SERVO Timeout element (%s,%d,%d) SSPC 190 PAUSE.G No communication (%s) SSPC 191 SERVO Target elem not exist(ST,C:%d,%s) SSPC 192 PAUSE.G Target elem not exist(PA,C:%d,%s) SSPC 193 WARN IAL detect overload (%d) SSPC 201 WARN Interference Detected(G:%d) SSPC 202 PAUSE.G Obstacle Detected(G:%d) SSPC 203 SERVO Check combination type mismatch SSPC 204 SERVO Two points not form a line SSPC 205 SERVO Three points not form a plane SSPC 206 SERVO Four points not form a box SSPC 207 SERVO Check combination not supported SSPC 208 WARN Unit vector formation error SSPC 209 SERVO Robot in too far(G:%d) SSPC 210 SERVO Comb check I/O Setting invalid SSPC 211 PAUSE.G Obstacle Detected(G:%d^2) SYST 1 PAUSE.G HOLD button is being pressed SYST 2 PAUSE.G HOLD is locked by program SYST 3 WARN TP is enabled SYST 4 WARN SOP is enabled SYST 5 WARN UOP is the master device SYST 6 WARN KCL is the master device SYST 7 WARN NETWORK is the master device SYST 8 WARN Nothing is the master device SYST 9 WARN Safety Fence open SYST 10 WARN Max num task reached SYST 11 WARN Failed to run task SYST 12 WARN Not in remote SYST 13 WARN Invalid program number SYST 14 WARN Program select failed SYST 15 WARN Robot Service Request failed SYST 16 WARN ENBL signal is off SYST 17 WARN Single step operation effective SYST 18 WARN Continuing from different line SYST 19 WARN Program not selected SYST 20 WARN Program not verified by PNS SYST 21 WARN System not ready, press reset SYST 22 WARN PNS not zero, cannot continue SYST 23 SYSTEM Teach Pendant communication error SYST 24 WARN PNSTROBE is OFF. Cannot start exec SYST 25 WARN Teach Pendant is different type SYST 26 WARN System normal power up SYST 27 PAUSE.G HOT start failed (Error:%d) SYST 28 WARN (%s) Program timed out SYST 29 PAUSE.G Robot was connected (Group:%d) SYST 30 PAUSE.G Robot was isolated (Group:%d) SYST 31 SYSTEM F-ROM parity SYST 32 WARN ENBL signal from UOP is lost SYST 33 WARN SFSPD signal from UOP is lost SYST 34 WARN HOLD signal from SOP/UOP is lost SYST 35 WARN Low or No Battery Power in PSU. SYST 36 WARN Semi power failure recovery SYST 37 ABORT.G Key switch broken SYST 38 PAUSE.G Operation mode T1 Selected SYST 39 PAUSE.G Operation mode T2 Selected SYST 40 PAUSE.G Operation mode AUTO Selected SYST 41 PAUSE.G Ovrd Select could not ENABLED SYST 42 PAUSE.G DEADMAN defeated SYST 43 PAUSE.G TP disabled in T1/T2 mode SYST 44 SYSTEM (Abnormal) TP disabled in T1/T2 mode SYST 45 PAUSE.G TP enabled in AUTO mode SYST 46 SYSTEM Control Reliable/CE Mark config mismatch SYST 47 WARN Continuing from distant position SYST 48 ABORT.G NECALC couldn't get work memory SYST 49 ABORT.G SFCALC couldn't get work memory SYST 50 WARN Invalid time in trigger request SYST 51 PAUSE.G SYTG overrun: %d %d %x %d %d SYST 52 WARN Trigger slot already used: %d SYST 53 WARN Invalid fast_DIN no: %d SYST 54 WARN Event-ID already used: %d SYST 55 WARN Event-ID not found: %d SYST 56 WARN Scan routine list full SYST 57 WARN Illegal interval SYST 58 WARN Duplicate scan routine SYST 59 WARN Scan routine not active SYST 60 WARN Duplicate cond/act table SYST 61 WARN Scan table list full SYST 62 WARN Scan table not active SYST 63 WARN Scan time record seq error SYST 64 WARN Bad scan table data SYST 65 ABORT.G SFCALC overrun SYST 66 PAUSE.G Teach Pendant communication error SYST 67 SYSTEM Panel HSSB disconnect SYST 69 WARN Program number out of range SYST 70 WARN No program name in table SYST 71 WARN Program not found SYST 72 WARN Program not enabled SYST 73 WARN Manual selection mismatch SYST 74 WARN Karel shell failed SYST 75 WARN Shell init failure SYST 76 WARN Shell condition setup failure SYST 77 WARN Entered INTERLOCK mode SYST 78 WARN Entered ISOLATE mode SYST 79 WARN Startup check failed SYST 80 WARN Fault must be reset SYST 81 WARN Not at home position SYST 82 WARN Not within resume tolerance SYST 83 WARN I/O is simulated SYST 84 WARN I/O forced unsimulated SYST 85 WARN Gen override not 100% SYST 86 WARN Gen override forced to 100% SYST 87 WARN Prog override not 100% SYST 88 WARN Prog override forced to 100% SYST 89 WARN Machine lock on SYST 90 WARN Machine lock forced off SYST 91 WARN Single step active SYST 92 WARN Single step forced off SYST 93 WARN Process not ready SYST 94 WARN Process forced ready SYST 95 ABORT.G Remote diagnose internal error SYST 96 ABORT.G Designated task is not valid SYST 97 WARN Fail to initialize Modem SYST 98 WARN Card Modem is removed SYST 99 WARN Card Modem is not responded SYST 100 WARN DSR in Modem OFF SYST 101 WARN Connection is stopped SYST 102 ABORT.G HDI not recorded SYST 103 WARN Not-home ignored SYST 104 WARN Resume tolerance ignored SYST 105 WARN Simulated I/O ignored SYST 106 WARN Gen override ignored SYST 107 WARN Prog override ignored SYST 108 WARN Machine lock ignored SYST 109 WARN Single step ignored SYST 110 WARN Process ready ignored SYST 111 WARN No home pos defined SYST 112 WARN No production start input defined SYST 113 WARN No style input group defined SYST 114 WARN No RSR input defined SYST 115 WARN No PNS select input defined SYST 116 WARN No RSR echo output defined SYST 117 WARN No PNS echo output defined SYST 118 WARN No PNS strobe input defined SYST 119 WARN No echo strobe output defined SYST 120 WARN No style option input defined SYST 121 WARN No decision input group defined SYST 122 WARN No style output group defined SYST 123 WARN No option output defined SYST 124 WARN No decision output group defined SYST 125 WARN No in-cycle output defined SYST 126 WARN No task-OK output defined SYST 127 WARN No isolate output defined SYST 128 WARN No interlock output defined SYST 129 WARN No manual style output defined SYST 130 WARN Program still running SYST 131 WARN Invalid manual style request SYST 132 WARN Manual request timed out SYST 133 WARN System trigger request early SYST 134 WARN Max. freq. exceeded ch.: %d SYST 135 WARN Invalid Clock, Please Reset SYST 136 WARN System Time was reset SYST 137 WARN Device not found SYST 138 WARN Motherboard not installed SYST 139 WARN Invalid motherboard request SYST 140 WARN Invalid IRQ specified SYST 141 WARN BMON was updated SYST 142 WARN ABS time in sytmrev in past SYST 143 WARN pkt_data_size too big SYST 144 WARN Bad DO specfied by %s SYST 145 WARN DO specfied by %s OFFLINE SYST 146 WARN n_pkts invalid SYST 148 PAUSE.G Dynamic Brake is Disabled SYST 149 WARN Dynamic Brake is Enabled SYST 150 WARN Cursor is not on line 1 SYST 151 WARN Start again (%s, %d) SYST 152 WARN Cannot force DO's in AUTO mode SYST 153 WARN Cannot SIM/UNSIM DO's in AUTO mode SYST 154 WARN No start in ISOLATE/BYPASS mode SYST 155 SERVO ABC overrun SYST 156 SYSTEM Unknown hard ware SYST 157 SYSTEM CE/RIA software does not exist SYST 158 PAUSE.G Robot cannot move in T2 mode SYST 159 WARN GO %d for Error Output not configured SYST 160 WARN Value outputted to GO %d out of limit SYST 161 WARN Cannot start Remote diagnostic SYST 162 PAUSE.G Servo On during Remote diagnostic SYST 163 WARN Cannot operate IO during Remote diagnostic SYST 164 WARN Teach Pendant communication error SYST 165 PAUSE.G TP intermittent communication error SYST 166 WARN TP intermittent communication error SYST 167 WARN Motion initialization is disabled SYST 168 WARN Robot(G:%d) is isolated SYST 169 WARN S/W Registration is temporary SYST 170 WARN S/W Reg. expires in %d days SYST 171 PAUSE.G S/W Reg. expires in %d days SYST 172 PAUSE.G S/W Registration has expired SYST 173 WARN See S/W Reg Screen (STATUS) SYST 174 SYSTEM Invalid SYST - CTRL start Req SYST 175 WARN System was updated SYST 176 WARN Software was updated SYST 180 SYSTEM OP log book internal error(%x) SYST 181 WARN Too big log to store SYST 182 WARN OP log was destroyed SYST 183 WARN sylog lib param error SYST 184 WARN No log to read SYST 185 WARN Log recording is interrupt. SYST 186 WARN Log was destroyed during reading SYST 187 WARN OP log book internal error(%x) SYST 188 WARN book(%d) was not created SYST 189 WARN There is no book TAST 0 WARN unknown error (TAST00) TAST 1 WARN TAST global vars failure TAST 2 PAUSE.G TAST error IO allocation TAST 3 PAUSE.G TAST IO initialization failed TAST 4 PAUSE.G TAST IO start failed TAST 5 WARN TAST time tick missing TAST 6 PAUSE.G TAST memory dispose failure TAST 7 PAUSE.G TAST RPM saving failure TAST 8 PAUSE.G TAST incorrect schedule num TAST 9 PAUSE.G TAST weave freq is too low TAST 10 PAUSE.G TAST software error (SRIF) TAST 11 PAUSE.G TAST software error (PMPT) TAST 12 PAUSE.G TAST software error (INTP) TAST 13 PAUSE.G TAST software error TAST 14 PAUSE.G TAST weave freq is too high TCPP 0 WARN Unknown (TC00) TCPP 1 WARN No global variables TCPP 2 WARN No mmr pointer TCPP 3 WARN No mir pointer TCPP 4 WARN No sysvar pointer TCPP 5 WARN No tcppir pointer TCPP 6 WARN Error allocating memory TCPP 7 WARN Error making TCPP mailbox TCPP 8 WARN Error making TCPP spmktsk TCPP 9 WARN Pnts too close before line:%d^5 TCPP 10 WARN Error writing PLAN mailbox TCPP 11 WARN Pred time skips first motion TCPP 12 WARN Invalid TCPP filter type TCPP 13 WARN Invalid TCPP start pos TCPP 14 WARN Invalid TCPP destination pos TCPP 15 WARN Invalid time into segment TCPP 16 WARN No cfseg data TCPP 17 WARN Modone computation error TCPP 18 WARN Begin Error Mode at line:%d^5 TCPP 19 WARN Speed Ovrd Mode at line:%d^5 TCPP 20 WARN TCPP internal cartseg error TCPP 21 WARN Allocate TCPP/VC memory error TCPP 22 PAUSE.G Invalid delay time specified TCPP 70 PAUSE.G Speed output failed (T_S[%d]) TCPP 71 PAUSE.G Min.speed >= Max.speed (T_S[%d]) TCPP 72 PAUSE.G Invalid index (T_S[%d]) TCPP 73 PAUSE.G Unknown target type TKSP 1 WARN Integer number out of valid range. Illegal integer: %s TKSP 2 WARN Real number out of valid range. Illegal real: %s TKSP 3 WARN Current string is too long. String: %s TKSP 4 WARN Quoted string not terminated before end of line. String: %s TKSP 5 WARN Character not valid without Id following. Character: %s TKSP 6 WARN Invalid constant value: %s TKSP 7 WARN New line must follow "&" (cancel new line) character. Character found: %s TKSP 8 WARN %% unexpected or directive not valid. Directive: %s TKSP 9 WARN Character found is unexpected. Character: %s TKSP 10 WARN Id exceeds %d characters. Id: %s TKSP 11 WARN Not enough memory to allocate %d number of bytes TKSP 12 WARN Syntax error encountered. TKSP 13 WARN Too many syntax errors encountered. TKSP 14 WARN Internal error. Parser stack underflow. TKSP 15 WARN File access failed - file not opened. File: %s TKSP 16 WARN Too many levels of nested %INCLUDE's. Current File: %s TOOL 1 PAUSE.L Tool Change is DISABLED. TOOL 2 PAUSE.L Machine lock is ENABLED. TOOL 3 PAUSE.L Illegal assignment of Tool axis. TOOL 4 PAUSE.L Tool not detached (AXISORDER). TOOL 5 PAUSE.L Tool not detached. TOOL 6 PAUSE.L Tool not attached. TOOL 7 PAUSE.L Another process is executing. TOOL 8 PAUSE.L Tool identify signal is OFF. TOOL 9 PAUSE.L Tool set signal is OFF. TOOL 10 PAUSE.L Tool Change canceled. TOOL 11 PAUSE.L Tool Change timeout. TOOL 12 SYSTEM Tool mastering data is lost. TOOL 13 PAUSE.L Tool mastering is failed. TOOL 14 PAUSE.L TOOL ATTACH is failed. TOOL 15 PAUSE.L TOOL DETACH is failed. TOOL 16 PAUSE.L Robot not mastered(Tool axis). TOOL 17 PAUSE.L Robot not calibrated(Tool axis). TOOL 18 PAUSE.L Ref pos not set(Tool axis). TOOL 19 PAUSE.L Another tool is attached. TOOL 20 PAUSE.L Calibrate motion is failed. TOOL 21 PAUSE.L PR[] index is not set. TOOL 22 PAUSE.L Touch torque is not set. TOOL 23 PAUSE.L Detect signal is not set. TOOL 24 PAUSE.L Tool does not stop. TPIF 1 WARN Mnemonic editor error (%s^1) TPIF 2 WARN Operating system error (%s^1) TPIF 3 WARN Window I/O error (%s^1) TPIF 4 WARN Memory write error TPIF 5 WARN Program is not selected TPIF 6 WARN SELECT is not taught TPIF 7 WARN Robot is not calibrated TPIF 8 WARN Memory protect violation TPIF 9 WARN Cancel delete by application TPIF 10 WARN Cancel enter by application TPIF 11 WARN Item is not found TPIF 12 WARN Kinematics solution is invalid TPIF 13 WARN Other program is running TPIF 14 WARN Teach pendant is disabled TPIF 15 WARN Bad position register index TPIF 16 WARN Memory access failed (%s^1) TPIF 17 WARN Memory read failed TPIF 18 WARN Unspecified index value TPIF 19 WARN This item cannot be replaced TPIF 20 WARN Mnaction search error TPIF 21 WARN Mnteach software error TPIF 23 WARN WJNT and RTCP are not compatible TPIF 30 WARN Program name is NULL TPIF 31 WARN Remove num from start of Program name TPIF 32 WARN Remove space from Program name TPIF 33 WARN Remove comma from Program name TPIF 34 WARN Remove dot from Program name TPIF 35 WARN Remove minus from Program name TPIF 36 WARN Not enough memory TPIF 37 WARN Program must be selected by TP TPIF 38 WARN Invalid char in program name TPIF 40 WARN Label already exists TPIF 41 WARN MNUTOOLNUM number is invalid TPIF 42 WARN MNUFRAMENUM number is invalid TPIF 43 WARN External change is valid TPIF 44 WARN Program is unsuitable for robot TPIF 45 WARN Pallet number is over max TPIF 46 WARN Motion option is over max TPIF 47 WARN Invalid program is selected TPIF 48 WARN Running program is not found TPIF 49 WARN Port number is invalid TPIF 50 WARN Macro does not exist TPIF 51 WARN Program has been selected by PNS TPIF 52 WARN FWD/BWD is disabled TPIF 53 WARN Not editing background program TPIF 54 WARN Could not end editing TPIF 55 WARN Could not recovery original program TPIF 56 WARN This program is used by the CRT TPIF 57 WARN This program is used by the TP TPIF 60 WARN Can't record on cartesian (G:%d) TPIF 61 WARN Group[%s] has not recorded TPIF 62 WARN AND operator was replaced to OR TPIF 63 WARN OR operator was replaced to AND TPIF 64 WARN Too many AND/OR operator(Max.4) TPIF 65 WARN Arithmetic operator was unified to +- or */ TPIF 66 WARN Too many arithmetic operator(Max.5) TPIF 67 WARN Too many arguments (Max.10) TPIF 68 WARN Too many items TPIF 70 WARN Cannot teach the instruction TPIF 71 WARN Cannot change sub type TPIF 72 WARN Cannot change motion group TPIF 90 WARN This program has motion group TPIF 91 WARN PREG access error TPIF 92 WARN Value %d expected %s TPIF 93 WARN USER menu must be selected TPIF 94 WARN USER2 menu must be selected TPIF 95 WARN Execution history table error TPIF 97 WARN Can't display running task's history TPIF 98 WARN %s was not run TPIF 99 WARN This program is being edited TPIF 100 WARN No vacant table space TPIF 101 WARN No such menu TPIF 102 WARN E.STOP is asserted TPIF 103 WARN Dead man is released TPIF 104 WARN Teach Pendant is disabled TPIF 105 WARN Program is not selected TPIF 106 WARN Program is already running TPIF 107 WARN FWD/BWD is disabled TPIF 108 WARN Form error, line %d, item %d TPIF 109 WARN \%v not specified correctly TPIF 110 WARN Screen used by other device TPIF 116 WARN System variable error: %s TPIF 117 WARN Cannot backup to device: %s TPIF 118 WARN File error for %s TPIF 119 WARN File compression failed TPIF 120 WARN Device failure TPIF 121 WARN Invalid copy. Use MOVE key. TPIF 128 WARN Verify logic of pasted line(s) TPIF 129 WARN Group motion inst. is pasted TPIF 131 WARN Please set application mask data TPIF 132 WARN Can't recover this operation TPIF 133 WARN Can't recover this command TPIF 134 PAUSE.G CTRL Upgrade is Armed TPIF 135 SYSTEM CTRL Upgrade is Started TPIF 136 WARN Restore ERR, see FRD:REST_LOG.LS TPIF 137 WARN TP: %s interactive login TPIF 138 WARN TP: %s diagnostic login TPIF 139 WARN TP: %s logged out TPIF 140 WARN Connection limit exceeded TPIF 141 WARN No memory for connection TPIF 142 WARN Menu limit exceeded TPIF 143 WARN Connection error TPIF 145 WARN Configuration change time out TPIF 146 WARN TP firmware version is too new TPIF 147 WARN TP firmware version is too old TPIF 148 WARN No memory for multi-window modes TPIF 149 WARN Must complete operation first TPIF 150 WARN Look mode only, use TP to edit TPIF 151 WARN Pane does not have focus TPIF 152 WARN Read Only Mode Enabled TPIF 153 WARN Edit operation not allowed TPIF 161 WARN Cannot change position ID TPIF 162 WARN Can't enter P-SPS in PAUSED TPIF 163 WARN Can't exit P-SPS in PAUSED TPIF 164 WARN This program has no motion group TPIF 165 WARN Can't resume in P-SPS TRAK 0 WARN Unknown error (TO00) TRAK 1 PAUSE.G Track jnt move not allowed TRAK 2 PAUSE.G Track error allocating data TRAK 3 PAUSE.G Track global variable failure TRAK 4 PAUSE.G Track illegal schedule number TRAK 5 PAUSE.G Track destination gone error TRAK 6 WARN Track destination gone warning TRAK 7 WARN Unsupported function code TRAK 8 WARN Not support semi hot start TRAK 9 PAUSE.G Track cart move not allowed TRAK 10 PAUSE.G Track no line track functn ptr TRAK 11 PAUSE.G Track no CIRC Wrist Joint TRAK 12 PAUSE.G Track no Maintenance Program TRAK 13 PAUSE.G Extreme entry position violation TRAK 14 PAUSE.G Extreme exit position violation TRAN 0 WARN Successful Translation. TRAN 1 WARN Undefined parse syntax error. TRAN 2 WARN "ROUTINE" expected. TRAN 3 WARN Quoted string expected. TRAN 4 WARN Number, Id, or quoted string expected. TRAN 5 WARN Number or Id expected. TRAN 6 WARN Type or Id expected. TRAN 7 WARN Parameter type expected. TRAN 8 WARN Integer, Id, or "*" expected. TRAN 9 WARN "*" expected. TRAN 10 WARN Integer or Id expected. TRAN 11 WARN Id expected. TRAN 12 WARN Invalid statement. ";" or new line expected. TRAN 13 WARN Invalid statement or "ENDxxx" or "UNTIL" expected. TRAN 14 WARN "FILE" or "HAND" expected. TRAN 15 WARN WHEN clause expected in a condition handler definition. TRAN 16 WARN Invalid or missing condition within a condition handler expression. TRAN 17 WARN "EVENT" or "SEMAPHORE" expected. TRAN 18 WARN Local condition handler expected in a MOVE statement. TRAN 19 WARN "CASE" expected within a SELECT statement. TRAN 20 WARN TO, ALONG, NEAR, AXIS, AWAY, RELATIVE, or ABOUT expected. TRAN 21 WARN Id or quoted string expected. TRAN 22 WARN Invalid read item. TRAN 23 WARN Variable expected. TRAN 24 WARN Id or system Id expected. TRAN 25 WARN Invalid or missing expression. TRAN 26 WARN "AFTER" or "BEFORE" expected in a local condition handler. TRAN 27 WARN "DOWNTO" or "TO" expected in the FOR statement. TRAN 28 WARN System Id expected. TRAN 29 WARN Number expected. TRAN 30 WARN "PROGRAM" expected. TRAN 31 WARN "=" expected. TRAN 32 WARN "." expected. TRAN 33 WARN ":" expected. TRAN 34 WARN "[" expected. TRAN 35 WARN "[" or "OF" expected. TRAN 36 WARN "]" expected. TRAN 37 WARN "," or "]" expected. TRAN 38 WARN "," or ")" expected. TRAN 39 WARN "(" expected. TRAN 40 WARN ")" expected. TRAN 41 WARN "," or ":" expected. TRAN 42 WARN ";" or new line expected. TRAN 43 WARN ";", new line, or ")" expected. TRAN 44 WARN "BEGIN" expected. TRAN 45 WARN "BY" expected. TRAN 46 WARN "CONDITION" expected. TRAN 47 WARN "DO" expected. TRAN 48 WARN "ENDSTRUCTURE" expected. TRAN 49 WARN "EVENT" expected. TRAN 50 WARN "FOR" expected. TRAN 51 WARN "GROUP" expected. TRAN 52 WARN "HAND" expected. TRAN 53 WARN "NODE" expected. TRAN 54 WARN "OF" expected. TRAN 55 WARN "THEN" expected. TRAN 56 WARN "TIMER" expected. TRAN 57 WARN "TO" expected. TRAN 58 WARN "," expected. TRAN 59 WARN "ERROR", "COMMAND", or "TPENABLE" expected. TRAN 60 WARN "CMOS" or "DRAM" expected. TRAN 63 WARN Value cannot be negative. TRAN 64 WARN Id is already defined in the current PROGRAM/ROUTINE. Id: %s TRAN 65 WARN Id must be defined before this use. Id: %s TRAN 66 WARN Label used in GO TO statement is never defined. Label: %s TRAN 67 WARN Parameters for routine not needed since already defined. Routine: %s TRAN 68 WARN Number of nested routines or structures exceeded maximum. TRAN 69 WARN Symbol definition table size exceeded. Reduce number of Id names. TRAN 70 WARN Id name on PROGRAM END statement does not match PROGRAM name. Id: %s TRAN 71 WARN Code size exceeded maximum. Break program into separately translated units. TRAN 72 WARN P-code file device full. TRAN 73 WARN Id is undefined, it must be defined before use in a CONST section. Id: %s TRAN 74 WARN Invalid class for Id, CONSTant expected. Id: %s TRAN 75 WARN Id is undefined, it must be defined before use in a TYPE section. Id: %s TRAN 76 WARN Invalid class for Id, TYPE expected. Id: %s TRAN 77 WARN Number of array dimensions exceeded maximum. TRAN 78 WARN Id name on ROUTINE END statement does not match ROUTINE name. Id: %s TRAN 79 WARN Program name may not be the same as any predefined Id. Id: %s TRAN 80 WARN Array dimensions must be specified for this Id. Id: %s TRAN 81 WARN Group number is not in valid range. TRAN 82 WARN PATH data type is not allowed. TRAN 83 WARN PATH, FILE, and vision data types are not allowed. TRAN 84 WARN File cannot be opened or created. File: %s TRAN 85 WARN Number of groups exceeded maximum. TRAN 86 WARN Data type of Id must be FILE. Id: %s TRAN 87 WARN Operator not defined on VECTORS. TRAN 88 WARN No valid operation for this data type combination. TRAN 89 WARN BOOLEAN data type expected. TRAN 90 WARN Statement ROUTINEs don't have return values. Statement Routine: %s TRAN 91 WARN ROUTINE called has less arguments than ROUTINE definition. Routine: %s TRAN 92 WARN Routine calls invalid within CONDITION and MOVE statements. TRAN 93 WARN Invalid class for Id, VARiable expected. Id: %s TRAN 94 WARN PATH assignments are invalid. TRAN 95 WARN Operator expected POSITION data type for left operand. TRAN 96 WARN INTEGER data type expected. TRAN 97 WARN Id is not user accessible or not a valid system Id. Id: %s TRAN 98 WARN Id type is not an ARRAY or indexing exceeded number of dimensions. Id: %s TRAN 99 WARN Id type is not a STRUCTURE. Id: %s TRAN 100 WARN Id type is not a field in a STRUCTURE. Id: %s TRAN 101 WARN Indexing invalid of Id. Id: %s TRAN 102 WARN Id type is not a ROUTINE. Id: %s TRAN 103 WARN ROUTINE has a return value, statement routine expected. Routine: %s TRAN 104 WARN ROUTINE called has more arguments than ROUTINE definition. TRAN 105 WARN Must enclose this "write protected" Id in parenthesis. Id: %s TRAN 106 WARN Invalid class for Id; VARiable, ROUTINE, PORT or CONSTant expected. Id: %s TRAN 107 WARN ROUTINE argument data type does not match the parameter definition. TRAN 108 WARN STRING data type expected. TRAN 109 WARN Data type of Id cannot be loaded by value. Id: %s TRAN 110 WARN Data type of Id cannot be loaded by value. TRAN 111 WARN Types may only be declared at the PROGRAM level. TRAN 112 WARN FROM, IN CMOS, or IN DRAM is only valid at the PROGRAM level. TRAN 113 WARN REAL data type expected. TRAN 114 WARN VECTOR data type expected. TRAN 115 WARN POSITION data type expected. TRAN 116 WARN This system Id is not valid in the MOVE statement WITH clause. Id: %s TRAN 117 WARN Only one group may be specified in this type of move statement. TRAN 118 WARN PATH data type expected. TRAN 119 WARN "WITH" group mask does not match "MOVE" group mask. TRAN 120 WARN Invalid Id, static VAR of type INTEGER expected. Id: %s TRAN 121 WARN Label name was previously used in other context. Id: %s TRAN 122 WARN Invalid class for Id, PORT expected. Id: %s TRAN 123 WARN Id is invalid for PULSE, only valid Id is DOUT. Id: %s TRAN 124 WARN This system Id is not valid in the CONDITION statement WITH clause. Id: %s TRAN 125 WARN Both operands in condition handler relations must have identical types. TRAN 126 WARN Port arrays must be indexed. Port: %s TRAN 127 WARN BOOLEAN, INTEGER, or REAL scalar static VAR expected. Id: %s TRAN 128 WARN In cond expressions, either a "NOT" or a "transition" are legal, not both. TRAN 129 WARN "NOT" is invalid before the Id in a relation condition. Id: %s TRAN 130 WARN "AND" and "OR" cannot both be specified in a condition. TRAN 131 WARN RETURN value expected in this ROUTINE. Routine: %s TRAN 132 WARN FOR statement loop index Id must be an INTEGER. Id: %s TRAN 133 WARN RETURN statement cannot have a return value in the main program. TRAN 134 WARN Expression ROUTINE return type does not match value being returned. TRAN 135 WARN Expected Id to be an INTEGER CONSTant. Id: %s TRAN 136 WARN Cannot READ into port values of any type. Port: %s TRAN 137 WARN Cannot load environment file, program already exists. Name: %s TRAN 138 WARN Not enough memory to allocate %d number of bytes. TRAN 139 WARN Data type of Id is not valid in this context. Id: %s TRAN 140 WARN RETURN statement invalid within USING...ENDUSING statements. TRAN 141 WARN This system Id is "write protected" from KAREL user programs. Id: %s TRAN 142 WARN Data type of Id is incompatible with right hand side. Id: %s TRAN 143 WARN Data cannot be stored into input ports. Port: %s TRAN 144 WARN Cannot convert VAX real number to IEEE format. TRAN 145 WARN READ/WRITE is invalid for this data type. TRAN 146 WARN Operation invalid for this data type. TRAN 147 WARN Operator not defined on INTEGERS. TRAN 148 WARN Operator not defined on REALS. TRAN 149 WARN Operator not defined on BOOLEANS. TRAN 150 WARN Operator not defined on STRINGS. TRAN 151 WARN Operator not defined on POSITIONS. TRAN 152 WARN PATH data type is not allowed; create a user- defined TYPE that is a PATH. TRAN 153 WARN Please move %%DEFGROUP before %%ENVIRONMENT statements. TRAN 154 WARN BYNAME is invalid. Argument expected. TRAN 155 WARN Must enclose this variable in parenthesis to pass by value. Id: %s TRAN 156 WARN Group number of Id does not match group specified. Id: %s TRAN 157 WARN Invalid port type for this operation. Port: %s TRAN 158 WARN Label is already defined in the PROGRAM. Label: %s TRAN 159 WARN More than one group in move statement expected. TRAN 160 WARN POSITION or VECTOR data type expected. TRAN 161 WARN Scalar or indexed array expected, this Id must be indexed. Id: %s TRAN 162 WARN Cannot load environment file, version mismatch. Version: %d TRAN 163 WARN PATH, FILE, and vision data types may only be specified at the PROGRAM level. TRAN 164 WARN "NODE" group mask does not match "MOVE" group mask. TRAN 165 WARN Invalid class for Id, VARiable or CONSTant expected. Id: %s TRAN 166 WARN Routine name was previously used in other context. Id: %s TRAN 167 WARN String size is greater than 128 or less than 1. Size: %d TRAN 168 WARN Path does not have a position node. Id: %s TRAN 169 WARN Path does not have a header. Id: %s TRAN 170 WARN Cannot load environment file, version too new. Version: %d TRAN 171 WARN Cannot load environment file, version too old. Version: %d TRAN 172 WARN Path does not have any node data defined. TRAN 173 WARN Translation cancelled. TRAN 174 WARN Unknown option '%c'. TRAN 175 WARN %cr - Create routine stack file (.RS) for local var access TRAN 176 WARN Label used in GO TO statement is not reachable. Label: %s TRAN 177 WARN Supersedes previous value of %%NOLOCKGROUP or %%LOCKGROUP. TRAN 178 WARN Id is already defined in another environment file. Id: %s TRAN 179 WARN Argument will be passed by value. Id: %s TRAN 180 WARN Internal error. Parser stack underflow. TRAN 181 WARN Internal error. <id> cannot be extracted. TRAN 182 WARN Internal error. Handle = %d, offset = %d TRAN 183 WARN Internal error. Production not reduced. Handle = %d, offset = %d TRAN 184 WARN Internal error. Unimplemented p-code generated. TRAN 185 WARN Internal error. Invalid Id class to generate address. TRAN 186 WARN Internal error. Cannot find routine in symbol table. Routine: %s TRAN 187 WARN Internal error. Value of Id exceeded range. Id: %s TRAN 190 WARN All Rights Reserved. TRAN 191 WARN Press any key to continue... TRAN 192 WARN %32s VARS 1 WARN Corrupt variable file VARS 2 WARN Open Error on File VARS 3 WARN %s array length updated VARS 4 WARN %s memory not updated VARS 5 WARN %s PC array length ignored VARS 6 WARN Unknown Variable Name VARS 7 WARN Unknown Type Code VARS 8 WARN Type Name not found VARS 9 WARN SV Load at CTRL Start Only VARS 10 WARN Variable/field write-protected VARS 11 WARN No data defined for program VARS 12 WARN Create var - %s failed VARS 13 WARN Variable Already Exists VARS 14 WARN Create type - %s failed VARS 15 WARN Too many vars/nodes/programs VARS 16 WARN Axis configuration mismatch VARS 17 WARN Sysvar version mismatch VARS 18 WARN Compatible Type Already Exists VARS 19 WARN Rename target exists VARS 20 WARN [%s]%s not fnd VARS 21 WARN Memory allocation failure VARS 22 WARN Duplicate creation TYPE mismatch VARS 23 WARN Array len creation mismatch VARS 24 WARN Bad variable or register index VARS 25 WARN Vision reference error VARS 26 WARN File sequence error VARS 27 WARN Variable used by other program VARS 28 WARN Value out of range VARS 29 WARN Requires PROGRAM password VARS 30 WARN Requires SETUP password VARS 31 WARN Requires INSTALL password VARS 32 WARN Variable size too big VARS 33 WARN Maximum path length exceeded VARS 34 WARN Variable cannot be accessed VARS 36 WARN CMOS memory is corrupt VARS 37 WARN Position register is locked VARS 38 WARN Cannot change CMOS/DRAM type VARS 39 WARN Data set created VARS 40 WARN Cannot load at CONTROL START 2 VARS 41 WARN Invalid Node Number VARS 42 WARN TEMP type invalid for CMOS create VARS 43 WARN Variable memory pool is invalid VARS 44 WARN Group number mismatch on load VARS 45 WARN Mismatch SV - %s System %s VARS 46 WARN Buffer size mismatch VARS 47 WARN Incompatible var file version VARS 48 WARN Name is too big VARS 49 WARN Bad Element in a Structure VARS 50 WARN PC Revision mismatch %s VARS 51 WARN Illegal operation VARS 52 WARN Variable %s converted VARS 53 WARN Input data pointer invalid VARS 54 WARN Sysvars - %s loaded VARS 55 WARN Program name is not unique VARS 56 SYSTEM All types in use for %s VARS 57 WARN Using %s for save VARS 122 WARN Allocate a larger buffer for the transfer VARS 123 WARN different file VARS 124 WARN to make it shorter. VARS 125 WARN Specify a valid ASCII value. VARS 126 WARN You must do this operation in a different context VARS 127 WARN with the new set of options VARS 128 WARN individual files created WEAV 0 WARN unknown error (WV00) WEAV 1 WARN Weave global variable failure WEAV 2 PAUSE.G Weave motion data missing WEAV 3 PAUSE.G Weave error allocating data WEAV 4 PAUSE.G Weave system variable failure WEAV 5 PAUSE.G Weave pattern does not exist WEAV 6 PAUSE.G Weave illegal schedule number WEAV 7 PAUSE.G Weave illegal frequency value WEAV 8 PAUSE.G Weave illegal amplitude value WEAV 9 PAUSE.G Weave illegal dwell value WEAV 10 WARN Weave too many pre-exec WS WEAV 11 WARN Unsupported function code WEAV 12 WARN Multi-group stop dwell invalid WEAV 13 PAUSE.G Incorrect weaving vectors WEAV 14 PAUSE.G Wrist Joint Limit WEAV 15 PAUSE.G Wrist axes 5 closes to zero WEAV 16 PAUSE.G Unknown wrist configuration error WEAV 17 PAUSE.G Run_ang exceeds tol_ang WEAV 18 PAUSE.G Invalid UTool WEAV 19 WARN WEAV 20 WARN WEAV 21 WARN WEAV 22 WARN WEAV 23 WARN WEAV 24 WARN WEAV 25 WARN WEAV 26 WARN WEAV 27 WARN WEAV 28 WARN WEAV 29 WARN WNDW 1 WARN Invalid screen name format WNDW 2 WARN Invalid window name format WNDW 3 WARN Invalid keybd. name format WNDW 4 WARN Invalid disp dev name format WNDW 5 WARN Bad number of rows WNDW 6 WARN Bad number of cols WNDW 7 WARN Bad row number WNDW 8 WARN Bad col number WNDW 11 WARN Unk. disp dev name WNDW 12 WARN Unk k/b dev name WNDW 13 WARN Duplicate screen name WNDW 14 WARN Duplicate window name WNDW 15 WARN Unknown screen name WNDW 16 WARN Unknown window name WNDW 17 WARN Window already attchd to scrn WNDW 18 WARN Invalid file name string WNDW 19 WARN Write to file w/o window WNDW 20 WARN Bad buffer length on read WNDW 21 WARN Invalid timeout value WNDW 22 WARN Zero term char mask in read WNDW 23 WARN Initial data too long WNDW 24 WARN Attempt to read with no kb WNDW 25 WARN Echo window for read not act WNDW 26 WARN Read for same keys/kbd active WNDW 27 WARN Too many pushes active WNDW 28 WARN Mis-match on push/pop seq WNDW 30 WARN Invalid time WNDW 32 WARN No match on var disp cncl WNDW 33 WARN Field width invalid WNDW 65 WARN window not attached to screen Cause An attempt was made to add or use more equipment than permitted. An arc instruction contained an illegal schedule number. No gas flow was detected during an arc start. The gas fault input was not ON after the gas output was set to OFF. A gas fault input was detected during welding. A wire fault input was detected during welding. A water fault input was detected during welding. A power fault input was detected during welding. A wire stick has occured. A wirestick was detected and wirestick reset was not performed. Wirestick reset may be disabled. Wirestick reset is not done during TIG welding or if welding is stopped by turning weld enable off. A wirestick was detected and the automatic wirestick reset failed to break the wirestick. The arc detect input did not stabilize during an arc start. The weld enable or a wire inch hardkey was pressed with the teach pendant enable switch OFF. The weld enable or a wire inch hardkey was pressed without holding the shift key. A program executing from the teach pendant attempted an Arc Start with welding from the teach pendant disabled. An Arc Start instruction was executed with welding disabled. The arc detect signal was lost during a weld. The arc detect input could not be read. Insufficient memory exists to plan an arc instruction. A program was aborted while welding. The programmed analog output is beyond the equipment limits. The arc instruction register is not an integer type. The equipment min to max range is too small. The binary range data for the A/D or D/A is too small. An analog scaling limit was modified while welding. The scaling was not changed. A wire stick is still detected after a system RESET. Motion has stopped longer than $arc_los_tim while welding. Welding was stopped by entering single step mode after welding began. The speed override is less than 100%. A task which does not have weld control attempted to execute an Arc Start or an Arc End instruction. Only one task is permitted to have weld control. The arc instruction does not have the equipment number This equipment mask is not supported now Another equipment is wire inching now. This program( task ) has already held the another equipment A task can only use a equipment. The named weld analog output signal is not scaled properly. The named weld I/O signal is not detected or configured properly. The weld equipment has been configured to use DeviceNet by setting the fields $VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the system variable $AWEPRR to non-zero values. However, the DeviceNet option is not installed. The weld equipment has been configured to use DeviceNet by setting the fields $VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the system variable $AWEPRR to non-zero values. However, the Explicit Messaging option is not installed. The weld equipment has been configured to use DeviceNet by setting the fields $VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the system variable $AWEPRR to non-zero values. However, DeviceNet hardware was not detected. The weld equipment has been configured to use DeviceNet by setting the fields $VENDOR_ID, $DEV_TYPE, and $PROD_CODE in the system variable $AWEPRR to non-zero values. A DeviceNet device definition could not be found for that product. ArcTool attempted to communicate with the Welding Equipment using the DeviceNet network, but could not because the link was not properly established. There was a communication error detected between ArcTool and the Weld Equipment. An operation was attempted which is not permitted while a weld is executing or paused. Auto AI/O setup for the mounted I/O module is not supported. So parameters are not set automatically. ArcTool failed to switch weld processes. ArcTool failed to find this process on the weld power supply. ArcTool is communicating with the weld power supply. The version number of the power supply is shown. The indicated parameter is out of range. Ramping is not allowed when switching weld processes. Motion has stopped longer than the time specified in weld schedulle and weld setup while welding. Internal error. Application is changed during welding. Imcomplete the analog signal conversion factor. The binary data($AWEPRR.$io_min/max_bin) is invalid. The difference is zero. The conversion factor data is invalid. It must be filled more than 2 tables at least. But the value of the second table is zero. The selected number of AO conversion factor data is over the number of the actual data array In this situation, the welding is disalbled by the following reason 1: In Single step mode 2: In Machine lock mode 3: In Dry run mode 4: No I/O board exist 5: No I/O assignment for welding 6: In Flush AMR status 7: In Application disabled mode 8: In Arc disabled status 9: In Skip welding status 10: In disable status mode by AWDBG The selected wire material is not supported for Servo Torch. The selected wire size is not supported for Servo Torch. The selected unit of inching speed is not supported for Servo Torch. Failed to convert weld schedule to wire feed speed command for Servo Torch. Internal error. Invalid sequence mode command is sent to Servo Torch. Cannot received WSTK signal from serial communication power supply. Configuration of Roboweld was invalid. So data for Robowelds were set inappropriately. RoboWeld internal error. Necessary signals for Simulation mode cannot be detected. Simulation mode is enabled. So actual welding is not performed. I/O signals were not set to sim/unsim appropriately when Simulation mode is. enabled/disabled. Memory size is too small to get memory area for necessary data. Detect invalid signal operation in welding. Detect invalid wire size. Detect invalid welding process. Detect invalid wire material. Arc loss time is invalid range. Communication with RoboWeld power source is timeout. RoboWeld internal error. Receive invalid data from Power Source. Detect 1st currency abnormal. Detect 2nd currency abnormal. Detect temperature abnormal. Detect high voltage. Detect low voltage. Detect start signal abnormal. Detect 3-phase power source abnormal. RoboWeld is detached. Communication with RoboWeld power source stopped in welding. I/O space for RoboWeld is already in use. I/O initialization error. Detect invalid wire FWD/BWD operation. Detect ARC off. Failed to receive unified data. Receive invalid command from power source. Retry to send the command to power source. Receive NAK from power source. Communication with power source is stopped. Sysvar $RBWLD is not setup for new EQ number. RoboWeld reset sequence is complete. Power supply communication error Wire feeder motor speed is over the limited speed. Wire feeder motor sensor line was connected off or wire feeder motor did not rotate correctly. While the motor should stop, the motor rotation was detected. ESTOP signal was input from the external. Exernal1 hold signal was input from the external. Exernal1 hold signal was input from the external. Power supply control memory error Weld power supply CPU error Torch switch was turned ON but the arc could not started within 4sec. The specified weld type has not been supported for this power supply. Changing weld type data now. Please wait for a moment. Complete to change weld type data. So you can do arc welding. The Arclink bus master did not respond to a heartbeat request within the maximum time period. The channel has been reset. A device on the Arclink did not respond to a request within the maximum time period. The channel has been reset. A device on the Arclink sent and unexpected error response to a request message. The channel has been reset. The Arclink bus master has detected an error or other condition that requires the Arclink network to be reset. This may be a normal event if a new device has been plugged into the network. The Arclink reset and initialization sequence is complete. The high speed event message expected during welding failed to arrive in time. The Arclink interface detected too many errors on the CANbus network. This is usually caused by noise or bad connections. The Arclink interface detected too many errors on the CANbus network. This is usually caused by noise or bad connections. The Arclink interface is not detecting any other devices on the CANbus network. The Arclink interface is detecting a high number of errors on the network. This is not fatal right now, but indicates potential problems on the network. The Arclink interface is unable to send messages due to too much traffic on the network. The Arclink interface has detected a fatal error condition and has reset the communications network. Coordinated Motion global variables are not loaded. A failure occurred while allocating memory. Leader segment MMR number does not match that of the follower Illegal Leader Interpolated Point Data is detected when trying to convert it to a transform Coordinated Motion is used for a group which has not been SETUP for coordinated motion. JOINT MOTYPE was used for a follower during coordinated motion. CIRCULAR MOTYPE Not Implemented Yet There is no leader in the coordinated motion There is more than one leader in the coordinated motion Invalid Angle detected in Point Data Error in reporting mailbox status Leader single group motion after coordinated motion not allowed Attempt to perform coordinated jog with a non-leader group Attempt to perform coordinated jog with a leader group which has multiple followers WRIST JOINT Motion is not supported with coordinated motion INCREMENTAL motion is not supported with coordinated motion Independent motion is not supported with coordinated motion Calibration for coordinated motion is not done Number of follower is zero or two or greater on this motion Follower can not reach relative speed in program Attempt to perform coordinated motion with non-kinematics robot Term type before coordinated motion is not Fine or CNT0 Setting of coordinated motion is not correct Teaching points is incorrect or Leader's mechanics is inaccurate System can't convert position properly Illegal transition (nonCD->CD or CD->nonCD) happens. Transition from one CD pair to another happens. But same follower group is used in both CD pair. Speed of TCP or Face Plate exceeded T1 speed limit. The specified directory can not be found. The specified file could not be found. The file already exists and could not be overwritten. A file cannot be copied to itself. The source variable was not a position type when converting between a Cartesian and joint position. The destination variable was not a position type when converting between a Cartesian and joint position. The requested type code doesn't match the passed variable type. An attempt was made to compare two positions that are not the same type. Two positions were compared and found not to be equal. Both arguments to ATAN2 were zero or an internal error occurred when attempting to convert a POSITION to XYZWPR. An attempt was made to divide by zero. The rotational angle is to great. An invalid device or path has been specified. The operation was cancelled because CTRL-C or CTRL-Y was pressed. The directory listing is finished. The destination file name contained both alphanumeric characters and the global character '*'. A time-based motion was specified along with distance before. Continuous Turn global variables are not loaded. This is an internal system error. This is an internal system error. This is an internal system error. The continuous turn axis that was selected is not a valid cont. turn axis, or cn_gear_n1 or cn_gear_n2 have a zero value A failure occured while allocating memory. Internal Continuous Turn error Invalid destination angle during linear motion. Incompatibility with Continuous Turn and other options. Continuous turn axis velocity is too high. cn_turn_no will not be valid because of high rotational speed. Continuous turn is not compatible with independent extended axes The Ind.EV motion option is not allowed. Programmed motion exceeds the speed limits on the continuous turn axis. Speed limit is 180 degrees per ITP time Attempted to end Continuous Rotation with a Relative Motion Specified condition does not exist The specified condition number already exists in the system, and has been superseded by the new condition. The specified condition is already enabled. No change has been made. The specified condition is already disabled. No change has been made. No more conditions are defined for the specified task. Break point has been encountered. Specified condition already exists. Condition was not superseded. May indicate two condition handlers for the same task with the same condition handler. There are too many conditions defined. It took too long to scan them all. The system was not able to setup the message packet to send to the PC. An ADD PC buffer built-in was called with a parameter that is uninitialized. The variable requested in the ADD Byname or Send SysVar routines does not exist. The data could not be copied to the data buffer because the buffer is too small. An ADD PC buffer built-in was called with a parameter that is uninitialized. An event number less that 0 or greater than 255 was used. Only wait flags of 0 or 1 are allowed. The maximum data buffer size supported is 244 bytes. A system error occurred when trying to send the data buffer to the PC. Status message only. A controller task is waiting for an event flag back from the PC. A controller task waited too long for an event flag from the PC. The controller task was aborted. Status message only. The PC set the event flag and the controller task is contining. A system timer cannot be created or set for this controller task. Register operation failed This is just a debug message The MACRO table must have at least 60 elements for the SEND PC MACRO option to be installed properly. Send PC Macro data error. The Send Data PC MACRO was not given any data to send. The wait action parameter must be 0 through 3. An error occurred in the TP program. A dictionary cannot be reloaded if it was loaded into FROM. There is no more permanent memory available in the system to load another dictionary. There are no dictionaries loaded for the specified language. The specified dictionary was not found. The dictionary element was not found. Only five levels of dictionary elements can be nested. The dictionary was never opened. The dictionary element was truncated because the KAREL string array is not large enough to hold all the data. The language list has completed. The dictionary list has completed. Only five dictionaries can be open by one task at one time. Not enough memory exists in TEMP pool on the controller. The dictionary was not loaded. The dictionary file does not exist on the specified device or in the specified directory. The dictionary text incorrectly specifies an element without a $. A reserved word was not recognized in the dictionary text. The dictionary text incorrectly specifies an element without using quotes. A reference to another element is expected. The cursor position is specified incorrectly or the values are outside the limits. A series of digits are expected after the # to specify an ASCII character code. An identifier is expected after the & to specify a reserved word. An unexpected character was found in the dictionary text file. The dictionary is already open by the task. Dictionaries loaded to memory do not need to be opened. Dictionaries loaded to FROM cannot be removed or a dictionary cannot be removed if another task has it opened. Not enough memory exists in TEMP pool on the controller. The dictionary was not loaded. The help dictionary element was not found. The function key dictionary element was not found. The dictionary containing the error message could not be found. The error message was posted to the error log. The dictionary text incorrectly specifies an element number. The dictionary text incorrectly specifies an element name. The dictionary text was specified incorrectly. The dictionary text was not specified in sequence. The dictionary text has a large gap between element numbers. The dictionary text was specified incorrectly. The dictionary text was specified incorrectly. The dictionary compressor expects a file extension. The dictionary compressor did not recognize the file extension. The dictionary compressor expects a file name. The dictionary compressor expects a facility number in the .KL command. An invalid command was specified for this type of dictionary file. The dictionary text was specified incorrectly. The include file could not be created. The form you are trying to compress is currently being displayed. The system device definition file is missing from the system. The application device definition file is missing from the system. There are too many DeviceNet motherboards connected to the robot controller. The specified board has failed to initialize. A system error has occurred. An invalid board index has been specified. An invalid MAC Id has been specified. The specified board is already on-line. The specified board is not on-line. The specified device is already on-line. The specified device is not on-line. The attempted DeviceNet command request has timed out. The specified board has not been initialized. The DeviceNet Interface system has failed. The specified board was not found in the system. The code file required to initialize the board cannot be accessed. The code file required to initialize the board cannot be read. There is a problem with the DeviceNet scanner code file. The board initialization routine has timed out. An error has occurred in the board initialization process. A data mismatch has occurred such that the system cannot find a device assigned for the specified board number and MAC Id. The system cannot find the specified device type in its list of defined device types. The device at the specified board number and MAC Id cannot be brought on-line. The specified board cannot be brought on-line. There is an error in the format of the specified device definition file, on the specified line. There is an error in the format of the specified device definition file, on the specified line. An unknown keyword has been found in the device definition files. The user must turn power off and on to the controller to bring online a newly-added device to a board's device list. An integer value in the device definition files is incorrect. The specified line was not found in a device definition file. The specified line was not found in a device definition file. The specified lines were not found in a device definition file. The specified lines were incorrect in a device definition file. A definition was incorrect in a device definition file. A definition was incorrect in a device definition file. The specified line was not found in a device definition file. The specified line was not found in a device definition file. The specified line was not found in a device definition file. The specified line was not found in a device definition file. The specified line was not found in a device definition file. The DeviceNet motherboard is not plugged into the back plane. The device definition file has too many I/O access modes designated as DEFAULT. Only one mode should be designated as DEFAULT. An problem has occurred with the specified daughter board or the DeviceNet network connected to it. The problem is not severe enough to disrupt communications, but should be addressed as soon as possible. The DeviceNet scanner has detected an abnormal number of communications errors on the network. This message is a warning that the scanner may go offline if errors continue to occur at an abnormal rate. The specified line was incorrect in the device definition file. An extraneous line was found in a device definition file. There is no space left in the DeviceNet I/O buffer. An error has occurred with the specified daughter board or the DeviceNet network connected to it. Power has been removed from the DeviceNet network. A network communications error has occurred on the network connected to the specified board. The board has received more messages than it can handle at one time. The board has missed a message over the DeviceNet network. The traffic on the DeviceNet network is too heavy for the board to communicate with the devices. All of the devices expected by the board to be on the network appear to be disconnected to the network. The board is not communicating to the network because there are too many errors. An error has occurred with the device at the specified board number and MAC Id. An error has occurred when attempting connection to the specified device. The vendor Id for the device, as specified in the device definition, is incorrect. The product code for the device, as specified in the device definition, is incorrect. The device type for the device, as specified in the device definition, is incorrect. The connection to the specified device has timed out. An unknown error has occurred with the specified device. An error has occurred when attempting connection to the specified device. You have two or more DeviceNet daughter boards with the same board number configuration. This cause code is posted together with DNET- 071 above to allow the user to easily identify the duplicate daughter board. Please see the Cause text for DNET-071 for more information. The system could not find the module type corresponding to a module on the specified device. An I/O configuration file (.IO file) containing DeviceNet configuration data was loaded at COLD START. The DeviceNet configuration data in this file is ignored. There is no more room in the Defined Device List system variable. At controlled start, I/O data assigned to DeviceNet devices is not active. The system variable for storage of devices is full. The device type used by this device is currently unknown to the system. The previous I/O configuration contains too many modules, devices, or device definitions to be loaded. This message appears when a board automatically restarts communication with a DeviceNet network, but some or all devices are not designated as autoreconnecting. Pressing RESET will attempt reconnection with these devices. A board which was previously in error state has automatically restarted communications with the DeviceNet network. The command to reset the specified board has failed. The command to reset the specified device has failed. The specified board is unable to acknowledge the stop-scanning command. The board is not acknowledging the command to take it off-line. The system does not recognize the module type of the module being loaded. The data file contains lines which specify both POLL access and STROBE access for the same device. The device definition file specifies a strobed- access device but the number of outputs is not equal to zero. The number of inputs specified in the device definition for this device does not match the number expected by the scanner when it communicates with the device. The number of outputs specified in the device definition for this device does not match the number expected by the scanner when it communicates with the device. The scanner board encountered an error while trying to read the device's vendor ID. The scanner board encountered an error while trying to read the device's device type. The scanner board encountered an error while trying to read the device's product code. The scanner board encountered an error while trying to set the communication packet rate for this device. The board was unable to achieve synchronization in the connection with the specified device. The board's MAC Id is not between 0 and 63. The board's baud rate is not one of: 125 KB, 250 KB, or 500 KB. The specified device has the same MAC Id as another device on the network. There was an attempt to add a device to the board's device list that was a duplicate of a device already on the list. A device expected to be on the network was not found. The board could not perform an operation because the bus was off-line. The board could not perform an operation because the it is actively scanning the network. The board could not perform an operation because the bus is not off-line. The board could not perform an operation because the it is actively scanning the network. The board could not perform an operation because the it is not actively scanning the network. An attempt to bring the board on-line was unsuccessful because the board was busy. The board has detected a fault on the DeviceNet network, and cannot communicate with devices. A device does not support the requested I/O connection(s). and cannot communicate with devices. Ack Fault-No acknowledge received during Duplicate MAC ID sequence. The device at the specified board number and MAC Id cannot be brought on-line. When a device has been added to a scan list, it cannot be brought online without cycling power to the controller. An error has occurred with the device at the specified board number and MAC Id. The command to reset the specified device has failed. This message appears when a board automatically restarts communication with a DeviceNet network, but some or all devices are not designated as autoreconnecting. Pressing RESET will attempt reconnection with these devices. The slave connection of the specified board is idle The remote Master has not yet connected to the slave connection. An invalid parameter has been specified for a DeviceNet KAREL built-in. The specified board number is invalid. The specified MAC ID is invalid. The Delta Tool/Frame global variables have NOT been properly loaded. Delta Tool/Frame system variables (e.g. $DXSCH[]) not found. Invalid Delta Tool/Frame schedule number. Requested Delta Tool/Frame schedule number has already been enabled. Try to disable a schedule which has not been enabled. Try to apply offset to a schedule which has not been enabled. Internal error: cannot find dxfndofs schedule. Wrong packet was sent to INTP to signal completion of updating $DXMOR deltatool or deltaframe offset. Attempt to enable deltajoint with deltatool and/or deltaframe in a schedule. Attempt to enable deltatool with deltaframe in a schedule. The specified motion group has been already enabled by DX function. The calculated offset orientation of this time is out of range specified by $DXRLINK.$ortmax. The calculated offset distance of this time is out of range specified by $DXRLINK.$locmax. UT of master robot is changed. A system error has occurred. A system error has occurred. A system error has occurred. A system error has occurred A system error has occurred. Case: Motion statment of program has not parameter Specified file device is not ready. Device is full. There is no more space to store data on the device. Device is protected. So, you cannot write to the device. Device is not assigned. The specified device is not recognized by the system. If RD then $FILE_MAXSEC is set to 0 Device is not mounted. You should mount the device before using it. You tried to mount the device which had been already mounted. Device name contains an illegal character. Illegal LUN is used. Specified directory does not exist Directory is full. You tried to create a file in the root directory which execeeded the maximum number of files allowed on the device. You tried to write to a write protected directory. Directory name contains an illegal character. The specified file was not found. You tried to access a protected file. You tried to access a file which is not open. You tried to create/delete/rename a file which is already opened. You tried to access a file which is locked. File size is invalid. End of file was detected. File name contains an illegal character. File number is illegal. File type contains an illegal character. File protection code is illegal. File access mode is illegal. File attribute in the SET_ATTRIBUTE request is illegal. Data block is broken which is used in FIND_NEXT request. Illegal request command is specified. Device management table is full. Path name contains an illegal character. Illegal parameter is detected. File management buffer is full. Illegal file position is specified. You tried to access a unformatted device. You tried to rename a file to an already existing file name. You tried to remove a subdirectory which contains some files or directories. There are too many lock requests to same file. You tried to create a sub-directory that already exists. You tried to read from a write only opened file or tried to write to a read only opened file. You tried to unlock file which you had not locked. $FILE_MAXSEC has not been set and must be be set before device can be formatted. A file operation has been attempted on a file which is not a standard file PChamp output device NOT ready or FULL A call to kread was made while a WOULDBLOCK read was pending A call to kread was made following a WOULDBLOCK read with a different buf_p Memory Card (MC) has been inserted and properly detected by the system Memory Card (MC) has been removed from the system Either the Memory Card (MC) is not properly inserted or the Card that is inserted is not a Memory Card type (SRAM or Flashdisk) Modem Card has been inserted and properly detected by the system Modem Card has been removed from the system Name contains an illegal character. The TEMP memory is too low to complete the file operation. Requested Memory Size ($FILE_MAXSEC) exceeds Max Available. RD Left at Actual Size Requested RD Size (Req) exceeds Max Available (Max). RD Left at Actual Size (Ac) Backup file is not correct. The indicated file is not loaded, when all files are restored in Automatic Software Update function Your listing has reached the end of the directory. You do not have to do anything for this warning message. The file name you are trying to create already exists on this device. The file you are trying to open does not exist on this device. Operation is not supported on floppy disk. The disk file capacity has been reached. The end of the file was reached while reading. An attempt was made to open more than one file. The protocol format was invalid. The disk has write protection enabled. The directory information is corrupted and unreadable. The checksum data is bad. Data is corrupted on disk and can not be read. There is a bad sector or track on the disk. The drive did not respond to a command. The disk has write protection enabled. Memory Card hardware error is detected. The Memory Card is not formatted. Force control board doesn't exist. Force controlboard doesn't exist. The error occurred from the force control board. The system cannot cammunicate with the force control board. Force control board has been disabled because of the alarm displayed at the same time. Force board has been disabled because of the alarm displayed at the same time. The program cannot control the specified motion group. The system cannot start force control. The system cannot communicate with the force control board. The tool number is set to 0. As a result of the force sensor diagnosis the error of the force sensor exceeded the tolerance. Force sensor is normal Initial force sensor data already setting up Initial force sensor data is uninitialized Tolerance data is uninitialized The force sensor output data is too large. The force sensor which is specified by sensor index does not exist. An INSERTION instruction was executed before an OFFSET CONDITION instruction. A position register was not taught in the OFFSET PR[] instruction. Force sensor error has occurred. The error occurred from the force control board. The error jump is not done, because label number is 0. Cannot execute instruction because Unused is selected. Initial force sensor data has been set now Another tuning mode is already enabled There is a schedule whose DOF is bigger than executed one Selected default data is not correct The default data still has not been selected Index value is not correct Number of array in selected default data is not correct The force group of program has not been existed in this system The mass data which has been calculated by entering data is out of range The damper data which has been calculated by entering data is out of range The input data is out of minimum range The input data is out of maximum range The setting data has not been set yet Mismatch the number of array data between the source data and default data The force data of selected program is not complete The specified data does not exist Because the ending condition switch is changed, the individual difference exceeds limit. Modified bearing rotation axis or groove direction is set to be the same as insert direction. This is impossible in the present case. Modified bearing rotation axis or groove direction is set to be the same as insert direction. This is impossible in the present case. Cannot set phase match impedance rate because auto impedance tuning is not finished. Modified insert direction is the same as groove direction. For this case, it cannot be realistically. Parent schedule's parent is child : Infinit loop There are two children for retry There are two children for insertion Child for retry can't have child Parameters of customized schedules were synchronized changed Parameters of customized schedules were not synchronized changed Software internal error. Software internal error. Software internal error. Input direction for the search menu is same as the insertion direction. Software internal error. Communication with the sensor board failed. Communication with the sensor board failed. Communication with the sensor board failed. A parity error occurred on the sensor board. A parity error occurred on the sensor board. The data request from the sensor board to the sensor head failed. Software internal error. An output error occurred from the sensor head. An excessive load was put on the sensor head. Cable is cut. The force control board or the R-J3 main control board has failed. Temperature output error occurred in the sensor head. Watchdog error occurred on the sensor board. The temperature measured at the sensor head is too low. The temperature measured at the sensor head is too high. internal error internal error internal error internal error The output data from the sensor head is frozen (unchanging). Communication failed between the sensor head and the sensor board. Error(s) occurred on the sensor board. The differential value of the force during force control is too large. A parity error occurred on the sensor board. A parity error occurred on the sensor board. internal error internal error Communication failed between the sensor board and the force sensor. The axis has approached a singularity point during force control. The robot has approached a singularity due to the positions of J1 and J6 during force control. One or more joint(s) has approached its stroke limit. internal error internal error internal error internal error Software internal error. A servo error occurred. Software internal error. the Force in X direction is too big. the Force in Y direction is too big. the Force in Z direction is too big. the Moment about X direction is too big. the Moment about Y direction is too big. the Moment about Z direction is too big. Software internal error Software internal error Software internal error Software internal error Software internal error Software internal error The robot did not contact the work surface during a required time period. Insertion did not complete during the required time. The orientation change during the insertion exceeded the limit value. Software internal error Software internal error Software internal error The insertion direction acquired by the end condition acquisition is wrong. The insertion length acquired by the end condition acquisition is wrong. The sign of the force command during torque error acquisition is different from the one during force control. Software internal error Software internal error Insertion time exceeded the upper limit during the phase match insertion. software internal error software internal error The object was inserted further than the specified length. Hold or E-stop aborted Contouring. Force control during Contouring. Contouring start. Contouring normal end. Position error during contouring exceeded the limit value Contouring option is not ordered Auto tuning for contouring is impossible parameter setting error Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Robot is not mastered yet. Robot is not mastered yet. Robot is not mastered yet. Software internal error Bad values for the system variables $CCI_GRP.$SJSW[] and/or $CCI_GRP.$SJSE[]. Software internal error Bad values for the system variables $CCS_GRP.$RANGE_F[] and/or $CCS_GRP.$RANGE_T[]. Software internal error Software internal error Software internal error Sensor board initialization failed. Sensor board initialization failed. Sensor board initialization failed. Software internal error Software internal error Software internal error Software internal error Software internal error Retry number of the search exceeded the limit. The robot moved beyond the search range limit before finishing the search. Force or Velocity command of the search direction is wrong. The velocity order for the search function is invalid. Search directions are invalid. 'search range' is smaller than 'Clearance & Chamfer'. 'Search acc. time' or 'Clearance & Chamfer' are zero. The value of Reverse switch is wrong. The values of 'Search frequency', 'Search range' or 'Clearance & Chamfer' are wrong. Software internal error Software internal error Software internal error Software internal error Software internal error Software internal error. Software internal error. Software internal error. Settling rate is out of range. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Vision compensated user frame is wrong. Software internal error. Software internal error. Software internal error. Software internal error. The value of 'Insert Force' is smaller than the lower limit (absolute value 0.5 kgf). Failed to acquire torque error data. Software internal error. Insertion direction acquired by the end condition acquisition is wrong. Display graph data on debug console The value of 'Individual Diff (-)' is Basic Data is less than zero or larger than the value of 'Insert Depth (Design)' in Basic Data. Software internal error. Software internal error. Software internal error. Software internal error. The sign of 'Initial Insert Force' in Performance Data is different from the sign of 'Insert Force'. The value of 'Velocity Adjust Gain' in Performance Data is illegal. The value of 'Starting Rate' in Performance Data is illegal. The value of 'Ending Rate' in Performance Data is illegal. Software internal error. Software internal error. Software internal error. Software internal error. The value of 'Individual Diff. (+)' in Basic Data is illegal. An environmental characteristic in the X direction could not be acquired in the impedance parameters auto tuning. An environmental characteristic in the Y direction could not be acquired in the impedance parameters auto tuning. An environmental characteristic in the Z direction could not be acquired in the impedance parameters auto tuning. An environmental characteristic in the W direction could not be acquired in the impedance parameters auto tuning. An environmental characteristic in the P direction could not be acquired in the impedance parameters auto tuning. An environmental characteristic in the R direction could not be acquired in the impedance parameters auto tuning. The force in the X direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. The force in the Y direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. The force in the Z direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. The force in the W direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. The force in the P direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. The force in the R direction became excessive while acquiring an environmental characteristic in the impedance parameters auto tuning. Force control is disabled in all directions during the impedance parameters auto tuning. Impedance parameters auto tuning in the X direction did not complete. Impedance parameters auto tuning in the Y direction did not complete. Impedance parameters auto tuning in the Z direction did not complete. Impedance parameters auto tuning in the W direction did not complete. Impedance parameters auto tuning in the P direction did not complete. Impedance parameters auto tuning in the R direction did not complete. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. Software internal error. The rotation angle exceeded the upper limit during the phase match insertion. Software internal error. Force exceeded the limit during clutch ins. tried to make auto tuning for clutch ins. Not customized force control were continuously executed Previous executed force control was not parent force control Final position of parent and initial position of child are different Parent finished with error Child is for insetion Software internal error. Software internal error. Software internal error. The FROM disk does not have enough available memory to perform the specified command. The device is not formatted. An invalid parameter is detected. Copying a file to the FROM disk requires that the RAM disk be mounted with enough memory available to temporarily contain the file. The device is not mounted. The device is already mounted. The specified device is not valid. The specified file already exists. The maximum number of files is already open. THerefore the requested command cannot be performed An invalid file position is specified. The position is beyond the end of the file or a negative position. No more files are allowed on the device. The requested command cannot be performed because the file is not opened with the proper access mode. This error is also caused by trying to update or append to an existing file on the FROM disk or to an existing compressed file on the RAM disk. Update and append are only allowed with uncompressed files on the RAM disk. The file cannot be created on the device because not enough consecutive blocks are available. The specified file is not found. The file name contains an invalid character or is blank. The file type contains an invalid character. The file is not open. The requested command cannot be performed because the file is already opened. The specified command is not supported for the device. The RAM disk does not have enough available memory to perform the specified command. Note that copying a file to the FROM disk requires that the RAM disk be mounted with enough memory available to temporarily contain the file. The end of the file is detected. The file identification number has reached the maximum number for the device. No blocks were purged for one of the following reasons: 1) No garbage blocks exist. 2) No spare blocks exist because the FROM disk is full. You are not allowed to purge the FROM disk because purge is disabled. One or more files on the FROM disk are corrupted. This may occur if the FROM is wearing out. The FROM disk is wearing out. Your listing has reached the end of the directory. You do not have to do anything for this warning message. The file name you are trying to create or copy to already exists on this device. The file you are trying to open or copy does not exist on this device. The requested operation is not supported. The disk file capacity has been reached. The end of the file was reached while reading. An attempt was made to open more than one file. The protocol format was invalid. The directory information is corrupted and unreadable. The checksum data is bad. Data is corrupted on the disk and can not be read. There is a bad sector or track on the disk. The drive did not respond to a command. The disk has write protection enabled. Protocol Entry structure ($PROTOENT) is invalid. It should be reset to default values. Server Entry structure ($SERVENT) is invalid. It should be reset to default values. Internet Address needs to be set. Host Name needs to be set. The Remote Node Name needs to be set. ER-1 or ER-2 Ethernet hardware is already running and can not be restarted without cycling power. The TCP/IP Stack has encountered a situation that may result in corruption or disruption in normal network activity. The Ethernet address needs to be set. The Ethernet Board firmware is not loaded. The Ethernet Board needs to be reinitialized. Data received from external device is invalid. Most likely caused by electrical noise on receivers. A buffer was passed to the Serial Port Driver which can not be accessed. The Host Comm system can not execute the requested command in the present operating mode. The Host Comm system can not allocate memory buffers for receiving or transmitting messages The Host Comm system is receiving messages but can not decode them. The Host Comm system is receiving checksum errors on all messages. There has not been any network activity on the Comm Tag for a period specified by Inactivity Timeout. The Comm Tag has been stopped as a result. The remote device is connected but is not responding to requests. The remote device indicates the operation was successfully terminated. The remote device did not indicate operation was terminated. The Host Comm Protocol does not support the requested function. The remote device is connected but it is not online. The Host Comm Protocol could not be started (Mounted) or stopped (dismounted) on the selected comm tag. The Host Comm Protocol could not establish communication with the remote device. Possible software mismatch. The selected hardware port defined for the Comm Tag could not be closed. The Comm Tag either does not have a protocol defined or if required does not have a port assigned. An attempt has been made either to read a file opened for write access only or to write a file opened for read access only. A bad address has been detected. The selected protocol requires a device port. Either the Comm Tag is STARTED or it is presently in use. The passed Device Type is not a Comm Tag type (Cx or Sx). The system does not support selected protocol. The System has run out of buffers to communicate with the Ethernet Remote PCB. An error occurred in the networking software. The Comm Tag does not have a valid username and password. An error occurred in the networking software. The Comm Tag does not have a remote host defined. The Ethernet PCB isn't initialized properly. Invalid buffer size in call Attempt to write before read. Error in Explicit Messsaging Task. Attempt to read before write. Explicit Messaging Connection broken Invalid Channel specified. Channel may not be online. Invalid Path Specified. Invalid Name specified. Connection Buffer size small. Domain Name Does Not exist Problem with DNS server. DNS Recovery Error . Server has no IP address listed. DNS is not properly configured No router name has been defined. The router name has been set to the robot name. Router does not have an address listed in the local host table. The router address will be set to the robot address. Internal software problem. Network memory service request occurs before any memory is not created. Timeout occured at getting memory access right. Internal software problem. Specified network memory buffer descriptor was not correct. Internal software problem. Network memory update request issued to automatic acknowledge transmit memory. Internal software problem. Specified buffer descriptor is not for transmit buffer. Internal software problem. Specified buffer descriptor is not for receive buffer. UDP open for datagram sending was failed. UDP open for datagram receiving was failed. invalid port/insufficient memory invalid port/insufficient memory invalid port/insufficient memory invalid port/insufficient memory invalid port/insufficient memory login made to a device using telnet logout made out of device using telnet TELNET connection attempt rejected. Please look at cause code for further information the device is already connected invalid login id supplied invalid password supplied the inactivity timer for the device expired the FSAC security feature is enabled and the client PC doesn't have sufficient privileges Insufficent access level valid port not configured for device connection from remote host detected The host name in the Client tag is not set correctly. If DNS is enabled, DNS server did not resolve the name. A request to mount a tag which was already mounted was received. The system variable $server_port in the Client tag or the host tag was invalid. The requested tag is not mounted The requested tag is not yet connected to the remote host/device The connection was aborted by remote host Connection was timed out by remote. Write buffer is full. The remote host may not be responding or the network is down. Write direction was shutdown by remote. Read direction was shutdown by remote. Remote host has not yet connected. The requested tag is in use. A request was received for a socket which is invalid A socket error was returned by the tcpip library. A diagnostic TP session was connected in interactive mode. Input is allowed. A diagnostic TP session was connected in monitor mode. Input is not allowed. A diagnostic TP session was disconnected. connection from remote browser detected response from DHCP server detected response from DHCP server detected no response from DHCP server DHCP server returned an IP address which is already in use Lease time expired and the robot could not renew the lease the ethernet interface was shut down this may be part of normal protocol operation this may be normal protocol operation Robot tried to renew IP address, but the renew attempt failed Initializing the DHCP operation DHCP operation in progress DHCP operation failed DHCP operation succeeded DHCP operation disabled FTP servers were not automatically started on loading option No free server tags found to start FTP servers An error occurred in the Ethernet networking software (TCP/IP). Either the file or the Comm Tag could not be found An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). The Comm Tag either does not have a protocol defined or if required does not have a port assigned An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). The file number passed does not match with any open files. An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). Access Ethernet socket table permission denied. A bad address has been detected The selected protocol requires a device port Either the Comm Tag is STARTED or it's presently in use An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). The passed Device Type is not a Comm Tag type (Cx or Sx) An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). System does not support selected protocol. An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). An error occurred in the Ethernet networking software (TCP/IP). Device is already in use Device does not support command Device in use Device is already allocated Device does not support attaching Device limit reached Device not available File Header indicates more data than found in file. System internal error Slave PCB is not installed Slave baoard is defective. Slave data exchange is stopped. Slave detects watch dog error. Can not find the group which is specified by IBS CAHNGE. Can not change the INTERBUS-S configuration by IBS CAHNGE. The slave length code setting is invalid. The offset or byte number of slave configuration is invalid. System internal error System internal error Slave PCB is not installed Slave baoard is defective. Slave data exchange is stopped. System internal error System internal error System internal error System internal error An error has occurred with the specified slave device. System internal error System internal error System internal error Transmission Quality Down System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error System internal error Slave detects watch dog error. System internal error System internal error System internal error BIT LENGTH is set with BYTE LENGTH Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Motion control for the specified group cannot be locked. Internal system error. Internal system error. The ATTACH statement requires the teach pendant to be disabled. Motion control cannot be released. Internal system error. Internal system error. Program data is corrupted. An error occurred while the program was running. Single step cannot be executed Program cannot be started. Program cannot be resumed. An error occurred when program execution was held. An error occurred when program execution was aborted. Backward motion cannot be executed. The specified task attribute is not found or is not read accessible. The currently executing line cannot be changed. The interrupt routine cannot be executed. An error occurred when motion was stopped. An error occurred when motion was canceled. An error occurred when motion was resumed. An error occurred when motion was held. An error occurred when motion was unheld. An error occurred trying to obtain the execution history. An error occurred trying to obtain the trace data. An error occurred trying to continue program execution. An error occurred trying to obtain motion information for the RELEASE statement. An error occurred during process motion. An error occurred during process application. The specified interrupt routine is not a valid type. The conversion of one position type to another failed. The vision built-in failed to return. Power failure was detected. Pos register is locked. Try to lock motion group even though this program cannot use motion group Failed to recover execution status. Too many stop data is created at one time. The specified motion groups are already unlocked. Some specified motion groups are already unlocked. The automatic start was done the defined times but the alarm was not fixed. And the automatic start count of auto error recovery function is over the defined maximum count. The error recovery DO status is OFF in the automatic start feature So the resume program cannot be exeucted automatically. $PAUSE_PROG should specify a program that has NO motion group. The program which is specified by $PAUSE_PROG doesn't exist. The program which is specified by $RESUME_PROG doesn't exist. An error occurred trying to access the local variable(s). The teach pendant program instruction is not available. The instruction is not taught. Instruction syntax error. The variable type is not correct. The index value is invalid. Analog I/O is not functioning properly. Digital I/O is not functioning properly. Group I/O is not functioning properly. Division by 0 was executed. A CASE instruction was executed before a SELECT instruction. The program timer cannot be started. The program timer cannot be stopped. The indicated value cannot be used for the OVERRIDE instruction. A user alarm occurred. The position register or frame setup instructions were executed in a program without a motion group. The position data is invalid. The indicated value is invalid for the motion group number. The SKIP instruction was executed before a SKIP CONDITION instruction. The SKIP instruction or SKIP CONDITION instruction cannot be executed. The PAUSE instruction cannot be executed. The ABORT instruction cannot be executed. The application instruction cannot be executed. The program CALL instruction cannot be executed. The WAIT instruction cannot be executed. The BRANCH instruction cannot be executed. The MOTION instruction cannot be executed. The position register cannot be read. The position register cannot be written. The register cannot be read. The register cannot be written. A condition WAIT instruction cannot be executed. The next line cannot be read. The frame number is invalid. The specified frame cannot be read. The specified frame cannot be written. The position variable cannot be read. The position variable cannot be written. Backward execution cannot be executed any more because the current program line is at the top. Backward execution was completed. This instruction cannot be executed backwards. The specified data type in the PARAMETER instruction is invalid for the parameter type. This type of parameter cannot be used. An OFFSET instruction was executed before an OFFSET CONDITION instruction. A position register was not taught in the OFFSET PR[] instruction. This program has no motion group defined. The MOTION instruction cannot be executed. The input line number is incorrect. The RECEIVE R[] instruction cannot be executed. The SEMAPHORE instruction cannot be executed. Pre-execution system of motion or application has some trouble and system pauses the program execution for safety. The MACRO instruction cannot be executed. The MACRO setup was invalid. The user frame number is invalid. The tool frame number is invalid. The user frame number in the positional data is not the same as the currently selected user frame number. The tool frame number in the positional data is not the same as the currently selected tool frame number. The specified parameter name cannot be found. The CAL_MATRIX instruction cannot be executed. The origin 3 points or destination 3 points are not taught. The wait time value is negative or exceeds the maximum value of 2147483.647 sec. The weld is not functioning properly. The data type of the position register was taught using joint type. Invalid torque value. A subscript is missing from a TPE PARAMETER statement that specifies an array. A field name is required in a PARAMETER statement that specifies a structure. The register type is not valid. The indicated value cannot be used for the AF instruction. A MOVE statement was executed in an interrupt routine while a motion in the interrupted program was still in progress. Specified program is already running This startment can exist in one in each line Skip startment can exist in one in each line During backward execution, a move is encountered that has a different group number from the previous motion statement. Torque limit value exceeds maximum value. Torque limit value was modified to the maximum value. This operator is not supported. The number of the condition exceeds the maximum number. This monitor statement cannot be executed. The sub type of specified ch program cannot be used. The motion option instructions (SKIP, TIME BEFORE/AFTER, and application instruction) cannot be taught together The EPT index in macro table doesn't point the program name defined in macro table. That is, the EPT index in macro table is incorrect. The DI monitor alarm for auto error recovery function occurs. The application instruction was executed. But this application instruction doesn't match to the application process data of this program. The application data of called program is different from that of the original program. This program doesn't have the application data Stack over flow to record the fast fault recovery nesting data The point for the fast fault recover cannot detected The fast entry cannot be performed in the karel program. MAINT program is not defined in fast fault recovery. It failed to execute MAINT program The parameter designated by AR register does not exist. When fast fault is enabled, the program was paused at the part of program change During fast fault recovery sequence, any alarm occurs. So the fast fault recovery position is not saved. The parameter designated by AR register does not exist. But this error does not occur at present. More than 6 motion statements with Distance Before are mixed Distance Before condition was not established. The parameter designed in CALL/MACRO instruction is not correct. This error is internal error. Distance Before condition was not established. Distance Before doesn't work if $SCR_GRP[ ].$M_POS_ENB is FALSE. Motion completed before trigger of DB condition. KAREL program error. This KAREL statement cannot be executed. KAREL program error. Execution entered into a FOR loop by the GOTO statement. The program stack overflowed. Too many local variables were declared or too many routines were called. KAREL program error. The specified value exceeds the maximum limit. KAREL program error. The dimensions of the arrays are not the same. KAREL program error. A condition handler error occurred. KAREL program error. The ATTACH statement failed. KAREL program error. The DETACH statement failed. KAREL program error. The CASE statement does not match any branches. KAREL program error. The specified parameter cannot be used in the with clause of the condition handler. KAREL program error. The index of the array is invalid. KAREL program error. Untaught or uninitialized data was used. KAREL program error. The wrong axis number was used. KAREL program error. The MOTION statement cannot be executed. KAREL program error. Execution cannot be returned from the routine. KAREL program error. A built-in routine error occurred KAREL program error. The routine cannot be called. KAREL program error. The specified condition was invalid. KAREL program error. The specified action was invalid. KAREL program error. The data type was invalid. KAREL program error. The built-in routine is not defined. KAREL program error. The END statement was executed in a function routine instead of a RETURN statement. KAREL program error. The argument value of a built-in routine was wrong. KAREL program error. The data value for the variable was too large. KAREL program error. The usage string in the OPEN FILE statement was invalid. KAREL program error. The file string in the OPEN FILE statement was invalid. KAREL program error. The FILE variable is already being used. KAREL program error. The file could not be opened. KAREL program error. The specified file was not opened before operation. KAREL program error. The value cannot be written to the variable. KAREL program error. Writing to the file failed. KAREL program error. Reading the variable failed. KAREL program error. Data read from the file is too short. KAREL program error. The string read from the file is wrong. KAREL program error. Reading from the file failed. KAREL program error. A file pre-defined by the system cannot be opened. KAREL program error. A file pre-defined by the system cannot be closed. KAREL program error. This routine cannot be used. KAREL program error. Closing the file failed. KAREL program error. The program name is invalid. KAREL program error. The variable name is invalid. KAREL program error. The variable cannot be found. KAREL program error. The data type defined by the BYNAME function and the variable type are mismatched. KAREL program error. Too many variables are passed using the BYNAME function. KAREL program error. The buffer to read ahead from the device overflowed. KAREL program error. The PAUSE statement cannot be executed. KAREL program error. The ABORT statement cannot be executed. KAREL program error. The digital input signal cannot be input. KAREL program error. The digital output signal cannot be output. KAREL program error. The HOLD statement cannot be executed. KAREL program error. The UNHOLD statement cannot be executed. KAREL program error. The STOP statement cannot be executed. KAREL program error. The CANCEL statement cannot be executed. KAREL program error. The RESUME statement cannot be executed. KAREL program error. The break point function cannot be executed. KAREL program error. The AMR operated by the RETURN_AMR built- in routine was not found. KAREL program error. The RETURN_AMR built-in routine cannot be used for an unoperated AMR. KAREL program error. The execution of the WAIT_AMR built-in routine was cancelled. KAREL program error. The READ statement timed out. KAREL program error. Another READ statement was executed while a READ statement was waiting for input. KAREL program error. The vector value was invalid. KAREL program error. The X-axis direction cannot be calculated in the FRAME built-in routine because P1 and P2 are the same point. KAREL program error. The X-Y plane cannot be calculated in the FRAME built-in routine because P1 and P3 are the same point. KAREL program error. The X-Y plane cannot be calculated in the FRAME built-in routine because P3 is located in the X-axis direction. KAREL program error. The target string was too short. KAREL program error. A FILE pre-defined by the system is not opened. KAREL program error. The last file operation failed. KAREL program error. I/O mode operates only from binary to hexdecimal. KAREL program error. The specified program cannot be used. KAREL program error. The WAIT_AMR built-in routine timed out. KAREL program error. The vision CPU board is not plugged in. KAREL program error. The operation overflowed in the vision built-in routine. KAREL program error. The vision built-in routine is not defined. KAREL program error. The parameter to the vision built-in routine is invalid. KAREL program error. The return value from the vision built-in routine is invalid. KAREL program error. System variables cannot be passed using the BYNAME function. A MOVE statement was executed in an interrupt routine while a motion in the interrupted program was still in progress. This local condition can't be recovered. Local variable or parameter is used for the condition. An invalid condition handler number was used in a condition handler definition, or an ENABLE, DISABLE, or PURGE statement or action A invalid program number has been specified in an ABORT PROGRAM, PAUSE PROGRAM, or CONTINUE PROGRAM condition or action. An invalid delay time has been specified in DELAY statement. An invalid value has been specified in bit field The specified path node is out of range. Too many motions are executed at the same time. Paused motion exists after the motion was resumed. OFIX is not available. Single step mode is enable. Stitch enable signal is off. Equipment conditon signal is abnormal Setting of Stitch speed is illegal. Please check motion type The motion statement is JOINT motion. Another program is in stitch mode. System is in T1 mode. To do Dry Run, the program must have all motion groups. Dry Run is activated on incremenatal motion statement. Dry Run can not start from incremental motion statement. Dry Run is activated on circular motion statement. Dry Run can not start from circular motion statement. This is used for cause code of INTP-433 to recommend to do backward eecution. Error occurred in Dry Run execution The item specified in left side of assignment statement is not available for output. Depth of Marker nesting is greater than 10. The marker that Any expression is not defined is read. Multiple tasks execute the same Marker at the same time. Program is paused by TC_ONLINE, because the result of the defined expression is FALSE. The setting of Background Logic can not be changed when the Background Logic is running. The Background Logic that was running at power down was changed before this COLD start. This Background Logic is stopped. There is the operator of data that can not be used in Mixed Logic. Mixed Logic means the expresstion that has parentheses. There is that operator or data that can not be used in Fast mode Backgound Logic. Fast Mode Background Logic can have only I/O ports and logical operators. There is the indirection of index, (ex. DI[R[1]]), in Fast mode Background Logic Fast mode Background Logic can not use indirection. The parentheses nesting is too deep. The maxmum number of nesting is 11. The combination of parentheses is wrong. Total size of Fast mode programs is greater than 4000 step. 4000 steps is approx. 4000 operands. There is recursive regerence of Marker. Master/Slave/SlaveAlone program cannot call KAREL program Program type is different between caller program and called program. Master program does not have the same motion group which is specified by the link pattern of robot link data. Slave program does not have the same motion group which is specified by the slave group of robot link data. Current tool frame number of master robot is different from the master tool No of robot link data of the slave program. Since robot is still moving, it is impossible to synchronize. The motion statement of slave program is JOINT motion. The position data of slave program is JOINT type. Master program is executed by TP. The motion group of specified program becomes to be master. The motion group of specified program becomes to be slave. Tracking of slave program is failed. Robot link calibration has not been done yet. The slave program cannot use Incremental instruction. The slave program cannot use Offset instruction. Synchronize of Master is falid for BWD. BWD of Slave program is not supported. Current status of the robot is Master(Manual). Current status of the robot is Slave(Manual). The synchro ID of the specified program is zero. The program whose synchro ID is different from current synchro ID is executed. Slave program cannot use single step execution. BWD is failed. Slave program cannot be executed directly. This motion group is not specified as master in SETUP. HOSTNAME, IP Address or group number about MASTER is not correct. HOSTNAME, IP Address or group number about SLAVE is not correct. Synchronization ID in program is invalid. Link Pattern Number in program is invalid. Master Number in program is invalid. Specified group number about MASTER is invalid. Specified group number about SLAVE is invalid. Specified SLAVE is not calibrated. No valid SLAVE is specified in Link Pattern data. At comm-buffer init, comm-processor is too busy. Hostname or IP Address, Group number setup is invalid. Timeout for Robot Link start Robot link communication stopped Detect Master HELD input signal Detect slave HELD input signal PS statement is not available for this system. Number of PS motion reached to limit. Number of PS item per one motion reached to limit. PS logic statement is not valid. PS time is not available for this motion type. Untriggered PS logic exists. PS system error. Failed to get current TCP. PS item which caused error still exists at paused status. PS item triggered immediately after motion start. PS item triggered immediately after motion start. PS item was not triggred. PS item was not triggred. Paused PS item was canceled at resume by BWD, single step or cursor change. PS time value is too large against distance value. Distance Before for this line was deleted. Distance Before for this line was deleted. Internal error. File format for IBGN is not correct. IBGN file cannot open. During IBGN recording, remote tcp motion and usual motion cannot used together No motion statement executed before RECORD start[ ] instruction ITP time in ASCII file is not same as this system. ITP time in ASCII file is not same as this system. Program can not be restarted because Constant Joint Path is disabled. Program is paused. Recording is stopped. RECORD start instruction doesn't work in single step mode There is no poin data in buffer. Program can not be executed by BWD Buffer for recording is full. Record stopped here. Program call or return from program occurred during recording. Tool changed during recording. User frame changed during recording. Jmp label occured during recording. Illegal speed unit for IBGN record. Buffer for executing is full. Teaching of IBGN instruction is not correct. File transfer by FTP protocol failed. When BWD execution is paused, FWD execution cannot be done until BWD execution finish. Index of IBGN REC END[ ] is different from IBGN REC START[ ]. Record of the 1st index was in progress when end instruction of the 2nd index was executed IBGN file cannot read because previous IBGN command does not finish. IBGN record file is being copied. Someone is updating IBGN file. Now IBGN file cannot be saved. Someone is saving IBGN file. Now IBGN file cannot be updated. IBGN START[ ] instruction is using one of IBGN file. Now IBGN file cannot be updated. There is no successful record data of specified index. Now anothre IBGN RECORD instruction is recording. Record file of Specified index isn't available now. Robot doesn't have record data of specified index. SENSPS file or IBGN file contains a line that has more than 255 characters. A robot overtravel has occurred Robot has not been calirated Other program has motion control You cannot do more than one rotational jog at a time The system call to clear hold flag failed. error No extended axis exist in this group with which to jog. The SHIFT key is not pressed Teach pendant is not enable The DEADMAN switch is not pressed The jog key was pressed before the shift key was pressed The selected tool frame changed while jogging The manual brake enabled Robot axis reaches its specified stroke limit Robot reaches its vertical fixture position Robot reaches its horizontal fixture position Follow-up time is over when softfloat is ON Robot reaches its R-Theta posture position Robot is not at R-Theta posture position PATH JOG has selected, but robot is not currently on a taught path, or tool Z direction is same teaching path, so Y direction can not be determined. Can not PATH JOG Use of multiple jog keys is not supported in PATH JOG PATH jog is disabled in JOINT path PATH jog is available only in PAUSE status This key is invalid at current jog mode J4 angle is not zero. J4 angle is zero. J4 joint jog is disabled. This direction is reverse direction from J4 = 0. Stroke limit with this TCP configuration. OFIX jog internal error. OFIX jog is not available. (1) The wrong port is set to the port you want to use. (2) The device may be out of order. Only able to process teach pendant programs. A when loading .TP file, invalid data was found. This may occur if a .TP file has become corrupted or if some other type of file e.g., a .PE file, has been copied or renamed to a .TP file. The program that is being loaded already exists in the system. Failure when writing data to the floppy. Failure when reading data from the floppy. The data you are trying to save to a file is either abnormal or broken, therefore the file cannot be loaded. When printing the program, there was an illegal position that did not match the group mask of the program. The file name and the program name are not the same. Their names must match. The daughter program name is not matched with the parent program name. The loading of the daughter program is failed The save/load/print operation cannnot be processed to daughter program directly. The specified file already exists in the floppy. The specified file does not exist in the floppy. The floppy disk has reached its limit and is full. An attempt was made to open more than one file. It could not access the disk. The disk has write protection. Could not access the device. Laser processing is executing by the other program task. This program doesn't have LE. This R-J system doesn't have laser tool. The revolution of the vein is lower. Mapping of assist gas signals is not correct. LE is executed without LP or LS. The other motion group is executing laser processing This R-J system doesn't have this EQ number. It is not possible to execute the program in RFHV. It is not possible to turn on High voltage switch while a program is executed. The number of EQ was changed. The kind of laser board was changed. The signal from assist gas equipment is OFF. The assist gas select value is 0. The assist gas select value is not correct. The shutter was not opend. The shutter was not closed. The index number of laser instruction is not correct. It is impossible to execute a joint motion while laser is processing. In the case that while laser processing is paused the robot is jogged, it is impossible to resume this program. The cabinet temparature is over heat. The laser oscillator is not ready. The chiller is not ready. The water volume of chiller is lower. The purge gas pressure is lower. The root blower temparature is over heat. Water leak or Over humidity is lower. The absober temparature is over heat. The laser gas leaks. The arrival to the destination pressure is too late. The voltage of the Lamp is lower. Overheat at the connection part of fiber. Window may be dirty. Or the fiber may not be connected. The safety interlock is enable. When the oscillator is not in PURGE, it is impossible to turn off R-J. Because servo off alarm of ROBOT happens, the oscillator becomes to LRDY. There are some undischarging lamps. The selection of tube is not correct. The shutter temparature is over heat. The external mirror is abnormal. RDI7 is broken. Hight sensor is ubnormal. Emergency stop is pressed The power supply system 1 is abnormal. The power supply system 2 is abnormal. The power supply system 3 is abnormal. The power supply system 4 is abnormal. The power supply system 5 is abnormal. The power supply system 6 is abnormal. The power supply system 7 is abnormal. The power supply system 8 is abnormal. The power supply system 9 is abnormal. The power supply system 10 is abnormal. The power supply system 11 is abnormal. The power supply system 12 is abnormal. The power supply system 13 is abnormal. The power supply system 14 is abnormal. The power supply system 15 is abnormal. The power supply system 16 is abnormal. The recovery of power faile is executed. The shutter is mecanically locked on operator pannel. The adjustment beam is active. The status of laser oscillator changes from LSTR to RFHV due to some alarm. The shutter is locked by the external signal. The beam is locked by the external signal. Warning of a power calibration. coefficient. The inverter 1 is abnormal. The inverter 2 is abnormal. The gress of turbo 1 is lack. The gress of turbo 2 is lack. The current of turbo 1 is abnormal. The current of turbo 2 is abnormal. The temparature of turbo 1 is over heat. The temparature of turbo 2 is over heat. The revolution of turbo 1 is abnormal. The revolution of turbo 2 is abnormal. The arrival signal of turbo 1 is not arrived. The arrival signal of turbo 2 is not arrived. The AD1 convesion is failed. The AD2 convesion is failed. The laser outout power is lower. The laser gas pressure is not appropriate. The laser gas pressure is negative. The voltage of the lamp is lower. The set power is over table's power. The beam reflection is abnormal. The laser process is not ready. No.1 Fiber is damaged. No.2 Fiber is damaged. No.3 Fiber is damaged. No.4 Fiber is damaged. Purity of water is inferior Lamp voltage is over. Span of shutter open is too long. Laser door is opend A little time is required until SIMMER ON is available after the achievement of LRDY. Power calibration was tried again in the power caliburation. Power calibration was tried while the program was running. Power calibration was tried in the alarm status. Power calibration was tried when the teachpendant is enabled. Power calibration was tried when the hardware shutter lock is unlocked. Power calibratin was tried unless LSTR condition. Power calibration was tried when $LASERSETUP$PWR_CALIB is NOT 1. Power calibration was halted manually from the teachpendant etc. Power calibration was halted from the external signal. The required condition for power calibration became not to be satisfied during the power calibration. The program was started in the power calibration status. Because Shutter is out of order, shutter state would not become ON nor OFF Shutter state signal is abnormal. When the FENCE is open, the Shutter gets open The conditions for assigning macros are not correct. It is not possible to assign a program with MOTION lock group to the User Key(UK) button. It is not possible to execute a program with MOTION lock group with the User Key(UK) button. It is not possible to execute a program when the teach pendant is disabled. It is not possible to execute a program when the teach pendant is enabled. The macro assign type already exists. This assign type is only enabled at REMOTE condition. This assign index is out of range. This SOP buttom is not enabled for macro execution. This UOP signal is not enabled for macro execution. The number of RI+DI is over the maximum number. You can assign RI and DI to macro assign type, but the total number of assignments possible is restricted by the system variable $MACROMAXDRI. $MACROMAXDRI must be set to 5 and never be changed. When the total number of assignments is over $MACROMAXDRI, this alarm occurs. Cannot execute this MACRO. The macro aborted while executing. Teach pendant is enabled, therefore motion control was not granted. The teach pendant is disabled, therefore motion control was not granted. The system is in error status, therefore motion control was not granted. Motion control was not granted because otion is still in progress. Motion control was not granted because brakes were engaged. The teach pendant currently has the motion control, therefore motion control was not granted. The program has the motion control, therefore motion control was not granted. Becasue the operator panel has the motion control, the motion control was not granted. Other device has the motion control, and the motion control was not granted. System internal error. System internal error. System internal error. ENBL input on the UOP is off. The motion control was not granted because servo was not up. The motion control was not granted because manual brake control is enabled. The specified program is being edited or executing. The specified program is being edit or executing. The specified program is being edited or executing. The specified program is protected by user. The specified break number does not exist. The specified line number does not exist in the specified or default program. The specified program name is different form that of the P-code file. The specified program type is different from that of the object being processed. The specified label id already exists in the program. The specified program already exists in the system. The number of the programs and routines exceeded the maximum possible number ( 3200 ). Specified label does not exist. The number of line data exceeded the maximum possible line number ( 65535 ). The specified line data does not exist. The specified line data can't be changed. The size of modified data is different from that of original data when replacing it. The specified program is being edited or executing. The specified item is locked to change by system. The number of the programs exceeded the maximum number. The specified break point data does not exist. The specified program does not exist in the system. The specified program does not exist in the system. The program must be opened with write access before attempting write operations Too many CALL instructions is used. The number of opened programs exceeded the maximum possible number( 100 ). 1. The specified program is editing or executing. 2. The specified program is entried to MACRO The specified position data does not exist. Position data already exists in the specified position you want to move. The specified program does not exist in the system. The operation can be apply only to TPE programs. The program must be opened before attempting read or write operations. The specified operation is not supported for this program type. The specified program is protected by user. The specified program is editing or executing. The specified position data does not exist. The specified program is editing or executing. EOF occurs in file access. When P-code file was scaned, EOF occurs. The program name length is different from that of the P-code data. The specified data was broken. This is the internal error. The specified program already exists in the system. The specified break point data already exists in the program. The port that has the program you want to load is not connected. The break point data can not be overwriten. The program is protected by user or executing. The break point data can not be removed. The program is protected by user or executing. The specified application data does not exist because the program does not correspond to the specified application. The specified application data does not exist because the program does not correspond to the specified application. The specified application data does not exist because the program does not correspond to the specified application. KAREL program version number is newer than that of the system. KAREL program version number is older than that of the system. Lack of the memory which can be used. Reference of the same position exceeded the maximum count (256). A routine exists in memory with a different parameter definition than the routine in the PC file being loaded. The data of the system been broken. System data in CMOS has been broken.. Program data has been broken at the power fail recover. System data in CMOS has been broken.. The TPE program which has the same name already exists. The TPE program cannot be created in this start mode. The KAREL program cannot be loaded in this start mode. Specified KAREL program cannot be loaded in this mode. Because the same name program has already been loaded at controlled start. Specified program has already been loaded at controlled start. Because of this, you can only delete the program at controlled start. The TPE header size specified is too big. Must be less than 256. The routine of the specified program has been already referred by the KAREL program. Because of this, the specified program must be the KAREL program. The user cannot use the specified program name as a TPE program. Invalid variable is used in the specified KAREL program. The write access to the Flash File(F-ROM) failed. Some program may be lost. The read access to the Flash File(F-ROM) failed. Some program may be lost. Program data has been broken. Lack of the temporary memory which can be used for the program. The specified program is being edited or executing. The unused program can not be deleted When the parent program exists, the daughter program cannot be deleted. The total number of position exceeds the maximum number(32766). The renumber operation failed. The specified program is broken. Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation System executes normal Single Step or Backward motion stop Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Invalid softpart MIR Invalid softpart SEG Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Limit error Position not reachable Or near by singularity Position near by singularity Wrist joint warning No kinematics Invalid limit number The position is near a singularity point. Kinematics is not defined Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Internal system error. This class of error should not be encountered by the user during normal operation Robot not calibrated Invalid joint speed limit Speed out of range Joint vel limit out of range Internal system error. This class of error should not be encountered by the user during normal operation Uninitialized destination position Uninitialized via position Speed limits used Invalid packet received by planner Invalid cancel request received by planner Planner received null seg when not expecting one Uninitialized base vector in relative moves Uninitialized distance in relative moves Invalid position type received by planner Configuration mismatch RS orientation planning error AES orientation planning error Degenerate circle Internal system error during circular planning Prgoverride is not within 0 to 100 Internal error: planner received invalid mocmnd Internal error: planner received invalid motype Internal error: planner received invalid termtype Internal error: planner received invalid segtermtype Internal error: planner received invalid orientype Speed is not within 0 to $speedlim Rotspeed is not within 0 to $rotspeedlim Contaxisvel is not within 0 to 100 Seg_time is negative Accel_ovrd greater than 500 Internal error: planner received invalid accu_num Missing via position for circular motion Internal error: planner received invalid extended position representation NULL MIR pointer Internal error: planner received segment belonging to another group Not used Internal error: planner received invalid mmr.gp_concurrent Group motion: not all segments are received $utool is changed before move Motype is not cartesian Internal plan error:seg in list not all planned Internal plan error:mir mismatch Internal plan error:atan2 error Extended axes not supported Internal system error. This class of error should not be encountered by the user during normal operation Not used Warning, there is not enough distance to perform corner blending Intellitrak On: $linear_rate and $circ_rate must be equal Interpolator overrun Taught points define an arc larger than half circle Internal interpolator error:failed to receive mir when expecting one Internal interpolator error:failed to receive fdo when expecting one Internal interpolator error: mir list is empty when it shouldn't be Internal interpolator error: seg list is empty when it shouldn't be Internal interpolator error: error in sending ENB packet Internal interpolator error: error in sending DSB packet Internal interpolator error: error in sending TRG packet Internal interpolator error: process motion had completed without being restarted Internal interpolator error: invalid filter type received Internal interpolator error: error in seg list management Internal system error. This class of error should not be encountered by the user during normal operation Cannot replan joint motion in interpolator for this move Warning message to indicate that switch filter cannot take place Incremental motion causes turn number mismatch Robot not calibrated Servo in still on Invalid brake mask Invalid kinematics solution Robot not mastered Robot in overtravel Robot servo is on Invalid reference position Invalid config string System internal error System internal error System internal error System internal error System internal error System internal error Group motion not supported Conflict in local condition list pointers Local condition list attached to SEG is not NULL Position near by singularity Group motion: circular motype for all groups not supported Local condition time after value is too big. System will use time after limit This is just a warning Backward path/subpath motion is not supported Backward last node motype can not be circular Two of the circular taught points are too close to each other. The circular motion softpart is not loaded in the system. Joint short motion softpart is not loaded in the system. Cartesian short motion softpart is not loaded in the system. The KAREL motion softpart is not loaded in the system. The KAREL motion function pointer is not initialized or does not exist. The Group Motion softpart is loaded and multi-group motion is specified The Motion Resume softpart is loaded and path resume motion is specified Joint Turbo Move softpart is not loaded in the system. Cartesian Turbo Move softpart is not loaded in the system. Mismatch in major axis turn number motion follows several linear motions, the turn number might be mismatched, causing the robot to slow down Two motion groups cannot synchronize with each other due to replanning of one group. This will cause slow down on both groups. CF:rotspeedlim exceeded PM: Distance move exceed tolerance. PM: Rotation move exceed tolerance. PM: Can't current record data. PM: Joint angle move exceed tolerance. PM: Can't output data PM: No interpolation data PM: Configuration changed PM: Internal error PM: Original path invalid PM: Joint data error (L:%d) Joint data are invalid. The recorded data may be around singular point and change configuration. Could not get the next motion instruction. This can happen due to: - Using unlocked position registers - Using IF/SELECT statements - Control transfer to another program - Changing the setting for a system variable in the program. Load is close to capacity. Overload. Detect another link robot is paused and restarted. Detect wrong configuration for robot link. Attempted operation needs motion control. Setup or group mask in program may be incorrect or robot is still moving. Setup or group mask in program may be incorrect or robot is still moving. Setup or group mask in program may be incorrect or robot is still moving. Robot link program is held. Cart filter is used for robot link. Robot link calibration data is not correct. Robot link version is not compatible with peer robot. Slave robot failed to get position data of master robot. Current UTOOL number is not correct. Current UTOOL data is not correct. Failed to send ACK from slave. Failed to send broadcast from master. Failed to read ACK from slave. Failed to read broadcast from master. Slave robot is still moving. Joint position data is used for slave program. Joint motion is not available for slave program. Utool of master robot is changed during link motion. Utool of slave robot is changed during link motion. Robot link is not available when machine lock status. Internal error Circular Start and Via points are too close to each other. Circular Via and Dest. points are too close to each other. Specified TimeBefore (anticipation) value was too large Auto singularity avoidance function ignores the taught configuration (flip,non-flip) to avoid detected singularity. As a result, the taught configuration may not be reached. WARNING: single step backward may result in different configuration from forward. This is a warning message and indicates that the taught point at the specific line is inside a singularity zone and the system modifies it in order to control the rotation of axis 4, by design. If \$ra_paramgrp[].\$use_start_j4 = TRUE, Auto singularity avoidance function will internally modify the destination point when the point is inside a pre-defined singularity zone in the following way: 1. the joint angle of axis 4 is kept the same as that at the start point 2. the location (x,y,z) of the point is the same as it was taught (no location error) 3. the orientation (w,p,r) of the point is kept close to the taught one as much as possible (minimal orientation error) Original Path Resume was used for Robot Link. But Resume condition was not satisfied. Dual ARC motion is not allowed at T1 mode. Jog motion of the robot in the status of Held or Link Incomplete is not allowed. Original path resume feature is not available under this configuration. Resume condition does not match among master and slaves This group motion does not have consistent resume flag. T1 mode rotation speed limit is used The speed has been reduced at T1 mode even though the command speed is not greater than $SCR.$SAFE_SPD Given position's J4 angle is not zero. Given position is out of stroke limit Specified motion group is OFIX disabled. By error, OFIX motion is not available. J4 angle is not 0 at start or destination. Configuration mismatch between start and dest pos. This robot is not setuped for OFIX E-Effector angle is not vertical to rail axis. Tool rotation angle is too large for 1 motion. Tool spin angle is too large for 1 motion. Linear or Circular motion just before OFIX must terminate motion with CNT0 or FINE. Accupath or CJP may be used. OFIX does not work with these option. OFIX can work with linear motion. Tool spin angle is too large. Detect J4 is not zero angle during interpolation. Reached to stroke limit within this TCP configuration. Wrist axis turn number is differ from position data OFIX motion does not reached to correct rotation angle OFIX motion does not reached to correct spin angle There is an axis which needs Magnetic Phase Detection (MPDT) in that group and MPDT have not finished for that axis. Calculation of Turbo move on Joint motion has an error Torque calculation of Turbo move due to TB parameter has an error Calculation of Turbo move on Joint motion has an error that iteration count is too high Calculation of Turbo move on Joint motion has an error Term type CD is not supported. Can't resume motion. Corner speed slows down automatically because of robot constraint. Can't maintain corner distance because path is short or speed is high. SPD value does not affect corner speed anymore. Can't maintain program speed on the path because of robot constraint. Resume motion cannot reach stop position Can't resume orginal path. Internal system error. Can't resume orginal path. Circular speed is reduced because of robot contraint Configuration mismatch Can't resume motion on the original path. Can't resume motion in single step mode. Can't resume motion on the original path. This alarm occurs at resume after HOLD/ESTOP/ALARM when the resume path may not be on the original path. For example, this alarm could occur when you change the taught position while the program is held, and so on. Can't resume motion on the original path due to motion condition. Can't resume motion on the original path due to command speed change. Change in teach pendant override setting while the program is resuming with disabling CJP. Error Recovery function is enabled while CJLP is enabled. Internal system error. This class of error should not be encountered by the user during normal operation Small circle but large orientation change   adjustment precheck   adjustment precheck minimal rotation This is notification for application process enabled in the fast fault recovery when the alarm position is found. Z offset is specified for INCREMENTAL motion. Z offset can not be applied for INCRE motion. This is notification that Z offset was not applied for the motion. Change in teach pendant override setting while the program is running. Teach pendant override setting too low to assure constant path. PS statement is not available with this motion type No register has been defined for use with the Collision Guard Update macro. The data contained in the Collision Guard macro register is not an integer or is not in the range of 1 to 200. Isolated offset destination Invalid motype with offset Segment too short using OFFSET BWD motion not supported Illegal transition (nonCD->CD or CD->nonCD) happens. Pass number is not acceptable Pass direction is not acceptable Pass number and direction are not acceptable Pass number is not in sequence Last pass was not welded to completion System internal error. The maximum number of software options/updates (50) is installed. Installation of software option/update has finished successfully. S/W option was skipped by installer. The specified software option was not installed properly. Software option has not been authorized for this configuration. The required floppy disk was not used. Software option is now authorized for this configuration. COLD Start is required to save installation Power down and then up is needed The LICENSE file, license.dat, is missing or corrupted The supplied PAC is not valid for this option. The option nesting tree is too deep. This option is not compatible with an option that is already installed. The KEY file, keyfile.dat, is missing or corrupted The distribution media does not contain, update.tx, so there are no updates to install. The distribution media does not contain, custom.tx, so there are no customizations to install. The distribution media contains updates or customizations, but has a different release version than this core. The function performed by the user is not supported or is invalid. An unknown register dump occurred. Usually a result of previous unrecoverable system error. Column/row/layer number is illegal. Increment value of parettaizing config screen is illegal. Route pattern unfound. Palletizing data is imcomplete. Cannot read/write to palletizing register. Don't teach palletizing instruction over 16 In FREE configuation, can not be set INTER over two directions Palletizing option doesn't support this speed type The PC Monitor task could not be notified. Not enough memory to create client connection Failure to connect to PMON Server The PC Monitor task had an initialization failure.. The PC Monitor task had an internal timer failure. The PC Monitor task had an internal task status read failure. The accompanying cause code identifies the failure. The PC Monitor Server lost a connection with the named client. The PC Monitor task had an internal CURPOS read failure. The PC Monitor task had an internal monitoring failure. The requested monitor number was not found in the list of monitors. The port type code specified is invalid. This error code can be returned by several of the Digital I/O-related builtins (e.g., SET_PORT_ASG) when an invalid port type code is supplied. The port number is invalid or not presently assigned. Port numbers must be in the range of 1- 32767. However, operator panel (SOP) port numbers can be zero. In most cases (e.g., DOUT[n] = Off and calls to the SET_PORT_SIM builtin), the specified port already must be assigned. Memory required for this operation is not available. There are not enough ports on the specified board or module to make the specified assignments. This error code can be returned from the SET_PORT_ASG built-in. The specified port number in an assignment is invalid. Port numbers must be in the range of 1 - 32767. The specified port number in an assignment (e.g., DIN[1] = ON) is invalid. The port number must be in the range of 1 - 32767. This error code is returned by the KAREL built- in SET_PORT_ASG when it is used as ade-assign request (with a physical port type of zero) and the logical ports specified are not presently assigned. The physical port to which ports are being assigned in a SET_PORT_ASSIGN built-in call does not exist. The number of ports in a SET_PORT_ASG call is invalid. This must be in the range of 1 - 128 for digital port types (e.g., DIN), 1-16 for groups, and 1 for analog port types. An invalid physical port number is specified in a call to the KAREL built-in SET_PORT_ASG. This must be greater than 0. The port numbers in a SET_PORT_ASG call overlap existing assignments. The rack and/or slot number specified in a call of the KAREL built-in SET_PORT_ASG is invalid or refers to an unused rack/slot number. An attempt was made to delete an analog input sequence that has not been defined. The specified analog input sequence is too long; sequences must have from 1 to 15 ports numbers. Attempt to set the state of an input port that is not simulated. Indicates that an error has been detected in communication between the MAIN CPU PCB and the process I/O board, Model-A I/O racks, or Model-B I/O interface units. The most common causes of this are the following: o Power to a remote I/O rack or Model-B I/O interface unit is interrupted. o The cable between the MAIN CPU PCB and the process I/O board, racks, or Model-B interface units has been disconnected or is faulty. o Electrical interference between the I/O cables and other cables. This can be eliminated by physically separating the I/O cables from other wiring. In very electrically noisy environments, it might be necessary to use optical isolators with these cables. An unknown device is connected to the I/O Link connector. This device is not recognized by the current controller software version. The devices connected to the I/O Link exceed the I/O link capacity. A total of 64 bytes of data each are available for input and output devices connected to the I/O link. Process I/O boards typically use 16 bytes of input and 16 bytes of output each. Digital modules generally use one byte for each 8 ports. Analog modules generally use two bytes per port There are no ports of the type (e.g., GIN) specified in an I/O statement or built-in call. The PLC interface board is bad or not installed. The PLC interface board is faulted. The serial link to a PLC has failed. The operation is not supported for the specified port type. One or more assignments to the process I/O board or module at the specified rack and slot was invalid when the controller was turned on. An A-B RIO or Genius Network board is installed but the PLC software option is not installed. The maximum of number of concurrent pulse output statements is 255. A PLC I/O board is not installed in the backplane. This indicates that an severe error has occured during I/O initialization at controller power-up. Other messages in the log will indicate the specific problems. Digital output port states are not recovered when semi-hot start is enabled because I/O device configuration or assignments have changed. All outputs will be reset to OFF. PMC function is not supported on this main board. Error occurs at SNPX communication. Communication between the Model B interface unit and DI/DO units, or between DI/DO units, is lost. The PLC Interface hardware (A-B RIO or Genius Network PCB) is already running and can not be restarted without cycling power. An attempt has been made to access to a port assigned to a device or board which is offline. This might be the result of an error or device having been set offline manually. An attempt was made to access a port assigned to a device which is offline. For DeviceNet ports, troubleshoot as follows: This might be caused by an error or the device being manually set offline. There are too many DIGITAL I/O ports. You can not do this operation when PMC peogram is running. The SLC2 is in an error state at the end of initialization. PMC program does not exit. PMC program format is incorrect. Saving of keep relay (K), Timer (T), Counter (C) and Data table (D) at last power down is failed. Current data of them may be old value. Illegal function command is found in PMC program. Integrated PMC option (A05B-2400-J760) is not installed. 1. File name must be LADDER.PMC ot PARAM.PMC. The other file name is used for save or load. 2. Device name to access is too long. One of the following is locked by another task. PMC program edit, DI/O port simulation change, PMC program backup. Step of PMC program is too big. Specified PMC address is not valid for R-J3 PMC. Specified PMC address is not assigned to any device. Specified PMC address can not be used as byte address. Specified PMC address can not be used as bit address. Specified address can not be used in specified function command. - F0-F255 and G0-G255 can not be used except MOVW. - Odd address of F0-F255 and G0-G255 can not be used in MOVW. Specified CNC address is invalid. There are more than 10 errors in PMC program. And error display is stoped. There may be more errors. PMC program data is invalid. To write PMC progeam to flash file, E-SOP must be pressed or start mode is controlled start. You can not clear alarm status during writting PMC program program to ROM. Faild to run PMC program. Purging flash file now. It takes a few minutes. Don't cut power until 'Flash file purge is completed' is displayed. Purge of flash file is completed. The DIO configuration file (.IO) file loaded is in a format that is too new to load on this controller The DIO configuration file (.IO) file loaded is in a format that is too old to load on this controller An invalid port assignment has been recorded The ControlNet card failed to initialize. Possible problems can be the following: * The board system variable for firmware is invalid. Correct the value or restore the system variables. * The board firmware is not supported. Restore system variables. If necessary reload the controller. * The card or the motherboard is defective ControlNet option encountered an internal error. The number is the system error in hexdecimal. The configuration loaded on the CNET daughterboard is invalid. The target connection is already owned by some other device. Duplicate MAC-ID detected The CNET card is not attached to the network. The connection for the device Mac listed encountered an error. The Er number is the ControlNet error code. The firmware for the card could not be loaded. The firmware file was not found Scan list was modified. ControlNet interface is stopped. All connections to the card are broken. No I/O is exchanged and all ports are Offline. This happens when a network configuration is being performed or the Scan list is being changed. A config tool is performing a network change. The CNET interface has restored the connections. The config tool has completed the network change. A config tool has modified the scan list of the interface card. The interface could not establish a connection as it was not found. Invalid connection type in scanlist. The vendor ID of the device in the scan-list and that of the actual device do not match. The connection size of the device in the scanlist does not match the target device. The connection has not been scheduled The Product Type of the device in the scan- list and that of the actual device do not match. The Major/Minor revison of the device in the scan-list and that of the actual device do not match. The target device does not have enough connections The connection has not been scheduled The connection to the remote device is lost. The device is not in correct state to respond to this connection request. Remote device refused the connection. This could be due to an invalid connection path. The Card has an invalid scan-list configuration. A group of consecutive scans were lost; if n1=1, scans were lost on the main processor; if n1 = 2, scans were lost on the communications processor; n2 = number of lost scans; if n2 is less than 5, this may not be a serious problem; n3 = total scans since pwr up since power-up. Generally indicates overloading of the indicated processor. A group of scans were lost within a run of 100 scans. If n1=1, scans were lost on the main processor; if n1 = 2, scans were lost on the communications processor; n2 = number of lost scans; if n2 is less than 20, this may not be a serious problem; n3 = total scans since pwr up since power-up. Generally indicates overloading of the indicated processor. An element could not be added to the system I/O scan When this error is posted, ControlNet I/O is not Operational. Possible causes are: * Invalid Configuration of scanner scan list * Too many I/O points for any given CNET device * Too many I/O points in the whole system Target device did not respond to the connection request. Network change was aborted. Connections will be restored and I/O will be exchanged. Unrecognized port type name supplied to tpptnptc The target (adapter) connection is idle. A scanner has not connected yet. All the ports corresponding to this device will be offline. There is an error with the Scan-list configuration. The input header size in case of scanner mode or the output header size in case of adapter is invalid. The number of slots for the device in the scan is invalid. System internal error PROFIBUS is not installed PROFIBUS PCB is abnormal. Configuration data is abnormal. Parameter data is abnormal. Slave Parameter sets is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Setting of slave is abnormal. Master firmware is abnormal. Master firmware is abnormal. Master firmware is abnormal. PROFIBUS PCB is abnormal. Slave is disconected. A status message exists in the slave specific diagnostic area in the received diagnostic data. This indicates an internal system error. The task name specified is invalid. The program name specified is invalid. The specified program cannot be found. The specified line number cannot be found. The specified program is already being executed. Execution cannot be started in sub-routine program. Resumption was attempted at a different line from the paused line. Resumption was attempted in a different program from the paused one. Motion control cannot be obtained. There is paused motion later than motion that was attempted to resume. This motion was paused by the MOTION PAUSE instruction. Only the RESUME MOTION program instruction can can resume the motion. The number of programs you attempted to start exceeded the maximum number. Backward execution cannot be used. The specified task is not running or paused. The specified task is not running. Too many programs are paused. The request to pause the program was ignored. The specified program was already aborted. The request to abort the program was ignored. The specified program is not paused. The motion path record is lost. Backward execution cannot be used. Backward execution cannot be used any more. The current line is on top of the memorized path. The task number specified is invalid. This indicates an internal system error. The specified task attribute is not found. The specified task attribute is write protected. The value for the specified attribute is invalid. The specified routine cannot be found. Motion control for the specified group cannot be locked. Not enough memory or the task attribute is not set correctly. There is no execution record in memory. Motion control for the specified group was reserved, but it cannot be obtained. Motion control for the specified group was already reserved by another program. Motion control is released. The teach pendant currently has motion control. The robot cannot be started until motion control is obtained. Motion control was already released. Motion control was already released by request of this program. Motion control was not released yet. Motion control was already released by the request of another program. The teach pendant was enabled while the program is executing. The teach pendant was disabled while the program is executing. The shift key was released while the program is executing. Motion control cannot be released because the robot is moving. The program is in the process of being aborted. The specified lines to which a move was attempted exceed the number of lines in the program. The user application task was forced to abort while the application is executing. The AMR may not have been completely processed. The user application task was not executed. FWD key was released while the program is executing. BWD key was released while the program is executing. Motion data output function is enable instead of machin lock id disable. A user with Install level access logged in. A user with Install level access logged out. A user with Setup level access logged in. A user with Setup level access logged out. A user with Program level access logged in. A user with Program level access logged out. A user was logged out because of a password timeout. A teach pendant program was created. A teach pendant program was deleted. A teach pendant program was renamed. A teach pendant program subtype was changed. For example, a .TP program was changed to a Macro (.MR). A teach pendant program comment was edited. The group mask of a teach pendant program was changed. Write protection was enabled for the program. This helps prevent mistaken edits of the program. Write protection was disabled for the program. The program can be edited. The ignore pause feature was enabled for the program. The ignore pause feature was disabled for the program. A teach pendant program line was edited. A teach pendant program line was deleted. A teach pendant program position was recorded. A teach pendant program position was deleted. A teach pendant program position number was changed. For some tool products, a teach pendant program may contain application related data. This message indicates the data has changed. For some tool products, a teach pendant program may contain application related data. This message indicates some data was deleted. The named file was loaded. The named file was loaded. The program name may differ from the file name. A schedule was edited. Press HELP for more information. The data in a schedule was copied to another schedule. The schedule was cleared, meaning the values were set to zero. This message is used to provide detailed information for PWD-027. For example: PWD -027 Edit Weld Sch 1 Voltage PWD -030 (24.0 to 25.0) Volts The Operator password level does not have access to the FULL MENUS. Either a timeout occurred or a user logged out. A user with Install level access logged in from SMON. A user with Install level access logged in from KCL. A user with Install level access logged in from Teach Pendant. A user with Install level access logged in from CRT/Keyboard. A user with Install level access logged out from SMON. A user with Install level access logged out from SMON. A user with Install level access logged out from SMON. A user with Install level access logged out from SMON. A user with Setup level access logged in. A user with Setup level access logged in. A user with Setup level access logged in. A user with Setup level access logged out from KCL. A user with Setup level access logged out from Teach Pendant. A user with Setup level access logged out from CRT/Keyboard. A user with Program level access logged in from Teach Pendant. A user with Program level access logged in from CRT/Keyboard. A user with Program level access logged out from Teach Pendant. A user with Program level access logged out from CRT/Keyboard. A user was logged out because of a password timeout from SMON. A user was logged out because of a password timeout from KCL. A user was logged out because of a password timeout from Teach Pendant. A user was logged out because of a password timeout from CRT/Keyboard. An attempt was made to add entry to a queue when the queue was full. An Attempt to use GET_QUEUE when there are no entries in the queue This is the normal result when no entries have been added or all have been removed by previous calls. A bad sequence_no value is used in an INSERT_QUEUE or DELETE_QUEUE call. The value may be less than 1 or greater than the sequence number of the last entry in the queue. n_skip parameter in COPY_QUEUE call is less than zero Incorrect number is specified for ORD builtin routine. Incorrect number is specified for SUBSTR builtin routine. Negative number is specified for length argument for SUBSTR builtin routine. Incorrect number is specified for semaphore id. Invalid group number is specified. Specified string variable does not have enough room to hold the return data. Incorrect file attribute id was specified. Incorrect file attribute value was specified. A non-existent register number is specified. Incorrect register type is specified. Position type is not correct for the operation. Illegal attribute id was specified. A non-tpe is specified. The specified value is out of range. Incorrect port id was used Value used in SET_HEAD_TPE for bfr_size is invalid. Attempt to access position data or type from TPE program when the position has not been recorded. Cannot unlock group while motion is executing. Cannot unlock group while stopped motion exists. Variable displayed for dynaoic display is not a static variable. Parameter may be a local or constant. Neither of these is permitted as the displayed variable in INI_DYN_DIS calls. The parameter designated by param_no does not exist. The parameter data type does not match the CALL/MACRO argument data type. Tag name supplied in MSG_CONNECT, MSG_DISCO, or MSG_PING call was too long. Dictionary name supplied in built-in call is too long. Call to apnd_mtn_opt, write_xyzwpr, or write_joint with option array not initialized Stream instruction program buffer is full. The streaming program is not currently running. The motion option data supplied in the motion write routine call is not valid, or does not match the specified motion type. A string containing over 16 characters passed as comment argument in a SET comment built-in call. Argrument truncated to 16 characters. The client could not encode its arguments in a remote procedure call. The client could not decode the results of a remote procedure call. The client could not send the data for a remote procedure call. The client could not receive a reply from a remote procedure call. The client timed out while waiting for a reply from a remote procedure call. The server received an older version of the RPC protocol. The client or server received an unauthorized remote procedure call. The server received a remote procedure call for a program which it does not support. The server received a remote procedure call which uses the wrong version of a program. The server received a remote procedure call for a procedure which it does not support. The server could not decode the arguments of a remote procedure call. The client could not determine the server for the remote procedure call. The remote procedure call failed. The server received a remote procedure call which uses the wrong version of a program. The versions supported are shown. The value for $RPM_CONFIG.$N_BUFFERS is invalid The value for $RPM_CONFIG.$DATA_SIZE is invalid There is not enough cmos memory for this rpm segment Attempt to playback a segment that is not recorded in the specified buffer Buffer number specifed is invalid This segment was not recorded There is no rpm data is stored in this segment Pitch value is too small Stand alone arc start used The segment for RPM is either zero length move or too short RPM data has coordinated motion but TPE doesn't have. Or RPM data has non-coordinated motion but TPE has. You cannot add the instruction to the same line. The size of mnemonic code exceeds maximum size of one line data. The TPP program being loaded uses an option which is not installed on the controller where the program is being loaded (target controller). This label number exists in another line. Robot Link slave program and slave alone program can not use JOINT motion statement. Current Tool frame number of Master robot is different from Master Tool Number specified in Program detail menu. Robot link Slave program can have only one motion line. System internal error During data reception, parity, overrun and framing errors occurred. An attempt was made for data transmission, but DSR signal at the sensor side is in OFF- state. The undefined TCC was received from the sensor. BCC of thereceived data from the sensor is wrong. The format of the received data is wrong. The answer from the sensor is not received within the allowable time. The interval of characters sent from the sensor exceeded the allowable time. Calculating transform matrix is impossible. Internal Servo Gun error This is an internal system error. This is an internal system error. A failure occured while allocating memory. This SPOT instruction format is not correct. This SPOT instruction is not available. Another TPP specified this equipment and now executing or paused. Pre-execution has some trouble and system pauses the program execution for safety. Instruction syntax error. This instruction is for air gun spot. Different motion group assigned motion group to robot TCP side tip and motion group in this program. Invalid servo gun group number. Some instructions(ex. INC) can not execute with servo gun SPOT instruction at the same program line. The index value is invalid. The register index value is invalid. Specified pressure is too high. This is an internal system error. Some servo gun configulation data are invalid. Specified pressure value is too low. Pressure coefficient-B value is bigger than specified pressure value. Invalid pressure coefficient-A value. Illegal torque limit value is specified. Acutal pressure is shortage. Acutal pressure is shortage. Servo gun condition BU is not initialized. Pressure condition is not initialized. Pressure condition value is invalid. Incomplete pressure calibration. Incomplete Wear Down calibration. Invalid BU condition number is specified. Invalid P condition number is specified. This instruction is not taught completly. Position type is JOINT. The convert value from specified pressure value to torque limit value exceeds the max torque value. Tip stick detection DI is ON When tear off function is executing, program cannot be started. The tip wear down value of gun side exceeds the increased error. The tip wear down value of robot side exceeds the increased error. The wear difference between the robot tips on the dual gun exceeds the specified tolerance. Pressure enable signal has not input after time out. Comp confiramation signal has not input after time out. Pressure enable signal number is illegal. Comp confirmation signal number is illegal. Measured thickness deviates more than specied tolerance. There is not enough permanent memory. It is impossible to allocate the system variable. The number of $SGGUN is less than the total axis number of servo gun group. User has started Servo Gun autotuning. User has successfully completed auto tuning. Auto Tuning Could not be completed. A FAULT exists. STEP mode is enabled. Machine Lock is enabled for servo gun. Hold is active. Cycle power. Backup stroke index for manual operation is not selected. The motion group number of the user program for manual pressure or manaul backup is not matched to the Servo Gun group. Specified backup stroke index is not set the valid stroke value. $EQNUM is not use in the system. The equipment specified by $EQNUM is not assigned to the Servo Gun Specified number is not valid for $GUNNUM. The Tip Wear Down Calibration is not completed. The tool frame number or user frame number is different from the standard position. System cannot read the position register which is specified by $PRINDEX. The pressure program name is not set correctly. The backup program name is not set correctly. Pressure data index for manual operation is not selected. Specified pressure data index is not set the valid pressure data. Servo gun lockout feature was enabled. Servo gun lockout feature was disabled. Servo gun lockout feature was activated. Servo gun lockout feature was activated. This equipment is set to Air Gun. Or the gun change setup is disabled. Machine lock for robot axes is enabled at gun attach instruction. Gun number assignment are wrong . Gun is not detached. Some AXISORDER are not 0. Gun is not detached. Gun attach input signal is OFF. Gun is not attached. Gun attach input signal is ON. Another program is executing GUN ATTACH or GUN DETACH instruction. $CHG_PHASE is not 0 at executing the instruction. Gun identify signal is OFF. Gun set signal is OFF. GUN ATTACH or GUN DETACH instruction is canceled while executing the instruction. GUN ATTACH or GUN DETACH instruction become timeout while executing the instruction. Mastering data of the gun is lost by a pause while mastering. Gun mastering is failed by a pause while mastering. GUN ATTACH instruction failed. Please see cause code. GUN DETACH instruction failed. Please see cause code. The mastering of servo gun axis has not been performed yet. System variable $master_done set FALSE. The calibration of servo gun axis has not been performed yet. System variable $calibrate set FALSE. Reference position has not been set when quick mastering. The another gun which is different from the gun number specified by GUN DETACH instruction is attached. While the calibrate motion, the detect condition was not triggered. The PR[] index for the calibrate motion is not set. The Touch torque for the calibrate motion is not set. The Detect signal for the calibrate motion is not set. At the Gun Zero Master[] instruction, Servo gun axis does not stop. At the Gun exhange[] instruction, the new gun could not be activated. Opposable gun type is required for target gun. Cannot do this operation while Gun Close is disabled. Misdetection occur while tip wear measurement for automatic gun zero master. Inform signal of maximum wear down for movable tip is invalid. Inform signal of maximum wear down for fixed tip is invalid. Specified register number is out of range. Specified position register number is out of range. Increased error limit for Movable tip is not set (0.0mm). Increased error limit for Fixed tip is not set (0.0mm). Excessive load is detected. Mastering of gun axis may be incorrect. Failed to reset pulse coder alarm. Tip wear measurement is uninitialized. The load threshold for tip wear measurement is not set. Standard pulse is not measured for tip wear measurement. Standard gun opening is not measured for tip wear measurement. DI index for detecting movable tip is not set. Failed to touch fixture for measurement by movable tip. Servo tuning is incomplete. Tip wear measurement was started from gun closed position. Misdetection occur while tip wear measurement for gun opening measurement. Magnetic Phase detection failed. Magnetic Phase detection is unavailable with the current calibration motion type. Gun closing motion to set reference position failed. The posted error occurred on gun index 1 of the dual gun. The posted error occurred on gun index 2 of the dual gun. Could not display the seal status display screen The system ready signal(DI) turns off when the sealant is dispensed. The high pressure signal(DI) is on for set time when the sealant is dispensed. The gun full open signal(DI) has been on for the set time since sealing start. Dispenser switch position does not match equipment set up One or more calibration procedures are not complete The dispenser should be full at this point, and is not. Both drums are empty Same fault occurs repeatedly Dry run parameter is ON. Robot lock parameter is ON. Sealing parameter is disabled. The system ready signal(DI) turns off when sealant is being dispensed. The high pressure signal(DI) has been on for the configured time during sealing. The Auto Purge feature has determined that the robot should purge now, but the robot is not at the proper purge position. The Auto Purge feature has determined that the robot should purge now, but the maximum number of purges it is allowed to perform in a row (as set in the equipment setup menu) has been reached. Gun full open signal(DI) has been on too long since since dispensing started. Gun full open signal(DI) has been on for too long while dispensing. Flow command output voltage is larger than the maximum output. The dispensing equipment controller has detected a fault in its hardware. A dispensing gun malfunction has been detected by the dispensing controller. A low pressure condition has been detected by the dispensing controller A high pressure condition has been detected in the dispensing gun nozzle The volume of material dispensed on the previous job was above the preset limit. The volume of material dispensed on the previous job was below the preset limit A error was detected in the flow meter readings. An incorrect bead condition was detected. An unknown error code was received from the dispensing controller. An error was encountered reading fault data from the dispenser An Emergency Stop condition was detected at the dispensing controller A fault was detected at the dispensing controller. At this point in the process, the dispenser should not be full. The first of the two drums is empty The second of the two drums is empty. Reload of shot meter took longer than the specified time. Volume calibration aborted due to user request or possible fault. Volume present signal not received from Pro- Flo unit. Material calibration aborted due to user request or possible fault. Material cal complete signal not received from Pro-Flo unit. Bead width calibration aborted due to user request or possible fault. User input was zero for bead width. User input was zero for material weight. User input was zero for specific gravity. Zero volume was detected from Pro-Flo analog signals. User input was zero for dispense time. Pressure calibration aborted due to user request or possible fault. User input was zero for material pressure. No change in analog signal from pressure transducer. Atomizing air calibration aborted due to user request or possible fault. User input was zero for air pressure. The Scale factor or bias is zero The volume timer expired Pressure calibration has not been completed. Analog voltage calibration aborted due to user request or possible fault. Analog voltage calibration has not been completed. Atomizing air calibration has not been completed. Voltage step for calibration has not been set yet. Material learn calibration has not been completed. Material learn timeout value is zero Low pressure atomizing air input was > or = high pressure Flow ctrl: volume calibration aborted due to user request or possible fault. Volume read was negative. Volume signal calibration has not been completed. At least one I/O signal assignment is zero. Dispenser ready signal (DI) from dispenser is not high. The index value of seal start instruction is invalid. The distance between sealing instructions is too small, the sealing schedule cannot be changed Robot moved with joint motion during sealing. Robot moved with joint motion during sealing. This equipment is not exist. SE instruction is not exist. Equipment is not set on this program. Other program is using this equipment now. Waiting for permission to enter zone The index value is unassigned Can't set volume set point while a program is running There is no SS instruction before SE. Unsuccessful execution of a MOV_ type program. Desired volume or bead width for first sealing schedule was zero. Tool offset calibration aborted due to user request or possible fault. Current utool is zero - has not been taught. Current REFPOS has not been taught - is zero. Difference between REFPOS and OFFSET positions was too large. Difference exists between REFPOS and OFFSET position configurations. File to be executed is not closed. File to be executed does not exist. Commanded tool position is not valid All grippers are not opened All grippers on this valve are not closed Sensors not reporting part present Sensors reporting part present Variable $sltlstup[1].valve is not assigned IO port is not set up as a complementary port Tool was commanded to the FLIP position, but sensors report that it isn't there. Tool was commanded to the UNFLIP position, but sensors report that it isn't there. Tool was commanded to the EXTEND position, but sensors report that it isn't there. Tool was commanded to the RETRACT position, but sensors report that it isn't there. Robot is not calibrated. Current robot position invalid. Internal tool offset calibration error. The high performance I/O triggering system (Motion Trigger) has returned a bad status. When this occurs, the redundant triggering system will take over, but the quality of the SSs and SEs will be poor. This condition is usually caused by one or more of the following: 1. A Gun On output is assigned to a output point which is nonzero and does not exist. 2. A Start Meter output is assigned to a output point which is nonzero and does not exist. 3. A Atomizing Air output is assigned to a output point which is nonzero and does not exist. 4. There is a problem with the software setup of the I/O system. 5. There is a problem with the hardware setup of the I/O system. In the Schedule number listed, the Gun On signal has been set up to turn on or off too long after the node the SS[] or SE is attached to. Currently, if this signal is set up to turn on or off greater than 100ms after the node, this warning will be posted and the signal will fore 100ms after the node. These are the formulas used to determine when the gun will be turned on or off relative to the node for seal schedule 'n': For SS[n]: Time_Before = EQUIPMENT_DELAY - GUNON_DELAY For SE: Time_Before = EQUIPMENT_DELAY - GUNOFF_DELAY Note that a NEGATIVE Time_Before means AFTER the node. While the robot is sealing, specified item cannot be chnaged. The Atomizing Air cannot be used with the high performance I/O triggering system (Motion Trigger) The analog output command of Atomizing Air exceeds the Maximum Analog Voltage (air) which is set in the setup screen The analog output command of Atomizing Air is clamped by Minimum Analog Voltage (air) which is set in the setup screen Calibration aborted due to user request or possible fault. Calibration of Atomizing Air has not been done yet. The calibration must be done before program execution. Application is changed during sealing. The analog output command for Flow control is clamped by Minimum Analog Output (flow) which is set in the setup screen The maxmimum analog output value for flow command is lower than the minimum analog output value in setup screen. The maxmimum analog output value for atomized air is lower than the minimum analog output value in setup screen. The Pre-Pressure instruction is executed when Pre-Pressure control is disabled. The Pre-Pressure instruction cannot be executed between SS and SE. The speed override is less than 100%. Internal error (system). Internal error (spot) . Internal error. Spot program instruction has illegal value. Weld completion signal has not input after Weld done time out value. Weld alarm signal has input. Gun close detect signal han not input. Backup Full open detect signal has not input. Backup half open detect signal has not input. Weld schedule number is illegal. Close backup signal is wrong. Close detect signal is wrong. Clamp signal is wrong. Full open detect signal is wrong type. Half open detect signal is wrong. Open backup signal is wrong. Gun pressure signal is wrong. Weld schedule signals are wrong. H/M/L Valve signal are wrong. Weld enable signal is wrong. Weld on signal is wrong. Weld completion signal is wrong. Weld completion signal has not input after Weld done time out. Weld completion signal has not input after Weld control time out. Spot input signals are wrong. Spot output signals are wrong. The number of equipment in program is wrong. value of register is illegal. Weld complete signal for Gun1 remain input at start of spot sequence. Weld complete signal for Gun2 remain input at start of spot sequence. Another program is using this spot equipment. Spot instruction has illegal schedule number. Spot output signals are wrong. The loaded equipment number does not much in this setting. Shift key is released The GUN/BU macro program name is not set. The motion group of GUN/BU macro program is not zero. Illegal function code was specified. System error. Serial port is not opened. Serial port has already been opened, and it was tried to be opened again. Serial port is not initialized. Serial port DSR is off. Serial port parity error occured. Serial port overrun error occured. Serial port frame error occured. Serial port parity error and overrun error occured. Serial port parity error and frame error occured Serial port overrun error and frame error occured. Serial port parity error, overrun error, and frame error occured. Serial port DSR is off and harware error occured. Serial port request count is illegal. System error. Cancel current serial port setup. This code does not appear at normal time. System error. Initialize serial port at power failure recovery. This code does not appear at normal time. System error. The operator panel emergency stop push button is pressed. The teach pendant emergency stop push button is pressed. The teach pendant deadman switch is released while the teach pendant is enabled. On the terminal block on the printed circuit board of the operator panel, no connection is established between the FENCE1 and FENCE2 signals. When a safety door is connected, it is open. A hardware limit switch on an axis was tripped. Usually, robot movement cannot exceed a limit beyond the maximum range of movement (software limits) for each axis. However, when the robot is shipped, the overtravel state is set for transit. A safety hand has broken. If no broken hand can be found, however, the most likely cause is the HBK signal of a robot connection cable being at the 0 V level. The external emergency stop push button is pressed. On the terminal block of the printed circuit board for the operator panel, no connection is established between EMGIN1 and EMGIN2. The brake fuse is blown on the EMG Control PCB. The pneumatic pressure alarm indicates the presence of a defect. If the pneumatic pressure alarm is not detected, however, the most likely cause is the PPABN signal of a robot connection cable being at the 0 V level. The belt broken robot digital input (RDI7) is asserted. The teach pendant attachment switch on the operator panel was operated while the teach pendant was enabled. Normal power on (hot start). Upon power-up with power restoration enabled (hot start), the configuration of the DSP modules on the axis control printed circuit board and the multi-function printed circuit board has been changed. A fan motor in the control unit is abnormal. The temperature of the control unit is higher than the specified value. Cooling water volume dropped. No robot internal mirror. The current for brake exceeded the specification. On the terminal block on the printed circuit board of the operator panel, no connection is established between signals *SVON1 and *SVON2. When an external switch is connected, it should be checked. The teach pendant cable is disconnected or a momentary break occurred in any one of the TP emergency stop circuits: TP emergency stop, DEADMAN, or fence. When HRDY is on, SRDY is off even though no other alarm cause is present. HRDY is the signal sent from the host to the servo system to specify whether to turn the servo amplifier's MCC on or off. SRDY is the signal sent from the servo system to the host to indicate whether the servo amplifier's MCC is on or off. Generally, if a servo amplifier's MCC is not turned on despite the signal for turning the MCC on having been issued, an alarm is issued for the servo amplifier. The host does not issue this alarm (SRDY off) if an alarm for the servo amplifier is detected. So, this alarm indicates that the MCC is not turned on when no error can be found. SRDY was already on when an attempt was made to turn on the MCC with HRDY. HRDY is the signal sent from the host to the servo system to specify whether to turn the servo amplifier's MCC on or off. SRDY is the signal sent from the servo system to the host to indicate whether a servo amplifier's MCC is on or off. A excessive servo positional error occurred when the motor stopped. When the robot moved, the servo positional error exceeded a previously specified value ($PARAM_GROUP.$MOVER_OFFST or $PARAM_GROUP.$TRKERRLIM). For example, this error will occur if the feedrate of the robot differs from that specified. The value entered with a command is too large. An attempt was made to exceed the maximum rated motor speed ($PARAM_GROUP.$MOT_SPD_LIM). The motor speed is clamped to its maximum rated value. An attempt was made to perform calibration, but mastering has not yet been completed. When the temporary stop alarm function ($SCR.$BRKHOLD_ENB=1) is enabled, this alarm is issued whenever a temporary stop is made. When this function is not to be used, disable the function. A user servo alarm was issued. This alarm is raised when the system variable $MCR_GRP[i].$SOFT_ALARM is set to TRUE. Only KAREL users can use this variable. An attempt was made to set a reference point for simple mastering, but calibration has not yet been completed. An attempt was made to perform simple mastering, but a required reference point has not yet been set An attempt was made to exceed the maximum joint speed ($PARAM_GROUP.$JNTVELLIM). The joint speed is clamped to its maximum rated value. The in-position monitor time ($PARAM_GROUP.$INPOS_TIME) has elapsed, but the in-position state ($PARAM_GROUP.$STOPTOL) h=as not yet been set. The *IMSTP signal, which is a peripheral device I/O signal, is applied. A pulse count detected when the controller was turned off differs from that detected when the controller was turned on. This alarm is asserted after exchange of the pulse coder or battery for backup of the pulse coder data, or loading backup data to the main board. CMC cannot work because the calculated motor speed exceeded the specification. Zero position master is done with mark position (not with zero position). A value specified with a command is too large. The servo amplifier magnetic contactor (MCC) is welded closed. This is an S-900-specific alarm. The energy produced by the regenerative discharge is excessive. As a result, all the generated energy cannot be dissipated as heat. When a robot is to be operated, a servo amplifier feeds energy to the robot. Along its vertical axis, however, the robot moves downward using potential energy. If the decrease in the potential energy exceeds the acceleration energy, the servo amplifier receives energy from the motor. This also occurs during deceleration even if the force of gravity has no effect. This energy is called regenerative energy. Normally, the servo amplifier dissipates this regenerative energy by converting it to heat. When the amount of regenerative energy exceeds the amount of energy that can be dissipated as heat, excess energy accumulates in the servo amplifier, thus triggering this alarm. The DC voltage (DC link voltage) of the main circuit power supply is abnormally high. The LED indicator of the servo amplifier PSM displays '7'. An excessively high current flowed through the main circuit of a servo amplifier. The LED indicator on the servo amplifier PSM displays '-'. One of the red LEDs (HC1 to HC6) above the 7-segment LED is lit, indicating the axis for which the HCAL alarm is detected. This alarm is issued to protect the motor when there is a danger of thermal destruction when the root-mean-square current value, calculated internally by the servo system, exceeds the maximum permissible value. Despite the external magnetic contactor for a servo amplifier being on, the DC voltage (DC link voltage) of the main circuit power supply or the control power supply voltage (+5 V) is excessively low. Never occurs on R-Model J. The servo amplifier's built-in thermostat was actuated. The LED indicator on the servo amplifier PSM displays '3'. An excessively large disturbance torque is estimated by the servo software. A collision was detected. The offset of a current feedback is excessively large. Disturbance estimated in the software exceeded the threshold value. There is a possibility that the load held in the wrist exceeded the robot specification. The DSP module program memory is defective. An FSSB communication error from SRVO to SLAVE occurred. An FSSB communication error from SLAVE to SRVO occurred. An FSSB 1 communication error occurred during initialization. Servo amplifier initialization failed. An FSSB 2 communication error occurred during initialization. The clock for the rotation counter in the pulse coder is abnormal. This alarm is issued when the battery for backing up the absolute position data of the pulse coder is not connected. The battery cable inside the robot might have become disconnected. The built-in rotation counter on the pulse coder is abnormal. This alarm is issued when the phase of a pulse signal generated by the pulse coder is abnormal. The battery voltage for the pulse coder has dropped below the allowable minimum. The pulse coder ROM checksum data is abnormal. The temperature inside the pulse coder has become too high, causing the built-in thermostat to actuate. A request signal was sent to the serial pulse coder, but no serial data was returned. A serial data change occurred during transfer. A serial data start bit or stop bit error occurred. The feedback speed is abnormally high (3750 rpm or greater). The pulse coder might be faulty. The pulse coder might be faulty, or noise might be causing the pulse coder to malfunction. The LED on the pulse coder has become disconnected. The absolute position of the pulse coder has not yet been established. The servo software detected a disturbance torque that was too high when motion starts, and tripped a Tip stick detection alarm. The line tracking pulse count overflowed. The line tracking pulse coder is disconnected. The clock for the rotation counter in the line tracking pulse coder is abnormal. This alarm is issued when the battery for backing up the absolute position data for the pulse coder is not connected. The built-in rotation counter on the line tracking pulse coder is abnormal. This alarm is issued when the phase of a pulse signal generated by the pulse coder is abnormal. This alarm is issued when the battery voltage for backing up the absolute position data of the pulse coder has dropped. The line tracking pulse coder ROM checksum data is abnormal. The motor has overheated. An error occurred during the communication between the pulse coder and the main CPU printed circuit board. An error occurred during the communication between the pulse coder and the main CPU printed circuit board. An error occurred during the communication between the pulse coder and the main CPU printed circuit board. This alarm is issued when the positional data sent from the pulse coder is considerably greater than the previous data. The pulse coder might be faulty. The pulse coder might be faulty. Or, noise might have caused the pulse coder to malfunction. The LED on the pulse coder has become disconnected. The absolute position of the pulse coder has not yet been established. A robot overtravel limit switch has been pressed. The hand broken (*HBK) robot input is asserted. The pneumatic pressure (PPABN) robot input is asserted. The controller door has been opened, emergency stop signals have been detected for a short time, or a hardware connection has been mis-wired. The controller door has been opened, emergency stop signals have been detected for a short time, or a hardware connection has been mis-wired. The FET current for brake of an extended axis (brake number 2 or greater) exceeded the specification. When the Enable/Disable switch is changed to enable, a reset is necessary for execution. Follow-up time is over. when softfloat is OFF. Follow-up time is over. when softfloat is OFF. While Cartesian Softfloat is being executed, the position error on the rectangular coordinates becomes greater than the tolerance that is set by the user. Acceleration time is much longer. The last angle update request does not match the current angle. Motion speed is too high to perform quick stop. The program was over in the process of a quick stop. The servo amplifier (PMS) overheated. The DC voltage on the main power circuit of the servo amplifier is lower than the specification, even though MCC is on. The current in the main power circuit of the servo amplifier exceeded specification. The cooling fan for the control circuit stopped. The back-up charge circuit for the amplifier has trouble. The cooling fan for control circuit stopped. The back-up charge circuit for the amplifier has trouble. DAL alarm of an amplifier. The feedback data from pulse coder was abnormal by; 1. Noize on the pulse coder. 2. The interpolation circuits of the pulse coder are broken. A servomotor's built-in thermostat was actuated. The servo amplifier overheated. Input power applied to the amplifier has been lost. The DC voltage of the main circuit power supply is excessively low. This alarm indicates a problem with the back-up charge circuit for the amplifier. The DC voltage of the main circuit power supply is too low. This alarm indicates a problem with the back-up charge circuit for the amplifier. The current in the main power circuit of the servo amplifier exceeded specification. An excessively high current flowed through the main circuit of a servo amplifier. The cooling fan for the control circuit stopped. The cooling fan for the control circuit stopped. The IPM module has trouble. Charging of the main circuit could not finish within the specified time. The DC voltage of the main circuit power supply is abnormally high. The energy produced by regenerative discharge is excessive. The IPM module has trouble. Charging of the main circuit could not finish within the specified time. The emergency stop button on the operator panel was pressed, or the external emergency stop function was activated. EMGIN1 and EMGINC are not strapped to each other. Or, EMGIN2 and EMGINC are not strapped to each other. The teach pendant deadman switch is released or the fence circuit is open. The deadman switch is released, the fence circuit is open, the operator panel ESTOP button is pressed, or the external ESTOP signal is received. Different DSM (Digital Servo Module) are mounted on the controller The DSM (Digital Servo Module) type is mismatched to the servo parameter version. The motor cannot rotate as fast as the calculated speed required for the current motion. The motor cannot rotate as fast as the calculated speed required for the current motion. The motor cannot rotate as fast as the calculated speed required for the current motion. The motor cannot accelerate as much as the calculated acceleration required for the current motion. The wrong CJ mode was used. Torque on the axis is over the limit. Acceleration is reduced automatically to avoid torque saturation The robot was going to move while identifying the payload. Internal system error. The initialization of the system variable or the internal work memory has not been done. Servo ready is off. The data region this command is going to use is already locked by an other task. The data this command is going to use is another group's data. There is no data that this command will use, or, the data in the buffer is not the data of the needed mode. The mass parameter is needed in order to estimate the current payload's parameters. The free memory is too small to be allocated. The motion command exceeded specification. The fence circuit is open or the SVON input circuit is open. The SVON input circuit is open. Servo is disconnected. The Non Teacher Enabling Device is released or servo is disconnected. The fence circuit is open or the SVON input circuit is open and mis-wiring on the SVON is detected. The SVON input circuit is open and mis-wiring on SVON is detected. Control Stop is detected. The control box fan motor has failed. The operator panel emergency stop push button is pressed and miswiring on SVEMG is detected. Or the operator panel emergency stop push button is pressed slowly so that SVEMG signal is delayed. The teach pendant emergency stop push button is pressed and miswiring on SVEMG is detected. The external emergency stop push button is pressed and mis-wiring on SVEMG is detected. The fence circuit is open and mis-wiring on SVEMG is detected. The teach pendant deadman switch is released while the teach pendant is enabled. And miswiring on SVEMG is detected. The SVEMG signal is detected while the fence is opened and the teach pendant is enabled and the Deadman switch is not released. Or, the controller door is opened while the fence is opened and the teach pendant is enabled and the Deadman switch is not released The FET current for the brake of an extended axis (brake number 2 or greater) exceeded the specification. Mis-wiring of the SVEMG signal on Robot 2 is detected. Mis-wiring of SVEMG signal on Extended robot is detected. Teach Pendant is disabled when mode switch is T1 or T2 and Robot1 and Robot2 are disconnected Or mis-wiring of hardware connection Transformer Overheat signal is asserted The fuse on Panel PCB is blown The fuse on 6 axis amplifier is blown The fuse on Aux axis amplifier is blown Total current of is over the limit. Because robot motion is too aggressive There is a lack of DSP chip for the axis, which is set in the $AXISORDER system variable. FSSB shows the amp module does not exist A single chain 1 (+24V) failure occurred. A single chain 2 (0V) failure occurred. A Non Teacher Enabling Device is released The teach pendant is disabled when the mode switch is in T1 or T2. Or, the controller door is opened. Or, there is a mis-wiring of a hardware connection. The teach pendant deadman switch is released. A chain failure alarm is detected in short term. A chain failure has been repaired. Reset chain failure detection cannot be executed. A single chain 1 (+24V) failure occurred when the SVON (Servo ON/OFF switch) input was asserted. A single chain 2 (0V) failure occurred when a SVON (Servo ON/OFF switch) input was asserted. A single chain 1 (+24V) failure occurred when the FENCE circuit was opened. A single chain 2 (0V) failure occurred when FENCE circuit was opened. A single chain 1 (+24V) failure occurred when External Emergency stop input was asserted. A single chain 2 (0V) failure occurred when External Emergency stop input was asserted. A single chain 1 (+24V) failure occurred. A single chain 2 (0V) failure occurred. Status of MAINON1 signal is still OFF even if SVEMG is ON It is abnormal of E.STOP circuit Single chain 1 (+24V) failure occured when Non Teacher Enabling Device is released Single chain 2 (0V) failure occured when Non Teacher Enabling Device is released Single chain 1 (+24V) failure occured when servo disconnected signal is asserted Single chain 2 (0V) failure occured when servo disconnected signal is asserted Weld occures on E.STOP unit MON3 status is ON when servo is ready The status of MON3 is abnormal FENCE1 status is still ON when FENCE signal is asserted FENCE2 status is still ON when FENCE signal is asserted SVOFF1 status is still ON when SVOFF signal is asserted SVOFF2 status is still ON when SVOFF signal is asserted EXEMG1 status is still ON when EXEMG signal is asserted EXEMG2 status is still ON when EXEMG signal is asserted SVDISC1 status is still ON when SVDISC signal is asserted SVDISC2 status is still ON when SVDISC signal is asserted NTED1 status is still ON when NTED signal is asserted NTED2 status is still ON when NTED signal is asserted T2 mode is not permited to move robot The operator panel emergency stop push button is pressed and miswiring on SVEMG is detected. The teach pendant emergency stop push button is pressed and miswiring on SVEMG is detected. Status of MON1,MON2,MON3 signals are abnormal on COLD START Value shows MON1,MON2,MON3 signal status Bit 0 : MON1 ON ,Bit 1: MON2 ON,Bit 3: MON3 ON SVOFF (Servo OFF signal) input asserted. SVOFF input circuit is detected and mis-wiring on SVEMG is detected. Single chain 1 (+24V) failure occured when SVOFF input (Servo OFF signal) is asserted. Single chain 2 (0V) failure occured when SVOFF input (Servo OFF signal) is asserted. Weld occures on E.STOP unit MON3 status is ON when servo is ready The status of MON3 is abnormal DC link high current alarm occured on the amp IPM over heat alarm occured External FAN alarm occured on the amp DC link high current alarm occured on the PSM Input power is abnormal or PSM unit is broken External FAN is abnormal on alpha PSM or alpha PSMR SVM communication error occurs Cable between PSM and SVM is disconnected SVM is abnormal. Or PSM is abnormal Discharge power of PSM dischege is abnormal Motion is too agressive. Fan, which is cooling for PSMR, is abnormal PSM control power is low voltage Cable between PSM and SVM is disconnected PSM is abnormal. Or SVM is abnormal Calculated velocity value is abnormal on Servo A safety hand broken is detected when setting of HBK is disabled. The most likely cause is the HBK signal of a robot connection cable being from 24V to the 0 V level. A safety hand broken is detected when setting of HBK is disabled. The most likely cause is the HBK signal of a robot connection cable being from 24V to the 0 V level. A signal of safety hand broken is not detected when setting of HBK is disabled. Setting of Hand broken is not correct A signal of safety hand broken is not detected when setting of HBK is disabled. Setting of Hand broken is not correct A signal of mamual brake mode enable is detected. Arm Bending Control (ABC) compensation value is too big. Magnetic Phase Detection (MPDT) process failed. Magnetic Phase Detection (MPDT) process time is up. Magnetic Phase Detection (MPDT) process cannot start because machine lock is enabled for that group. Magnetic Phase Detection (MPDT) process cannot start because servo ready(SRDY) is off. There are no specific E.STOP signals when ESP signal is ON Enable/Disable switch or deadman switch on teach pendant are abnormal SVOFF (Servo OFF signal) input asserted. Or E.STOP occurs Or E.STOP circuit is abnormal Retry count of pulse coder exceeded a limit value of $PLS_ER_LIM when $PLS_ER_CHK=1 Position feedback compensation count of pulse coder exceeded a limit value of $PLS_CMP_LIM when $PLS_ER_CHK=1 Power off is required to reset CMAL alarm Power off is required to update parameters Special checking space is not clear. The priority of space is invalid Space Check function is not compatible with AccuPath. AccuPath is not allowed. Space Check function is not compatible with Continuous Turn CTV option. The CTV motion option is not allowed. The space is disabled while waiting. Interaction is detected. Interaction is detected. Interaction is detected. Internal error. APDT setting is too many. Faied to get distance The model type in combination setting screen is invalid. The index number in combination setting screen is invalid. The group number specified in combination setting is invalid. The group is not calibrated. Invalid tool number The hand number related to the current tool number is invalid. There is no calibration data for the group. There is an invalid model elemnt. Failed to get element position The taught group number of the fixture elements is invalid. The model type in combination setting screen is invalid. The index number in combination setting screen is invalid. The group number specified in combination setting is invalid. The group is not calibrated. Invalid tool number The hand number related to the current tool number is invalid. There is no calibration data for the group. There is an invalid model elemnt. Failed to get element position The taught group number of the fixture elements is invalid. This combination is originally disabled on setup screen. This combination is originally disabled on setup screen. This combination is already enabled by another program. another program disabled this condition. Specified condition has invalid host name. Specified condition has invalid host name. Approach wait intruput signal is turned to ON Approach wait limit has passed. Approach wait cannot be used with: Tracking motion of slave of simultaneous robot link Continuous turn function. IASTOP[*] = TMP_DIS is executed. Resume from different line when a program is paused. IAWAIT[*] = ENABLE is executed. Resume from different line when a program is paused. The group number specified to Approach_RATE[] instruction is invalid number. The rate value specified to Approach_RATE[] instruction is invalid. It must be the value from 0% to 100% Comm init error Invalid hostname Invalid IP address Specified host is too many Enabled element is too many Invalid element Receive invalid data Invalid data exists to send Target element is too old information Target is OFF or comm stopped Specified element does not exist Specified element does not exist APDT task is overload Collision Detected for the group Check combination type mismatch Two points not form a line Remed: Move the two points apart Three points not form a plane Remed: Move the three points apart Four points not form a box Remed: Move the four points apart Check combination not supported Remed: Check the check combinations Unit vector formation error Remed: Internal error Robot goes into obstacle for more than 3 ITPs before resulting the priority issue Remed: Internal error I/O Point used for combination checking is invalid Remed: Use a non-zero index for the corresponding I/O point Collision Detected for the group You attempted an operation while the hold button (input) is pressed. If a HOLD statement is executed in a Karel program, the held condition can only be cleared by the same program using the UNHOLD statement/action, or by aborting the program. If a motion is attempted in such condition, this error message is displayed. The attempted operation could not be done because the teach pendant is enabled. The attempted operation could not be done because the System Operator Panel is enabled. The attempted operation could not be done because the User Operator Panel is enabled. The attempted operation could not be done because KCL is the master device. The attempted operation could not be done because the NETWORK command processor is the master device. The system variable $RMT_MASTER is set to disable all devices. Therefore, no remote device can issue motion. The attempted operation could not be done because the safety fence is open. The number of task has reached the maximum. The system has failed to run the program. Remote condition is not satisfied. The specified PNS number is not in the range of 1 to 9999. PNS operation has failed by some reason. RSR operation has failed by some reason. ENBL signal in UOP is off Single step operation is effective Attempt to continue program from different line from paused line Program has not been selected Program specified by PNS is different from current selected program. This error occurs in R-J Mate only An error has been detected by the system Paused program cannot be continued if PNS input ports are not zero This error occurs in R-J Mate only A communication cable is broken. Because PNSTROBE is off, prod_start could not be processed The type of teach pendant being connected, is different from the one that was disconnected. System has executed normal power startup HOT start has failed for one of the following reasons: 1. Power failed during system start up. 2. Flash ROM module was changed. 3. A run-time error occurred. 4. System internal error 1. 5. System internal error 2. $PWR_HOT,$PWR_SEMI program has been aborted by the system due to time out (40sec) The connect/isolate key was turn to the connect side The connect/isolate key was turn to the isolate side An error has occurred accessing F-ROM ENBL input signal from UOP is lost SFSPD input signal from UOP is lost HOLD input signal from SOP/UOP is lost Battery in PSU board is low in power. System did semi-hot start Improper input from Key switch Operation mode T1 Selected Operation mode T2 Selected Operation mode AUTO Selected DI index is invalid The mode switch was changed from T1 or T2 mode to AUTO mode and the DEADMAN was already pressed. The DEADMAN must be released when switching to AUTO mode The mode selector is in T1 or T2 and the TP ON/OFF switch is in the OFF position The mode selector is in T1 or T2 and the TP ON/OFF switch is in the OFF position and SVOFF is ON. This is an abnormal condition. The mode selector is in AUTO and the TP ON/OFF switch is in the ON position Either 1.Control Reliable or CE Mark hardware exists but the CR or CE Mark option has not been loaded,or 2.The Control Reliable/CE Mark option has been loaded but the hardware is not available. Attempt to continue program from distant position from stopped position. OS couldn't give NECALC soft part enough memory OS couldn't give SFCALC soft part enough memory Invalid time used in TG request Excessive time iin trigger routines First number indicates event routine (1) or scan routine (2). Second number indicates individual overrrun (1) or excessive cumative CPU use (2). Third number: event number(hexadecimal) or scan routine address Fourth number: limit (microseconds or 100ths of one pct) Fifth number: time used (microseconds or 100ths of one pct) Specified entry already used Specified Fast-DIN number is invalid Specified event ID already in use Specified event ID is not presently in use A call to syscnrtn was made when the scan list was full. A maximum of 10 scan routines, including the standard table scanning routine, may be active at one time. The interval parameter in a call to syscnrtn was greater than 1000000 (1 second). syscnrtn was called specifying a routine and data_p that is already being scanned syclclsc was called with a routine and data_p that that does not match any active scans syaddtbl called with pointer to table that is already in the scan list syaddtbl called when all 10 condition/action table slots are already in use sycncltb called with cond/act table that is not active. System error: consecutive time interval start calls System error: Invalid data in scan table The following can result in this error: Too many cond/action sets (max = 10) Invalid condition code Invalid action code Too many actions (max = 3) SFCALC task can't get enough MPU power. Communication with the Teach Pendant was interrupted. Panel HSSB communication is disconnected. The selected style number is zero or greater than the size of the style table. There is no program name in the style table. The selected style program does not exist on the controller. The selected style program is not enabled. The style input does not match the manually selected style. Communications with the Karel shell extension failed. The shell was unable to start due to resource allocation failures. The shell could not set up its required condition handlers. The controller is interlocked with the PLC The controller is isolated from PLC control. One or more of the pre-startup system checks failed. The system is in a faulted state. The program can not start because the robot is not at the defined home position. The program can not be resumed because the robot has been moved from the position on the path where it stopped. One or more I/O points are simulated. The system has forced all I/O to be unsimulated. The general speed override is not 100% The system has forced the general speed override to 100% The program override is not 100%. The system has forced the program speed override to 100%. The machine lock is on, motion can not occur. The system has forced machine lock to the off state. The program is in single-step mode. The system has forced single-stepping to be off. The program can not start because the process is not ready. The system has forced the process equipment to the ready state. Internal Error in Remote Diagnose function. User bypassed not-home condition at program startup. User bypassed TCP position tolerance at program resume. User bypassed I/O simulated at program startup. User bypassed general override < 100% at program startup. User bypassed program override < 100% at program startup. User bypassed machine lock at program startup. User bypassed single-step condition at program startup. User bypassed process not ready at program startup. No home position defined for motion group 1. The production start input, which is required with the current program selection options, has not been defined. The style number input group, which is required with the current program selection options, has not been defined. One or more RSR inputs, which are required with the current program selection options, have not been defined. One or more PNS selection inputs, which are required with the current program selection options, have not been defined. One or more RSR echo outputs, which are required with the current program selection options, have not been defined. The PNS echo outputs, which are required with the current program selection options, have not been defined. The PNS strobe input, which is required with the current program selection options, has not been defined. The acknowledgement strobe output, which is required with the current program selection options, has not been defined. One or more style option inputs, which are required with the current program selection options, have not been defined. The decision code input group, which is required with the current program selection options, has not been defined. The echo/manual style output group, which is required with the current program selection options, has not been defined. One or more style option outputs, which are required with the current program selection options, have not been defined. The decision code output group, which is required with the current program selection options, has not been defined. The in-cycle output, which is required with the current program selection options, has not been defined. The task_OK output, which is required with the current program selection options, has not been defined. The isolate mode output, which is required with the current program selection options, has not been defined. The interlock mode output, which is required with the current program selection options, has not been defined. The manual style request output, which is required with the current program selection options, has not been defined. The shell is already running an active program. The manual style request cannot be done. There is also a secondary error posted that gives the reason. The specified manual style was not requested by the PLC within the allowable time period. A request for a system trigger function (scan routine, etc) was made before the tables for these are initialized. A frequency input connected to one of the HDI inputs momentarily or for an extended time had a frequency exceeding the setting for the maximum. The channel or input number is indicated in the alarm text. The system clock has an invalid time. The clock may not have been set. The system clock was reset by an Operator. The requested device is not installed on the motherboard. The specified motherboard is not installed. The specified motherboard index is not a valid value. An invalid interrupt number was specified by the device driver. BMON was automatically updated because of a newer version. The time specified for a timed event has already passed The event will trigger immediately pkt_data_size parameter in syinpev_gen call is too big. Invalid or unassigned DOUT number specified in the indicated system variable. DOUT specified in the indicated system variable is Off-line. n_pkts_parameter in syinpev_gen call is invalid. Dynamic Brake is disabled by dynamic brake release request signal (DI[$DYN_BRK.$DI_IDX]). Dynamic Brake is enabled because dynamic brake release request is turned off. The program is started except from the 1st line. After the program is started except from the 1st line, respond YES in the prompt box on at the teach pendant. Attempt to force output signal while controller is in AUTO mode Attempt to force output signal while controller is in AUTO mode Production start received when controller is in ISOLATE or BYPASS mode ARM Bending Control function can't get enough MPU power. This PCB is not used on this controller. CE/RIA software does not exist in this controller. The mode selector is in T2. Robot cannot move in T2 mode. GO dedicated for the Error Output feature is not configured Value to be outputted to GO with Error Output feature is out of limit for this group output. Remote diagnostic is not started because the servo is on status. Servo is turned ON during remote diagnostic Attempt to operate IO during Remote diagnostic Communication with the Teach Pendant was interrupted. Intermittent error happened on the communication with the Teach Pendant. Intermittent error happened on the communication with the Teach Pendant. Motion initialization is intentionally disabeled. Attempt to operate on an isolated Robot S/W Registration is in effect S/W Registration is in effect S/W Registration is in effect S/W Registration is in effect S/W Registration is in effect Invalid System System was updated System softwre is updated by Auto Software update function. Internal system error The Through Arc Seam Tracking (TAST) variables are not loaded An IO memory allocation error has occurred An analog port number error has occured IOSETRTN error has occurred Time tick missing in TAST IO memory An IO memory disposition error has occurred RPM data saving error has occurred An invalid TAST schedule number was specified An invalid weaving frequency was specified for TAST Internal system error (SRIF) Internal system error (PMPT) Internal system error (INTP) Internal system error Weaving frequency is too high for TAST System internal error. TCP Speed Prediction global variables are not loaded. This is an internal system error. This is an internal system error. This is an internal system error. This is an internal system error. A failure occured while allocating memory. This is an internal system error. This is an internal system error. The program positions prior to this line are too close together to allow proper speed prediction to be performed. It is also most likely that the robot can not perform at the programmed speed either. This is an internal system error. The first motion segment time (time between first two taught points) is shorter than the prediction equipment delay time as specified by $TCPPIR.$TCDELAY. The motion was commanded using an invalid motion filter type. The start position is not valid. The destination position is not valid. The time computed for the current segment exceeds the segment length. The Cartesian Filter data is not valid. The internal Motion Done computation generated an error. The program positions beginning with this line have caused an error condition which makes further speed prediction invalid. The speed prediction task has therefore entered an error handling mode within which it discontinues speed prediction but provides the actual robot speed as an output reference with an affective equipment delay time of 0. (That is, with $TCPPIR.$TCDELAY = 0.) A speed override occured beginning with this line causing an error condition which makes further speed prediction invalid. The speed prediction task has therefore entered an error handling mode within which it discontinues speed prediction but provides the actual robot speed as an output reference. Internal error when searching cart segment. Internal error when allocating memory to TCPP AccuPath segment. Internal error specified delay time for TCP extention is too big A failure occured while writing I/O or register. Minimum speed is not less than maximum speed. Specified index of TCP_SPD[] is invalid. Specified target type is invalid. The Tool Change Setup is disabled. Machine lock for robot axes is enabled at TOOL ATTACH instruction. Tool number assignment are wrong . Tool is not detached. Some AXISORDER are not 0. Tool is not detached. Tool attach input signal is OFF. Tool is not attached. Tool attach input signal is ON. Another program is executing TOOL ATTACH or TOOL DETACH instruction. $CHG_PHASE is not 0 at executing the instruction. Tool identify signal is OFF. Tool set signal is OFF. TOOL ATTACH or TOOL DETACH instruction is canceled while executing the instruction. TOOL ATTACH or TOOL DETACH instruction becomes timeout while executing the instruction. Mastering data of the tool is lost by a pause while mastering. Tool mastering is failed by a pause while mastering. TOOL ATTACH instruction failed. Please see cause code. TOOL DETACH instruction failed. Please see cause code. The mastering of servo tool axis has not been performed yet. System variable $master_done set FALSE. The calibration of servo tool axis has not been performed yet. System variable $calibrate set FALSE. Reference position has not been set when quick mastering. The another tool which is different from the tool number specified by TOOL DETACH instruction is attached. While the calibrate motion, the detect condition was not triggered. The PR[] index for the calibrate motion is not set. The Touch torque for the calibrate motion is not set. The Detect signal for the calibrate motion is not set. At the calibration motion, Servo tool axis does not stop. Illegal case occured on software. Illegal case occured on software. Illegal case occured on software. Illegal case occured on software. The program was not selected yet, when the program was displayed at the TEACH screen. This taught statement needed the SELECT statement before the current line. The robot has not been calibrated properly. The program is write protected. Program is protected Program is protected Item is not found below this line Cannot translate position data You cannot select a program when another program is running or paused. You cannot edit a program when the teach pendant is disabled. Specified aa invalid index of position register Illegal case occured on software. Illegal case occured on software. Specified index value is invalid. This item cannot be replaced Illegal case occured on software. Illegal case occured in software. Wjnt and RTCP are not compatible. Program name is not set properly. Start of program name is numeric. Space is included in program name. Comma is included in program name. Dot is included in program name. Minus is included in program name. There is not enough memory available. Only the Teach Pendant default program can be edited on the CRT Invalid character in program name Same label No. already exists Specified MNUTOOLNUM number is invalid Specified MNUFRAMNUM number is invalid You cannot change the robot (group), because the function that select robot by external DI is valid. The group mask of program differs from selected robot (group) Cannot teach more than 16 Palletizing instructions in one program, Too many motion options for default motion Program type is wrong There is currently no program running that can be monitored. Port is not set for outside device A program is not assigned to this macro command When a program has been selected by PNS, you cannot select program from SELECT screen When the Disabled FWD function has been selected, you cannot execute the program by TP The program has not been selected by BACKGROUND editing 1. There is not enough memory. 2. The background program is invalid. Failed recovering original program which has been selected by the BACKGROUND The program of BACKGROUND cannot be selected by the CRT and TP at the same time The program of BACKGROUND cannot be selected by the CRT and TP at the same time This current position is in singularity This position data has not been changed to displayed groups because you selected the function key which did not record the position, when checking in singularity All AND operators on this line were replaced with OR operators. All OR operator on this line were replaced by AND operators. You cannot mix AND OR operaotr on a the same line Too many AND/OR operators (Max.4 on a single line) Arithmetic operator on this line was changed to +- or */. Cannot mix arithmatic + and - operators with * and / operators on the same line. Too many arithmetic operators (Max.5 on a single line) Too many arguments (Max.10 for a program or a macro) Too many items in one line. Cannot teach the instruction. Cannot change sub type Cannot change motion group The program specified in $PWR_HOT, $PWR_SEMI and $PWR_NORMAL must not have motion group. An error occurred when accessing a position register. The value_array that was passed to a built-in was incorrectly specified. The error line shows the index into value_array where the error occurred and the type expected by the built-in. A KAREL program called a user interface built- in which required the USER menu to be displayed on the teach pendant or CRT. A KAREL program called a user interface built- in which required the USER2 menu to be displayed on the teach pendant or CRT. Software internal error The execution history of the executing program cannot be displayed The program of $PWR_HOT, $PWR_SEMI or $PWR_NORMAL is not executed The program specified in $PWR_HOT, $PWR_SEMI and $PWR_NORMAL is not executed, when the program is in editing. Illegal case occured on software. Illegal case occured on software. FWD execution is selected while, E.STOP is asserted. FWD execution is selected while, DEADMAN switch is released. FWD execution is selected while, TP is disabled. FWD execution is requested without selection of program. FWD execution is requested when program is running. When the Disabled FWD function has been selected, you cannot execute the program by TP The Form Manager detected an error on the specified line with the specified item. The Form Manager detected an error when displaying a %v item. The screen you are attempting to use on the TP is currently displayed on CRT or the screen you are attempting to use on the CRT is currently displayed on TP System variable name is invalid The default device is not valid for backup File error Failed creating compressed file Device failure Cannot COPY a file on a Memory device to the same Memory device. The reverse motion copy function does not support the following motion option instruction. 1. Application command 2. Skip, Quick Skip 3. Incremental 4. Continuous turn 5. Time before The group motion instruction is copyied. The reverse motion copy function does not supported group motion instruction. This program has no application mask Because the data for UNDO can not be saved, this operation can not recover by UNDO function Palletizing command and Compliance control command can not be recovered by UNDO function CTRL Upgrade is Armed CTRL Upgrade has Started CTRL Upgrade Restore Failed Position ID cannot be changed by the system variable setting Edit screen can't enter P-SPS while program is paused outside of the P-SPS. Edit screen can't exit P-SPS and enter the caller program while program is paused inside of the P-SPS. This program has no motion group defined. The MOTION instruction cannot be teached. P-SPS is executed when the program is paused in parent line. System internal error Illegal joint move error System internal error System internal error Schdule out of range error Destination out of window error Destination out of window error System internal error Semi hot start is not supported for this function error Illegal cartesian move error The Line Tracking function pointers do not exist. error Wrist-joint motion is not supported for CIRCULAR motions during Line Tracking. error Maintenance program is not supported for Tracking. error The TCP (Line Tracking) or Extended Axis (Rail Tracking) has been commanded beyond the Entry Limit defined in the *System* parameter, ($LNCFG.$ENTRY_XTRM). The TCP (Line Tracking) or Extended Axis (Rail Tracking) has been commanded beyond the Exit Limit defined in the *System* parameter, ($LNCFG.$EXIT_XTRM). An error has occured trying to read specifed file. This file is corrupt or the media is bad The variable file does not exist on the device, director or media. A variable being loaded from a variable file exists in memory. The array length reflects what was in the variable file. A variable being loaded from a variable file exists in memory. The variable file data cannot be loaded A variable being loaded from a variable file exists in memory. The array length reflects what was in the variable file. Referenced variable does not exist Referenced type code does not exist Referenced type name does not exist A variable load has been requested while controller is capable of motion The variable or field you are trying to access is write protected Referenced program name does not have variables Named variable could not be created. Referenced variable already exist in memory Named type could not be create The limit of variables types, programs or nodes has been reached The variables you are trying to load are were created on a controller with a different axis configuration The system variable file you are attempting to load is not compatible with the loaded software version Referenced type already exists in memory You are attempting to rename a program to a program which already exists Referenced variable is not found in the system There is no more permanent memory available in the system Variable that is being created already exists but is of a different type than what you are attempting to load/create Variable that is being created already exists but has different dimensions than what you are attempting to load/create You are attempting to use an invalid index into an array or path Do not have vision hardware on this system so cannot load vision variables The file which has been loaded is: A. Not a variable file B. A file on bad media C. A file not compatible with your current software. Variable is used by another program Value that you entered is not a valid value. It is either too big or too small The operation that you are attempting is password protected. The operation that you are attempting is password protected. The operation that you are attempting is password protected. The variable you are loading is larger than 65,535 bytes or has an array element larger than 32,767 bytes A path can only contain 2,007 nodes. The CMOS variable that you attempted to delete was created This could also be because a KAREL program, Network or KCL was adding deleteing or doing a node operation when access was attempted CMOS memory has been destroyed Position register is locked by program operation An existing variable is being created in a different memory area (CMOS vs DRAM) Permanent memory was successfully allocated. Variables may not be properly created if loaded at this time. Path insertion or delete of a node occured with node number which exceeded the number of nodes in a path. The type definition for the variable being created is in temporary DRAM memory. This means variable cannot be remembered after power off The memory pool for this variable does not exists on the controller. An auxiliary board has probably been removed or replaced The variable file has different number of groups defined than controller. The robot type referenced in the loaded SV file is different than the type that the controller is setup for. The version of the saved PC image and saved VR image are different. This is probably because power was removed in the middle of the operation. A system variable file created on an earlier version has been loaded. The specified variable changed since that early release so it has been converted. Some infommation in the system variable may have been lost The variable data pointer specified is incorrect Or an invalid pointer was sent to the controller from a PC. A system variable file created on an earlier version has been loaded. Another program exists with the same program name in first eight Characters. Program name must be unique in the first eight characters. Internal system error Weave variables not loaded Internal system error Not enough memory Weave system variables not loaded or initialized Internal system error Invalid weave schedule number Frequency value invalid Weave amplitude value invalid Weave dwell value invalid Several weave statements pre-executed Internal system error Stop dwell is specified but the program has multiple groups. Stop dwell is not supported for multiple groups. Moving dwell is executed. Weaving vector can not be calcurated because direction of weaving vector is not correct Wrist axes reaches to its limit Joint 5 is too close to zero Unknown wrist configuration error The angles of Weaving direction away from its best direction is larger than allowed tol_ang The current utool has null value Format of screen name in DEF_SCREEN, ACT_SCREEN, or ATT_WINDOW_S call is invalid. Format of window name in ATT_WINDOW_D, ATT_WINDOW_S, or DET_WINDOW call or an OPEN statement is invalid. Invalid display device name in DEF_SCREEN or ATT_WINDOW_D call Invalid format of display device name in DEF_SCREEN or ATT_WINDOW_D call Invalid n_rows in DEF_WINDOW call Invalid n_cols in DEF_WINDOW call Invalid value of row parameter in ATT_WINDOW_S, AT_WINDOW_D, or SET_CURSOR call Invalid value of col parameter in ATT_WINDOW_S, AT_WINDOW_D, or SET_CURSOR call Unknown display device name in DEF_SCREEN or ATT_WINDOW_D call Keyboard device specified in a PUSH_KEY_RD or POP_KEY_RD call or OPEN statement is invalid Screen name specified in DEF_SCREEN call is already defined Window name specified in DEF_WINDOW call is already defined The screen name specified in a ATT_WINDOW_S, DET_WINDOW, or ACT_WINDOW call is not defined The window name specified in a ATT_WINDOW_S, ATT_WINDOW_D, or DET_WINDOW call or an OPEN statement is not defined The window name specified in a ATT_WINDOW_S, ATT_WINDOW_D is ready attached to the specified screen The file name in an OPEN statement begins WD: or KB: but is not a valid format. A write was issued to a file opened to a keyboard (KB:knam), but not a window The buffer_size parameter in a INI_DYN_DISI INI_DYN_DISR, INI_DYN_DISS or READ_KB call is invalid The time_out value in a READ_KB call is Invalid The terminate character mask in a keyboard read is zero. The init_data value is longer than the buffer size parameter A READ_KB call or READ statement was executed on a file that was OPENed to a window but not a keyboard A READ_KB call was executed where the specified file is opened to a window that is not attached to the active screen and the terminate mask included the no_window bit A READ_KB call was executed where the the keyboard for the specified file currently has another READ_KB call or READ statement that accepts some of the same classes of keys and the terminate mask included the kbd_busy bit The maximum depth of key read PUSH operations has been exceeded. This indicates that the pop_index specified in a POP_KEY_RD call is not the expected value, indicating that call are being made out of order. The interval parameter in a INI_DYN_DISI, INI_DYN_DISR, or INI_DYN_DISS call is invalid There is no currently active dynamic display for variable and window specified in a CNC_DYN_DISI, CNC_DYN_DISR, or CNC_DYN_DISS call. The field_width parameter in a call to one of the INI_DYN_DIS builtin routines is invalid. The window specified in a DET_WINDOW call is not attached to the specified screen. Remedy To Be Determined Change the schedule number to one shown in the weld data screen. Check the gas supply. Check the gas valve and the gas flow switch. Check the gas supply. Check the wire supply. Check the water supply. Check the power supply. Secure the robot and equipment. Cut the wire. Secure the robot and equipment. Cut the wire. Secure the robot and equipment. Cut the wire. Check the wire and weld equipment. Adjust the weld schedule and/or adjust the arc detect time in the Weld Equipment SETUP screen. Enable the teach pendant. Try again while holding the shift key. Disable the arc for testing from the teach pendant or change the Weld System SETUP to permit welding during teach pendant execution. Welding can be enabled using the teach pendant arc enable key or the remote arc enable input. Also check the machinelock and dry run settings in the Test Cycle screen. Check the wire feeder. Check the welding schedule, speed or arc loss time. Check the process I/O board connection. Try reducing the number of programs. Check if the program ends without an Arc End instruction. Modify the weld parameters used in the arc instruction to be within the equipment limits. Use a register that is an integer type. Enter new min or max values for the equipment. Modify the correct system variable fields within $AWEPRR. Turn off the controller and turn it on again. Secure the robot and equipment. Cut the wire. If no motion is needed during welding, increase the arc loss time in the Weld Equipment SETUP screen or disable arc loss detection in the Weld System SETUP screen. To continue welding you must exit single step mode. Set the speed override to 100% to weld or disable welding to continue at a low speed. Allow the task which has weld control to end or abort before attempting to weld with another task. Please set the equipment number to the program attribute data or the arc instruction Please change the equipment mask Please stop wire inching for another equipment by releasing the shift key or user key Please control the equipment by the another task Adjust the weld analog output scaling in the Weld I/O screen using the CONFIG function key. Verify the I/O hardware is connected and the signal is assigned a port number in the Weld I/O screen. Use the CONFIG function key if the signal is unassigned. Add the DeviceNet option or choose a weld equipment model which does not require DeviceNet. If the weld equipment model is correct and does not require DeviceNet then set the $AWEPRR fields mentioned above to zero and cycle power. Add the Explicit Messaging option or choose a weld equipment model which does not require DeviceNet. If the weld equipment model is correct and does not require DeviceNet then set the $AWEPRR fields mentioned above to zero and cycle power. Add DeviceNet hardware or choose a weld equipment model which does not require DeviceNet. If the weld equipment model is correct and does not require DeviceNet then set the $AWEPRR fields mentioned above to zero and cycle power. You can add a DeviceNet definition for this product or if the weld equipment you are using does not support DeviceNet you can set the $AWEPRR fields mentioned above to zero and cycle power. Verify the Weld Equipment is ON. Verify the DeviceNet cable is connected. Check the DeviceNet I/O screen board status and device status. Verify the Weld Equipment is ON. Verify the DeviceNet cable is connected. Check the DeviceNet I/O screen board status and device status. Try the operation after the program ends or is aborted. Verify mounted I/O module and set system variables of $AWEPRR[] in system variable screen manually if need. The weld power supply may be OFF, unconnected, or data in the second process may be incorrect. Enter a different number or use the SEARCH parameters and function key. This message is for notification and information. It does not indicate a problem. Enter a number within range. Complete the process switch first, then ramp with another arc start instruction. If no motion is needed during welding, increase the above time in the system variable screen. Sometimes this error requires cycling the controller power. Please change the program. Please set it. Please set correct value. Please set conversion factor more than 2 tables Please select the correct number of AO conversion factor data Please remove the specified reason to perform the welding. Please select the correct wire materal. Please select the correct wire size. Please select the correct unit of inching speed If another alarm is also occured at the same time, please check it and remove the cause of the alarm. If no other alarm is occured, some internal error is occured. Internal error. Cycle power to recover. Confirm which type of weld equip is used. Confirm the connection with serial communication power supply. Confirm the setting of serial port. Remove all Robowelds by selecting other equip in weld equip select screen. Then select and setup Roboweld again, if you want to use Roboweld. Cycle power to recover. Verify that AI/O and WDI/O signals are assigned appropriately. This is not an error. There is no need to do anything. Verify that AI/O and WDI/O signals are assigned appropriately. Change memory module into the one which has appropriate size and do INIT start. Reset and try again after Arc OFF. Set proper wire size. Set proper welding process. Set proper wire material. Set proper arc loss time. Confirm port setup and connection cable. Please call FANUC service. Confirm noise environment and cable. Check currency. Check currency. Check overload. Check voltage. Check voltage. Check start signal. Check 3-phase power source. Confirm port setup. Confirm another error message and port, cable setup. Confirm another I/O device and $IO_START in $RBWLD. Confirm another I/O device and $IO_START in $RBWLD. Confirm wire control sequence. Confirm welding device and workpiece status. Confirm port setup, noise environment, cable status. Confirm noise environment, cable setting. Confirm noise environment, cable setting. Confirm noise environment, cable setting. Confirm welding setup, cable connection, then reset. Confirm $RBWLD and $RBWLD_CFG setup. Arc welding is now available. Confirm RS-422 communication line. After check try again. If the same alarm occurs, inform of the service. Check the wire feeder motor. After check try again. If the same alarm occurs, inform of the service. Check the wire feeder motor sensor line. After check try again. If the same alarm occurs, inform of the service. If the motor was rotated actually, the control board in wire feed controller may be broken. Turn off the power and remove the reason then power on. Remove the reason. Remove the reason. Turn off the power then try again. If the same alarm occurs again, inform of the service. Turn off the power then try again. If the same alarm occurs again, inform of the service. #NAME? Check the setup of process type, wire size, wire material in weld equipment setup screen and pulse mode in weld schedule. Then change them. Check the Arclink connections and the weld controller devices that are on. the Arclink network. Check the Arclink connections and the weld controller devices that are on the Arclink network. Check the Arclink connections and the weld controller devices that are on the Arclink network. If this is unexpected, then check the connections and other devices on the Arclink network. The Arclink network is ready for welding. The Arclink network is automatically reset. If this error persists, it indicates a problem with the communications network or welding equipment. Check Arclink network connections and shielding. Check Arclink network connections and shielding. Check the Arclink cable connections and make sure that the welding equipment is also connected and powered on. Check the Arclink cable connections and noise sources. Cycle power on the robot controller and weld controller. If this problem persists, contact tech support. Perform a controlled start and initialize motion softparts. Check amount of memory being used by the system. Call FANUC Robotics. Call FANUC Robotics. Check motion statement. Perform Coordinated Motion SETUP and perform a COLD START. Use LINEAR or CIRCULAR MOTYPE instead Use LINEAR MOTYPE instead Check motion statement. Perform Coordinated Motion SETUP and then perform a COLD START. Check motion statement. Perform Coordinated Motion SETUP and then perform a COLD START. Internal Error, call FANUC Robotics. COLD START. Issue non-coordinated motion involving the follower group Select leader group for coordinated jog Select only one leader/follower pair Delete Wjnt motion instruction Delete INC instruction Change Independent motion to Simultaneous motion Execute calibration of coordinated motion in SETUP screen Set number of follower correctly or set group mask correctly Teach follower and leader position again to reach relative speed Initialize robot library correctly Change term type before coordinated motion to FINE or CNT0 or JOINT motion Check setting of coordinated motion in SETUP screen And set correctly Check the mechanics and reteach the points Call FANUC Robotics. Add or remove motion option COORD. Insert non coordinated motion between coordinated motion of different pair. Specify slower speed or change to AUTO mode. Check the device and path that you entered. If none entered, check the system default device from the FILE Menu or from the KCL command, CHDIR. Check to make sure the file has been spelled correctly and that it exists. Also verify the device and path name are correct. Make sure the overwrite option has been specified. Change the name of the destination file so it is different from the source file. The valid postion types are POSITION, JOINTPOS, XYZWPR, and XYZWPREXT. The valid postion types are POSITION, JOINTPOS, XYZWPR, and XYZWPREXT. Internal error. Insure that the type code matches the variable type. Both positions must be the same type. Convert one before comparing. The two positions were not equal within the specified tolerance. This could be a normal occurence. This warning is the logical opposite of SUCCESS. If calling ATAN2, insure that both arguments are not zero. If converting a POSITION, then it is not converable to an XYZWPR. This is an internal error. Insure that the divisor is not equal or close to zero. Make sure that the rotational angle is no greater than 100 times PI, or about 314.15926... Check the device and path that you entered. If none entered, check the system default device from the FILE Menu or from the KCL command, CHDIR. Repeat the operation. This is a notification. You do not have to do anything for this warning message. Use only alphanumeric characters or a single global character when renaming a file. Do not use these options in combination. Perform a controlled start and initialize motion softparts. Perform a cold start on the controller. Perform a cold start on the controller. Perform a controlled start and initialize the motion softparts. Check Continuous turn axis, cn_gear_n1, and cn_gear_n2 Select different continuous turn axis and/or set correct gear ratio for continuous turn axis. Check amount of memory being used by the system. Record error and report to hotline Check compatibility of motion options. Remove other options. Lower contaxisvel. This warning may be ignored if cn_turn_no is not used. Remove Ind.EV option or disable continuous turn on the group Lower the speed either through KAREL or Teach Pendant Continuous Rotation must be ended with an absolution motion Use an absolution motion to end continuous rotation Check for condition statements to verify if the specified condition has really been created or not. This is just a notification, and you do not have to do anything for this warning message. This is just a notification, and you do not have to do anything for this warning message. This is just a notification, and you do not have to do anything for this warning message. No action is required. No action is required Either renumber the condition handler or avoid re-defining the same condition handler. Reduce the number of conditions defined. System probably out of memory. Cold start. All parameters must have a value when calling the create a data buffer to PC built-ins. Check program and variable name spellings. Check variable data type. Only integer, real and string data is supported. The variable requested in the ADD Byname or Send SysVar routines is of a data type that is not supported. Check variable data type. Only integer, real and string data is supported. Check program and variable name spellings. An ADD PC buffer built-in was called with the index parameter set too big or too small. Set the index parameter correctly. Make sure the data buffer is big enough for your data. Make sure the data buffer is big enough for your data. If there is too much data to send, you might have to use more than one event to send the data. All parameters must have a value when calling the create a data buffer to PC built-ins. A Send PC built-in was called with a parameter that is uninitialized. All parameters must have a value when calling the send PC built-ins. Use an event number from 0 to 255. Use a legal wait flag. Use a legal data buffer size. Check other alarms in alarm log for details. A Send to PC MACRO was called with a parameter that is illegal. The parameter is uninitialized or the wrong data type. Check the MACRO call in the TP program. Check PC communications. Check PC communications. Status message only. A controller task was waiting for an event flag back from the PC. The PC is taking too long. The controller task has continued without receiving the event flag. Check PC communications. N/A Cold start Check if the register is defined and if it has the right value. Must ABORT ALL and retry N/A Increase the MACRO table size. Check other alarm log errors for more details. Check MACRO parameters. Check MACRO parameters. A send PC MACRO was called with a parameter that is uninitialized. All parameters must have a value. A MACRO was called without a parameter that must be entered. Check the MACRO call in the TP program. Check the TP program. A MACRO was called with a parameter that is illegal. The parameter has the wrong data type. Check the MACRO call in the TP program. Load into a different language and use KCL SET LANG to set the language. Clear all unnecessary programs, dictionaries or variables. Use the DEFAULT language or a language in which a dictionary has been loaded. Use KCL LOAD DICT to load the dictionary into the DEFAULT language or the current language. Check the dictionary or element number to be sure it is specified correctly. Fix the dictionary text file to include fewer nested levels. Remove the close operation. Increase either the size of the string or the number of strings in the array. This is a notification. You do not have to do anything for this warning message. This is a notification. You do not have to do anything for this warning message. Load the dictionary to memory or close an unused dictionary. This is a notification of insufficient memory resources on the controller. The hardware and software configurations need to be verified. Select the proper device/directory and try again. Make sure all dictionary elements begin with $. Check for misspelling or look up the correct word in the KAREL Reference Manual. Make sure all dictionary text is surrounded by double quotes. Use a backslash if you want an actual quote to appear in the text. For example, \"This is an example\" will produce "This is an example" Use the element number to reference the element. Make sure the cursor position is valid. For example, use @1,1 for the first row and col respectively. Remove the # or look up the ASCII character code in the KAREL Reference Manual. Remove the & or look up the reserved word in the KAREL Reference Manual. Make sure all dictionary text is correct. This is a notification. You do not have to do anything for this warning message. Do not try to open the dictionary file. Do not try to remove a dictionary loaded to FROM. Remove the dictionary from the same task which loaded it. This is a notification of insufficient memory resources on the controller. The hardware and software configurations need to be verified. Check the dictionary to be sure the help dictionary element was specified correctly. The help dictionary element must be specified with a question mark (?) followed by the element number. Check the dictionary to be sure the function key element was specified correctly. The function key element must be specified with a caret (^) followed by the element number. Refer to the System Reference Manual for the error message. See error window or the Alarms menu for the error message. Make sure all dictionary elements begin with $ followed by the element number. Make sure all dictionary elements are specified as ",element_name" after the add constant name. Make sure all dictionary elements are specified as "+add_const_name" after the element number. Make sure all dictionary elements are specified in sequential order. Reduce the gap in the element sequence. Each missing element uses up five bytes of memory. Verify that each .LIT is matched with a .END. Remove the extra command. Use the .etx file extension for error text, the .utx file extension for uncompressed text, or the .ftx file extension for form text. Use the .etx file extension for error text, the .utx file extension for uncompressed text, or the .ftx file extension for form text. Specify a file name after the command. Specify the facility number after the file name. Check the command and if a form is used, verify the file extension is .ftx. Verify that each .FORM is matched with a .ENDFORM. Make sure a valid file name has been specified. Abort the KAREL program that is displaying the form. INIT start and reload the DeviceNet Interface option. If the error still exists, document the events that led to the error and call your FANUC Robotics technical representative. INIT start and reload the DeviceNet Interface option. If the error still exists, document the events that led to the error and call your FANUC Robotics technical representative. Turn off controller power. Disconnect one of the DeviceNet motherboards. Re-connect any DeviceNet cables to the other DeviceNet motherboard. Power on your controller. Make sure the board parameters are correct. Make sure the board is properly connected to the network and power is supplied. Document the events that led to the error and call your FANUC Robotics technical representative. Specify a board index between 0 and 3. Specify a MAC Id between 0 and 63 inclusive. Take the board off-line before attempting the operation. Put the board on-line before attempting the operation. Take the device off-line before attempting the operation. Put the device on-line before attempting the operation. Check all network connections. If all connections appear to be in order, re-attempt the command. Initialize the board by attempting to put it on-line, and then cycle power. Then, re-attempt the operation. Cold start the system. If the problem persists, INIT start or reload the system. If the problem continues to persist, document the events that led to the error and call your FANUC Robotics technical representative. Make sure the daughter boards are properly configured and properly seated on the motherboard. Cold start the system. If the problem persists, INIT start and reload the DeviceNet Interface option. Cold start the system. If the problem persists, INIT start and reload the DeviceNet Interface option. Cold start the system. If the problem persists, INIT start and reload the DeviceNet Interface option. If the problem continues to persist, document the events that led to the error and call your FANUC Robotics technical representative. Turn the controller off. Make sure the motherboard is correctly seated on the back plane. Cold start the controller. If the problem persists, document the events that led to the error and call your FANUC Robotics technical representative. Cycle power to the controller. If the problem persists, turn the controller off and check the motherboard connection to the back plane. Cold start the controller. If the problem persists, document the events that led to the error and call your FANUC Robotics technical representative. Turn the controller off and cold start the controller. If the problem persists, delete the board from the Board List screen, reconfigure the board, and re-add devices to the Device List. Cycle power. Also, check the device MAC Id configurations. Check the selected device type on the Device List. Next, check the Defined Device List and the Standard Device Definition List for the required device type. If it does not appear, go to the Defined Device List and add the required device definition, then select it on the Device List screen. When you have finished, turn off then turn on the controller. Make sure the device is properly connected to the network. Check the device's MAC Id and baud rate configuration. Check the board's baud rate configuration on the Board Detail screen. Check the board's network connection. Cold Start the controller. Make sure the board is properly connected to the network. Check that network power is being supplied. Check that baud rates for the board and devices are in agreement. Cold Start the controller. Contact your FANUC Robotics technical representative to obtain a correct device definition file. Contact your FANUC Robotics technical representative to obtain a correct device definition file. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Cycle power to the controller. You will then be able to bring the device online. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Turn off the controller and make sure the motherboard is properly seated into the back plane of the controller. Cold start the controller. Remove the DEFAULT designation from all I/O access modes except one. Refer to the next DNET alarm posted in the alarm log for specific alarm recovery information. Check your network topology to ensure conformance with DeviceNet standards. Check that your network terminators are in place and properly connected. Check that your network power supply is able to handle all of the devices on the network. Ensure that you are using properly shielded cables and connectors. Contact your FANUC Robotics technical representative to obtain the correct device definition files. Check the Standard Device Definition List to see if device types have been properly loaded. If not, contact FANUC Robotics to obtain the correct device definition files. Contact FANUC Robotics to report the problem. Provide all details of the DeviceNet network, including number and type of devices, baud rates, MAC Ids, and network wiring configuration. Refer to the Cause and Remedy of the cause code (displayed immediately below this error code on the teach pendant). Check the cable connecting the daughter board to the DeviceNet network. Also, check the connection to the power source. Cycle power to the controller. Check that the board's baud rate corresponds to that of the devices. Check cable connections to both the board and devices. Check that the proper device definitions are selected for the devices on the network and that parameters are correct for user-defined devices. Turn off both the controller and the DeviceNet network power, then cold start the controller. The problem may be momentary; attempt to bring the board on- line again. If the problem persists, check that the board baud rate corresponds to the baud rate of the devices. Turn off then turn on the controller. The problem might be momentary; attempt to bring the board on- line again. If the problem persists, check that the board baud rate corresponds to the baud rate of the devices. Turn off then turn on power to the controller. Check that the board baud rate agrees with the baud rate of the devices. If no baud rate problem exists, turn off both the controller and the DeviceNet network power, then turn on both. Check cable connections to the board and to the devices. If a device has been disconnected, reconnect and press RESET on the teach pendant. Check that the board baud rate is the same as baud rate of the devices. Check that the baud rate of the board and of the devices is the same. Make sure that power is connected to the DeviceNet network. Press RESET on the teach pendant. If the problem persists, begin removing devices from the network; after each device is removed, press RESET. When the board is brought on-line, check the device configuration and the parameters of the device definition. Refer to the Cause and Remedy for the cause code (displayed directly beneath this error code on the teach pendant). Check that the baud rate of the device agrees with the board baud rate. Check that the device is properly connected to the network; make sure the device is receiving power from the network. Inspect the device definition to see that the I/O type, access mode, and size of I/O are correct. Press RESET on the teach pendant to re-attempt connection. Delete the device from the Device List. Check the device documentation for the correct vendor Id. Make corrections in the device definition and add the device to the Device List. Delete the device from the Device List. Check the device documentation for the correct product code. Make corrections in the device definition and add the device to the Device List. Delete the device from the Device List. Check the device documentation for the correct device type. Make corrections in the device definition and add the device to the Device List. Check the device's connection to the network. Make sure the device baud rate agrees with the board baud rate. Attempt to bring the device on-line by pressing RESET on the teach pendant. Document the events that led to the error and call your FANUC Robotics technical representative. Make sure the error code number is noted and reported. Check that the baud rate of the device agrees with the board baud rate. Check that the device is properly connected to the network; make sure the device is receiving power from the network. Inspect the device definition to see that the I/O type, access mode, and size of I/O are correct. Press RESET on the teach pendant to re-attempt connection. Re-configure the DIP switches on your daughter boards so that you no longer have duplicates. DIP switch configuration information is found in the User's Guide to the FANUC Robotics DeviceNet Interface. Please see the Remedy text for DNET-071 to fix this problem. View the module list for the device and delete or change the module in question. If this module was previously functional, cold start the controller and attempt to use this module type again. If the problem persists, perform an INIT start and re-load the DeviceNet Interface option. Reload the .IO file at controlled start. Delete any unneeded device definitions from the Defined Device List before adding a new one. This message is for informational purposes only. To make DeviceNet I/O active, COLD start the controller. If there are devices which are off-line, delete these devices unless they are required to be kept on the Device List. After entries in the device list are freed, new devices can be added. This error occurs during the I/O restore. Cold start the controller, add a new device definition corresponding to the specified device, then add the device to the device list. Make sure you have the same memory configuration as the system on which the I/O configuration was saved. Pressing RESET will attempt reconnection with the non- communicating devices and clear this message. This message is intended for user notification only and does not indicate the presence of an error situation. Refer to the Cause and Remedy for the cause code (displayed directly beneath this error code on the teach pendant). Refer to the Cause and Remedy for the cause code (displayed directly beneath this error code on the teach pendant). Check DeviceNet connection to the board, as well as DeviceNet power to the network. If board is already in ERROR state, this error can be disregarded. Check DeviceNet connection to the board, as well as DeviceNet power to the network. If the board is already in the ERROR state, this error can be disregarded. Make sure the device definition data files are the same between the current system being loaded and the system on which the I/O configuration was saved. Contact FANUC Robotics for the correct definition files. Contact FANUC Robotics to obtain the correct device definition files. Contact FANUC Robotics to obtain the correct device definition files. Delete the device, correct the device definition, then re-add the device to the device list. Delete the device, correct the device definition, then re-add the device to the device list. Check that the device baud rate matches the board baud rate. Check also the device's connection to the network. Check that the device baud rate matches the board baud rate. Check also the device's connection to the network. Check that the device baud rate matches the board baud rate. Check also the device's connection to the network. Check that the device baud rate matches the board baud rate. Check also the device's connection to the network. Reset the device if possible. Check that the device baud rate matches the board baud rate. Check also the device's connection to the network. Reset the device if possible. Check the Board Detail screen to see if the board's MAC Id is between 0 - 63, inclusive. If it is not, change the MAC Id to a valid value and press RESET on the teach pendant. If the MAC Id appears valid, cold start the controller. If the problem persists, document the events that led to the error and call your FANUC Robotics technical representative. Check the Board Detail screen to see if the board's baud rate is one of the above values. If it is not, change the baud rate to a valid value and press RESET on the teach pendant. If the baud rate appears valid, cold start the controller. If the problem persists, document the events that led to the error and call your FANUC Robotics technical representative. Check that no other devices have the same MAC Id, particularly those connected to a different master on the same network. Change the MAC Id of the offending device at both the device and on the Device List, and attempt to bring it on-line. If the problem persists, cold start the controller and try again. If the problem continues, document the events that led to the error and call your FANUC Robotics technical representative. If the desired device is already on the network and a second one is not being added, you may ignore the error. Otherwise, change the MAC Id of one of the duplicate devices. Check that the device is connected to the network. Check that the device baud rate matches the board baud rate. Reset the device if possible. Cycle power to the controller. If the problem persists, document the events that led to the error and call your FANUC Robotics technical representative. Press RESET on the teach pendant to attempt to bring the board on-line. If the problem persists, cycle power to the controller. If the problem continues to persist, cycle power to the DeviceNet network. Take the board off-line and re-attempt the operation. Take the board off-line and re-attempt the operation. Take the board off-line and re-attempt the operation. Bring the board on-line and re-attempt the operation. Wait ten seconds and re-attempt to bring the board on-line. If the problem persists, check board connection to the network, baud rate, and network power. Check that the baud rate of the board matches the baud rate of all devices on the network. Also, check that power is being supplied to the network. If the problem persists, cycle power to the controller, and then to the network if the problem continues. Check the device documentation to ensure that the requested I/O connection is supported. Check it the Interface is not the only node on the network. Check the baudrate of the interface and make sure it is the network baudrate. Check physical wiring of the network. Make sure the device is properly connected to the network. Check the device's MAC Id and baud rate configuration. Check the board's baud rate configuration on the Board Detail screen. Check the board's network connection. Cold Start the controller. Cycle power to the controller. You will then be able to bring the device online. Refer to the Cause and Remedy for the cause code (displayed directly beneath this error code on the teach pendant). Refer to the Cause and Remedy for the cause code (displayed directly beneath this error code on the teach pendant). Pressing RESET will attempt reconnection with the non- communicating devices and clear this message. Make sure the remote Master is online and configured properly. Refer to the cause code to determine which parameter is invalid. Make sure the board number is an integer between 1 and 4, inclusive. Make sure the MAC ID is an integer between 0 and 63, inclusive. Check the application installation manual for the proper installation procedure for Delta Tool/Frame. Check the application installation manual for the proper installation procedure for the Delta Tool/Frame system. Check all schedule numbers used within the specified program to verify that they are within the allowable range specified for the $DXSCH[] system variable. Use END_OFFSET or abort program to disable schedule. Check to see if the requested schedule has been disabled before, or whether the requested schedule has not been enabled at all. Check to see if the requested schedule has been disabled before, or whether the requested schedule has not been enabled at all. Notify FANUC Robotics. Notify FANUC Robotics. Do not enable deltajoint with deltatool and/or deltaframe in a schedule. Do not enable deltatool with deltaframe in a schedule. Abort the enabled DX function before this start. Decrease the speed of the Master robot or Check the noize on the Ethernet. Decrease the speed of the Master robot or Check the noize on the Ethernet. Don't change UT of master during robot link. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that let to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that let to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that let to the error and call your FANUC Robotics technical representative. Set up parameter Case: L1 and L2 is differ L2 is longer than L1 This figule don't write Change them like L1 is longer than L2 Case: Length and Width is differ Width is longer than length This figule don't write Change them linke Length is longer than Width Case: R is longer than Width This figule don't write Change R and L2 Case: L1 is too short BRC is differ This figule don't write Change L1 or BRC Case: Length is too short BRC is differ This figule don't write Change Length or BRC Case: L1 is too long BRC is differ This figule don't write Change L1 or BRC Case: Length is too long BRC is differ This figule don't write Change Length or BRC Case: L2 is too short BRC is differ This figule don't write Change L2 or BRC Case: Width is too short BRC is differ This figule don't write Change Width or BRC Case: L2 is too long BRC is differ This figule don't write Change L2 or BRC Case: Width is too long BRC is differ This figule don't write Change Width or BRC Case: $FCMIN_INTR is too short $FCMIN_INTR is differ Change $FCMIN_INTR Case: $FCMIN_INTR is too long $FCMIN_INTR is differ Change Lof Case: BRC is differ Change BRC Case: BRC is long BRC is differ Change BRC Case: MJ is longer then circuit MJ is differ Change MJ Case: MJ is short MJ is differ Change MJ Case: This figule don't write confirm each parameter Case: Cutting time turn out long, in the case Piercing offset is TRUE Piercing offset don't execute Case: This data number don't set up Case: Change speed value Case: Group setup is wrong Case: Speed unit don't set up Set up speed unit in data menu Case: MJ is long MJ is differ Chang MJ Case: Diameter is too long BRC is differ This figule don't write Change Diameter or BRC Check if the device is mounted and ready to use. Check if the device name is correct. Delete any unnecessary files or change to a new device. Release the device protection. If RD set $FILE_MAXSEC else sys err Mount the correct file device. Mount device only once. Check spelling and validity of device name. This is an internal error. Check the validity of the logical unit number. Check validity of directory name. Delete unnecessary files in the root directory. Release the protection to the directory. Check spelling of directory name. Check that the file exists and that the file name was spelled correctly. Release the protection from file. Open the file before accessing. Close file before such operations. Release the lock. Change file size to be correct. This is a notification. You do not have to do anything for this warning message. Check spelling of file name. Use a valid file number which is the ID returned from an open request. Check the spelling and validity of the file type. Check if the protection code is correct. Check if the access mode is correct. Check that attribute specified is valid. You should keep the data block which is returned from the previous FIND_FIRST or FIND_NEXT request. Check if the request code is corect. Dismount any unnecessary devices. Check if the path name is correct. Check that all parameters for the request are valid. Close unnecessary files. Check that the file position parameter from SEEK request is positive and not beyond the end of file. Format the device before using it. Change the new file name to be unique or delete the existing file. Remove all files and directories in the subdirectory before removing subdirectory. Unlock any unnecessary file lock requests. Use a unique name for new sub-directory Open a file with correct access mode. Don't unlock a file that is not locked. You can only unlock files which YOU have locked. Set variable $FILE_MAXSEC to valid value. 800 is a good default value. Use a standard file device (e.g., FR: or RD: Check device OR delete old files on device Do not call kread again until the packet from the previous read has been rcvd Call kread with the same buf_p as was used in the original kread call Start MC access after receiving this message Reinstall Memory Card if you wish to continue Either insert a MC or exchange inserted card with a MC Start Modem Card access after receiving this message Reinstall Modem Card if you wish to continue Remove any non alpha numeric character which is not an underscore. Try one of the following: 1. Remove unnecessary files/programs from the system. 2. Remove unused options from the controller by reloading with fewer options. 3. Add more D-RAM to the system. Adjust Requested Memory Size ($FILE_MAXSEC) to less than or equal to the Max Available Adjust $FILE_MAXSEC Memory Size (Req) to less than or equal to the Max Available (Max) Try again file backup operation to the other device or using the other media. Please check cause code This is a notification. You do not have to do anything for this warning message. Delete the file of this name or choose a different file name. Open a file that does exist on the device. Use only operations supported on floppy disk. Delete some unneeded files or use a disk with sufficient free space. Do not attempt to read beyond the end of a file. Do not attempt to open more than one file at a time. Retry the operation. Remove write protection from the disk or use a disk that is not write protected. Try another disk or reformat the disk. Try another disk, or reformat the disk Clean the disk drive, try another disk, or reformat the disk. Check the cable to the drive and make sure drive power is on. Remove write protection from the disk or use a disk that is not write protected. Check Memory Card I/F unit connection or battery of the card. Format the card with UTILITY menu on FILE screen. 1. Turn the controller OFF. 2. Mount the force control board. 1. Turn the controller OFF. 2. Mount the force control board. Refer to the manual for the force control board. Please check the force control board. Refer to the remedy of the alarm displayed at the same time. Refer to the remedy of the alarm displayed at the same time. Please check the default motion groups in the program. Please check the force control board. Please check the force control board. Please set the correct tool number. Replace the force sensor. No action is required. If you want to change the initial force sensor data, Please change the system variable $CCS_GRP.$INIT_SW to 0. Please initialize the force sensor data. Please set up the system variable $CCS_GRP.$INIT_TOL. Check the force sensor Please specified correct sensor index. Add an OFFSET CONDITION instruction before the INSERTION instruction. Teach the position register. Please check the state of the force sensor. Refer to the remedy of the force control alarm which occurred before this alarm. Select appropriate function type. No action is required. Remove another tuning instruction Execute tuning with a schedule of biggest DOF Please confirm the default data of system variables Please select the default data at the default menu Please enter the index value Please confirm the number of array in the default data ($CCBD_ARRAY[x,y].$BDDN or $CCID_ARRAY[x,y].$IDDN) Please create this statement in this system again Please enter proper data Please enter proper data Please enter proper data Please enter proper data Please confirm and enter proper the data Please confirm the data and enter proper the data in the default data Please confirm the force data of selected program Please confirm and enter the proper data Verify the pushing depth Verify the insert direction in 'Basic Data'. Verify the bearing rotation axis. Do auto tuning and set phase match impedance rate again Verify the groove direction. Verify parent and child relationship And set right parent number Parmitted number of child for retry is only one Parmitted number of child for insertion is only one Prohibited operation If you don't want to synchronized chage, turn off synchronized switch If you want to synchronized chage, turn on synchronized switch Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Select the other directions Contact FANUC Robotics to report the error. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove the source of the noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. This alarm occurs when the number of errors exceeds the serial allowed number or the total allowed number. Therefore, this alarm can be avoided by increasing the serial allowed number (system var $CCS_GRP.$ALARMSERAL) or the total allowed number (system var $CCS_GRP.$ALARMTOTAL). If the alarm still occurs after increasing these numbers, go to the next step. 6. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove any sources of noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. This alarm occurs when the number of errors exceeds the serial allowed number or the total allowed number. Therefore, this alarm can be avoided by increasing the serial allowed number (system var $CCS_GRP.$ALARMSERAL) or the total allowed number (system var $CCS_GRP.$ALARMTOTAL). If the alarm still occurs after increasing these numbers, go to the next step. 6. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove any sources of noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. This alarm occurs when the number of errors exceeds the serial allowed number or the total allowed number. Therefore, this alarm can be avoided by increasing the serial allowed number (system var $CCS_GRP.$ALARMSERAL) or the total allowed number (system var $CCS_GRP.$ALARMTOTAL). If the alarm still occurs after increasing these numbers, go to the next step. 6. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove any sources of noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 6. Replace the sensor head. If this alarm occurs again, go to the next step. 7. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor head. 1. Make sure that the value of 'Insert Force' in 'Basic Data' is not too large. If not, go to the next step. 2. Bad impedance parameters can cause vibration during force control. Increase the Mass value in the impedance parameters. Re-connect or replace the cable. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the force control board. If this alarm occurs again, go to the next step. 3. Replace the R-J3 main board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor head. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove any sources of noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 6. Replace the sensor board. If this alarm occurs again, go to the next step. 7. Replace the sensor head. 1. Check the temperature around the sensor head. If it is not low, go to the next step. 2. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 3. Replace the sensor board. If this alarm occurs again, go to the next step. 4. Replace the sensor head. 1. Check the temperature around the sensor head. If it is not high, go to the next step. 2. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 3. Replace the sensor board. If this alarm occurs again, go to the next step. 4. Replace the sensor head. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Check the force sensor output data on TP (Force sensor status screen). The value must vary slightly over time due to sensor background noise. If the value is constant, it is frozen; go to the next step. 2. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 3. Replace the sensor board. If this alarm occurs again, go to the next step. 4. Replace the sensor head. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Remove any sources of noise in the sensor system. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 4. Make sure that the shield lines of the cables are connected to the frame ground. Make sure that the peeled part of the cable in the cabinet is properly connected to the earth plate. If this alarm occurs again, go to the next step. 5. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 6. Replace the sensor board. If this alarm occurs again, go to the next step. 7. Replace the sensor head. Refer to the remedy of the alarm displayed at the same time. 1. Gradually increase the values of the 'Mass' and 'Damper' impedance parameters. 2. Decerase the value of 'Insert Force' or 'Pushing Force' in Basic Data. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor board. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Replace the sensor board. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Move the robot to a safe pose. 2. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 3. Check the sensor cable connectivity. Check also for cut lines. If there is nothing wrong, go to the next step. 4. Replace the sensor board. If this alarm occurs again, go to the next step. 5. Replace the sensor head. There are two possible robot poses which cause this alarm: 1. The angle of J5 is 0 degrees. 2. The sum of the angles of J3 and J5 is 90 degrees. Be sure to avoid approaching these states during force control. Force control must not be executed while J6 is directly above J1 (the robot base). Force control must not be executed near a joint limit. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Change the position and orientation of the robot. If this alarm occurs again, go to the next step. 2. Replace the force control board. Refer to the remedy of the alarm displayed at the same time. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the force control board. If this alarm occurs again, go to the next step. 3. Replace the R-J3 main board. see the manual. see the manual. see the manual. see the manual. see the manual. see the manual. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Check the distance betweent the approach position and contact position - 5 mm or less is appropriate. 2. Make the value of 'Approach Velocity' in Basic Data larger. 1. The orientation of the robot might have changed too much during the force control. If so, correct the approach position. 2. The clearance between the object and work area might be too small. 3. The 'Insert Velocity' in Basic Data might be too small. 4. The 'Insert time MAX Limit' in Basic Data might be too short. 1. Check that the orientation of the insertion task is correct. 2. Check that 'Change MAX Limit' in Basic Data is not too small. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Execute the end condition acquisition again. Execute the end condition acquisition again. Reverse the sign of 'Insert Force' in Basic Data, or execute the torque error acquisition again. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Increase the value of 'Phase Match Rot Vel' in Basic Data. 2. Increase the value of 'Phase Match Torque' in Performance Data. 3. Phase match insertion works well in a range of about 20 degrees. Make sure that the phases of the workpiece and the object match in this rotation. 4. Make sure that the insertion clearance is large enough. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Check that the distance between the approach point and the Insertion finishing point is appropriate. 2. Check that the value of 'Insert Depth (Design)' in Basic Data is appropriate. 3. Increase the value of 'Individual Diff.(+)' in Basic Data. Restart appropriately. Abort Contouring before you satrt force control. It is not an error. It is not an error. Reduce the velocity command or increase the limit value Order the Contouring option Don't make Auto tuning for contouring Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Master the robot, then turn the controller OFF, then ON again. Master the robot, then turn the controller OFF then ON again. Master the robot, then turn the controller OFF then ON again. Contact the FANUC service center and report the error status. Default values are: $CCI_GRP.$SJSW[1],[2],[4],[6] = 0, $SJSW[3],[5] = 5 $CCI_GRP.$SJSE[1],[2],[4],[6] = 0, $SJSE[3],[5] = 3 Set the above values, then turn the controller OFF, then ON again. Contact the FANUC service center and report the error status. Default values are: $CCS_GRP.$RANGE_F[1],[2],[3] = 40 $CCS_GRP[1].$RANGE_T[1],[2],[3] = 400 Set the above values, then turn the controller OFF, then ON again. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the EPROM. If this alarm occurs again, go to the next step. 3. Replace the sensor board. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the sensor board. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the sensor board. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Check the values of the following parameters 1.the search range 2.the search frequency 3.the clearance & chamfer Check the parameter 'search range' Make the velocity command smaller Set the 'reverse switch' ON Set the values of the search force or torque other than zero. Set the values of the velocity or angular velocity other than zero. Sign for the search force and velocity must be same. Set the different value for the different direction. This value >= 1 and continuous integer Set different direction to the search direction 1 and 2 for 'cylinder hole search' and 'clutch ins.' Make 'search range' >= 'Clearance & Chamfer'. Set the values 'Search frequency', 'Search range' or 'Clearance & Chamfer' non-zero. Set the 'reverse switch' ON. Reduce the value of 'Search frequency'. Reduce the value of 'Search range'. Reduce the value of 'Clearance & Chamfer'. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. 1. Turn the controller OFF, then ON again. If this alarm occurs again, go to the next step. 2. Replace the sensor board. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. The value of 'Settling Rate' in Performance Data must be between 0 and 100. Contact FANUC or FANUC Robotics and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Re-acquire the offset data with vision. Contact the FANUC service center and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Make the absolute value of 'Insert Force' in Basic Data larger than 0.5 kgf. 1. Make sure that the distance between the approach position and the contact position is not too long. (5 mm is appropriate.) 2. Increase the value of 'Approach Velocity' in Basic Data. Contact the FANUC service center and report the error status. Execute the end condition acquisition again. No action is required. Make the value of 'Individual Diff (-)' positive and smaller than the value of 'Insert Depth (Design)'. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Make the sign of 'Initial Insert Force' in Performance Data the same as the sign of 'Insert Force'. 'Velocity Adjust Gain' must be between 0 and 3. 'Starting Rate' must be larger than 12.5. 'Ending Rate' must be smaller than 95. Contact the FANUC service center and report the error status. Contact the FANUC service center and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact the FANUC service center and report the error status. 'Individual Diff. (+)' must be between 0 and 10000. Modify the force control parameters in the following order; then execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. Modify the force control parameters in the following order; then execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. Modify the force control parameters in the following order; then execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. Modify the force control parameters in the following order; then execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. Modify the force control parameters in the following order; then execute the impedance parameters auto tuning again. 1. The impedance change for the environmental characteristic acquisition might be too rough. Increase the system variable $CCSCH_GRPxx[i].$TD.$NUM_KEI[1]. [The schedule number is calculated as ((xx-10)*5+i). Modify the appropriate $CCSCH_GRPxx[i]. 2. The desired force might be too small. Increase the desired force. 3. The desired force might be too large. Decrease the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Execessive force was generated during the auto tuning. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. If the prepared default data for the application is used, this error should not occur. Try to copy the default data corresponding to the application into the schedule data. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Correct the errors in the following order; then execute the impedance parameters auto tuning again. 1. Stop any vibration sources that are near the robot. 2. The desired force might be too small. Increase the desired force. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. 1. Increase the value of 'Phase Match Push F' in Basic Data. 2. Make sure that the clearance between the workpiece and the object is not too small. Contact FANUC or FANUC Robotics and report the error status. decrease the amplitude of the search check if the approach point is in a center auto tuning for clutch ins. is prohibitted 1. Customize two force control schedule 2. Move robot position before second force control execution Execute child force control immediately after parent force control Execute child force control immediately after parent force control 1. If you want to retry, set same frame number and reversed insert direction 2. If you want to insert, you can't execute child after errror of parent Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Contact FANUC or FANUC Robotics and report the error status. Delete all unnecessary files and then purge the device. If the device is still full, then backup the files to an off-line device and reformat the device. Format the device before using it. Verify all the parameters for the requested command are correct. Mount the RAM disk before specifying the command. Mount the device before using it. This is a notification. You do not have to do anything for this warning message. Verify the device name. Delete the file first or specify overwrite if available with the command. Either close one or more of the files or set $OPEN_FILES to a larger number and perform a cold start. Check the file position. Delete any unnecessary files or dismount and remount MF: device which will increase the maximum number of files allowed. Open the file with the proper access mode. Delete all unnecessary files and then purge the device. For more information on purging, refer to the PURGE_DEV Built- in in the FANUC Robotics SYSTEM RJ-2 Controller KAREL Reference Manual. If the device is still full, then backup the files to an off-line device and reformat the device. Verify the file name and the specified or default device is correct. Verify the file name is correct. Verify the file type is correct. File not open Open the file before accessing. Close the file before specifying the command. This is a notification. You do not have to do anything for this warning message. Delete all unnecessary files and then purge the device. For more information on purging, refer to the PURGE_DEV Built- in in the FANUC Robotics SYSTEM RJ-2 Controller KAREL Reference Manual. If the device is still full, then backup the files to an off-line device and reformat the device after setting $FILE_MAXSEC to a larger number. This is a notification. Your do not have to do anything for this warning message. You must backup all your files, reformat the device, and restore the files. Refer to chapter 9, "File System", in the FANUC Robotics SYSTEM RJ-2 Controller KAREL Reference Manual for more information. If you require more blocks, you must backup all your files, reformat the device, and restore the files. Refer to chapter 9, "File System", in the FANUC Robotics SYSTEM RJ-2 Controller KAREL Reference Manual for more information. Set $PURGE_ENBL to TRUE and retry the purge operation. You may wish to set $PURGE_ENBL to FALSE before running a program or application which requires fast cycle time. You should backup all your files, reformat the device, and restore the files. Refer to chapter 9, "File System", in the FANUC Robotics SYSTEM RJ-2 Controller KAREL Reference Manual for more information. If the problem persists, the FROM may need to be replaced. The system will continue to operate as long as enough blocks are available. When too many blocks become bad, the FROM will need to be replaced. This is a notification. Delete the file on this device or choose a different file name. Open or copy a file that exists on the device. Use only supported operations, or check command syntax. Delete some unneeded files or use a disk with sufficient free space. Do not attempt to read beyond the end of a file. Do not attempt to open more than one file at a time. Verify protocol field in the setup menu and retry the operation. Clean the disk drive,try another disk or reformat the disk. Try another disk, or reformat the disk Clean the disk drive, try another disk, or reformat the disk. Check the cable to the drive and make sure drive power is on. Remove write protection from the disk or use a disk that is not write protected. Return Protocol Entry structure to initial values from Setup and Operations manual. Return Server Entry structure to initial values from Setup and Operations manual. Set Internet Address in the Setup Host Comm TCP/IP Protocol Menu. Set Host Name and Internet Address in the Host Comm TCP/IP Protocol Setup Menu. Set Remote Node Name in the Host Comm TCP/IP Protocol Setup Menu. Turn off and then turn on the controler. Copy ETHERNET.DG file from MD: and save it. Note the PANIC string. Cycle power to the controller and contact the Support hotline and provide them with that information. Set the Ethernet address in Configuration Menu. Load the Ethernet Board firmware in BMON. Install or reseat the Ethernet Board. The error can be cleared by Stopping and Starting the Tag in Host Comm Setup Menu. Ensure program can run on this version of controller. You might need to retranslate your program. Stop and Start the Host Comm Tag in the Host Comm Setup Menu to reset the operating mode. Either add more memory to the controller or reduce the number of simultaneous connections. Correct port settings: data rate, data size, stop bits, etc to match external device. Ensure that the external device is using the same protocol. Restart the Comm Tag. Check cabling between the devices and/or insure the device is powered. The cancel command was successful. The command might have been completed before the cancel command was received. Check the Host Comm Protocol to ensure the function is supported. Set the remote device online. Either use another Comm Tag or Stop and Undefine the selected Comm Tag under Menus-Setup-HostComm-Show Ensure both local and remote are using compatible software versions. Power the controller OFF and then ON and try again. If the error occurs again a cabling or hardware problem might exist with the port. DEFINE a protocol to the Comm Tag or assign a port. If possible, close and reopen the file with the correct access parameters. Verify the tag has a supported protocol then UNDEFINE and DEFINE the Comm Tag First ensure the Port has No Use from Port Init Setup. Then assign it to the selected Comm Tag. Either STOP the Comm Tag or select another Tag. Only Comm Tags can be used with this command. Either select another protocol or install the selected protocol. Reduce the number of simultaneous connections as there is not enough memory. Consult your network administrator. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Enter a valid username and password for the Comm Tag. Consult your network administrator. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Enter a remote host name in SETUP TAGS menu Current Remote and Startup Remote fields. Ensure both Ethernet PCB firmware and Main PCB Ethernet tasks are activated. Ensure correct buffer size Make a read call after write before making a new write call. Unrecoverable - Contact Help Desk. A write should precede read. Check cable & remote device. Close connection and open again. Make sure the channel specified is online or specify the correct channel Verify Path format specified EM:/DNET/1/10/40 DNET-Protocol, 1-Channel,10-MAC Id 40-buffer size Also verify values are legal. Verify Explicit Messaging mapping system variables are correctly set and the values are legal. Reopen connection with correct buffer size. Make sure your host name and local domain name are correct. Your DNS server may not have the. current host listed. Verify that you DNS server is running. Check with your DNS administrator to verify that the server is working properly. Verify that the host name and local domain name and formated correctly. Verify that your server supports recursive queries. Verify that your server grants access to your robot. Your host name is valid and is recognized by the DNS server. The server has no IP address for the host queried on. Have your DNS administrator provide the server with an IP address for the host queried on. Go to the DNS configuration menu and verify that the server IP address and local domain name are correct. If your network has a router, then define a router in the TCP/IP set up menu. If your network has a router, then define an address for it in the local host table. Network memory should be created before accessing. Network may overload if this error occurs frequently. Verify that correct buffer descriptor is specified. Verify that correct buffer descriptor is specified. Verify that correct buffer descriptor is specified. Verify that correct buffer descriptor is specified. Confirm that UDP port was consumed by another network application. Verify that there is RLSYNC entry in $SERVENT system variable. Verify that port number for RLSYNC is correct. Verify that a correct port number is specified Verify that a correct port number is specified Verify that a correct port number is specified Verify that a correct port number is specified Verify that a correct port number is specified This is not an error This is not an error Correct the cause of failure and try again ensure the device is not connected and try again ensure the login id is valid and try again ensure the password is valid and try again log in again or increase the timer value for the device from the TELNET screens make an entry for the PC in the FSAC table check the access level for the device from the TELNET screens configure a valid port for device from Port Init screens first not an error Change the host name to be a valid name in the client tags. Do not try to remount a tag without dismounting it. Set the $hosts_cfg[n].$server_port sysvar for the server tag or $hostc_cfg[n].$server_port for the client to a valid number Mount the tag before using it Use MSG_CONNECT to connect the tag before opening it. Check the remote host and reconnect to it Reconnect to remote host. Check remote host and network connection. Check remote and reconnect to remote host Check remote and reconnect to remote host Wait for remote to connect. Stop using the remote tag. If necessary close any open file to the tag and disconnect the tag by using MSG_DISCO. Re-establish the connection. Retry the operation. All sockets may be use. Free some resources by closing some connections to telnet, ftp or socket mesg If that is not feasible, the same error may occur again. not an error not an error not an error not an error not an error not an error check your cable and server configuration check your network/server configuration check your cables/server configuration lease may have expired. check cabling/server configuration and start DHCP again from the DHCP screens not an error not an error Please check network cabling, and DHCP server setup Not an error Not an error Please check network cabling and DHCP server setup Not an error Not an error Please start FTP servers manually Please start FTP servers manually Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Either retype the file name or DEFINE the Comm Tag. Please refer to the section of Defining and Starting FTP on a Device in the manual of Ethernet Controller Backup and Restore- FTP Setup and Operations. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. DEFINE a protocol to the Comm Tag or assign a port Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Copy the conditions which caused this to occur. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. First ensure the Port has No Use from Port Init Setup. Then assign it to the selected Comm Tag Either STOP the Comm Tag or select another Tag. Please refer to the section of Defining and Starting FTP on a Device in the manual of Ethernet Controller Backup and Restore- FTP Setup and Operations. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Only Comm Tags can be used with this command. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Either select another protocol or install the selected protocol. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Consult your network administrator or call the FANUC Robotics Service Hotline for assistance. Free Device for use Check useage against device Wait for command complete then retry Wait until Device free then retry Check useage against device Check that device is valid Check device installation Delete file and try to get copy from original source Notify FANUC Slave PCB is installed . Please exchange Slave board Plase check Cable and Master status. Plase check other device status. Please reset the group name by using the sub-menu on TP program. Please confirm to match the INTERBUS-S configuration which is specified IBS CHANGE and the real configuration. Please modify the slave length code setting. Please modify the offset or byte number of slave configuration setting. Notify FANUC Notify FANUC Slave PCB is installed . Please exchange Slave board Plase check Cable and Master status. Notify FANUC Notify FANUC Notify FANUC Notify FANUC Refer to the Cause and Remedy of the cause code (displayed immediately below this error code on the teach pendant). Notify FANUC Notify FANUC Notify FANUC Check the slave device or the cable. Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Notify FANUC Plase check other device status. Notify FANUC Notify FANUC Notify FANUC Serch slave which has non-zero BIT LENGTH and BYTE LENGTH. in config detail screen Then set 0 to all of BIT LENGTH or all of BYTE LENGTH Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Please see manual IBS SYS FW G4 UM E from Phoenix Contact Check the teach pendant enable switch and other running programs to determine who has motion control.  Perform a cold start:  1.Turn off the robot.  2.On the teach pendant, press and hold the SHIFT and RESET keys.  3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative.  Perform a cold start:  1.Turn off the robot.  2.On the teach pendant, press and hold the SHIFT and RESET keys.  3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Disable the teach pendant. Abort the running or paused program.  Perform a cold start:  1.Turn off the robot.  2.On the teach pendant, press and hold the SHIFT and RESET keys.  3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative.  Perform a cold start:  1.Turn off the robot.  2.On the teach pendant, press and hold the SHIFT and RESET keys.  3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. For TPE programs, if possible, reload program from back-up device. If a back-up is not available, it may be necessary to re-create the particular routine. For KAREL programs, re-translate and re-load the program. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the attribute. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Resume the program after hot start is complete. Wait a moment Clear motion group mask in program detail screen Refer to the error cause code. Use MENU to display the Alarm Log screen. Decrease number of stop data. Change the specify of motion group. Change the specify of motion group. Lock the motion group. Please fix the alarm by manual. Please check the condition of error recovery DO status Please set another program with no motion group. Please check $PAUSE_PROG. Please check $RESUME_PROG. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the appropriate option is loaded. Teach the instruction. Reteach the instruction. Check the variable type. Check the index value. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the value. Add a SELECT instruction before the CASE instruction. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the value. Refer to the user alarm code. Use MENU to display the Alarm Log screen. Set up the motion group in the program DETAIL screen. Check the position data. Check the value. Add a SKIP CONDITION instruction. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the frame number. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Do not use backward execution at this point Do not use backward execution from this point. Set the cursor to the following line. Check the data type. Check the parameter type. Add an OFFSET CONDITION instruction before the OFFSET instruction. Teach the position register. Remove the MOTION instruction or set up the motion group in the program DETAIL screen. Check the line number. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Press RESET to clear the error and continue the program. If this error continues to occur, perform a cold start by turning off the robot, then while pressing SHIFT and RESET on the teach pendant, turn the robot back on. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the MACRO setup. For more information on setting up macros, Refer to the KAREL and TPP Setup and Operations Manual. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the user frame number. Check the tool frame number. Check the parameter name. Refer to the error cause code. Use MENU to display the Alarm Log screen. Teach the origin 3 points or destination 3 points. Input a correct value. Refer to the error cause code. Use MENU to display the Alarm Log screen. Change position register data to cartesian. Input a correct value. Correct the PARAMETER statement to include the subscript of the desired array element. Correct the PARAMETER statement to include the name of the desired field Check the register type. Check the value. One (or both) of the following should correct this problem: 1. Add CANCEL or STOP condition handler action before the call to the interrupt routine in the condition handler. 2. Add a DELAY 500 statement before the first move in the interrupt routine to allow the motion to complete. Abort specified program Delete the extra statement Delete the extra skip statement Use FWD execution carefully Set torque limit value less than or equal to the maximum value. Check the operator Refer to the KAREL and TPP Setup and Operations Manual for more information. Reduce the number of condition. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the sub type of this CH program. Delete the motion option instruction Please set the correct EPT index for the program name defined in macro table. %s^7 This alarm is defined by the customer. Therefore the customer knows the remedy for this alarm. Please change the application process data of this program to the adequate application for this application instruction. Please change the structure of program Please define the application data in the program detail screen Reduce the nesting of the program Use TP program. Confirm the MAINT program name is correct or MAINT program exist in acutual. Please confirm the index of AR register and the parameter in CALL/MACRO command in main program. Check whether the CONT terminaton exists at end of sub- program If exist, please change it to FINE. This is the limitation of the fast fault recovery function. Please confirm the index of AR register and the parameter in CALL/MACRO command in main program. Please change teaching so that less than 5 motion statements are mixed. Please make distance value larger. Document the events that led to the error and call your FANUC Robotics technical representative. Please make distance value larger. Please set $SCR_GRP_[ ].$M_POS_ENB to TRUE. Please change distance value. Check the KAREL translater software version. A GOTO statement cannot be used to enter or exit a FOR loop. Check the label of the GOTO statement. For KAREL programs, refer to the KAREL Reference Manual, Stack Usage and the %STACKSIZE Translator Directive. Check the value. Check the dimensions of the arrays. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check the CASE value and branches. Check the parameter. Check the length of the array and index value. Teach or initialize the data before using it. Check the axis number and the data value. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Verify the routine is loaded. Check the condition. Check the action. Check the data type. Check the appropriate option is loaded. Add a RETURN statement to the function routine. Check the argument value. Check the variable's type and data value. Check the usage string in the OPEN FILE statement. Check the file string. If no device is specified, the default device is used. Close the file before reusing the FILE variable or add a new FILE variable. Refer to the error cause code. Use MENU to display the Alarm Log screen. Open the file before operation. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Make sure the data in the file is valid. Check the data of the file. Refer to the error cause code. Use MENU to display the Alarm Log screen. Use the file defined by the system without opening it. Do not try to close it. Make sure you have the correct routine type and name. Refer to the error cause code. Use MENU to display the Alarm Log screen. Make sure you have the correct program name. Make sure you have the correct variable name. Verify the program name and variable name. Make sure you have the correct data type and variable type. Decrease the number of BYNAME functions. Increase the buffer size. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Check program operation. Operate the AMR using the WAIT_AMR built-in routine. The program executing the WAIT_AMR must be restarted. Check the device being read. Remove nested reads. Check the vector value. Teach P1 and P2 as different points. Teach P1 and P3 as different points. Teach P3 out of the X-axis direction. Increase the target string size. Check the use of this file. Reset the error using the CLR_IO_STAT built-in routine. Check the specified mode. Refer to the error cause code. Use MENU to display the Alarm Log screen. If an AMR was expected within the time-out value check logic in the task that sould have posted the AMR Plug in the vision CPU board. Modify program so fewer vision builtins are executing at the same time. Check the appropriate option is loaded. Check the parameter of the vision built-in routine. Check the return value from the vision built-in routine. Pass without using BYNAME or use GET_VAR and SET_VAR instead. One (or both) of the following should correct this problem: 1. Add CANCEL or STOP condition handler action before the call to the interrupt routine in the condition handler. 2. Add a DELAY 500 statement before the first move in the interrupt routine to allow the motion to complete. Refer to the error cause code. Use MENU to display the Alarm Log screen. Use global variable to recover local condition. Correct the condition handler number. Condition handler numbers must be in the range 1-1000. Use a valid program number. Prorgam numbers must be in the range 1..$SCR,$MAXNUMTASK + 2. Use a valid delay time. Delay time must be in the range 0..86400000 . Use a valid value for the bit field. Check the path node. Decrease the number of motions executed at the same time. Execute the next motion after the completion of the last motion. Resume the motion that was previously paused. Please check motion type and options Please disable single step Please turn on stitch enable signal Please check Equipment conditon signal Please check stitch speed Change the motion statement to LINEAR motion. Please force abort another program if it is executing stitch or it paused in stitch area. Please select the other mode Please enable all motion group for the program. If some groups should not be affected by Dry Run, please set $DRYRUN.$GRP_MASK to set the motion group. Please move cursor to the other line, or do backward execution Please move cursor to the other line, or do backward execution Dry Run is activated on interruption routine. Dry Run can not start from interruption routine. Please do backward execution to exet interrupt routine. This is only message Please see the other errors. Don't use the item for output. Reduce the nesting of Marker. Define Marker expresion before read. Please check recursive reference of Markers Check TC_ONLINE expression. Please stop Background Logic. Please execute the Background Logic by manual. Please use the operator or data as normal Logic instruction. Please remove the operator or data, or execute this program as Normal mode Backgroug Logic Please remove the indirection, or execute this program as Normal mode Backgroug Logic Please divide the expression to two line. Check the parantheses pairs. Please set execution mode of some Backgroung programs Normal Please check recursive reference of Marker. Master/Slave/SlaveAlone program cannot call KAREL program Master/Slave/SlaveAlone program cannot call Normal program which has motion group. Master/Slave/SlaveAlone program can call Normal program which does not have motion group. Master/Slave/SlaveAlone program can call different type of program. Master/Slave/SlaveAlone program can call only same type of program. Slave program cannot be execute without remote status. Satisfy the remote condition Master program must have the same motion group which is specified by the link pattern of robot link data. Slave program must have the same motion group which is specified by the slave group of robot link data. Current tool frame number of master robot and the master tool No of robot link data of the slave program must be same number. After robot stops completely, countinue the program again. Change the motion statement of slave program to LINEAR motion. Change the position data of slave program to LINEAR type. Slave program is paused, when master program is executed by TP. Change the robot to normal from master. Then, please try to execute again. Change the robot to normal from slave. Then, please try to execute again. Calibrate the robot link. Remove the Incremental instraction. Remove the Offset instraction. Change the Slave robot to be synchronize waiting state. BWD of Slave program is not supported. When robot is Master(Manual), you cannot use external program execution. To use external program execution, please change the status to Master(Alone) at the manual operation screen. When robot is Slave(Manual), you cannot execute other Slave program. To execute other Slave program execution, please hold the program to exit Slave(Manual) status. Synchro ID 0 is not available number. Please set another synchro ID. Please change the synchro ID to fit the current synchro ID. Please release single step key. BWD is failed. Slave program must be called by normal program. Use another group as master or change SETUP. Confirm RobotLink and HOST Comm TCP/IP SETUP. Confirm RobotLink and HOST Comm TCP/IP SETUP. Modify Synchronization ID at Program List Screen. Modify Link Pattern Number at Program List Screen. Modify Master Number at Program List Screen. Confirm group number setup about MASTER. Confirm group number setup about SLAVE. Calibrate SLAVE robot. Confirm Link Pattern at RobotLink SETUP screen. Increase $RK_SYSCFG.$RMGR_PHTOUT by 100. Check HOST Comm TCP/IP and RobotLink SETUP. Check another robot and robot link program Check another robot is paused or communication status Check master robot status Check slave robot status Please check robot type Please modify program. Please modify program. Please confirm PS logic statement. Set time val to 0. Else change motion type or speed unit. Please confirm PS trigger condition. Please record the detail of last operation which caused this alarm. Then please cycle power to recover. Please confirm calibration and mastering. Do BWD motion to clear the remaining PS items. Please check and modify PS trigger condition. Please check and modify PS trigger condition. Please check and modify PS trigger condition. Please check and modify PS trigger condition. If you will continue program execution, please confirm canceled PS contents. Please reduce time value or enlarge distance value. Don't change line for restart or don't enable dryrun. Don't change line for restart or don't enable dryrun. Please do COLD start. After check and modify the contents of the file, then try again. Check file and then try again. Modify programand try again. Execute at least one motion statement before RECORD start[ ]. Check whether ASCII file is correct. Check whether ASCII file is correct. Enable Constant Joint Path function. To start recording, start your program again from the beginning. Disable single step. Check IBGN**.IBG file. Check the number of point in IBGN file. Check whether IBGN END instruction is exist. Check whether IBGN END instruction is taught before IBGN instruction. Check setting for communication. Afetr BWD execution finish, do FWD execution. Use proper index. Please do COLD start. Wait for a while and resume program. Wait for a while and try again. Wait for a while and try again. Wait for a while and try again. Please make sure record is successful. Access record file before another record stars. If index is wrong, record file isn't found. Execute IBGN RECORD END instruction Then start another reocrd Access record file before another recording starts. Check ascii file and fix it. Use the MANUAL FCTNS OT release menu in to find out which axis is in an overtravel condition. Release overtravel by holding the SHIFT key and pressing the RESET key. At this time the servo power will be turnned on. If the SHIFT key is released, the servo power will be turnned off again. You can only use JOINT to jog the axis out of overtravel. If you want to jog the overtraveled axis further into the overtravel direction, you have to release the axis by moving the cursor to the axis direction you want, then press release function key in the OT release menu. At this point you can jog the axis to that direction. Set the system variable $MASTER_ENB to 1. Select SYSTEM then Master/Cal, to display the Master/Cal menu. Select a method for calibrating the robot. If the robot can not be calibrated, mastering is required. If the robot has been master before, set the system variable $DMR_GRP[].$master_done to TRUE then calibrate the robot again. For more information on mastering and calibrating the robot, refer to the KAREL and TPP Setup and Operations Manual. Abort the program that has motion control by pressing FCTN key then selecting ABORT. Only press one rotational jog key at a time. Perform a cycle start. This is a notification. You do not have to do anything for this warning message. You must press the SHIFT key when jogging the robot. Release the jog key then hold the SHIFT key and press the jog key to jog. Hold the DEADMAN and turn on the teach pendant before jogging the robot. Press the DEADMAN switch, then press the RESET key to clear the error Release the jog key. Then,hold the SHIFT key then press the jog key Release the SHIFT key and the JOG key. The new TOOL frame will take effect automatically. To start jogging, hold down the SHIFT key and press the JOG key. Engage all the brakes by pressing EMERGENCY STOP button, then press the RESET key. To start jogging, press the shift and the jog key. The robot already reach the stroke limit and cannot jog in the current direction any more. Extend the axis limit if it does not exceed the robot and software specifications. To continue jogging, release the JOG key then press it again. To continue jogging, release the JOG key then press it again. Make the system variable $SFLT_FUPTIM larger. To continue jogging, release the JOG key then press it again. Jog J4 to reach R-Theta posture (0, +180, -180). Use shift-FWD to execute program path, or specify another jog frame. Use only one jog key at a time. PATH jog is available in LINEAR and CERCULAR path PATH jog is available only in PAUSE status Change jog mode Move J4 to zero position. Now OFIX jog is available. Press opposite jog key. Confirm TCP's XYZ location. Contact FANUC Robotics. Check cause code. (1) Set the currect port. (2) Check the device if it works fine. Select a TPE program. Generate (using SAVE, with $ASCII_SAVE = FALSE) and load a valid .TP file. Note: An existing TP program in the controller might have been corrupted as a result of your attempt to load the invalid file. You might have to reteach the teach pendant program, before you save it as a .TP file. Before you load the program, delete the program already in the system. Check the connection of the device. Check the connection of the device. The file cannot be loaded with the data as it is. The data must be normal to load the file. Reteach the position data so that the group number matches the group mask of the program. Rename the file to be same as the program name. Please verify the daughter program name. Please check the content of the specified file Please specify the parent program. Before you write the new file to the floppy, delete the file that already exists on the floppy. Check the file name or content of the floppy. Either use a new floppy disk or delete an unnecessary file in order to make room for saving to the floppy. Do not attempt to open more than one file at a time. Check if the correct device is set to port and it turns on. Remove the write protection. Connect the correct device to the correct port. Change this program. Please add LE instruction. Please execute this program in R-J system which has laser tool. Please check the vein. Please check I/O mapping of assist gas signal. Please check this program. Please check this program. Please change EQ number in the program attribute. Please execute it after laser oscillator become to be LSTR. Please wait for the end of the program execution. Please do control start. Please do control start. Please check assist gas equipment. Please check assist gas select value in the schedule data. Please check assist gas select value in the schedule data. Please check the shutter and shutter alarm mask time in setup data. Please check the shutter and shutter alarm mask time in setup data. Please check the index number of the laser instruction. Please change the motion type of this motion statement. Please try again from the first. Please cool down the cabinet. Please check the laser oscillator is turned on. and I/O link cable is normal. Please check the chiller. Please check the water volume of chiller. Please check the purge gas process. Please cool down the root blower. Please stop chiller equipment and examine the chiller to be appropriate. Please cool down the absober. Please check the laser gas process. Please check the laser gas process or change gas feed back gain. Please check the lamp. 1. Clean the window. 2. Check the connection part of the fiber. Please take away safety interlock. Please turn off R-J after the oscillator is in PURGE. Please reset the alarm and turn on HVON switch. Please check the lamps. Please check that. Please cool down the shutter. Please check the external mirror. Please check RDI7. Please check hight sensor. Please reset emregency stop button. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. Please check this power supply. If you want to be output beam, please change the lock switch to OFF. If you want to be output beam, please change the adjustment beam switch to OFF. Please reset the alarm and turn on HVON switch. If you want to be output beam, please change the signal status to UNLOCK. If you want to be output beam, please change the signal status to UNLOCK. Please clean the mirror. Please check the inverter 1. Please check the inverter 2. Please fill up the vacancy. Please fill up the vacancy. Please check the turbo 1. Please check the turbo 2. Please cool down turbo 1. Please cool down turbo 2. Please check the turbo 1. Please check the turbo 2. Please check the turbo 1. Please check the turbo 2. Please check AD converter 1 or check noise in I/O link Please check AD converter 2 or check noise in I/O link Please check power process of oscillator. Please check gas pressure process of oscillator. Please check gas pressure process of oscillator and I/O link. Please check the lamp. Please check power table value in setup data. Please check power process and power sensor. Examine No.1 Fiber. Examine No.2 Fiber. Examine No.3 Fiber. Examine No.4 Fiber. Examine water Examine Lamp Examine shutter Examine the door Please turn the SIMMER on again. No action needs. Please do it when the program is not running. Please reset the alarm. Please change the teachpendant to be disabled. Please change the shutter lock switch to be locked. Please do it in LSTR condition. Please change the value of $LASERSETUP$PWR_CALIB to 1. No action needs. No action needs. No action needs or please check the condition. Please start the program unless the power calibration status. Examine the shutter and shutter state signal. Examine the shutter and shutter state signal. Examine shutter and shutter state signal. Examine the cable between FENCE and Shutter close input on laser oscillator. Check if there is a double definition or if the index is over the range. Remove the motion lock group from the program. Remove the motion lock group from the program. Enable the teach pendant. Disable the teach pendant. Change the assign type to another. Create REMOTE condition. Change the assign index. Change the value of the $MACRSOPENBL system variable. Refer to the SYSTEM R<#0106>J Software Reference Manual, Chapter 2, <#007F>System Variable Alphabetical Description", for more information on setting system variables. Change the value of the $MACRSOPENBL system variable. Refer to the SYSTEM R<#0106>J Software Reference Manual, Chapter 2, <#007F>System Variable Alphabetical Description", for more information on setting system variables. First deassign the other RI or DI assignments. Then assign the new macro as RI or DI. Refer to the error cause code. Use to display the Alarm Log screen. The macro will begin executing from the first line at the next execution. Disable the teach pendant, and try the operation again. Enable the teach pendant, and try the operation again. Clear the error by pressing RESET, and try the operation again. Wait until the robot comes to a complete stop. Make sure all brakes are released and try the operation again. Disable the teach pendant, and try the same operation again. Pause or abort the program, and try the same operation again. Set the $rmt_master system variable correctly, and try the operation again. Set the $rmt_master system variable correctly, and try the operation again. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Set ENBL input ON. Wait for a few seconds until servo is up and ready. Disable the manual brake control. Abort the specified program. Or select it again after selecting another program. Abort the specified program. Or select it once more after selecting another program. Abort the specified program. Or select it once more after selecting another program. Cancel the protection of the specified program. Specify the correct break number. Specify a correct line number. Specify the same program name. Specify the same program type. Specify another label number. Specify another program name. Or delete the registered program. Delete unnecessary programs or routines. Set the index to an existing label. Delete unnecessary line data. Specify another line number. Specify another line number or the data of same size. Abort the specified program. Or select it once more after selecting another program. Specify another item. Delete unnecessary programs. Specify another break point. Specify another program or create the same program first. Specify another program or create the same program first. Open the program with write access before writing. Abort the unnecessary programs. Or, remove unnecessary CALL instructions. 1. Abort the specified program. Or select it once more after select another program. 2. Remove the program form the MACRO entry. Specify another position. Specify another position. Or, delete the data in the specified position. Specify another program or create the same program first. Select a TPE program. Open the program before reading or writing. Specify a program whose program type matches the operation. Cancel the protection of the specified program. Abort the specified program. Or select it once more after select another program. Specify another position. Abort the specified program. Or select it once more after select another program. The P-code data may be broken. Translate the specified KAREL program again. Then reload the P-code. Check the program name of the specified program.  Perform a cold start:  1.Turn off the robot.  2.On the teach pendant, press and hold the SHIFT and RESET keys.  3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Specify another program name. Or delete the registered program. Specify another break point. Check the port setting and the connected device. Cancel the protection of the program. Or, abort the program. Cancel the protection of the program. Or, abort the program. Specify another application data. Then create the program in the current system. Specify another application data. Create the program in the current system again. Specify another application data. Create the program in the current system again. Translate the program with an older version of the Translator. Translate the program with a newer version of the Translator. Delete unnecessary programs. Set new position ID for the referenced position. Update the calling convention in the KAREL program being loaded or delete the obsolete routine from system memory. Please power up again. Turn power off and then back on. Delete the program and create it again. Press the RESET key to clear the error. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Turn power off and then back on. Delete the teach pendant (TP) program. Then load the specified KAREL program again. Select the function menu to change the start mode. Select the function menu to change the start mode. Load the program at controlled start. Delete the program at controlled start. Change size to range of 1-256. If necessary, use multiple header records. Change the program name, or delete the KAREL program which refers the routine of the specified program. Check the varialbe used in the specified KAREL program. The Flash File(F-ROM) may be broken. Create or load the lost program again. The Flash File(F-ROM) may be broken. Create or load the lost program again. Please power off and on. Then check the program data of the specified program. Delete unnecessary programs. Or, change the D-RAM module to the bigger one. Abort the specified program. Or disable the teach pendant and press continue. Or select SKIP to skip over this file. Please cycle power. Please delete the parent program before the daughter program. Please delete the unused position. Please cycle power. Delete the program and create it again. Press the RESET key to clear the error. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. The system may have been corrupted. This may have been caused by any of a number of reasons including: Incorrect loading and setup loading incompatible options, mixing software version when adding options and other memory corruption problems. The following is a list of possible remedies: 1. Perform a cold start. 2. Perform an init start and setup the robot again 3. Confirm that any options or additional software not on the original software distribution media is the same version number. If the main system software was supplied on several disks or memory cards, make sure that you are using a matched set. Also make sure that the installation manual being used is for this version of software. If any of the software version are not matched, a complete re-load with the correct software will be necessary. 4. Confirm that no incompatible or mutually exclusive option have been loaded. 5. Full software reload. 6. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 This is a normal condition. No action is required Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Make sure the correct basic motion softpart is installed Make sure the correct basic motion softpart is installed Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Reteach the position out of limits Reteach the position that is not reachable Reteach the position that is near a singularity point. Wrist joint warning Use joint motion Set limit number correctly Reteach the position that is near a singularity point. Define Kinematics Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Refer to Remedy of MOTN-000 Calibrate the robot. Set $SPEEDLIMJNT correctly Set speed correctly Set $JNTVELLIM correctly Refer to Remedy of MOTN-000 Teach destination position Teach via position This is just a notification. You do not have to do anything for this warning message. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Initialize base vector Initialize distance Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Reteach the destination position so that its configuration string matches the start position's configuration string. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Reteach via and/or destination positions Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Set $prgoverride within 0 to 100 Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Set speed within 0 to $speedlim Set Rotspeed within 0 to $rotspeedlim Set contaxisvel to within 0 to 100 Set seg_time positive Set accel_ovrd within 0 to 500 Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Teach via position Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Do not change $utool for this move Must set motype to cartesian Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Refer to Remedy of MOTN-000 Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. If corner blending is still required for the line shown reteach pos further apart Set $linear_rate equal to $circ_rate. cycle power Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. If arc bigger than half circle is intended use two or more Circular instructions to teach the circle. If the intended arc is smaller than half circle then circle's via point is not between Circle's start and destination points. Check the taught points and make the necessary changes. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Refer to Remedy of MOTN-000 Use FINE in last L statement This is just a notification. You do not have to do anything for this warning messsage. Change position to absolute position Calibrate the robot Turn off servo Check brake mask reteach position Master the robot. Refer to the Setup and Operations Manual specific to your application. Reset over travel jog the robot outside over travel position Turn off servo Check reference position Reteach your config string Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Reteach position that is near a singularity point. Reteach motype No corrective action required Remove backward command Change last node motype Re-teach the points. Ideally circular points should be evenly spaced. Otherwise a small change in one point can drastically change the programmed circle. Load the circular softpart Load joint short motion softpart Load cartesian short motion softpart Load the KAREL motion softpart. Check that the KAREL Motion softpart has been loaded, and restart the controller. Check that the Group Motion softpart has been loaded, and restart the controller. Check that the Motion Resume softpart has been loaded, and restart the controller. Load joint Turbo Move softpart Load cartesian Turbo Move softpart Reteach position Change the current motion's motype to linear or change the previous motion's motype to joint. If the problem persists, re-teach the path. If slow down is not acceptable, re-teach the path. Set $cf_paramgp[].$cf_framenum=1 or 2 and cycle power or reduce speed or use FINE in prev line Please check position data(XYZ) in IBGN file. Please check position data(WPR) in IBGN file. Please call FANUC service. Joint might be move too fast because of around singular point. Please teach point except singular point again. I/O data in ibgn.txt might be different from that in SENSPS.txt. Please check I/O data in SENSPS.txt. Interpolated data do not exist. Please check interpolation data in IBGN.txt. Configuration has been changed. Please check configuration in IBGN.txt. Please call FANUC service. Please set original path resume function to TRUE Please retry to record the data again except singular and configration's change point. Use LOCK PREG instruction to lock position registers. Remove conditional branching (IF/SELECT) if possible. Consolidate programs if possible. Move the parameter instruction to a different line if possible. Change tool/hand to satisfy load condition Change tool/hand to satisfy load condition Pause and restart all the link robot. Confirm setup data and program detail data. Confirm motion control status. Confirm setup data and group mask in program. Confirm setup data and group mask in program. Confirm setup data and group mask in program. Confirm each link robot's position and restart. Please call FANUC service. Confirm the calibration setup. Confirm software version is consistent between robots. Confirm communication status and setup data. Confirm UTOOL number. Confirm UTOOL data. Confirm communication status. Confirm communication status. Confirm communication status. Confirm communication status. Confirm program that slave is already stopped at link end. Use XYZWPR data for slave program. Use cartesian motion. Confirm master program as not to change utool. Confirm slave program as not to change utool. Confirm robot position and disable machine lock. Please call FANUC service. Re-teach the points. Ideally circular points should be evenly spaced. Otherwise a small change in one point can drastically change the programmed circle. Re-teach the points. Ideally circular points should be evenly spaced. Otherwise a small change in one point can drastically change the programmed circle. 1. Reteach the previous point to make motion segment longer. 2. Specify smaller TimeBefore value. Re-touch up the point to make the taught configuration is reachable. If you do not want the system to modify the destination point, please set \$ra_paramgrp[].\$use_start_j4 = FALSE Abort and re-run the program. Please change to T2 or AUTO mode Change status to MASTER or ALONE at MANUAL screen to jog the robot. Disable original path resume feature. Check if original path resume is enabled, and match the resume condition for all robots. Abort the program and continue from the same instruction line. Or backward execution the same line then continue the program. Reduce speed or Use (deg/sec) or sec as speed unit This is just a notification that the robot may move with lower speed than production mode even though the command speed is not greater than safe speed. Confirm position data Confirm position data Confirm motion group and robot type Check cause code. Confirm position data Confirm position data Confirm robot type Confirm position data Reduce tool rotation angle Reduce tool spin angle Change term type of previsou motion. Confirm software option. Confirm motion type. Confirm tool spin angle between start and destination Confirm start and destination position are both J4 = 0 position. Change position data. Confirm position data turn number and actual turn number. Fix turn in config data. Confirm destination's wrist axis position data Confirm destination's wrist axis position data Execute Magnetic Phase Detection process for that axis. Please call FANUC service. Please call FANUC service. Please call FANUC service. Please call FANUC service. Change termtype FINE or CNT. Abort and run program. If slow down is not acceptable, re-teach the path. Lengthen path or reduce speed. This is just a notification. You do not have to do anything for this warning messsage. This is just a notification. You do not have to do anything for this warning messsage. Abort program and rerun Abort program and rerun Can't generate corner between two motion because of motion instruction. And CNT or CD is ignored. Use LOCK PREG instructiion when PR[] is used for positiion or OFFSET instruction is used. Reduce program speed not to display. Reteach the destination position so that its configuration string matches the start position's configuration string. Abort and run program. Then, the resumed motion may not be on the original path. Abort program and rerun. Reset and resume the program. If the same alarm still occurs after resume, please do the either operations - run the program with Single Step mode - BWD the program. CAUTION: The resumed motion may not be on the original path. Abort and run program. Then, the resumed motion may not be on the original path. Modify back the command speed, or abort program Set Teach Pendant's override to the desired value and resume the program. Please don't change override right after resuming. Please disable Error Recovery function. Refer to Remedy of MOTN-000 Reteach circular points motion error will occur, use CLR_Adj to clear the adj value motion error will occur, use CLR_Adj to clear the adj value has the limit error, adjust taught points This is just notification. Please don't use incremental motion if you need Z offset Set Teach Pendant's override to the desired value and resume the program Increase override setting and resume the program Please check program. Use the Collision Guard SETUP screen to define a register for use with the macro. Enter the correct data into the Collision Guard macro register. Must have at least two points Internal error: motion type is not Joint, Linear, or Circular. If this error persists, contact FANUC Robotics. Increase distance between points Multi-Pass does not support backward motion. Please do not use Shift-BWD in Multi-Pass. Add or remove motion option COORD. Use correct pass number Pass direction can only be 0: Normal or 1: Reverse. First pass direction must be 0 Check the pass number and direction Use correct pass number Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. None required. Options/updates will load but not be logged. This is just a notification. You do not have to do anything for this warning message. Some options cannot be overlayed, you may need to delete some options first. Reinstall the option. Call your FANUC Robotics technical representative. Reinstall the option using the required floppy disk. This is a notification. No action is needed. COLD Start. There may be further instructions at completion of COLD start Turn the controller off, and then back on Do a full load from the original distribution media. Obtain a valid PAC for this option. Install sub-options first. You cannot have both options. Do a full load from the original distribution media. None required. None required. None required. Consult the appropriate manual and verify the useage of the attempted operation. Try it again, if possible. If you try again and still get this error, record the events that led to the error and contact your FRNA tech representative. Contact the FRNA hotline and provide the following information for further investigation. o Record the entire error message(s) that occurred including any program running at the time of the system error. o Retrieve the following files from the File Menu: md:\histe.ls md:\histr.ls md:\hists.ls md:\histp.ls md:\conslog.ls md:\errall.ls o In addition for a system V5.22 or greater, do a diagnostic backup from the file menu to send to FRNA. Cycle power on the controller. If error message persists, then contact the FRNA hotline for further investigation. Please confirm palletizing register. Please correct increment value Check route pattren in palletizing route pattern screen. Teach bottom point all? Teach rout point all? Check palletizing register index palletizing instruction don't teach more than 16 in this program, Please teach another program. In FREE configuation, can be set INTER only one direction (ROW, COLUMN or LAYER) Please select the other motion statement. Refer to the associated error code. OS -012 System error This error may be seen when attempting to monitor a variable or I/O point using the .StartMonitor method. It occurs when you have performed a restore from a controller that did not have the PCIF option installed. To fix this error, set system variable $SCR.$LPCOND_TIME to 40 and cycle power. This variable is set to zero on controllers that do not have the PCIF option installed. When set to zero, the task that performs monitoring is not started on powerup. Perform COLD start of controller. Check physical connections and check to see if PMON server is running on the PC Refer to the associated error code. Refer to the associated error code. Refer to cause code. This is a warning and may be normal. Refer to the associated error code. Somehow, PMON is out of sync with the PC. In some cases, this may be normal if the PC is attempting to clean up after an internal error. Use one the port types defined in IOSETUP.KL. Correct the port number. Delete unneeded KAREL programs and/or variables to free memory. Correct either the first port number or the number of ports. Correct the port number so that it is within the valid range. Correct the port number so that it is within the valid range. Correct the port number. Correct the rack number, slot number, port type, or port number. Correct the number of ports, so that it is within the valid range. Correct the physical port number, so that it is greater than 0. Correct the first port number or number of ports or delete existing assignment using the Digital I/O CONFIG screen or a SET_PORT_ASG call with physical port type zero. Correct the rack and/or slot number. Check the rack and/or slot number and that an analog input sequence has previously been defined. Supply a sequence of an appropriate length. Use the I/O menu or the SET_PORT_SIM KAREL built-in to set the port simulated or do not set the port. Check the cabling between theMAIN CPU PCB (JB-18 connector) and the process I/O board and/or model A or B interface modules. Check power to the remote Model A I/O racks and model B I/O interface modules. If corrections to these do not correct the problem, check the four numbers displayed in this error message. The first value must be interpreted bit-wise. If a bit is 1, the corresponding condition has been detected: Bit 0: (CFER) A CRC or framing error has been detected by the SLC-2 chip on the MAIN CPU PBC. This is most frequently the result of the problems listed above. Otherwise, it might indicate faulty SLC-2 chip, wiring between this and the JB-1B connector on the main PCB, or faulty process I/O, model-A I/O rack, or model-B interface unit. Bit 1: (CALM) An error has been detected by a slave SLC-2 (process I/O board, Model-A rack, or Model B interface unit). More information is provided by the second number displayed with the PRIO-020 error. Bit 2: (CMER) A communication error has been detected by a slave SLC-2. The potential causes are similar to those for a CFER. Bit 3: (IPRER): Internal parity error accessing SLC-2 internal RAM. This indicates a faulty SLC-2 chip. In this case, Replace the device with a device that is compatible with the current software or install a version of software that recognizes the device. Disconnect some devices. Change the port type, add I/O hardware with the required type of ports, or define ports (e.g., GIN or GOUT) of the specified type. Check that the PLC interface board is properly installed. Check the LED status on PLC interface board. Refer to the FANUC Robotics manual, A User's Guide to the FANUC Robotics SYSTEM R-J3 Controller Remote I/O interface for an Allen-Bradley PLC or A User's Guide to the FANUC Robotics Genius Network Interface for GE FANUC. Check the LED status on the PLC interface board. Refer to the FANUC Robotics manual, A User's Guide to the FANUC Robotics SYSTEM R-J3 Controller Remote I/O interface for an Allen-Bradley PLC or A User's Guide to the FANUC Robotics Genius Network Interface for GE FANUC. Check the LED status on PLC interface board. Refer to the FANUC Robotics manual, A User's Guide to the FANUC Robotics SYSTEM R-J3 Controller Remote I/O interface for an Allen-Bradley PLC or A User's Guide to the FANUC Robotics Genius Network Interface for GE FANUC PLC. Check the specified port type. Check the connections and power to the board or rack and that the module(s) are firmly installed. If the board or module has been permanently removed, moved to a different Model A slot or had its switch settings changed (model B), use the CONFIG option on the Digital I/O menu to delete or update the assignment(s). Install the PLC I/O (A-B/GENIUS) software option. Refer to the FANUC Robotics manual, A User's Guide to the FANUC Robotics SYSTEM R-J3 Controller Remote I/O interface for an Allen-Bradley PLC or A User's Guide to the FANUC Robotics Genius Network Interface for GE FANUC. Modify program logic to ensure that not over 255 pulses are active at one time. Install a PLC I/O board into the backplane Refer to the installation procedure in A User's Guide to the FANUC Robotics SYSTEM R-J3 Controller Remote I/O interface for an Allen-Bradley PLC or A User's Guide to the FANUC Robotics Genius Network Interface for GE FANUC. Check other error messages displayed on the TP alarm screen. The conditions indicated by these messages need to be corrected and the controller powered down and up before the robot can be used. Cold start the application. Change main board or remove PMC function. If you need clear this alarm, please turn off K17.2 (SDO[10139]). PMC does not run at power up, and this alarm does not occur until you order to run PMC program. Please refer cause code. Check the power and cabling from Model B interface unit and DI/DO unit, or between DI/DO units. Turn off and then turn on the controller. For DeviceNet ports, troubleshoot as follows: Check the status of the DeviceNet board using the Digital I/O DeviceNet screen. If the status field for the board is OFF, set it ONLINE. If the status is ERROR, check the following: 1.) The daughter board is installed on the Interface board. 2.) There is power on the network. If these do not indicate a problem, set the board ONLINE. If the board is ONLINE, check the DEV LST screen entry for the indicated device. If the status field for the device is OFF, set it ONLINE. If the status is ERROR, check the following: 1. The device is physically present on the network. 2. The baud rate is set correctly. 3. There are not devices with duplicate MAC-Id's on the network. 4. The device with the required MAC-Id is the device type indicated in the DEV LST screen. First, determine the port type and number being accessed. Then use the appropriate Digital I/O CONFIG screen to determine the DeviceNet board and device MAC-Id to which the port is assigned. Check the status of the DeviceNet board using the Digital I/O DeviceNet screen. If the status field for the board is OFF, set it ONLINE. If the status is ERROR, check the following: 1.) The daughter board is installed on the Interface board. 2.) There is power on the network. After the problem is corrected, use the Digital I/O DeviceNet DEV LST screen to set the board ONLINE. If the board is ONLINE, check the DEV LST screen entry for the indicated device. If the status field for the device is OFF, set it ONLINE. If the status is ERROR, check the following: 1. The device is physically present on the network. 2. The baud rate is set correctly. 3. There are no devices with duplicate MAC-Id's on the network. 4. The device with the required MAC-Id is the device type indicated in the DEV LST screen. Once the problem is corrected, use the DEV LST screen to set the device ONLINE. Disconnect some DIGITAL I/O devices. Please stop PMC program execution. Check SYSFAIL of the other PCB. Also check the main PCB. Download PMC program. Download PMC program again. Load PARAM.PMC file. Please check PMC program. Please install Integrated PMC option. 1. Change file name to LADDER.PMC for PMC program, PARAM.PMC for PMC parameter file. 2. Make device name string short. Please try again later, or use the other method. Please check PMC program step size. Please check address in PMC program. Please check address in PMC program. Please check address in PMC program. Please check address in PMC program. Please check address in PMC program. Please check PMC type of FAPT LADDER II. Check the other PMC errors. Chack PMC program, and load again. Press E-STOP or do controlled start. Press wait until writing PMC program is completed. Refer to the previous error messages. It is message only. It is message only. Save the DIO configuration on a compatible version and load this file. Save the DIO configuration on a compatible version and load this file. No action is neccesary; the invalid assignment will not be in effect until it is corrected or the DIO configuration is changed. Look at possible causes. Remedies are mentioned therein. Please look up the error to find the root cause. Reload the configuration from the config tool. For adapter mode, verify that all paramters are correct. Verify that EDS files used for the config tool are valid. Verify that the configuration of the scan- list is valid in the config tool. Verify all connections to the target device from all scanners on the network. Inputs to a device cannot be multicast Check MAC-IDs of all devices on the network Check wiring to the card. Check for duplicate MAC-ID. Ensure that there is atleast one other device on the network. Refer to cause code if listed. If not, refer to the ControlNet error code in the System manual or the ControlNet specification Refer to cause code. Verify Board sys vars to check for validity of values Verify Board sysvars $CN_BD_INFO[%d] are set correctly. Cycle power to the controller for the changes to take affect. Finish the change. When the network is completed, the connections will be restored. If scan list is changed, the power will have cycled for the interface to the restarted. Finish the change. When the network is completed, the connections will be restored. If scan list is changed, the power will have cycled for the interface to the restarted. This is a caution message to the user. This is a caution message to the user. At this point, a network config needs to performed using a network config tool such as RSNetworx. Verify the scan-list configuration and match it with the target device. Verify the connection paths. The connection path expected by the scan- list can be found in the EDS file for the target device. The connection path supported by the target device can be found in its documentation. Verify that the target device and the EDS file used by the Scanner config match. Use correct EDS file in the scan-list config tool and reload the scan-list. Use correct EDS file and reconfigure the scan-list of the CNET interface on the system. Verify correct size and reload the scan-list using the config tool Run a network configuration tool such as RSNetworx and configure the network. Use correct EDS file and reconfigure the scan-list of the CNET interface on the system. Use correct EDS file and reconfigure the scan-list of the CNET interface on the system. Close some connections to target device. Run a network configuration tool such as RSNetworx and configure the network. Check network connections. Check to see that the remote device is online. Check the status of the remote device. Run a network configuration tool such as RSNetworx and configure the network. Check if any other scanner has exisiting connection to the device. Verify that the correct EDS file is being used for the device. Check the target device configuration. Check the configuration on the scanner config tool. Verify correct EDS files are used. Verify Input and Output sizes to devices. Review software configuration to determine how loading can be reduced. Review software configuration to determine how loading can be reduced. Verify all I/O is valid. Check all CNET devices and ensure the sizes are resonable. Max I/O is limited by that allowed for the system. Verify that the target device is online and the status is OK. Verify that correct EDS file was used for the Scan-list configuration in the scanner configuration tool. This is a caution message. Supply name from element tp_daio_tp_names_c in tpdaio*.utx Check the remote scanner configuration. Check the sizes and other configuration parameters such as vendor ID, product code, product type, revision and connection path and verify they are correct. Verify that the scanner is online. Refer to the cause code. Enter a valid header size. The valid header is less that or equal to the total connection size. The total connection size is a sum of the I/O size and the header size. Verify the configuration in the scanner config tool and reload the configuration. Verify that the EDS files are valid. Notify FANUC Please install PROFIBUS PCB. Please exchange PROFIBUS PCB Please change configuration data on Master Please change parameter data on Master Please change Slave Parameter sets on R-J2 Master Please change slave setting. Please change slave setting. Please change slave setting. Please change slave setting. Please change slave setting. Please change slave setting. Please change slave setting. Please exchange PROFIBUS PCB Please exchange PROFIBUS PCB Please exchange PROFIBUS PCB Please exchange PROFIBUS PCB Please connect cable to Slave. Please invstigate the specific diagnostic data. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Check the task name. Check the program name. Check the program name. Check the line number. Check the program name. Check the line number. Check the line number. Check the program name. Check the teach pendant enable switch and other running programs to determine who has motion control. Resume the motion paused the last time. Use RESUME MOTION instruction in the program. Abort dispensable programs or perform a CTRL start and select PROGRAM INIT option to increase the number of tasks allowed. Do not use backward execution at this point Check the task name. The task name is always the name of the program that was run. The task name will not change even if the running program calls a routine from a different program. Check the task name. Resume or abort some programs. Change the NOPAUSE task attribute or use the KCL PAUSE command with the FORCE option. Check the program name. Change the NOABORT task attribute or use the KCL ABORT command with the FORCE option. Pause the program. Do not attempt backwards execution at this time. Do not use backwards execution here. Do not use backwards execution here. Check the task number. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Check the attribute. Do not try to change the attribute. Check the attribute value. Check the routine name and verify it is loaded. Check the teach pendant enable switch and other running programs to determine who has motion control. Set the trace buffer length using the KCL SET TASK TRACELEN command. Turn on tracing using the KCL SET TRACE ON command. Check the teach pendant enable switch and other running programs to determine who has motion control. Check the other running programs to determine who has motion control. Disable the teach pendant. If you had expected that the task may have already released the group, this may not be an error. Otherwise, check UNLOCK_GROUP usage. If you had expected that the task may have already released the group, this may not be an error. Otherwise, check UNLOCK_GROUP usage. If you had expected that the task may have already locked the group, this may not be an error. Otherwise, check LOCK_GROUP usage. If you had expected that another task may have already released the group, this may not be an error. Otherwise, check UNLOCK_GROUP usage. Disable the teach pendant and resume the program. Enable the teach pendant and use shift-FWD to resume execution. Hold the shift key and press the FWD key to resume execution. Check the status of robot motion. Wait a second. If this error continues to occur, perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Check the line number. This requires no special action for the user. Start the user application task before executing the application. Hold the FWD key with shift key to resume execution. Hold the BWD key with shift key to resume execution. Please disable motion data output in test cycle menu. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. Log in, if required. Adjust the timeout value if it is too short. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. Press the TP MENUS hardkey and select SETUP PASSWORDS. Log in with either the Install, Setup, or Program password level. Press the TP FCTN hardkey and select QUICK/FULL MENUS to return to FULL MENUS. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. This is a status message you can use for tracking operations performed by the users. Log in, if required. Adjust the timeout value if it is too short. Log in, if required. Adjust the timeout value if it is too short. Log in, if required. Adjust the timeout value if it is too short. Log in, if required. Adjust the timeout value if it is too short. Use GET_QUEUE to remove entries or use a larger value for queue size in the INIT_QUEUE call. No remedy is required. Correct the value Use zero or a positive value Specify a number less than the string length. Specify a number less than the string length. Specify a positive number. Specify a number between 1 and 32. Specify exisiting group number. specify larger size string variable. Specify correct file attribute id. Specify correct attribute value. Specify a correct register number. Specify the correct register type for the attempted operation. Specify correct position type. Specify correct attribute id. Specify a program name other than a Karel program. Specify a value within the range. Specify correct port id. Use buffer size in the range 1-255. Record position data using the TPP TOUCHUP function Wait until executing motion has completed. Resume stopped motion and wait until motion has completed or cancel stopped motion. Copy constant or local variable to static variable and use this inINI_DYN_DIS* call. Confirm the param_no and the parameter in CALL/MACRO command in main TPE program. Confirm the parameter data type in CALL/MACRO command in main TPE program. Use tag name not over 12 characters. Use name of 4 or less characters. Initialize the array by calling INIT_MTN_OPT Wait for stream program execution to complete more instructions, then retry. Issue the function on an active stream program. Initialize and fill the motion options correctly. Use comment string of 16 or fewer characters. Check the cause code. Check the cause code. Check the cause code. Check the cause code. Check the server connection. Update the client software to use the same version of the RPC protocol. Check the cause code. Update the server software. Update the client or server software. Update the server software. Check the client software. Check the system variables which configure the offline RPC server. Check the cause code. Update the client or server software. Set $RPM_CONFIG.$N_BUFFERS in the range 1-100 Set $RPM_CONFIG.$DATA_SIZE in the range 4-32 Increase the cmos memory by deleting unused TPE Or increase pitch value so that rpm do not need so much cmos space. Check that RECORD is active for this segment and using the correct buffer number. Use a buffer number in the range 1- $RPM_CONFIG.$N_BUFFERS Re-record the whole path Check the position number Or re-record again Time pitch value have to equal or greater than 100 Use motion attached arc start instruction Zero length RPM motion is not allow Use same coordinated motion type (CD or non-CD) to both TAST and RPM program. Please reduce the instruction like a parameter string. Determine what options are installed on the controller on which the program was saved (source cpntroller) and are not installed on the target controller Then, on the source controller, check which of these is used in the program. Assuming the option(s) are authorized for the target controller, install the necessary options. If some of these options are not authorized, it ay be necessary to remove uses of the unauthorized option uses and re-save the program on the source controller. Select another label number. Record this line as LINER or CIRCULAR motion statement Robot Link slave program and slave alone program can not use JOINT position representation. Record this line as CARTESIAN position representation Change Tool frame number of Master Robot or change master tool number in Program detail menu. Please teach only one line in slave program. Notify FANUC Check that the communication setting between the robot and sensor sides is not wrong. Check that the specification and desconnection of cable connecting the robot and sensor. Check the data sent from the sensor. Check the data sent from the sensor. Check the data sent from the sensor. Check that the sensor side does not stop due to an error, for example. Check that the sensor side does not stop due to an error, for example. Check the compensation data sent from the sensor. Record error and report to hotline. Record error and report to hotline. Record error and report to hotline. Check amount of memory being used by the system. Perform a cold start on the controller. Record error and report to hotline. Reteach this instruction with current configulation. Force abort another TPP. Press RESET to clear the error and continue the program. If this error continues to occur, perform a cold start by turning off the robot, then while pressing SHIFT and RESET on the teach pendant, turn the robot back on. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Reteach the instruction. Reteach servo gun SPOT instruction. Check the motion group of this program or robot group motion of servo gun configulation. Check the servo gun group motion of servo gun configulation. Reteach this SPOT instruction to another line. Check the index value. Lower pressure. Record error and report to hotline. Check servo gun configulation data. Higher pressure. Lower Pressure coefficient-B. Change pressure coefficient-A value from 0.1 up to 100. Check the max motor torque in servo gun setup menu. Check the specified pressure and pressure coefficientA,B. Check the status of tip contack. Check the status of tip contack. Add a servo gun condition instruction. Add a servo gun condition instruction. Please calibrate pressure in Pressure Calibration menu. Please calibrate in Wear Down Calibration menu. Specify existing BU condition number. Specify existing P condition number. Teach this instruction. Change position type to XYZWPR. Check the specied pressure value. Check the max torque value. Restart program after tear off function finished. Some chips may stick to the gun side tip. Please check the tip. Some chips may stick to the robot side tip. Please check the tip. Replace or dress the tips and run the tip wear program for each gun. Alternatively, increase the difference tolerance in the wear down check screen. Check the reason of pressure enable signal off. Or Fix the value of time out($SPOTEQSETUP[1].$PEN_TMOUT). Check the reason of comp confirmation signal off. Or Fix the value of time out($SPOTEQSETUP[1].$NSE_TMOUT). Setup pressure enable signal in SPOT I/O. Setup comp confirmation signal in SPOT I/O. Check part or re-enter part thickness. Please increase the size of S-RAM module. Or, decrease the value of $SGSYSCFG.$M_GUN_NUM. Please increase $SGSYSCFG.$M_GUN_NUM to be larger than the total axis number of servo gun group. No remedy required. This is a warning message to log the event. User should cycle power to use servo gun. Restart on tuning menu and try again. Clear ALL FAULTS and start tuning again. Disable STEP mode and start tuning again. Disable Machine lock from TEST CYCLE Menu and start tuning again. Clear HOLD and start tuning again. Cycle power before proceeding. Set the stroke in the backup stroke setup screen. And set TRUE to the item of MANUAL Change the motion group number of the program to match the Servo Gun Set the valid backup stroke to the specified backup stroke index. Set the valid equipment number to $EQNUM. Set the equipment number which is assigned to Servo Gun to $EQNUM. $GUNNUM can be set only 1 or 2 which is corresponding to GUN1 or GUN2 Please perform the Tip Wear Down Calibraiton. Change the frame number to same number of standard position. Check the number of $PRINDEX. Set correct program name in manual operation setup screen. Set correct program name in manual operation setup screen. Set the pressure data in the pressure data setup screen. And set TRUE to the item of MANUAL Set the valid pressure data to the specified pressure data index. Just a notification, no action neccessary. Just a notification, no action neccessary. Just a notification, to let user know he is in this mode and that groups may be disabled automatically for him Just a notification, to let user know he is in this mode and that groups may be enabled automatically for him Set the equipment type to Servo Gun in initial setup screen, and Enable Gun change. Release machine lock. Confirm Gun number assignment. GUN ATTACH instruction can be executed only when no gun is attached. GUN ATTACH instruction can be executed only when no gun is attached. GUN DETACH instruction can be executed only when a gun is attached. Wait until another program end GUN ATTACH/DETACH instruction. Confirm the setting for Gun identify signal. Confirm the setting for Gun set signal. Do COLD START the system. Do COLD START the system. Do COLD START the system. Then master the gun by manual operation. Continue to retry mastering. Please see cause code. Please see cause code. Please perform the mastering of the servo gun axis. Please calibrate the servo gun axis. Quick mastering may not be possible. Fixture or zero master. Verify the gun number of GUN DETACH instruciton. Verify the detect condition in the gun change setup screen. Please set PR[] index for the calibrate motion in the gun change setup screen. Please set Touch torque for the calibrate motion in the gun change setup screen. Please set Detect signal for the calibrate motion in the gun change setup screen. After servo gun axis stops, execute the Gun Zero Master[] instruction. Make sure that the each servogun has valid axisorder Set gun type as opposable, if appropriate. Enable Gun Close. Remove the cause and measure again. Set a valid number to Inform Signal(Gun). Set a valid number to Inform Signal(Robot). Set a valid register number. Set a valid position register number. Set Increased error greater than 0.0mm. Set Increased error greater than 0.0mm. Master the gun. Reset pulse coder alarm again. Run a user program calling TWKINIT. Run a user program calling TW0THOLD. Run a user program calling TW1MTCLB. Run a user program calling TW1MTFIX. Set correct DI index. Confirm gun master positoion and fixture. Complete servo auto tuning. Confirm the gun mastering. And start measurement from gun opened position. Remove the cause and measure again. Record error and report to hotline. Change the calibration motion type(to 7or8) in the Gun change screen. Confirm Touch torque(%) on the Gun change screen is appropriate. Correct the error on the gun number corresponding to gun index 1. Correct the error on the gun number corresponding to gun index 2. The current program was created incorrectly, and does not have its application data area defined. Re-create the program correctly and copy data from the existing program. Check the system ready signal of the sealing equipment or disable the system ready signal. Check the high pressure signal of the sealing equipment, disable to check the high pressure signal, or set the time high pressure timeout to a larger value. Check the gun full open signal of the sealing equipment, disable the check for this feature, or set the timeout for a longer period. The gun full open signal(DI) has been on for the set time since sealing start. Check the gun full open signal of the sealing equipment, disable the check for this feature, or set the timeout for a longer period. Check key switch on the dispensing equipment and equipment setup Visit equipment SETUP menu and complete all calibration procedures Check that the dispenser is full for this operation. Check sealant supply drums to be sure they are properly filled Check dispensing equipment and clear the reported fault Set DRY RUN parameter to OFF and run calibration again. Set ROBOT LOCK parameter to OFF and run calibration again. Set Sealing parameter to enable and run calibration again. Check the sealing equipment ready signal or disable the check of the equipment ready signal. Check the sealing equipment high pressure signal, disable the check for the high pressure signal, or set the timeout value for a longer period Move the robot to the purge position and purge manually or run the next JOB. Increase the maximum number of purges allowed or remove the disposable mixing tip from the gun, to prepare it for long term inactivity. Check gun full open signal of sealing equipment, disable the check of this signal, or set the timeout value for this function to a longer period. Check the gun full open signal of sealing equipment, disable the checking of this alarm, or set the timeout value to a longer time. Decrease the motion speed or increase the maximum output. Perform maintenance and debug procedures as described in the dispensing equipment manual. Perform dispensing gun maintenance and debug procedures. Check the pressure sensors at all points in the system. Perform standard system debug and maintenenace procedures. Follow standard dispensing gun debug and maintenance procedures. Verify that the volume limits are correct for the specified job. Verify that the volume limits are correct for the specified job. Verify that the flowmeter is operating correctly. Perform dispensing gun maintenance procedures. Check the dispensing controller for an error condition. Also check the communication link between the dispensing controller and robot controller. Check the communications link between the dispenser and robot Clear the fault and perform the proper Emergency Stop recovery procedure. Perform the standard dispenser fault recovery procedure. Check that the dispenser is not full at this point in the operation. If it is not full, verify that the dispenser full indicator signal is operating correctly. This is a warning to the operator that the drum may need service This is a warning to the operator that the drum may need service. Check your dispensing equipment for faults, to make sure time out is long enough. If unknown cause -- see next most recent alarm for help. Run calibration again - check Pro-Flo unit for malfunction. If unknown cause -- see next most recent alarm for help. Check Pro-Flo for malfunction or increase dispense time. If unknown cause -- see next most recent alarm for help. Run calibration again - do not enter zero for bead width. Run calibration again - do not enter zero for material weight. Assign a nonzero value for specific gravity. Run cal again. - Check Pro-Flo for malfunction. Assign a nonzero value for dispense time. Run cal again. - If unknown cause -- see next most recent alarm for help. Check why material pressure is zero during calibration. Check pressure transducer and ensure varying pressures during cal. If unknown cause -- see next most recent alarm for help. Check why air pressure is zero during calibration. Do the calibration procedures Check dispensing equipment for faults, or give the time out variable more time Perform pressure calibration before running this calibration. If unknown cause -- see next most recent alarm for help. Perform analog calibration before running this calibration. Perform atom air calibration before running this calibration. Set voltage step to nonzero value before running this calibration. Perform material calibration before running this calibration. Set timeout to nonzero value before running this calibration. Check atomizing air equipment If unknown cause -- see next most recent alarm for help. Check dispensing equipment and run calibration again. Perform volume signal calibration. Set proper I/O ports for all necessary dispenser I/O. Check dispenser for futher information. Check the index value of this SS instruction. Increase the distance between sealing instructions, or delete one of the sealing instructions. Change motion type from joint to linear or circular. Change motion type from joint to linear or circular. Check the equipment number in the program detail display. Add an SE instruction. Set the equipment number in the program detail display. Change the equipment number or check interlock of each program. Wait until other equipment is done in zone, or Check I/O for proper communication Set the I/O port index to the correct value Volume set points must be established after program execution Check SS instruction on this program. Ensure MOV_ program is executable. Reset holds and emergency stops. Enter a valid setting for desired volume or bead width. If unknown cause -- see next most recent alarm for help. Teach utool before running this calibration. Teach REFPOS before running OFFSET calibration. Check for damaged tool, change tip and run calibration again. Run calibration again while maintaining REFPOS configuration Perform cold start or temporarily SELECT a different file. Create and teach the file. Check supply air to the tool Check proximity sensors on the tool Check to see if release mechinism is working Check to see if clamping mechinism is working Check sensor correct operation Check sensor correct operation Go to Tool Setup and setup gripper configuration Set up IO port as a complementary port Check supply air to the tool Check proximity sensors on the tool Check supply air to the tool Check proximity sensors on the tool Check supply air to the tool Check proximity sensors on the tool Check supply air to the tool Check proximity sensors on the tool Calibrate robot and run calibration again. Run calibration again. Contact FANUC Robotics Hotline. Go to the Equipment Output menu and verify that all the Gun on, Start Meter, and Atomizing Air outputs are correctly defined or their indexes are set to zero. If the VALUE of a output port is '****', then the index number must be set to zero and the robot must be cold started. You must cold start the robot after changing anything on this menu. There is no real danger in this condition. You should be aware that if you try to turn the gun on or off after 100ms AFTER the node, the signal will always be fired 100ms after the node and this warning will be posted. To correct this problem, make the equipment_delay more positive or the gunon/gunoff delay more negative, to move the firing of the signal up earlier. Please change it after sealing is finished Please disable Motion Trigger function Decrease the atomizing air pressure of sealing schedule or increase the maximum output. Increase the atomizing air pressure of sealing schedule. If unknown cause -- see next most recent alarm for help. Perform the Caribration of the Atomizing Air in the setup screen. Please change the program. Increase the flow command in sealing schedule. Correct maximum or minimum output value for flow command in setup screen. Correct maximum or minimum output value for atomized air in setup screen. Enable Pre-Pressure control in SETUP screen. Execute Pre-Pressure command before or after sealing. Set the speed override to 100% Please call Fanuc service center. Please call Fanuc service center. Please call Fanuc service center. Look at spot instruction again. Setup Spot I/O again or increase Weld done time out value. Detect cause that weld alarm occurred and remove it. Setup Spot I/O again. Setup Spot I/O again. Setup Spot I/O again. look at Weld schedule number again. Check close backup signal type(SDO or RDO) and index. Check close detect signal type and index. Check clamp signal type and index. Check Full open detect signal type and index. Check Half open detect signal type and index. Check Open backup signal type and index. Check Gun pressure signal type and index. Check Weld schedule signal type and index. Check H/M/L Valve signal type and index. Check Weld enable signal type and index. Check Weld on signal type and index. Check Weld completion signal type and index. Check Spot I/O again or increase Weld done time out. Check Spot I/O again or increase Weld control time out. Check Spot input signals. Check Spot output signals. Check the number of equipment in program. look at register again. Check the weld complete signal input length. Check the weld complete signal of spot weld device. Check the weld complete signal input length. Check the weld complete signal of spot weld device. Please abort the another program which use the same equipment. Check Spot instruction. Check Spot output signals. Please power off. Please push shift key Set valid macro program name in the stop setup screen. Clear the motion mask of the macro program. System error. Open serial port before using it. Do not try to open the serial port which has already be opened. Initialize the serial port before using it. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check target device status. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check if serial port setup is correct. Check if cable is broken. Check if there exists a noise source near controller. Check target device status. Check the hardware. System error. System error. System error. Twist the operator panel emergency stop push button clockwise to release. Press RESET. Twist the teach pendant emergency stop push button clockwise to release. Press RESET. Press teach pendant deadman switch. Press RESET. Establish a connection between FENCE1 and FENCE2, then press the RESET key. When a safety door is connected, close the door before starting work. Perform the following steps: 1. Jog the robot off of the overtravel switch: 1) Press MENUS. 2) Select MANUAL FCTNS. 3) Press F1, [TYPE]. 4) Select OT_RELEASE. The axis that has overtraveled will display TRUE in either OT_MINUS or OT_PLUS. 5) Move the cursor to the OT_MINUS or OT_PLUS value of the axis in overtravel. 6) Press F2, RELEASE. The value of the overtraveled axis should change back to FALSE. 7) Press and hold down the SHIFT key until you have completed Steps 1) through 4). 8) Press RESET and wait for the servo power to turn on. 9) Press COORD until the JOINT coordinate system is selected. 10) Continuously press and hold the DEADMAN switch and turn the teach pendant ON/OFF switch to ON. 11) Jog the overtraveled axis off of the overtravel switch. When you have finished jogging, you can release the SHIFT key. 12) Turn the teach pendant ON/OFF switch to OFF and release the DEADMAN switch. NOTE: If you accidentally release the key during this procedure, you will need to repeat Step7). 2. While you hold down the SHIFT key, press RESET to clear the alarm. 1. While holding down the SHIFT key, press the alarm release button to clear the alarm. 2. While holding down the SHIFT key, position the tool to the workplace by jogging. 1) Replace the safety hand. 2) Check the cable. 3. Check cable RP1 for loose connection, damaged pins, or damaged cable. 4. Replace the servo amplifier. If using external emergency stop, clear the source of the fault, and press RESET. If not using external emergency stop, check the wiring at EMGIN1 and EMGIN2. Replace the fuse. Check the LED (FALM) on the printed circuit board for emergency stop control to determine whether the fuse has blown. If the pneumatic pressure alarm is not detected, check the cable. 1. If the belt is found to be defective in any way, repair it and then press the RESET key. 2. When the belt is found to be normal, the signal RDI[7] in the robot connection cable might be abnormal. Check the cable. 3. Check the system variable $PARAM_GROUP.$BELT_ENABLE. Reconnect the teach pendant cable to continue operation. This is just a notification. You do not have to do anything for this warning message. Turn on the power in cold start mode. Check the fan motors and fan motor connection cables. Replace any faulty fan motor(s) and/or cable(s). 1. If the ambient temperature is higher than the specified temperature (45 degrees C), provide ventilation to reduce the ambient temperature to the specified value. 2. Check that the fans are operating normally. If not, check the fan motors and fan motor connection cables. Replace any faulty fan motor(s) and/or cables(s). 3. If the thermostat on the backplane printed circuit board is faulty, replace the backplane unit. Consult your FANUC Robotics technical representative. Consult your FANUC Robotics technical representative. 1. Verify that the RM1 cable that carries the signal wires from the the controller to the robot is securely connected and that the pins and cable are not damaged. 2. Check the brake cable. 3. Replace the servo amplifier if bad. Establish a connection between *SVON1 and *SVON2. Check the teach pendant cable and connections. 1. Check whether the door is open. Also check the door switch. 2. Check the following cables. Replace them if necessary: connector CRR15 on the emergency stop board, terminals A1 and A2 on the MCC contactor, and connector CRR20 on the emergency stop board that connects to terminals 1, 2, 3 of the MCC contactor. 3. Replace the magnetic contactor and then the emergency stop printed circuit board. WARNING: Before you continue to the next step, perform a complete controller backup to save all of your programs and settings from memory for this robot. After you complete the next step, restore the saved data to the new Main CPU board if memory has been lost. Otherwise, you could injure personnel, damage equipment, or lose data. 4. Verify that the battery is securely connected to the Main CPU board before removing the board. Replace the axis control card on the Main CPU board. 5. Replace the MCC contactor. 6. If this does not clear the alarm, verify that all connectors are securely connected. WARNING: Before you continue to the next step, perform a complete controller backup to save all of your programs and settings from memory for this robot. After you complete the next step, restore the saved data to the new Main CPU board if memory has been lost. Otherwise, you could injure personnel, damage equipment, or lose data. 1. Verify that the battery is connected to the Main CPU board before removing the Main CPU board. Replace the axis control card on the Main CPU board. 2. Replace the servo amplifier. 3. If this does not clear the alarm, verify that all connectors are securely connected. 1. Check whether the applied load exceeds the rating. If so, reduce the applied load. If an excessive load is applied, the torque required for acceleration, deceleration, and so forth exceeds the maximum available torque of the motor. Therefore, it might prove impossible to correctly respond to an issued command, resulting in the output of this alarm. 2. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier. If the voltage is found to be 170 VAC or below, check the input power supply voltage. A sub-standard voltage, applied to a servo amplifier, results in a lower-than-normal torque. Therefore, it might prove impossible to correctly respond to an issued command, thus resulting in the output of this alarm. Check phase-to-phase voltage across the three pins of connector CRM38A or CRM38B of the servo amplifier. 3. If the input power supply voltage is found to be 170 VAC or higher, replace the servo amplifier. 4. Check the motor power cables (RM1, RM2, RM3) for damage, to cable or pins, and that the connector is securely connected. 1. Check whether the applied load exceeds the rating. If so, reduce the applied load. If an excessive load is applied, the torque required for acceleration, deceleration, and so forth exceeds the maximum available torque of the motor. Therefore, it prove impossible to respond to an issued command correctly, causing this alarm to occur. 2. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier. If the voltage is found to be 170 VAC or below, check the input power supply voltage. A sub-standard voltage, applied to a servo amplifier, results in a lower-than-normal torque. Therefore, it might prove impossible to correctly respond to an issued command, thus resulting in the output of this alarm. Check the phase-to-phase voltage across the three pins of connector CRM38A of the servo amplifier. 3. If the input power supply voltage is found to be 170 VAC or higher, replace the servo amplifier. 4. Check the motor power cables (RM1, RM2, RM3) for damage, to cable or pins, and that the connector is securely connected. WARNING: By completing the next step you will be altering the Perform a cold start: 1. Turn off the robot. 2. On the teach pendant, press and hold the SHIFT and RESET keys. 3. While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. This is just a notification. However, you should attempt to eliminate this error and not repeat the circumstances that led up to it. Perform mastering from the calibration screen [6 SYSTEM CALIBRATION]. Disable [TEMPORARY STOP/SERVO OFF] on the general item setting screen [6 GENERAL SETTING ITEMS]. This is just a notification. You do not have to do anything for this warning message. Perform calibration by performing the procedure below: 1. Turn on power. 2. Execute [CALIBRATION] from the calibration screen [6 SYSTEM CALIBRATION]. Set a reference point for simple mastering from the calibration screen. Every attempt should be made to eliminate this error. 1. Check whether the applied load exceeds the rating. If so, reduce the applied load. If an excessive load is applied, the torque required for acceleration, deceleration, and so forth exceeds the maximum available torque of the motor. Therefore, it might prove impossible to correctly respond to an issued command, resulting in the output of this alarm. 2. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier. If the voltage is found to be 170 VAC or below, check the input power supply voltage. A sub-standard voltage, applied to a servo amplifier, results in a lower-than-normal torque. Therefore, it might prove impossible to correctly respond to an issued command, thus resulting in the output of this alarm. Check phase-to-phase voltage across the three pins of connector CRM38A of the servo amplifier. 3. If the input power supply voltage is found to be 170 VAC or higher, replace the servo amplifier. 4. Check the motor power cables (RM1, RM2, RM3) for damage, to cable or pins, and that the connector is securely connected. Turn on the *IMSTP signal. First perform an APC reset and remaster the robot: 1. Press MENUS. 2. Select SYSTEM. 3. Press F1, [TYPE]. 4. Select MASTER/CAL. 5. Press F3, [RES-PCA]. 6. Press RESET. 7. Perform a Cold start. WARNING: By completing the next step you will be altering the positional reference for the robot since you are replacing hardware. You must slowly verify all positional data and touch-up any paths or points that have changed. Otherwise, you could injure personnel or damage equipment. 8. Remaster the robot if needed. If remastering is performed, you must verify all of your robot paths to prevent damage to equipment. If the pulse mismatch is not reset: 1. Check the pulse coder cable from the motor. 2. Check the internal cable set next. 3. Check the P1 cable from the robot to the controller, verify that there are no pins damaged at the robot base connection and that there is not damage to the cable. 4. Replace the pulse coder and remaster Reduce the motion speed or disable CMC. This message is only for S-420iR. S-420iR has the mark at non-zero position for J2 and J3. So Zero position master is not done with zero pos for S-420iS. Confirm the position of each axis to be at mark position. If the robot is not S-420iR, $scr_grp.$robot_model may be wrong. Set correct $scr_grp.$robot_model. Document the events that led to the error and call your FANUC Robotics technical representative. 1. If this alarm occurs with a SRVO-049 OHAL1, turn the power off for 15 seconds. Then turn the power back on. 2. Check the cable between the servo amplifier and the axis control printed circuit board. 3. Replace the servo amplifier. 4. Replace the axis control printed circuit board. When the LED indicator of the servo amplifier PSM displays '8' (DCOH alarm) (the DCOH alarm is issued when the thermostat detects overheating of the regenerative resistor): 1. This alarm might be raised when acceleration/deceleration is frequently performed or when a large amount of regenerative energy is generated in the vertical axis. In such cases, the robot should be used under less demanding conditions. 2. Check fuse FU1 on the servo amplifier. 3. Replace the regenerative resistor. 4. Check the cable between the servo amplifier (CRR45A) and the regenerative resistor. Replace it if necessary. 5. If this does not clear the alarm, verify that all connectors are securely connected. 1. Check the three-phase input voltage applied to the servo amplifier. When the voltage is 253 VAC or higher, check the input power supply voltage. If the motor is abruptly accelerated or decelerated while the three-phase input voltage exceeds 253 VAC, this alarm might be issued. 2. Check whether the applied load is within the rated value. If the rated load is exceeded, reduce the applied load. If a load exceeds the rated value, built-up regenerative energy might cause this alarm to be issued even when the three-phase input voltage satisfies the specifications. 3. Check the cables (CN3 and CN4) in the amplifier. Replace them if necessary. 4. Check the cable between the main CPU printed circuit board (JRV1) and the printed circuit board for the emergency stop control (JRV1). 5. Replace the servo amplifier. 1. Relax operating conditions if cooling down clears this problem. 2. Disconnect the motor power line from the terminal block of the servo amplifier, then turn on the power. If this alarm is still issued, replace the servo amplifier. 3. Remove the motor power line from the terminal block of the servo amplifier, then check the insulation between U, V, and W of the motor power line and GND. If a short circuit is found, check the motor, robot connection cable, or robot internal cable. If any abnormality is found, replace the faulty hardware. 4. Remove the motor power line from the terminal block of the servo amplifier, then check the resistance between U and V, V and W, and W and U of the motor power line using a measuring instrument capable of detecting very low resistances. If the measured resistances differ from each other, check the motor, robot connection cable, or robot internal cable. If any abnormality is found, replace the faulty hardware. 5. Replace the servo amplifier. 6. If this does not clear the 1. Check the operating conditions of the robot. If the robot's ratings, such as the rated duty cycle and load, are exceeded, modify the use of the robot such that the rated values are not exceeded. 2. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier connector CRR38A, which is 3-phase, and connector CRR39, which is single-phase. If the applied voltage is found to be 170 VAC or less, check the input power supply voltage. 3. Replace the servo amplifier. 4. If this does not clear the alarm, verify that all connectors are securely connected. 5. Replace the motor. When the LED indicator on the servo amplifier displays '6' (this alarm is issued when the control power supply voltage (+5 V) is excessively low): 1. Replace the servo amplifier. 2. Replace the power supply PCB. None applicable. 1. Check the operating conditions of the robot. If any of the ratings specified for the robot, such as its rated duty cycle or load, are exceeded, modify the use of the robot so that the ratings are not exceeded. 2. Check whether the fuse (F1, F2) in the servo amplifier has blown. 3. Replace the servo amplifier. 4. If this does not clear the alarm, verify that all connectors are securely connected. 5. Replace the transformer. 1. Check whether the robot has collided with an object. If so, reset the system, then move the robot away from the location of the collision by jogging. 2. Check that the applied load does not exceed the maximum rating. If the rated load is exceeded, reduce the applied load. If the robot is used with an excessive load applied, the estimated disturbance might become excessively large, resulting in this alarm being output. 3. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier. If the applied voltage is found to be 170 VAC or less, check the input power supply voltage. 4. Replace the servo amplifier. 1. Replace the servo amplifier. 2. If this does not clear the alarm, verify that all connectors are securely connected. If operation is allowed to continue, a detection error might result. On the status screen containing the disturbance value, specify a new value for the acceptable disturbance limit. WARNING: Before you continue to the next step, perform a complete controller backup to save all your programs and settings from memory for this robot. After you complete the next step, restore the saved data to the new main CPU board if memory has been lost. Otherwise, you could injure personnel, damage equipment, or lose data. Replace the axis control card on the main CPU board. Check the FSSB hardware connection. Check the FSSB hardware connection. Check the FSSB 1 hardware connection of fiber cables between the amplifier and DSP card. Check the servo amplifier or connection of the servo amplifier. Check the FSSB 2 hardware connection of fiber cables between the amplifier and DSP card. If this alarm occurs along with a SRVO-068 DTERR, SRVO-069 CRCERR, or SRVO-070 STBERR, disregard this alarm and refer to the other three alarm remedies. Replace the pulse coder or motor and master the robot. Correct the cause of the alarm, then turn on power again after setting the system variable $MCR.$SPC_RESET to TRUE. Master the robot. 1. Eliminate the cause of the alarm. Set the system variable $MCR.$SPC_RESET to TRUE, and turn the power off and then on again. Master the robot. 2. Replace the pulse coder. Master the robot. NOTE: The RCAL alarm might be displayed when any of the SERVO-068 DTERR, SERVO-069 CRCERR, or SERVO-070 STBERR alarms is raised. In this case, however, this alarm can be safely ignored. Replace the pulse coder. After replacing, master the robot. NOTE: If a DTERR, CRCERR, or STBERR alarm is issued, this alarm might also be output at the same time. Should this occur, however, this alarm can be safely ignored. Replace the battery. When this alarm is issued, immediately replace the battery while the system power is turned on. If the BZAL alarm is issued because the battery is not replaced in time, positional data will be lost, thus making it necessary to master the robot. If this alarm occurs along with a SRVO-068 DTERR, SRVO-069 CRCERR, or SRVO-070 STBERR, disregard this alarm and refer to the other three alarm remedies. Replace the pulse coder or motor and master the robot. 1. Check the operating conditions of the robot. If any of the ratings specified for the robot, such as its rated duty cycle or load, are exceeded, modify the use of the robot so that the ratings are not exceeded. 2. If this alarm is issued, even when the power is turned on and the motor has not overheated, replace the motor. 1. Check the shielding for the pulse coder cables to ground. The ground wire is the yellow and green wire connected to the robot base. 2. Inspect the pulse coder cable set for breaks, internal robot set, and P1 cable running from the robot to the controller. WARNING: By completing the next step you will be altering the positional reference for the robot since you are replacing hardware. You must slowly verify all positional data and touch-up any paths or points that have changed. Otherwise, you could injure personnel or damage equipment. 3. Replace the pulse coder and remaster the robot. 4. Replace the P1 cable. 5. Replace the internal cable set. 1. Check the shielding for the pulse coder cables to ground. The ground wire is the yellow and green wire connected to the robot base. 2. Inspect the pulse coder cable set for breaks, internal robot set, and P1 cable running from the robot to the controller. WARNING: By completing the next step you will be altering the positional reference for the robot since you are replacing hardware. You must slowly verify all positional data and touch-up any paths or points that have changed. Otherwise, you could injure personnel or damage equipment. 3. Replace the pulse coder and remaster the robot. 4. Replace the P1 cable. 5. Replace the internal cable set. 1. Check the shielding for the pulse coder cables to ground. The ground wire is the yellow and green wire connected to the robot base. 2. Inspect the pulse coder cable set for breaks, internal robot set, and P1 cable running from the robot to the controller. WARNING: By completing the next step you will be altering the positional reference for the robot since you are replacing hardware. You must slowly verify all positional data and touch-up any paths or points that have changed. Otherwise, you could injure personnel or damage equipment. 3. Replace the pulse coder and remaster the robot. 4. Replace the P1 cable. 5. Replace the internal cable set. 1. This alarm does not indicate the main cause of the problem issued together with the PHAL alarm (SRVO-064). 2. Check whether the load applied to the robot exceeds the maximum rating. If the rated load is exceeded, reduce the applied load. After replacing, master the robot. 3. Replace the pulse coder of the motor. Replace the pulse coder, then master the robot. Perform simple mastering and improve the shielding. Replace the pulse coder, then master the robot. Jog the robot along each axis for which this alarm is issued, until the alarm is not re-issued after being cleared. Reset the robot by using the teach pendant reset and JOG the robot away from any obstruction. If no tip stick detection or collision, the load on the robot may exceed the specification. Check input power to the servo amplifier. It should be greater than 170 VAC phase-to-phase. Also check the voltage between U-V, V-W, and U-W. Each should measure the same ( 210VAC). Contact your FANUC Robotics technical representative. 1. Check the pulse coder cable. 2. Replace the pulse coder. Refer to the SRVO-061 remedy. Refer to the description for the SRVO-062 BZAL alarm. Refer to SRVO-063. Refer to the description for the SRVO-064 PHAL alarm. Refer to the description of the SRVO-065 BLAL alarm. Refer to SRVO-066 remedy. Refer to the description of the SRVO-067 OHAL2 alarm. Refer to the description of the SRVO-068 DTERR alarm. Refer to the description of the SRVO-069 CRCERR alarm. Refer to the description of the SRVO-070 STBERR alarm. Refer to the description of the SRVO-071 SPHAL alarm. Refer to description of the SRVO-072 PMAL alarm. Refer to the description of the SRVO-073 CMAL alarm. Refer to description of the SRVO-074 LDAL alarm. Refer to description of the SRVO-075 Pulse not established alarm. Refer to SRVO-005. Refer to SRVO-006. Refer to SRVO-009. Close controller door and press RESET. If the reset is not effective, correct the hardware connection. Close controller door and press RESET. If the reset is not effective, correct the hardware connection. Check the brake for zero or abnormally low impedance. Then check the brake cable. Then check 200VAC. Then check the servo amplifier or emergency stop control PCB if brake ports are used. Press the RESET key to enable the robot. Make $SFLT_FUPTIM larger. Make $SFLT_FUPTIM larger. Find and remove the cause of the position error becoming greater. Or, make the tolerance larger, turn off and then turn on the controller. The tolerance is the value of the following system variables. X direction [mm] : $PARAM_GROUP[].$CB_IX Y direction [mm] : $PARAM_GROUP[].$CB_IY Z direction [mm] : $PARAM_GROUP[].$CB_IZ Contact your FANUC Robotics technical representative. Contact your FANUC Robotics technical representative. Reduce the motion speed. Press RESET. Refer to the maintenance manual. Refer to the maintenance manual. Refer to the maintenance manual. Refer to the maintenance manual. Check the cables and connections between the amplifier (CN1) and the MCC. Check the fuse (F1,F3) in the transformer. If using a B-cabinet, replace the EMG control printed circuit board. Replace the amplifier. Check or replace the fan. Check the cables and connections between the amplifier (CN1) and the MCC. Check the fuse (F1,F3) in the transformer. If using a B-cabinet, replace the EMG control printed circuit board. Replace the amplifier. Refer to the maintenance manual. 1. If the alarm disappeared by power off/on, please make sure the cable shields are grounded. 2. If this problem occurs repeatedly, replace the pulse coder and master the robot. Refer to SRVO-049. If the robot is overloaded or the duty cycle exceeds specification, this alarm occurs. Check the regenerative discharge transistor. Check the thermostat on the servo amplifier after the servo amplifier has cooled. It should not be open. If the problem persists, replace the servo amplifier. Check the controller cabinet fans for blocked filters; clean them if necessary. Check the connections and cables of the input power. Refer to SRVO-047. Refer to SRVO-147. Check each interphase voltage of the three-phase voltage (200 VAC) applied to the servo amplifier. If the applied voltage is found to be 170 VAC or less, check the input power supply voltage. Replace the servo amplifier. 1. Check the cable between the servo amplifier (CN1) and the MCC. Replace it if necessary. 2. For a model using the B cabinet, check whether the transformer fuses (F1 and F3) have blown. 3. Replace the printed circuit board for emergency stop control. 4. Replace the servo amplifier. Disconnect the motor power wires from the servo amplifier and turn on power. If an HCAL occurs, replace the transistor module or servo amplifier. Measure the resistance between GND and U, V, W individually on the cable terminals. If shorted, determine if the cable or motor is bad. Check the resistance between U-V, V-W, and W-U using a measuring instrument sensitive enough to detect small resistances at the cable terminations. If the resistances are the same, replace the servo amplifier. If the resistances are different, determine if the cable or motor is bad. If the problem persists, replace the SIF module on the axis control for the defective axis. Refer to SRVO-045. Check the fan. Replace it if necessary. Check or replace the fan. 1. The IPM might be overheated. Reset the emergency stop after approximately ten minutes. Disconnect the power lines from the terminals on the amplifier, and check the insulation of PE from U, V, and W. 2. If there are short circuits, disconnect the motor connector power lines and check the insulation of PE from U, V, and W. 1) Replace the motor if U, V, and W short-circuit with PE. 2) Replace the power lines if U, V, and W do not short-circuit with PE. 3. Noise on the actual current (IR, IS) running in the amplifier module might cause this alarm. Remove this noise such as with taking ground of sealed earth. 4. Replace the amplifier. The DC link might cause a short-circuit. Check the connections. Also, electric resistance to restrict charge current might be defective. Replace the wiring board. Refer to SRVO-044. Refer to SRVO-043. Replace the IPM module. Refer to the maintenance manual for details. The DC link might cause a short-circuit. Check the connections. Electric resistance to restrict charge current might be defective. Replace the wiring board. Refer to the maintenance manual for details. Release the emergency stop button. If the external emergency stop function has been activated, remove the cause. If no cause can be found, and no jumper is installed between EMGIN1 and EMGINC or between EMGIN2 and EMGINC on the terminal block of the emergency stop control printed circuit board, but cables are connected to the terminals, check the cables. Press teach pendant deadman switch or determine the cause of the fence and then press RESET. Remove the cause then press RESET. Change the DSM hardware to be same. Change the current DSP-IV module to DSP_V or initialize the robot library again to load the correct servo parameter file. This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. Internal motion error. Contact your FANUC Robotics technical representative immediately. This is just a notification. You do not have to do anything for this warning message. Press RESET. Be careful not to move the robot while identifying the payload. Perform Power OFF/ON: 1. Turn off the robot. 2. Turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Remove the cause of Servo ready not being on. Then, press RESET. Wait the other task finishing the process. And, retry. Get the data of the group that this command is to use. And, retry. Get the needed data. And, retry. Specify the mass parameter when estimating the current payload's parameters. Please increase Controller's memory (temporary memory). Internal motion error. Contact your FANUC Robotics technical representative immediately. Close the fence circuit or SVON input circuit, and then press RESET. Close SVON input circuit, and then press RESET. Refer to the maintenance manual for details. Connect servo, and then press RESET. Refer to the maintenance manual for details. Press the Non Teacher Enabling Device or connect servo, and then press RESET. Refer to the maintenance manual for details. Power off. Correct the wiring on SVON. Close the fence circuit or SVON input circuit, and then press RESET. Power off. Correct the wiring on SVON. Close the SVON input circuit, and then press RESET. After this alarm, a fence open or SVON input alarm is detected. See the remedy of the next alarm. Check and/or replace the fan. Refer to the maintenance manual for details. Check the wiring of SVEMG. If the wiring of SVEMG is not connected, correct the wiring of SVEMG. If the wiring has no problem, twist the operator panel emergency stop push button clockwise to release. Press RESET. Refer to the maintenance manual for details. Check the wiring of SVEMG. If the wiring of SVEMG is not connected, correct the wiring of SVEMG. If the wiring has no problem, twist the teach pendant emergency stop push button clockwise to release. Press RESET. Refer to the maintenance manual for details. Power off. Correct the wiring on SVEMG. If using external emergency stop, clear the source of the fault, and press RESET. Refer to the maintenance manual for details. Power off. Correct the wiring on SVEMG. Close the fence circuit and then press RESET. Refer to the maintenance manual for details. Power off. Correct the wiring on SVEMG Power on. Press the teach pendant deadman switch. Press RESET. Refer to the maintenance manual for details. Close the controller door. If door is not opened, correct the wiring on SVEMG. Or correct the enable switch and deadman switch on the teach pendant. Press RESET. Refer to the maintenance manual for details. Check the brake for zero or abnormally low impedance. Then check the brake cable. Then check 200VAC. Then check servo amplifier or emergency stop control PCB if brake ports are used. Refer to the maintenance manual for details. Power off. Correct the wiring of SVEMG on the controller of the second robot. Close the fence circuit and then press RESET. Power off. Correct the wiring on SVEMG on controller of Extended robot. Close fence circuit and then press reset. Change the TP Enable/Disable switch to ON And press RESET If the reset is not effective, correct hardware connection Change program to be slow down Replace fuse on 6 Panel PCB Replace fuse on 6 axis amplifier Replace fuse on Aux axis amplifier Change program speed to be slow Check whether the number of the DSP is enough on the DSP board related to the axis number of $SCR_GRP[].$AXISORDER[]. Change the DSP board that has enough DSP. Or change the setting of $AXISORDER. Check whether fiber cable to the amp is connected correctly. Or change the fiber cable to the amp And check whether power of the amp is normal or not. Or verify whether the setting of $AXISORDER[] and $AMP_NUM[]. are correct or not Repair the circuit of the chain 1 (+24V) on the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 2 (0V) on the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Push RESET on the teach pendant. Press the Non Teacher Enabling Device and then press RESET. Set the TP Enable/Disable switch to ON, close the controller door, and press RESET. If the reset is not effective, correct the hardware connection. This is just a notification. If this error occurs with a deadman switch release alarm, release the deadman switch again and press the deadman switch. Or, if this error occurs with another safety signal error, reproduce the same safety error and press RESET. If SRVO-230 or SRVO-231 occur, refer the to cause and remedy of these errors. The status of the chain failure has changed to normal when the system checked the chain failure again. Press RESET. Repair the circuit of the chain 1 (+24V) on the hardware. Press the emergency stop on the teach pendant and twist the teach pendant emergency stop push button clockwise to release. Press RESET. Repair the circuit of chain 1 (+24V) on the SVON hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 2 (0V) on SVON the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 1 (+24V) on FENCE the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 2 (0V) on the FENCE hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 1 (+24V) on the External Emergency stop hardware. Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG the screen. Press RESET on the teach pendant. Repair the circuit of the chain 2 (0V) on the External Emergency stop hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 1 (+24V) on the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of the chain 2 (0V) on the hardware. Set CHAIN FAILURE detection to TRUE on the SYSTEM/CONFIG screen. Press RESET on the teach pendant. Repair the circuit of E.Stop hardware Power off/on again Repair the circuit of the chain 1 (+24V) on Non Teacher Enabling Device hardware. Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of the chain 2 (0V) on Non Teacher Enabling Device hardware. Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of the chain 1 (+24V) on Servo disconnect signal circuit. Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of the chain 2 (0V) on Servo disconnect signal circuit. Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of MON3 on E.STOP unit Repair the circuit of MON3 on E.STOP unit Repair the circuit of FENCE1 Repair the circuit of FENCE2 Repair the circuit of SVOFF1 Repair the circuit of SVOFF2 Repair the circuit of EXEMG1 Repair the circuit of EXEMG2 Repair the circuit of SVDISC1 Repair the circuit of SVDISC2 Repair the circuit of NTED1 Repair the circuit of NTED2 Change mode switch to T1 ot AUTO Check the wiring of SVEMG. If the wiring of SVEMG is not connected, correct the wiring of SVEMG. If the wiring has no problem, twist the operator panel emergency stop push button clockwise to release. Press RESET. Refer to the maintenance manual for details. Check the wiring of SVEMG. If the wiring of SVEMG is not connected, correct the wiring of SVEMG. If the wiring has no problem, twist the teach pendant emergency stop push button clockwise to release. Press RESET. Refer to the maintenance manual for details. Repair the circuit of MON1,MON2,MON3 on E.STOP unit Determine the cause to input SVOFF and repair. Power off. Correct the wiring on SVEMG Close SVOFF input circuit, and then press reset. Repair the circuit of chain 1 (+24V) on SVOFF hardware Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of the chain 2 (0V) on SVOFF hardware Set CHAIN FAILURE detection to TRUE on SYSTEM/CONFIG screen And push reset button on Teach pendant Repair the circuit of MON3 on E.STOP unit Repair the circuit of MON3 on E.STOP unit Check input power to PSM Check the voltage between U-V,V-W,and U-W. Change PSM unit Exchange external FAN Change cable between PSM and SVM Change SVM. Or change PSM Change program speed to be lower Or check whether Fan for PSMR is working If the fan is out of order, exchange the fan Change cable between PSM and SVM Change PSM. Or change SVM Check status of pulse coders and motors Power off and on to reset Press reset key to clear alarm. Verify whether robot has hand broken equipment or not. If it doesn't have, HBK signal status is changed Press reset key to clear alarm. Verify whether robot has hand broken equipment or not. If it doesn't have, HBK signal status is changed Change Hand broken to Enable. Press reset key to clear alarm. Change Hand broken to Enable. Press reset key to clear alarm. Change mamual brake mode to disable. Press reset key to clear alarm. Internal motion error. Contact your FANUC Robotics technical representative immediately. This is an internal error. Contact your FANUC Robotics technical representative. Increase $SCR.$MPDT_TIMLMT value 1000 by 1000 until this alarm does not occur. If this alarm occurs when $SCR.$MPDT_TIMLMT is 20000, contact your FANUC Robotics technical representative. Disable machine lock for that group. Clear the reason of SRDY off. If alarm can not reset when reset key is pressed this is abnormal status of E.STOP circuit Then fix E.STOP circuit Fix Enable/Disable switch or deadman switch Set SVOFF signal to be OFF And press RESET key. If the alarm can not reset when reset key is pressed this is abnormal status of E.STOP circuit Then fix E.STOP circuit Call your FANUC Robotics technical representative. Call your FANUC Robotics technical representative. Turn off/on the controller. And execute single axis mastering on the axis And execute calibration Turn off/on the controller. Wait for the special checking space to clear. Set the priority valid Not use AccuPath or disable space check function Remove CTV option or disable space check function This is only information. You can reset the alarm with SHIFT+RESET and can jog the robot to the out of the interacted area. This key operation disable the interaction check temporarily while the SHIFT key is being pressed. You can reset the alarm with SHIFT+RESET and can jog the robot to the out of the interacted area. This key operation disable the interaction check temporarily while the SHIFT key is being pressed. Please call customer service. And report %x. Reduce the number of interaction element or combination setting. Confirm the model type in the combination setting. Confirm the index number in the combination setting. Confirm the index number in the combination setting. Perform the calibration for the group. Confirm current tool number Confirm the hand number. Perform the calibration between the group and the base frame gorup. Check the link type and link number of the model element. Confirm the taught gourp number of the fixture elements. Confirm the model type in the combination setting. Confirm the index number in the combination setting. Confirm the index number in the combination setting. Perform the calibration for the group. Confirm current tool number Confirm the hand number. Perform the calibration between the group and the base frame gorup. Check the link type and link number of the model element. Confirm the taught gourp number of the fixture elements. If you want to use this one,enable this combination on setup screen. Enable this combination on setup screen. Disable this combination first. Enable this combination by the program that use this one. Input correct host name. Input correct host name. If you want to enable this combination, please enable it. If you want to disable this combination, enable it by IASTOP instruction. If you don't want to use this condition, please disable it. If you want to use this condition, enable it by IAWAIT instruction. Specify the correct group number. Specify the correct rate value. Confirm hostname, IP address Confirm hostname, IP address Confirm hostname & IP address Reduce target host Reduce enabled element Confirm element contents Confirm target host's setup Confirm own element setup Confirm target host is working Check target host and communication line Confirm own setup & target setup Confirm own setup & target setup Increase ITP Abort the program and jog away Change check combination type Abort the program and jog away Clear the hold button (input), and try the same operation. Meaning: The condition that the robot is being held is locked by the program, and it could not be cleared. Wait until the UNHOLD statement is executed by the karel program, or abort the karel program. Disable the teach pendant, and try the same operation again. Turn the REMOTE switch on the SOP to REMOTE side, and try the same operation again. Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the $RMT_MASTER system variable correctly. Refer to the SYSTEM R-J2 Software Reference Manual, Chapter 2 "System Variables", for more information on system variables. Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the $RMT_MASTER system variable correctly. Refer to the SYSTEM RJ-2 Software Reference Manual, Chapter 2 "System Variables", for more information on system variables. Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the $RMT_MASTER system variable correctly. Refer to the SYSTEM R-J2 Software Reference Manual, Chapter 2 "System Variables", for more information on system variables. Turn the REMOTE switch to local (if the operation is attempted from the SOP), or set the $RMT_MASTER system variable correctly. Refer to the SYSTEM R-J2 Software Reference Manual, Chapter 2 "System Variables", for more information on system variables. Close the safety fence, and try the same operation again. Abort one of the running task. Refer to the error cause code. Use MENU to display the Alarm Log screen. Turn the remote switch on. Specify correct program number. Refer to the error cause code. Use MENU to display the Alarm Log screen. Refer to the error cause code. Use MENU to display the Alarm Log screen. Set ENBL signal ON Disable single step switch Respond YES or NO in the prompt box on at the teach pendant Select a program from the program select menu on the teach pendant, or using PNS Select a correct program from the program select menu on the teach pendant Press RESET to clear error condition Set all PNS input ports to OFF Check the teach pendant cable. Replace the cable if necessary. Set PNSTROBE input to ON Connect the same type of teach pendant as disconnected. This is just a notification. You do not have to do anything for this warning message. COLD start is selected automatically. Decrease program size so that it can be executed within the time out limit This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Determine and correct the cause of loss of this signal. Determine and correct the cause of loss of this signal. Determine and correct the cause of loss of this signal. new battery of same kind. This is just a notification. You do not have to do anything for this warning message. Please fix the CE Sign key switch This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. This is just a notification. You do not have to do anything for this warning message. Please set valid DI index Release the DEADMAN and press RESET. Turn the TP ON/OFF switch to ON. Press RESET. Call your FANUC Robotics technical representative. Turn the TP ON/OFF switch to OFF. Press RESET. If the Control Reliable/CE Mark option has not been loaded, load the Control Reliable/ CE Mark option. If it has been loaded then this is a system without the Control Reliable/ CE Mark hardware and the system must be totally reloaded WITHOUT the Control Reliable/CE Mark option. Respond ABORT or CONTINUE in the prompt box on at the teach pendant Please increase Controller's memory Please increase Controller's memory Time must be less than 6,000,000 us Event or scan routine need to be made more efficient, scan rate reduced, or system variable values increased to permit more CPU usage. Use cancel request to delete old entry Use Valid Fast-DIN Use unique event ID or cencel previous request Check event ID Either cancel scan routines that are no longer needed or combine scan routines Use a value in the range 1-1000000 Don't request the same rtn/data_p twice Don't cancel a non-existent scan Add table only once Cancel tables that are no longer needed or combine tables. Check for duplicate sycncltb call or wrong table pointer Contact Fanuc Robotcs wth information on events leading up to error Contact Fanuc Robotcs wth information on events leading up to error Please reduce some software options or disable some motion groups which had been enabled. Too much communication may have caused the interrupt. Check the teach pendant cable. Replace the cable if necessary. Check panel HSSB hardware connection. Select a valid style number, or adjust the size of the table. Put a valid program name in the proper place in the style table. Create a program for the style, or put a valid program name in the style table. Set the VALID field to YES in the style table. The PLC must send a style code that matches the manual selection. Cold start the controller. Cold start the controller. Cold start the controller. This is an informational message. There is no error. This is an informational message. There is no error Look for a previous message that indicates exactly which check failed and take corrective action. Reset the fault before trying the operation again. Move the robot to the home position. Jog the robot back to the correct position. Unsimulate all I/O before trying to start the program. This is an informational message. Set the override to 100%. This is an informational message. Set the override to 100%. This is an informational message. Turn off the machine lock. This is an informational message. Take the system out of single-step mode. This is an informational message. Make the process equipment ready for running a program. This is an informational message. Internal error None needed - warning only. None needed - warning only. None needed - warning only. None needed - warning only. None needed - warning only. None needed - warning only. None needed - warning only. None needed - warning only. Enable at least one reference position for group 1 as a home position, or disable the home position startup check. Set up a production start input in the Cell Input I/O menu and restart the robot. Set up a style number input group in the Cell Input I/O and Group I/O menus and restart the robot. Set up the RSR inputs in the Cell Input I/O menu and restart the robot. Set up the PNS selection inputs in the Cell Input I/O and Group I/O menus and restart the robot. Set up the RSR echo outputs in the Cell Output I/O menu and restart the robot. Set up the PNS echo outputs in the Cell Output I/O and Group I/O menus and restart the robot. Set up a PNS strobe input in the Cell Input I/O menu and restart the robot. Set up an acknowledgement strobe output in the Cell Output I/O menu and restart the robot. Set up the style option inputs in the Cell Input I/O menu and restart the robot. Set up a decision code input group in the Cell Input I/O and Group I/O menus and restart the robot. Set up a style output group in the Cell Output I/O and Group I/O menus and restart the robot. Set up the style option outputs in the Cell Output I/O menu and restart the robot. Set up a decision code output group in the Cell Output I/O and Group I/O menus and restart the robot. Set up an in-cycle output in the Cell Output I/O menu and restart the robot. Set up a task-OK output in the Cell Output I/O menu and restart the robot. Set up an isolate mode output in the Cell Output I/O menu and restart the robot. Set up an interlock mode output in the Cell Output I/O menu and restart the robot. Set up a manual style request output in the Cell Output I/O menu and restart the robot. Finish or abort the current program before requesting a new program selection. Examine the secondary error message. Determine why the PLC did not respond to the request, or increase the timeout value. Defer any of these requests until late in the cold-start process Reduce or eliminate the noise on the signal with additional grounding or shielding. If the frequency dip switch setting on the HDI Pulse Module is for the low range (640 Hz) and normal input frequencies will be above this, change the settings. Change the dip switch setting to the high range (1000 Hz) and the system variable $FQINT_SETUP[n].$FREQ_MAX_AL to 1020. If the frequency dip switch setting on the HDI Pulse Module is for the high range (1000 Hz) and normal input frequencies will always be below the low range change the setting to the low range. If the device providing the frequency (a flow meter for example) is providing frequencies above 1000 Hz, either change settings on the meter or change the type of meter so that the frequency provided is reduced. To disable this alarm, change the setting of the system variable $FQINT_SETUP[n].$FREQ_MAX_AL to 1200 if using the HDI Pulse Module or to 0 otherwise. Reset the system Clock using the SYSTEM Clock TP page Check the system Clock using the SYSTEM Clock TP page Request only valid devices. Specify only installed motherboards. This is a programming error. Specify only index 0 or 1 Specify an IRQ from 3 through 7 only. Check BMON version. Specify a later time for the event Use size <= MAX_PKT_DATA in sytglib.h Set the sysem variable to zero (no port used) or to a valid port number and ensure that the indicated DOUT is assigned. Set the device to which the DOUT is assigned On-line. Use value in the range of 1 to 20, or zero if evnt_rtn_2 not used If you would like to turn on servo, please turn off dynamic brake release request signal. It is message only. Respond YES or NO in the prompt box on at the teach pendant Start the same program again. Exit AUTO mode before doing this operation Exit AUTO mode before doing this operation Put controller into AUTO or INTERLOCK mode before doing this operation Please reduce some software options or disable some motion groups which had been enabled. Mount the correct PCB. Install CE/RIA option to this controller. Change the mode switch to T1 or AUTO mode. Configure GO dediocated for the Error Output feature. Configure GO using more digital outputs. Retry after turn OFF servo Turn OFF servo Do not operate IO during Remote diagnostic Too much communication may have caused the interrupt. Check the teach pendant cable. Replace the cable if necessary. Check the teach pendant cable. Replace the cable if necessary. Is there any source of electrical noise ? Check the teach pendant and replace the teach pendant if necessary. Check the teach pendant cable. Replace the cable if necessary. Is there any source of electrical noise ? Check the teach pendant and replace the teach pendant if necessary. Check the setting of the system variable $SCR.$DSB_MOINIT. Do not operate on an isolated Robot Contact FANUC to obtain an authorization key Contact FANUC to obtain an authorization key Contact FANUC to obtain an authorization key Contact FANUC to obtain an authorization key Contact FANUC to obtain an authorization key Go through CTRL start to correct None. This is just a notification. You do not have to do anything for this warning message. Cold start controller Perform a controlled start to initialize motion softparts Perform a cold start of controller Check a connection of process IO board Perform a cold start of controller Change the value of weaving frequency to be lower or the value of comp timing on TAST data screen to be longer Perform a cold start of controller Check RPM softparts was loaded correctly If same position IDs are used at same RPM record section, change position IDs to different one Change the schedule number to be in range (1 - 20) Change the frequency value to be higher Perform a cold start of controller Perform a cold start of controller Perform a cold start of controller Perform a cold start of controller Change the value of weaving frequency to be lower Notify FANUC Robotics. Perform a controlled start and initialize motion softparts. Perform a cold start on the controller. Perform a cold start on the controller. Perform a cold start on the controller. Perform a controlled start and initialize the motion softparts. Check amount of memory being used by system. Perform a cold start on the controller. Perform a cold start on the controller. The positions being executed prior to the one specified should be moved further apart, or the programmed speed should be decreased. Perform a cold start on the controller. Extend time of first motion segment (increase distance or decrease speed) to allow TCP Speed Prediction to begin during the first motion segment. Check program setup to ensure proper program header data, motion types, and position data. Check the values for the current and previous positions. Check the values for the current and previous positions. Check the value for the current position data. Check to make sure that the Cartesian Filter option has been properly loaded and initialized. No action is necessary, but the TCP Speed value will not be valid for several motions. Check the error log to find speed limit errors which may be causing this TCPP error to occur. Check the program beginning with this line to determine if the robot can not function as programmed. Modify the program to avoid all such speed limit errors. In cases which list speed limit errors for the wrist axes, the error can often be eliminated by changing the motion command from using mm/sec speed commands to using deg/sec speed commands which better control motion with large wrist orientation changes. Normal prediction will resume automatically once the speed override has propagated through the system. No further action is required. The user should avoid this during production program execution and should be aware that it may invalidate live application testing since neither the robot nor the speed prediction task are performing as programmed. No action is necessary, but the TCP Speed value will not be valid. Check amount of memory being used by system. Perform a cold start on the controller. System problem. Need to fix the problem by modifying code. Check whether both target type and index are valid. Correct the speed values. Correct the index. Correct the target type. Enable Tool Change. Release machine lock. Confirm tool number assignment. TOOL ATTACH instruction can be executed only when no tool is attached. TOOL ATTACH instruction can be executed only when no tool is attached. TOOL DETACH instruction can be executed only when a tool is attached. Wait until another program ends TOOL ATTACH/DETACH instruction. Confirm the setting for Tool identify signal. Confirm the setting for Tool set signal. Do COLD START the system. Do COLD START the system. Do COLD START the system. Then master the tool by manual operation. Continue to retry mastering. Please see cause code. Please see cause code. Please perform the mastering of the servo tool axis. Please calibrate the servo tool axis. Quick mastering may not be possible. Fixture or zero master. Verify the tool number of TOOL DETACH instruction. Verify the detect condition in the Tool Change Setup screen. Please set PR[] index for the calibrate motion in the Tool Change Setup screen. Please set Touch torque for the calibrate motion in the Tool Change Setup screen. Please set Detect signal for the calibrate motion in the Tool Change Setup screen. After servo tool axis stops, execute calibration motion Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Select a program in the SELECT screen. Teach the SELECT statement before the current line. Calibrate the robot properly.. Release protection of the program on the SELECT screen. Release protection of the program on the SELECT screen then delete the program. Try edit after release protection by application Try another item or close search function Check the configuration of robot and $MNUTOOL/$MNUFRAM system variables Select a program after aborting the program which is currently run ning or paused. First enable the teach pendant, then edit the program. Check the index of position register Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Check specified index value. Try another item or close replace function Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Remove Wjnt or RTCP before adding the other. Set a proper program name Remove numeric value from beginning of program name. Remove space from program name. Remove comma from program name. Remove dot from program name. Remove minus from program name. Delete unused program. Select the program on the Teach Pendant before editing on the CRT Remove invalid character from program name Change to different label No. Check system variable $MNUTOOLNUM Check system variable $MNUFRAMNUM Set system variable $MULTI_ROBO.CHANGE_SDI to ZERO Check selected robot (group) or check program attributes group mask Teach another program. Decrease motion options for default motion Select TPE program Run program before attempting to monitor. Set port for outside device Assign a program to this macro command Turn off the PNSTROBE signal. Select the Disabled FWD in the function menu, then you can release from the Disable FWD Select the BACKGROUND program in the SELECT screen 1. Delete unnecessary programs. 2. Confirm the background program. End editing by the END_EDIT of [EDCMD] again before executing the origianl program which has been selected by the BACKGROUND End editing by the END_EDIT of [EDCMD] at the CRT End editing by the END_EDIT of [EDCMD] at the TP You can record this position on joint type only by selecting the function key. Check this recorded position again before excution You cannot mix AND and OR operator on a the same line. Verify that all logical operators on this line are the same before execution. Verify all logical operators on this line before execution Teach the logical operation on another line Verify all arithmetic operators on this line before execution Teach the arithmetic operation on another line Check arguments of the program/macro Remove items in this line. Check the sub type of the program. Check sub type of the program Check sub type of the program Set * to all motion group in program detail screen on TP. Refer to the error cause code on the ALARM log screen. Make sure the value_array specifies the correct names for the variables and that the types expected are correct. Use FORCE_SPMENU(tp_panel, SPI_TPUSER, 1) before calling the user interface built-in on the teach pendant. Use FORCE_SPMENU(crt_panel, SPI_TPUSER, 1) before calling the user interface built-in on the CRT. Use FORCE_SPMENU(tp_panel, SPI_TPUSER2, 1) before calling the user interface built-in on the teach pendant. Use FORCE_SPMENU(crt_panel, SPI_TPUSER2, 1) before calling the user interface built-in on the CRT. Perform a controlled start (it isn't necessary to re-set the new item) Use this screen when the program is paused or aborted. Refer to the error cause code. Use the Alarm Log screen. Select the other program Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Turn the E.STOP off. Then select FWD execution Press and hold down the DEADMAN, then select FWD execution Enable the teach pendant. Then select FWD execution. Select a proram for execution Then select FWD execution Abort the running program before requesting FWD execution Select the Disabled FWD in the function menu, then you can release from the Disable FWD Refer to the cause code on the ALARM log screen for the actual error. To specify the %v enumeration type in a form dictionary, use lower case v followed by the dictionary element which specifies the program name and variable name of the variable which contains the display values. For example: "Enum Type: " "-%6v(enum_fkey)" $-,enum_fkey "TPEX" &new_line "CHOICE_ARRAY" In the above example, CHOICE_ARRAY is a KAREL string array variable in program TPEX which contains the enumeration choices. The enumeration choices are displayed in a subwindow. Exit from the screen on the other device Check the spelling and format of the name. Select a valid device and try again Perform a cold start: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the error is not cleared, document the events that led to the error and call your FANUC Robotics technical representative. Check backup device Check device and try again Use the MOVE key and try again Check the above motion option instruction. And modify the copied statement correctly. Check the group motion instruction. And modify the copied statement correctly. Please set the application mask in the program detail screen Check the cause code. If the memory is full, please delete program or disable UNDO function. This error is posted because CTRL Upgrade cannot be done while operating robot. Continue with CTRL Upgrade or ABORT This error is posted because CTRL Upgrade is underway. Allow the process to complete. with CTRL Upgrade or ABORT See FRD:REST_LOG.LS for a listing of files and status of attempt to load each. Retry failed files from file menu. Set the system variable $POS_EDIT.$LOCK_POSNUM to FALSE to change position ID. Abort program to enter P-SPS. Abort program to exit P-SPS. Change the MOTION instruction or set up the motion group in the program DETAIL screen. Please do BWD to parent line. program DETAIL screen. Cycle start controller Change to linear move Increase RAM size Increase RAM size Use legal schedule Move conveyor back reteach destination No action required No action required Change to joint move Reload the tracking softparts. Change motion type to non-wrist-joint motion. Disable Maintenance Program in Error Recovery menu, or use Resume Program for error recovery. Adjust the Entry Limit or change the Tracking Boundary to be inside of this limit Adjust the Exit Limit or change the Tracking Boundary to be inside of this limit Try a different file. Place correct media in drive or select the proper device/directory and try again. This is just a notification. You do not have to do anything for this warning message. Clear the program and load the variables first before loading program. This is just a notification. You do not have to do anything for this warning message. Load PC file or VR file to create the variable Load PC file or VR file to create the type Load PC file or VR file to create the named type Create an error condition such as E-stop and load of variables is allowed This variable is not to be changed by customer for safety or other reasons If you are trying to change $SCR variables just change $PARAM_GROUP and cold start Load PC file or VR file to create the named program Refer to the error cause code. Use the Alarm Log screen to display the cause code. This is just a notification. You do not have to do anything for this warning message. Refer to the error cause code. Use the Alarm Log screen to display the cause code. You must delete some programs or reorganize programs to make more room These variable cannot be used on this controller You must use the default system variable file supplied with your version of software This is just a notification. You do not have to do anything for this warning message. Use a different program name or delete the program and and variables from existing program Load PC file or VR file to create the variable You must delete unneeded programs, dictionaries or variables to make room Delete existing variable before creating it as a different type Delete existing variable before creating it with conflicting dimensions Use a valid index Load these variables on an appropriate system Try a different file or convert the current file to an updated version. Delete other program which references these variables Consult your SYSTEM RJ-2 Controller Software reference Manual for valid values for the variable you are changing You must go to the password setup screen and enter the PROGRAM password You must go to the password setup screen and enter the SETUP password You must go to the password setup screen and enter the INSTALL password Make the array size smaller or use a path data type for large arrayed variables Maximum path length is 2,007 Maximum node size is 32,767 You must break up the large path into smaller paths Delete the variable in the same start mode that the variable was created. For example if a CMOS variable was created at CONTROLLED start it must be deleted at CONTROLLED start. If if is because of some access conflict the attempt the operation again when no other variable accesses are in progress. Controller initial start must be performed Wait until program is finished Delete the variable or change the memory type to be used. This is just a notification. You do not have to do anything for this message. Load variables at COLD start or at CONTROLLED START 1 before save image operation. Perform operation with a valid node number. The program with the type definition for the variable you are creating must be loaded at controlled start. This implies the type definition is image. Put the old board in back into the controller. If this board is not not available then an INITIAL START is required You must configure the groups from controlled start setup before loading variable files Setup the controller for the proper robot type and load system variables which were saved on a compatible robot Load the PC file again. This is informational. This is an error in the application Check all pointers being sent from the PC using RPC calls. This is informational. Change the name of the program Cold start controller Controlled start, initialize motion softparts Cold start controller Remove unneeded loaded variables and programs Controlled start, init motion softparts Delete Program line Change weave schedule to be in limits Change frequency to be within limits Change amplitude to be within limits Change dwell to be within limits Warning only Cold start controller Change Weave setup to use Moving Dwell Change path direction or setting of UTOOL to plan weaving vector correctly. Change wrist configuration to allow wrist axes away from its limit. Change wrist configuration to avoid singularity Change wrist configuration Change torch angle or increase the value of tol_ang Use a valid utool Screen names must be 1-4 alpla- characters Supply a valid screen name Window names must be 1-4 alpla- characters Supply a valid window name Use TP for teach pendand screen or CRT for KCL screen Device names must be 1-4 alpla- characters Supply a valid device name n_rows value must be 1 to 50 Correct the value n_cols value must be 1 to 132 Correct the value For ATWINDOW_S or AT_WINDOW_D calls, row must be in the range 1-(display_device_size-window_size+1) Correct the row parameter value For SET_CURSOR calls, the value must be in the range 1-50 For ATWINDOW_S or AT_WINDOW_D calls, col must be in the range 1-(display_device_size-window_size+1) Correct the col parameter value For SET_CURSOR calls, the value must be in the range 1-132 Use TP for teach pendand screen or CRT for KCL screen Use 'TP' for teach pendant keys or 'CRT' for KCL keyboard If the screen is a system-defined, it cannot be redefined. If the existing screen definition is not being changed, this may not be a problem. Otherwise, it may be necessary to cold-start the controller to delete the existing definition: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. If the window is a system-defined window, it cannot be redefined. If the window is a system-defined, it cannot be redefined. If the existing window definition is not being changed, this may not be a problem. Otherwise, it may be necessary to cold-start the controller to delete the existing definition: 1.Turn off the robot. 2.On the teach pendant, press and hold the SHIFT and RESET keys. 3.While still pressing the SHIFT and RESET keys, turn on the robot. Use the name of a defined screen Use the name of a defined window If the present attach is acceptable, this may not be a problem. Otherwise it will be necessary to call DET_WINDOW The following forms are valid: WD:wnam KB:knam WD:wnam/knam KB:knam/wnam where wnam and knam are 1-4 alpha-numberic characters Correct the format of the file name Either change the OPEN to specify a window or do not WRITE to the file Specify a value in the range 10-128 for INI_DYN_DISx calls; for READ_KB calls, specify a range of 1-128, unless the accept mask is zero, when a buffer_size value of zero is permitted. The value must be less than 65535000. Use a valid value Use a non-zero value for the terminate character mask Either increase the value of buffer_size or specify a shorter string for init_value Either modify the OPEN FILE statement to specify a keyboard or do not use the file in a READ_KB call or READ statement This may be a normal result if the user intended READ_KB requests to fail if the required window is not displayed. Otherwise, either modify the terminate mask or use ATT_WINDOW_D or ATT_WINDOW_S to attach the required window. This may be a normal result if the user intended READ_KB requests to fail if the Keyboard is in use. Otherwise, modify the terminate mask, modify the accept mask of this or the conlicting read, or use a PUSH_KEY_RD call to suspend conficting reads Check for situations in which a PUSH_KEY may be executed and no POP_KEY is exected. Check the logic in use of PUSH_KEY_RD and POP_KEY_RD to ensure that the pop_index values are being suplied in the correct order. If more than one task is issuing PUSH_KEY_RD and POP_KEY_RD calls, extra care is required This must be in the range 1-32767 (ms) Check the variable and window names. Also check logic to see that dynamic display had been started and not already cancelled. Value must be in the range of 0-255 This is only a warning. It can be ignored or avoided by not detaching windows that are not attached. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: vendredi 9 juillet 2004 15:18 To: Evrat, Sebastien Cc: Kato, Seigo Subject: RE: FEFAX 2383 V630PXX software error codes and remedy Could FANUC provide FREU/FRXX error codes with cause and remedy file (excel, pdf, Xml...) for V630PXX software? FANUC will send error codes with cause and remedy file for V630P at July 12th. -----Original Message----- From: Borys, Matthew [mailto:[email protected]] Sent: Tuesday, August 31, 2004 4:58 PM To: Evrat, Sebastien Cc: Bröckling, Thomas; FREU PSG; Nowak, Glenn; McCaig, Derrick; Dinsmoor, Claude; Niederquell, Bradley Subject: RE: FREU: Karel form not displayed with V6.22N-O and earlier. The status returned is a standard error code. That means it is a decimal number of the form FFCCC where FF is the Facility Code and CCC is the Error Number. For example, the number 11006 is SRVO-006 (SRVO is Facility Code 11). It is slightly different when the status represents an OS error as yours did. OS is Facility Code 0. The number is not simply 12 as you might expect. It has 256 added to it for coding reasons. In your case, you take the 268 you received and subtract 256 to see that it represents OS-012. The rule of thumb is that if the status is less than 1000, it is an OS error and you must subtract 256 to get the Error Number. Could FANUC provide FREU/FRXX error codes with cause and remedy file (excel, pdf, Xml...) for V630PXX software? Cc: Bröckling, Thomas; FREU PSG; Nowak, Glenn; McCaig, Derrick; Dinsmoor, Claude; Niederquell, Bradley The status returned is a standard error code. That means it is a decimal number of the form FFCCC where FF is the Facility Code and CCC is the Error Number. OS is Facility Code 0. The number is not simply 12 as you might expect. It has 256 added to it for coding reasons. The rule of thumb is that if the status is less than 1000, it is an OS error and you must subtract 256 to get the Error Number.